Predictable Pricing For Production-Grade Automation

Workflow runs aren't metered — every plan runs under a fair use policy, so normal automation is covered even at scale. If your organisation's usage runs well beyond typical patterns, we'll work with you to add a Flow Pack: a flat-rate capacity top-up, not a per-task penalty rate.

The best way to determine the right plan is to walk through the process with our team. What looks like one process from a business perspective may require several workflows — or several activities that look separate may be handled within a single end-to-end workflow.

For example, you might want to automate one approval process, but if employees can initiate it through several different forms, the architecture will involve multiple workflows. On the other hand, invoice intake, data extraction, validation and posting the result to your CRM may all be designed as one end-to-end Zenphi workflow.

In a 30-minute conversation, our experts can review your use case, suggest the most efficient workflow architecture and recommend the appropriate plan with a quote.

That doesn't automatically mean you need more workflows. Our team will first look at whether a 50-step workflow is the best way to structure the automation.

For more complex processes, it can sometimes make sense to move parts of the logic into reusable subflows called by the main workflow. This can make the automation easier to maintain, troubleshoot and scale.

If 50+ steps genuinely belong in a single workflow, that's fine too — it is still considered one workflow for plan purposes.

Not at all. The number of business entities, systems or accounts involved does not determine the number of workflows you need.

If they are all part of one process, they can be incorporated as steps within the same workflow. A workflow can interact with multiple systems and even connect to different Google Workspace accounts as part of a single end-to-end automation.

What matters is the process you're automating — not how many entities it touches.

No. Zenphi doesn't charge based on the number of employees benefiting from your automations. What matters is primarily how many processes you need to automate.

In Zenphi, a user is typically someone who designs, manages or maintains workflows. The employees who interact with those workflows don't need paid licences simply because they participate in a process.

So whether 20 or 2,000 people submit forms, receive automated emails, complete approval tasks or ask an AI agent for the status of their request, that doesn't turn them into paid Zenphi users.