Worked example: n8n daily lead enrichment
The default scenario runs 120 times per day for 22 active days, so monthly workflow runs are 120 x 22 = 2,640.
n8n prices cloud plans by workflow executions regardless of steps, so the 8 action steps per workflow do not multiply the billable unit count. Billable units are 2,640 executions.
Starter includes 2,500 executions, so this workload is 140 executions over Starter. Pro includes 10,000 executions and costs EUR 50/month on the referenced annual-billing page.
Utilization on Pro is 2,640 / 10,000 = 26.4%, leaving 7,360 included executions. Cost per run is EUR 50 / 2,640 = EUR 0.0189 before add-ons, self-hosted infrastructure, or AI API charges.
How the automation tier estimate works
The calculator turns runs per day and active days into monthly workflow runs. For n8n, the billable unit is monthly workflow executions. For Zapier and Make, the billable unit estimate multiplies monthly runs by billable action steps, then adds extra monthly units for retries, replays, or credit-consuming features.
The recommended tier is the first sourced plan threshold that fits the unit count. When a platform exposes a variable usage selector or custom sales quote, the result uses the current quote input and labels the result as quote-based.
How many Zapier tasks will my automation use?
For planning, estimate successful action steps per run and multiply by monthly runs. AI steps, code, paths, and app actions can add task usage, so replace the estimate with Zapier task history once the workflow is live.
How many Make credits will my scenario use?
Most ordinary Make actions can be planned as one credit each, but code execution and some AI Provider features can consume more. Use scenario history after testing to replace the rough billable-actions-per-run input.
What this estimate excludes
The result excludes AI API tokens, vector database charges, self-hosted servers, managed databases, staff review time, error handling, maintenance, implementation effort, and taxes. Use the related calculators to finish the cost picture.
What to do next
Run a small live test, export actual usage, add retries and failure paths, then update the quote field with the current provider price before choosing a production platform tier.