Pricing starts with workflow scope and approval complexity.
We scope pricing around the workflow you need first, the document and approval load around it, and the deployment support required to put it into production.
Plans
Starter
Perfect for individuals getting started with AI
- 1 user
- 2 apps
- 5 GB storage
- ~400K tokens
- Standard support
Pro
Best for growing teams and small businesses
- 1 user
- 5 apps
- 20 GB storage
- ~2M tokens
- Priority support
Business
For established businesses with advanced needs
- 3 users
- 10 apps
- 100 GB storage
- ~8M tokens
- Priority support
Enterprise
Custom solutions for large organizations
- 10 users
- 30 apps
- 500 GB storage
- ~80M tokens
- Standard support
What shapes the starting package
Workflow scope
Pricing starts with the workflow you want to operationalize first, whether that is vendor onboarding or another related approval-heavy process.
Document and approval load
Volume, document mix, approver count, and request-more-information branching affect the scope of the deployment.
Governance depth
Authorization, approvals, audit posture, and the level of control your team requires before wider rollout.
Deployment scope
Scope depends on what the deployment should own, how work moves forward after approval, and how much rollout support your team needs.
Pricing follows workflow shape, not a one-size-fits-all tier.
Deployment scope depends on the workflow, the approval path, the document load, and the level of governance the team needs in production.
- Start with one production workflow and the operator experience around it.
- Match the rollout to your approval depth, document volume, and support needs.
- Add more workflows when the operating model is delivering value.
Prefer a simple rollout-shape visual that supports scoped deployment and clear operating scope rather than generic pricing decoration.
Pricing questions
How is pricing scoped?
Pricing is scoped around the workflow, the document and approval complexity, the governance depth, and the rollout support required to put it into production.
Can we add more workflows over time?
Yes. Many teams begin with one workflow, put it into production, then extend the same model into more approval-heavy work.
Why is pricing conversation-led?
Because workflow scope, packet volume, governance depth, and rollout needs vary materially. A fixed table would hide the differences that shape a successful deployment.