Moxo appears on most lists of customer onboarding software. Its own published evidence suggests it belongs on a different list.
Moxo’s customers are banks and small practices, not SaaS companies
This is the most useful thing to know about Moxo, and it answers the fit question faster than any feature comparison.
Moxo’s customer stories are dominated by financial institutions: Citibank, Scotiabank, BNP Paribas, Emirates Bank, Raiffeisen Bank, Bank of Queensland, Van Lanschot, Stonehage Fleming and Keebeck Wealth Management. Around them sit large enterprises in adjacent sectors – FIS, Global Payments, Savills, Procore, ChenMed, Zeta Global – and then a long tail of small professional practices: accounting and tax firms, law practices, mediation and therapy providers.
Moxo leads with throughput numbers. Peninsula Visa cut visa processing time by 93%, from days to hours. Flex Racing scaled to handle 150% more orders. BNP Paribas appears under onboarding and account management, which for a bank means opening accounts.
Nothing in that list is a B2B SaaS company getting software customers live. The pattern is many short, repeatable, largely transactional interactions, a great deal of it consumer-facing: opening an account, processing an application, engaging a patient, collecting documents from an individual. Moxo describes itself the same way in financial services, calling the product a client interaction hub spanning consumer banking, business banking and investment management.
B2B software onboarding is a different job. It runs on fewer and longer projects, several stakeholders on the customer side, real configuration decisions, and a plan that changes as both sides learn. The hard part is coordination rather than volume.
The entry tiers are gone: pricing now starts at $500 a month
Moxo changed its published pricing in August 2026. Until then it published a Free plan (two flows per month) and a $99 Business plan (ten flows per month). Both were removed in the repackaging: the only published price is now Team at $500 per month, and everything above it is a custom quote.
That move matches the logo wall. The results Moxo advertises were never two-flows-a-month operations – a visa service cutting processing time by 93% runs volume that lands well beyond Team’s 250 flows per year. The pricing now says openly what the customer list already implied: this is an enterprise product, bought through a sales conversation.
For a small practice that would have started on Free or the $99 plan, there is no longer a published path in.
What the flow model means in practice
Moxo organizes work around a flow rather than a project. A team designs the route, roles, controls and decision points in advance, then automation moves participants through it.
Within that model the product is capable. Flows support conditional branches, parallel subflows, waits, milestones and role-based handoffs, so one template can handle different client types and exceptions. Forms, file requests, review steps and eSignatures sit inside the flow, and magic links take a participant straight to the action they owe without an account. Reporting covers workspaces, actions, durations and overdue steps. Role-based access, timestamped audit trails, SSO and private-cloud or on-premises deployment support regulated operations.
For a repeatable, compliance-sensitive process, designing the route up front is the right architecture. The route is supposed to be fixed, and the value is in executing it consistently and provably.
The mismatch appears when the work is a consultative implementation. Moxo publishes no Gantt or project-planning view for durations, dependencies and overlapping workstreams as one customer project, because a flow engine does not need one. Teams that reshape the plan with the customer as the project develops are working against the model rather than with it.
What Moxo does well
- Structured data and document collection. Forms, questionnaires, file requests, review steps and eSignatures inside the workflow.
- Regulated process control. Role-based access, approvals, timestamped audit trails, SSO and flexible deployment.
- Adaptive workflows. Branches, waits, subflows and parallel work let one template cover several client types.
- External participation without accounts. Magic links for individual actions; a branded portal on the quote-only tiers.
- Native AI and integrations. Agents for preparation, review and reporting, with API, webhooks and MCP on the higher tiers.
Where Moxo falls short for onboarding teams
- It is process-centered rather than project-centered. Excellent at routing actions through a defined flow, with no published view for planning a customer implementation as a project.
- The portal is not in the published plan. Team covers magic-link actions and a custom domain. Portals, portal messages, resources and the flow catalog require the quote-only Scale tier.
- Governance features sit above the published plan. REST APIs, webhooks and MCP now come with Team, but SAML SSO and the audit log require quote-only tiers.
- Usage is flow- and credit-based. Buyers must forecast both workflow volume and AI consumption rather than running unlimited onboarding projects.
- The problem it solves is broader than onboarding. Teams buying only for collaborative SaaS onboarding inherit agent-building, compliance controls and general orchestration concepts that are not central to their journey.
How much does Moxo cost?
Moxo publishes three packages since its mid-August 2026 repackaging, and only one carries a price. Team costs $500 per month, or $5,000 per year, and includes 250 flows and 25,000 AI credits per year with unlimited seats. It covers the workflow engine, forms, file requests, eSignatures, payments, magic links, a custom domain, REST APIs, webhooks and MCP connectivity.
What Team does not include is Moxo’s portal proposition. Portals, the flow catalog, portal resources and messages, SAML SSO, native CRM integrations and the audit log start at Scale, which is quote-only (1,000 flows and 100,000 AI credits per year). Enterprise is also custom, adding advanced agent controls, custom pages and the embeddable SDK.
The former Free plan (two flows per month) and $99 Business plan were removed in the same change, and there is no self-serve trial – a free trial is available on request only.
For an onboarding evaluation, the practical consequence is that the client-facing portal – the part that made Moxo comparable to onboarding platforms at all – no longer has a published price. Teams should model expected flow volume and AI-credit usage before comparing total cost, because the pricing unit is process executions rather than customers or seats.
Is Moxo a good choice for customer onboarding?
It depends entirely on what kind of onboarding you mean.
For account opening, KYC and KYB, case intake, application processing or document-heavy client service at volume, Moxo is a serious option with results to show. A 93% cut in processing time is a real number, and the compliance and deployment depth behind it is not something a lighter tool matches.
For a B2B SaaS or professional-services team getting customers live, the fit is weaker, and the reason is not a missing feature. Moxo is designed around executing a predefined process at volume, while that work is a coordination problem between two organizations over several weeks. The customer base Moxo publishes offers a SaaS buyer little evidence either way, published pricing starts at $500 per month, and the full portal sits behind a quote-only tier.
Teams whose problem is a collaborative onboarding journey should compare Moxo against platforms built for that specifically, where the plan is expected to change as the project does.