Workflows
Which parts of the outbound motion OXO runs—from prospecting and enrichment to outreach, calling, reply handling and CRM operations.
PRICING / COMMERCIAL MODEL
OXO uses a usage-based pricing model. Your commercial plan is shaped by what the system operates, how much activity moves through it, and where your team needs control.
Build your commercial planWhich parts of the outbound motion OXO runs—from prospecting and enrichment to outreach, calling, reply handling and CRM operations.
The number of markets, campaigns, contacts, channels and actions moving through the system.
The approval gates, governance rules, handoffs and implementation support your team requires.
Confirm ICPs, channels, campaign types, team roles and the outcomes OXO will own.
Model expected account, contact, campaign and channel activity.
Choose approval gates, exclusions, handoff logic and governance requirements.
Finalise the usage model, rollout scope and commercial terms before activation.
Packages can include account discovery, buying signals, data enrichment, personalised outreach, sales calling, reply classification and CRM updates.
Pricing considers active campaigns, contacts processed, channels used and the operating frequency required by your go-to-market plan.
Advanced plans can account for integrations, approvals, governance, workflow design, phased rollouts and multi-team operating requirements.
No. OXO is designed around usage and the outbound workflows the system operates rather than charging primarily for user seats.
The current commercial model depends on workflow scope, campaign volume, channels, governance and rollout complexity. Those inputs need to be mapped before a responsible quote can be produced.
Yes. A team can begin with a focused use case or market and expand after the operating model is proven.
Bring your target markets, approximate campaign volume, required channels, current tools, approval needs and the team roles involved in handoffs.
It can. Standard configurations differ from programmes requiring custom CRM logic, governance, phased deployment or complex integrations.