How run-based pricing compares with per-step pricing
Many automation tools bill every step inside a workflow. Bizomate bills the run — one pass of a workflow, however many steps it has. Here is what that means for your bill, including when the two come out about the same.
What each one counts
A run starts when the trigger fires and ends when the last step finishes. Per-step pricing counts each step in it; we count the run once.
The same month, counted both ways
Twelve workflows, each running 400 times a month, with six steps on average — the example on our Pricing page.
12 × 400 × 6. Adding a step to any workflow raises it again.
12 × 400. Adding a step changes nothing — Pro covers it, with 20,200 to spare.
Where the difference grows
The more steps a workflow has, the wider the gap. Loops widen it most: per-step pricing often counts every item a loop handles as a step.
| Workflow | Steps | Runs a month | Counted per step | Counted on Bizomate |
|---|---|---|---|---|
| Order alerts | 6 steps | 400 | 2,400 | 400 |
| New lead to CRM | 8 steps | 1,000 | 8,000 | 1,000 |
| Daily report that goes through 50 rows | 3 steps and a loop | 30 | 1,590 | 30 |
| Forward an email to Teams | 1 step | 2,000 | 2,000 | 2,000 |
When they come out about the same
If most of your workflows are one or two steps — forward an email, copy a row — per step and per run count nearly the same. Then compare the price of each run, the history you keep and the support you get, not the counting.
What does not change with steps
A price that stays the same when you add a step Conditions, lookups and AI steps count the same as any other — they are all inside the run Your plan’s price, fixed in rupees for a company in IndiaWhat happens at your limit
Nothing stops at your limit, and there is no penalty rate. We tell you at 80% and 100%, keep running to 110%, then offer more runs at your plan’s own price for the rest of the month.
Work out your own number
Three numbers in the run calculator, and you know which plan fits.