A business process automation tool plan can look harmless at $9, $15, or $19 per month until the real meter starts running. The line item that matters may not be the seat price. It may be 100 tasks, 1,000 operations, two active scenarios, 200 steps, 750 tasks, 2,500 executions, or a sales-quoted tier that appears only after a workflow has become hard to unwind.
Pricing below was last checked in June 2026. Treat it as a budgeting map, not a contract: vendors change packaging, regional prices differ, annual billing can change the monthly equivalent, and enterprise quotes depend heavily on scope.
| Tool | Free or lowest visible entry point | Starter paid price | Main billing model | Budget watchpoint |
|---|---|---|---|---|
| Zapier | Free plan: 100 tasks/month and single-step Zaps | Pro starts at $19.99/month with 750 tasks | Per-task | Friendly for testing and low-volume handoffs; expensive when routine events fire all day |
| Make | Free plan: 1,000 operations/month and 2 active scenarios | Paid starts at $9/month with 10,000 operations | Per-operation | A single workflow can consume multiple operations, so the free-to-paid jump is only part of the cost story |
| Stepper | Free plan: 200 steps/month and 5,000 credits | Pro is $19/month for unlimited steps under fair-use terms | Per-step / credit-based | The word “unlimited” still needs the fair-use policy behind it |
| n8n | Self-hosted Community Edition is free | Cloud starts at $24/month with 2,500 executions | Self-hosted or execution-based cloud | Lowest absolute software cost if someone can own hosting, updates, and troubleshooting |
| Power Automate | Basic automation is included with some Microsoft 365 plans | Premium is $15/user/month | Per-user | Predictable for Microsoft-heavy teams, but connectors and premium features change the real answer |
| Cflow | Free trial | $7–$11/user/month | Per-user | Simple to budget when headcount is stable; less appealing when every occasional approver needs a paid seat |
| Pipefy | Entry pricing varies by packaging | Starts at $23/user/month, billed annually | Per-user | Good for process ownership and forms; seat count becomes the ceiling |
| Appian, Pega, UiPath, Workato | Usually not meaningfully comparable to free SMB tiers | Quote-based enterprise pricing, often starting far above small-team tolerance | Enterprise contract | Procurement, implementation, governance, and volume commitments matter more than public list price |
The Price Tag Is Usually the Wrong Unit
The cheapest plan on a pricing page is rarely the cheapest operating setup. What matters is the thing the vendor counts. Zapier counts tasks. Make counts operations. Stepper counts steps and credits. n8n Cloud counts executions, while self-hosted n8n moves much of the cost into infrastructure and maintenance. Power Automate, Cflow, and Pipefy lean toward per-user pricing, which makes the monthly bill easier to forecast when the team size is known.
That difference sounds small during a demo. It is not small after the workflow goes live. A “new form submission → create CRM record → notify Slack → create invoice draft → update spreadsheet” automation may look like one workflow to the person using it. To a billing system, it may be several chargeable events. The same business process can be cheap, reasonable, or irritatingly expensive depending on which counter sits underneath it.
For a deeper feature-level comparison after the budget tier is clear, see Best Process Automation Tools 2026: Tested and Compared. This article stays on the cost behavior first, because that is where most small teams get surprised.
Four Pricing Models, Four Different Failure Points
Per-task and per-operation tools are attractive because they let a solo worker or small team test automation without a large commitment. Zapier’s free plan offers 100 tasks per month and single-step Zaps, while its Pro plan starts at $19.99 per month with 750 tasks. Make’s free plan offers 1,000 operations per month and two active scenarios, and its paid plan starts at $9 per month with 10,000 operations. Lindy’s 2026 testing and pricing comparison places these connector-style tools in the same practical buying set, but the units are not interchangeable.[1]
Stepper sits in a similar low-friction category, with a free plan of 200 steps per month and 5,000 credits, plus a $19/month Pro plan described as unlimited steps under fair use.[2] The useful part is the accessible entry point. The part to read twice is the fair-use language, because “unlimited” in workflow automation still has to survive normal business usage.
Per-user pricing behaves differently. Cflow lists pricing at $7–$11 per user per month with a free trial, positioning itself as a no-code workflow platform for SMBs.[3] Power Automate Premium is $15 per user per month, while basic automation is included with some Microsoft 365 plans. Pipefy starts at $23 per user per month on annual billing. Those numbers are easier to pencil into a quarterly budget than a task meter, but they make every additional participant matter.
Self-hosted pricing is its own lane. n8n’s Community Edition is free and fully featured when self-hosted, while n8n Cloud starts at $24 per month with 2,500 executions. On paper, the self-hosted option is the obvious low-cost outlier. In practice, someone has to install it, secure it, update it, monitor failures, manage credentials, and understand what broke when an API changes. For technical teams, that trade can be excellent. For a nonprofit treasurer or founder who already owns six other systems, the “free” part can become a time debt.
Enterprise platforms such as Appian, Pega, UiPath, and Workato belong in a different buying universe. Moxo’s 2026 list of business process automation tools is useful for seeing the breadth of the category, but public comparison tables can make small-team products and procurement-led enterprise systems look more comparable than they are.[4] Once a tool is quote-based, the relevant questions shift from “Can we afford the starter plan?” to implementation scope, governance, security review, minimum contract size, and who is responsible when automation touches regulated or high-value work.
Who Each Model Rewards
Per-task tools reward low-volume, high-value automation. A freelancer who sends a few dozen lead notifications, invoice reminders, or file handoffs each month may get real relief from Zapier or Make without crossing a paid ceiling. A student group or small nonprofit can use the free tier to prove that a workflow works before asking anyone to approve a recurring expense.
The same tools punish noisy workflows. If every website form, CRM update, payment event, and support ticket triggers multiple downstream actions, the task meter becomes the bill. This is where a plan that looked cheaper than a team lunch starts behaving like a software subscription that needs an owner. The uncomfortable question is not whether the automation works. It is whether the workflow fires often enough that the billing unit becomes the dominant design constraint.
Per-user tools reward stable teams. A five-person operations team can estimate a Cflow, Pipefy, or Power Automate bill more cleanly than it can estimate a task-based bill if the monthly automation volume is uncertain. The tradeoff appears when occasional approvers, seasonal staff, outside contractors, or department heads need access. Per-user pricing is predictable only when the user list is predictable.
Microsoft-heavy teams should price Power Automate separately from the sticker number. Some basic automation is already included in Microsoft 365 plans, so the first useful workflow may not require another vendor at all. Premium connectors, advanced usage, and licensing boundaries can still change the bill. The deeper Microsoft-specific version of that problem is covered in Power Automate Pricing 2026: What the Free Tier Actually Gets You.
Self-hosted n8n rewards technical ownership. It is not just “cheaper Zapier.” It is a different operating model. A capable team can keep software spend low and avoid per-task anxiety, especially when workflows are frequent. A nontechnical team may instead pay with delayed fixes, fragile credentials, and automations nobody wants to touch. For that no-code versus code-first decision, the useful comparison is less about taste and more about who will be accountable after the first month; see How to Choose Between No-Code and Code-First Workflow Orchestration Tools.
A Cheap Automation Can Still Be a Bad Buy
Automation can absolutely pay for itself when the process is worth automating. Elementum cites Ardent Research showing invoice processing costs falling from about $12.88 to about $2.78 per invoice, an approximately 80% reduction.[5] That is the kind of number that gets finance attention for the right reason: fewer manual touches, fewer delays, and less staff time spent moving the same data between systems.
The condition is just as important as the savings. A process that is inconsistent, poorly owned, or full of exception handling does not become clean because a workflow tool sits on top of it. McKinsey’s 73% failure context around automation and transformation efforts is a useful brake on the idea that cheaper automation automatically creates productivity. If the underlying process is broken, the team may simply buy a faster way to create rework.
Before choosing a platform, map the workflow in plain terms: trigger, required data, approval owner, exception path, system of record, and failure notification. The practical version of this work is covered in The BPM Workflow Lifecycle: A Practical 5-Step Guide. The budget version is simpler: do not automate a workflow you cannot already explain.
Hidden Costs to Price Before the Demo Ends
- Multi-step automations: one business event may create several billable tasks, operations, steps, or executions.
- Scenario and workflow caps: Make’s free plan includes two active scenarios, which may be enough for testing but tight for day-to-day operations.
- Different counting rules: a Zapier task, a Make operation, a Stepper step, and an n8n execution are not the same unit.
- Seat sprawl: per-user tools become expensive when viewers, approvers, or occasional collaborators need paid access.
- Self-hosting labor: n8n Community Edition can reduce software spend, but hosting, updates, credentials, logs, and uptime still need ownership.
- Quote opacity: Appian, Pega, UiPath, Workato, and similar enterprise platforms may require sales conversations before the real budget appears.
- Contract terms: annual billing, regional pricing, negotiated discounts, and minimum commitments can change the usable monthly cost.
- Broken-process automation: the tool bill is wasted if the workflow creates errors, duplicate approvals, or unclear ownership faster than before.
Vendor-owned comparisons are still worth reading, but they need a filter. Stepper, Cflow, Moxo, and Lindy all publish useful category material, and several include current pricing or hands-on notes.[1][2][3][4] They also have a reason to frame the market in a way that favors their own product or audience. Use them for discovering options and checking packaging, then verify the final shortlist against the vendor pricing page and your own expected volume.
Which Tool Fits Which Budget Pattern
Low-volume freelancers, students, and small nonprofits
Start with a free plan, but treat it as a sandbox. Zapier, Make, and Stepper make sense when the goal is to prove a handoff works and the monthly event count is modest. The budget mistake is building daily operations around a free ceiling, then discovering that the workflow becomes essential at the same moment it becomes billable.
Growing SMBs with recurring workflows
Estimate monthly volume before comparing starter prices. Count how many times the trigger fires, then count the downstream actions. If the workflow runs constantly, a per-task tool may still be right, but it needs a usage forecast. For a broader small-business versus enterprise cost view, see Process Automation Tools for Small Business vs Enterprise.
Microsoft-heavy teams
Check Power Automate before adding another standalone automation product. If the team already lives in Microsoft 365, included automation may cover simple internal workflows. The paid Premium tier at $15/user/month becomes easier to justify when it avoids duplicate tooling, but harder to justify if only one narrow workflow needs a premium connector.
Technical teams that can own infrastructure
Put n8n on the shortlist. Self-hosting can keep software costs low and reduce anxiety around task growth, especially for frequent internal workflows. The deciding question is whether someone is explicitly responsible for the system. If the answer is “whoever has time,” the cloud plan or a managed no-code tool may be cheaper than the hidden labor.
Enterprise buyers
Do not compare Appian, Pega, UiPath, or Workato against a $9 Make plan as if they solve the same purchasing problem. Enterprise tools may be appropriate when governance, auditability, complex integrations, role controls, and service commitments matter more than entry price. They are poor fits when the real need is a few affordable handoffs between common SaaS apps.
The Decision Rule
Estimate monthly automation volume before choosing a tool. Free plans are testing sandboxes, not operating plans. Pick per-task or per-operation platforms when volume is low, occasional, or easy to forecast. Choose per-user platforms when the number of people is the real constraint and the workflow volume is harder to predict. Consider n8n when someone can own the technical work. Treat enterprise platforms as procurement-grade systems, not bargain alternatives to SMB automation tools.
References
- I Tested 8+ Automation Software Tools. Here Are the Best in 2026 — Lindy.ai
- Best Business Process Automation Tools in 2026 — Stepper.io
- The Best Business Process Automation Software in 2026 — Cflow
- Top 20 business process automation tools for 2026 — Moxo
- Business Process Automation: Enterprise Strategy in 2026 — Elementum