Moxo Pricing: Everything you need to know

Moxo offers four pricing plans: Free, Business, Pro, and Enterprise.

The Free plan costs $0 per month. Business costs $99 per month or $960 per year. Pro is an annual-only, sales-led plan priced at $4,800 per year. Enterprise pricing is customised.

Moxo does not price its plans around users alone. Each tier includes limits on the number of processes you can run, the number of steps each process can contain, and the amount of billed AI work performed inside those processes.

This guide explains how each Moxo plan works, what flows and AI credits mean, which capabilities unlock at each level, and what to consider before choosing a plan.

Key takeaways

• Pick a plan based on your needs.  Business can be purchased monthly or annually through a self-serve model. Pro and Enterprise are sales-led.
• Not every AI interaction consumes credits. Flow-building assistance, agent-building chat, step setup support, reports chat, and FAQ keyword responses do not reduce AI credit balances.
• The right plan depends on process volume, step complexity, AI usage, integrations, security requirements, and the level of operational control required.

How much does Moxo cost?

Moxo has four plans, starting with a free option for testing low-volume processes and extending to custom Enterprise pricing for larger or more technically complex deployments.

The annual Business plan works out to $80 per month, compared with $99 when paying monthly. This produces a saving of $228 over one year.

Pro is structured differently. It does not offer a selectable monthly billing option. The plan is purchased annually for $4,800 through a sales-led process.

A nominal monthly equivalent may sometimes be shown to communicate the annual price, but buyers should not interpret this as a month-to-month Pro subscription.

The subscription price also does not reveal the full difference between plans. Flow limits determine how often a process can run, while step limits determine how much work can happen inside each process.

A simple approval flow may fit comfortably within ten steps. A process involving intake, document extraction, multiple reviews, parallel approvals, system updates, revisions, and follow-ups may require far more.

How does Moxo pricing work?

Moxo pricing is primarily structured around four factors:

Flow volume. How many times your processes run during the billing period.

Steps per flow. How many actions, decisions, integrations, and control points sit inside each process.

AI execution. How much billed AI work takes place inside those flows.

Capability level. Which workflow, integration, reporting, security, and deployment controls the organisation needs.

Moxo coordinates processes involving internal teams, external stakeholders, business systems, and AI agents. Humans remain responsible for approvals, exceptions, and decisions that require judgment. AI handles the preparation, validation, routing, monitoring, and follow-up work surrounding those decisions.

What is a flow in Moxo?

A flow is a single active instance of a reusable workflow template.

While a template defines the process logic, a flow represents each time that process is executed for a specific subject, such as an individual customer or vendor.

Consequently, the number of flows consumed depends on the volume of activity rather than the number of unique templates created.

What is a step in Moxo?

A step is a single action or decision point within a flow, such as completing a form, signing a document, or triggering system logic. As steps dictate process complexity, they impact pricing. A step may ask someone to complete a form, upload a document, approve a request, sign an agreement, make a selection, attend a meeting, or perform another structured action.

Free plans support 10 steps per flow, Business supports 50, and Pro/Enterprise plans offer unlimited steps.

A team could have enough monthly flow capacity but still need a higher plan because its processes are too complex for the lower tier’s step limit.

What are Moxo AI credits?

AI credits measure certain types of AI execution inside a Moxo process.

Billed AI activity may include:

Preparing information. AI can pre-fill fields, stage documents, or assemble context before a participant sees a task.

Reviewing submissions. AI can check whether files, forms, or responses meet defined requirements and flag issues for revision.

Extracting data. AI can pull structured information from documents and make it available to later steps.

Summarising or generating content. AI can summarise documents, conversations, or process activity and produce written outputs.

Advising participants. AI can prepare recommendations or supporting context before a human makes a decision.

Running agent actions. More advanced AI agents can use tools, connected systems, APIs, or iterative execution loops.

The amount of AI capacity required depends on how often these actions run and how many AI actions sit inside each flow.

A workflow that uses AI once to check a form will consume credits differently from one where several agents extract data, validate files, prepare recommendations, and generate an output.

However, not every AI interaction consumes credits. Moxo does not bill AI credits for:

• Flow Builder chat
• Agent Builder chat
• Step Setup co-pilot assistance
• Reports Chat
• FAQ keyword-tier responses

This means teams can use AI to design, configure, and analyse processes without every interaction reducing the production AI allowance.

Buyers should still confirm the expected credit consumption of the specific AI actions they intend to run.

Does Moxo charge per user?

Moxo’s public plans are not presented as standard per-user subscriptions. The plans are structured around flows, AI credits, step limits, and access to more advanced capabilities.

This can be useful for processes involving many occasional participants. A flow may include internal operators, managers, customers, vendors, partners, or contractors who only need to complete one action.

External participants can access relevant tasks through secure links and process-specific portals. Basic portal functionality is available on the Free plan, so portals should not be treated as a capability that only unlocks at higher tiers.

Organisations should still confirm whether their selected plan applies any limits to internal members, external contacts, participant volume, portal configuration, or deployment requirements.

The practical pricing question is therefore not simply, “How many users do we have?”

It is: How many processes will we run, how complex will each one be, and how much AI execution will happen inside them?

Moxo pricing plans compared

This table summarises the major differences. Exact packaging and limits should always be confirmed against the current pricing page and the final commercial agreement.

What is included in the Moxo Free plan?

The Moxo Free plan ncludes:

• 2 flows per month
• 250 AI credits per month
• Up to 10 steps per flow
• Basic portal capabilities
• Core workflow and AI-building tools

The Free plan is best understood as a way to test a process rather than run a high-volume production operation.

What can you do with the Free plan?

The Free plan can support a simple proof of concept.

A team might use it to build a lightweight approval process, test a basic onboarding journey, collect a form and supporting documents, or demonstrate how a workflow moves between several participants.

It also gives teams access to AI-assisted process building. The Flow Builder chat and Step Setup co-pilot do not consume AI credits, so users can experiment with designing and configuring a workflow without using the full execution allowance.

The ten-step limit is the main design constraint.

A short process may fit comfortably within ten steps. A workflow that includes several review cycles, branches, integrations, approvals, and follow-ups may not.

Who is the Free plan best for?

The Free plan is a good fit for:

Teams evaluating Moxo. It allows a buyer to understand how templates, flows, steps, roles, and AI execution work before committing budget.

Internal proof-of-concept projects. Operations teams can model one process and show stakeholders how the process could run with clearer ownership and less manual chasing.

Very low-volume workflows. A process that only runs once or twice per month may fit, provided it stays within the ten-step limit.

Learning and experimentation. Teams can use the plan to explore workflow building, AI-assisted setup, basic participant experiences, and core process actions.

The Free plan is unlikely to be enough for a recurring customer, vendor, employee, or approval process that runs every week.

Moxo pricing plans compared

What is included in the Moxo Business plan?

The Moxo Business plan includes:

• 10 flows per month
• 1,000 AI credits per month
• Up to 50 steps per flow
• Audit logs
• E-signatures
• PDF forms
• Webhooks
• Advanced reports

Business is the first tier designed for regular operational use rather than testing alone.

What does Business add over Free?

The biggest change is process depth.

The step limit increases from 10 to 50, which gives teams room to build more complete workflows with several stages, participants, checks, and follow-ups.

Business also adds capabilities that make processes easier to govern and connect.

Audit logs give teams a record of what happened, who acted, and when.

Electronic signatures allow agreements or approvals to be completed inside the workflow.

PDF forms help teams collect structured information in documents that already have a fixed format.

Webhooks allow Moxo to send workflow events to another system.

Advanced reports help process owners understand completion, delays, bottlenecks, and performance.

The value of reporting depends on the decisions it enables. A report is useful when it helps an operations leader identify a step that regularly causes delays, a team that needs more capacity, or a process that produces too much rework.

Who is the Business plan best for?

Business is a strong fit for:

Small teams running recurring processes. Ten flows per month may suit a department handling a limited number of onboarding, approval, review, or service-delivery processes.

Teams that need stronger process records. Audit logs and electronic signatures make the plan more appropriate for processes where completion history matters.

Processes requiring structured documents. PDF forms can help when participants need to fill or sign a standard document.

Teams that need basic system notifications. Webhooks allow Moxo to notify another application when something happens inside a flow.

Operations leaders who need process visibility. Advanced reports provide more context than manually checking individual flows.

The Business plan may become restrictive when the same process runs several times per week or when the workflow requires advanced integrations, reusable subflows, AI agent roles, or unlimited steps.

What is included in the Moxo Pro plan?

Moxo Pro is an annual-only, sales-led plan and includes:

• 500 flows per year
• 50,000 AI credits per year
• Unlimited steps per flow
• Subflows
• REST API steps
• Agent roles
• Time booking
• Business-level capabilities

Pro is intended for production workflows that are too complex or too frequent for the lower tiers.

What does Pro add over Business?

The main advantage is flexibility.

Business supports up to 50 steps per flow. Pro removes that limit, allowing teams to build longer processes with more stages, branches, participants, integrations, and review cycles.

Subflows let teams build a reusable process once and place it inside several larger workflows.

For example, an identity verification process could be used inside customer onboarding, vendor onboarding, and account-change requests without rebuilding the same steps each time.

REST API steps allow workflows to retrieve or update information in external systems.

This is useful when a process must check a CRM record, send data to an internal application, create a record in another system, or continue only after an external condition is met.

Agent roles allow AI agents to take defined execution responsibilities inside a process. An agent may prepare information, review a submission, advise a participant, or perform connected actions, while humans retain responsibility for approvals and exceptions.

Time booking allows scheduling to sit inside the process rather than being coordinated through separate email threads.

Who is the Pro plan best for?

Pro is suitable for:

Teams running Moxo as part of day-to-day operations. Five hundred flows per year gives organisations more room to run recurring processes across departments or stakeholder groups.

Processes with many handoffs. Unlimited steps allow teams to model the full process rather than compressing it to fit a plan limit.

Organisations connecting several systems. REST API steps support deeper integration with systems of record and operational tools.

Teams building reusable process components. Subflows help standardise recurring sections of larger processes.

Operations using AI as an execution layer. Agent roles are relevant when AI must prepare, validate, route, monitor, or act inside the workflow.

Processes that include scheduling. Time booking can be embedded into onboarding, consultations, reviews, service delivery, or other multi-party workflows.

Pro is likely to be the practical starting point for organisations running complex customer, vendor, finance, legal, or cross-department operational processes.

What is included in the Moxo Enterprise plan?

Moxo Enterprise includes:

• Custom flow capacity
• Custom AI credit capacity
• Unlimited steps per flow
• SAML SSO
• Enterprise security and compliance controls
• MCP Server connectivity
• Advanced deployment and implementation support
• Pro-level capabilities

Enterprise pricing will depend on the process volume, technical architecture, security requirements, support level, and deployment model involved.

What does Enterprise add over Pro?

Enterprise focuses less on basic workflow depth and more on governance, scale, security, and technical flexibility.

SAML SSO allows organisations to connect Moxo to their identity provider and control how internal users sign in.

Enterprise security and compliance controls become important when workflows handle regulated information, require formal access policies, or must go through internal security review.

MCP Server connectivity allows supported AI agents and systems to interact through a standardised tool and context layer.

Custom capacity gives larger organisations room to negotiate flow and AI usage around actual operating requirements.

Advanced implementation support may be relevant where several teams, systems, regions, or business units need to be brought into the same operating model.

Who is the Enterprise plan best for?

Enterprise is best for:

Large organisations with high process volumes. Custom capacity is more practical when standard allowances no longer match usage.

Companies with formal identity and access requirements. SAML SSO is often required by enterprise IT teams.

Regulated or security-conscious environments. Enterprise controls help support stricter governance, access, and audit needs.

Complex multi-system deployments. MCP Server connectivity and custom implementation support may be needed where Moxo sits across several applications and operational processes.

Multi-department programmes. Enterprise is better suited to organisations standardising process orchestration across teams rather than launching a single departmental workflow.

For current certification language or security claims, buyers and writers should rely on approved Moxo security documentation rather than making assumptions.

Which Moxo plan should you choose?

The right Moxo plan depends on the process you want to run, not only your company size.

Choose Free when you are validating a process

Free is the best starting point when the goal is to learn how Moxo works or demonstrate a simple workflow internally.

It is suitable when:

• The process runs no more than twice per month.
• The workflow fits within ten steps.
• You do not need Business-level governance or integration features.
• You are building a proof of concept rather than a production deployment.

Choose Business when you need regular, contained workflows

Business is appropriate when a team has moved beyond experimentation and wants to run a limited number of recurring processes.

It is suitable when:

• You need up to ten flows per month.
• Each flow fits within 50 steps.
• You need audit logs, electronic signatures, PDF forms, webhooks, or advanced reports.
• The process is owned by one team or department.
• You do not yet need subflows, REST API steps, agent roles, or SAML SSO.

Choose Pro when Moxo becomes part of core operations

Pro is the likely fit when the process is too complex or frequent for Business.

It is suitable when:

• You need unlimited steps per flow.
• You need reusable subflows.
• The workflow must call external systems through REST APIs.
• AI agents need defined roles in the process.
• Scheduling is part of the workflow.
• The process spans several teams or external stakeholders.
• You expect to run up to 500 flows per year.

Choose Enterprise when the deployment requires custom scale or governance

Enterprise is designed for organisations with requirements that go beyond standard process orchestration.

It is suitable when:

• You need custom flow or AI capacity.
• Your IT team requires SAML SSO.
• Security and compliance controls are part of the buying decision.
• You need MCP Server connectivity.
• The deployment spans several teams, systems, or business units.
• You need a more involved implementation and support model.

What happens when you exceed your Moxo plan limits?

The public plan limits make it important to estimate usage before purchasing.

A team could exceed its allowance in several ways:

• Starting more flows than the plan includes
• Running more AI actions than the available credit balance supports
• Building a process that exceeds the step limit
• Requiring a capability that only exists on a higher plan

Moxo offers capacity expansion packs, AI credit top-ups, and a one-year rollover window for unused operational capacity and AI credits. These commercial terms should still be confirmed for the selected plan and contract.

Before purchasing, ask:

What happens when flow capacity is exhausted? Confirm whether additional capacity can be purchased without changing plans.

How are extra AI credits priced? AI-heavy workflows may require more capacity than the default allowance.

Does unused capacity roll over? Confirm which plan types and capacity categories qualify.

Can the plan be upgraded during the contract? This matters if the process volume grows faster than expected.

Are top-ups automatic or manual? Automatic top-ups may prevent processes from stopping unexpectedly, but they also affect cost control.

Do test and failed flows count? Ask how testing, retries, cancellations, and revisions affect the allowance.

How Moxo fits into complex business processes

Many operational processes still depend on email, spreadsheets, chat messages, and disconnected systems. The issue is rarely that teams do not know what should happen. The issue is that execution breaks down between people, systems, and organisations.

A request may start in one system, move to email for review, continue in a spreadsheet, and then wait for an external participant. The process owner remains accountable for the outcome but has limited visibility and spends time chasing every handoff.

Moxo provides an execution layer for this type of work.

AI agents handle preparation, validation, routing, reminders, and monitoring. Your team handles the decisions that require judgment and accountability.

Getting started with Moxo

Moxo pricing starts for free  and scales through Business, Pro, and custom Enterprise plans.

Free is designed for testing simple, low-volume processes. Business supports recurring workflows with stronger reporting, document, audit, and webhook capabilities. Pro adds the volume and process depth required for more complex operations, including unlimited steps, subflows, REST API steps, agent roles, and time booking. Enterprise is designed for custom capacity, advanced security, SAML SSO, MCP Server connectivity, and larger deployments.

The right plan depends on three practical questions:

How often will the process run?

How many steps and systems are involved?

How much AI execution will happen inside each flow?

The best way to evaluate the price is to compare the total cost with the manual coordination, delays, rework, and operating capacity the process consumes today.

To confirm the right plan and estimate your required flow and AI capacity, speak to the Moxo team. Or get started for free

Frequently asked questions

Does Moxo have a free plan?

Yes. Moxo’s Free plan costs $0 and includes 2 flows, 250 AI credits per month, and up to 10 steps per flow. It is best suited to testing, proofs of concept, and very low-volume processes.

What is the difference between a template and a flow?

A template is a reusable workflow blueprint. A flow is one active instance of that template. If a customer onboarding template is started for ten customers, that creates ten flows.

Does every Moxo AI action consume credits?

No. Flow Builder chat, Agent Builder chat, Step Setup co-pilot, Reports Chat, and FAQ keyword-tier responses do not consume AI credits. Production AI actions such as extraction, review, preparation, summarisation, and agent execution may consume credits.

Is Moxo priced per user?

Moxo’s public pricing is structured around flows, AI credits, step limits, and plan capabilities rather than a standard per-user fee. Buyers should still confirm any participant or account limits that apply to their selected plan.

Which Moxo plan includes portals?

Basic portal capabilities are available on the Free plan. Higher tiers add more advanced workflow, integration, data, branding, governance, and deployment capabilities.

Which Moxo plan includes subflows?

Subflows are available on Pro and Enterprise. They are not included in Free or Business.

‍