The payback period for a workflow build
A workflow's payback period is the simplest number in automation. How to calculate it, and what a healthy one looks like.
Nikolas Gannon · · 1 min read · Automation
The payback period is the simplest number in automation: how long until the workflow pays for itself. It answers the only question that matters before you build.
The calculation
Payback months = build cost ÷ monthly value.
Build cost is the fixed price. Monthly value is the hours saved per month times the loaded hourly cost, plus recovered revenue.
What healthy looks like
A single workflow from about $500 that saves ten hours a month at $60 an hour pays back in under a month. Even a larger build usually pays back inside a year when the workflow touches real volume.
What makes payback short
- Frequency. A task that happens 40 times a week beats one that happens twice.
- Loaded cost. Count salary, on-costs and overhead, not just the hourly wage.
- Recovered revenue. Faster follow-up and reliable invoicing are usually the bigger half of the value.
What makes it long
Low-frequency tasks, one-off jobs and admin that is annoying but cheap. If the payback looks like a year or more, the honest answer is usually not to build. That is a normal result, not a failure.
Why this matters when buying
When a consultant quotes you, run the math yourself. If the numbers do not work, say so. A good consultant would rather not build a workflow that does not pay for itself, because a client who loses money tells everyone.
The summary
Payback is the measure that keeps automation honest. Calculate it before you build, measure it after, and let it decide what comes next.
If you want help running the numbers on your first workflow, the free systems audit covers it.
Free resource: Workflow automation audit workbook
Free resource: Software bill review checklist
Read next: Automation ROI: how to calculate it · How to start with one workflow · The proposal timeline: from scope to handoff
Questions
What is the payback period?
The time it takes for the value of a workflow to cover what it cost to build.
What is a healthy payback?
Months, not years, for most single workflows. A year or more means the workflow may not be worth it.
What makes payback short?
High-frequency tasks, loaded staff costs and recovered revenue. Low-frequency admin is rarely worth automating.