Guide / Automation
What business process automation actually costs and returns
Automation pricing runs from a $30 monthly Zapier plan to six-figure consulting engagements, and most of the ROI numbers floating around are vendor marketing. Here is what the credible research actually says about costs, time saved, and payback, and how the three main ways of buying automation compare.
What the research says about returns
The headline potential is real. McKinsey Global Institute's analysis of over 2,000 work activities found that about half of the activities people are paid to do could technically be automated with already-demonstrated technology (McKinsey, Jobs lost, jobs gained). That is a ceiling, not a forecast, but it explains why the opportunity keeps showing up in survey data.
On the ground, the numbers are more modest and still good. Zapier's survey of 2,000 knowledge workers at companies under 250 employees found that 94 percent perform repetitive, time-consuming tasks, and 66 percent of those using automation say it lets them focus on more creative work (Zapier, State of business automation). A separate Zapier study found 88 percent of small businesses say automation lets them compete with larger companies (Zapier, business resiliency report). HubSpot's State of AI research puts the time savings from AI tools at roughly two and a half hours per day for professionals who use them (HubSpot, State of AI).
Payback timelines have data behind them too. Deloitte's Automation with intelligence survey found executives expect intelligent automation to cut costs by about 22 percent and lift revenue by 11 percent over three years, and organizations automating at scale reported an average payback period of around nine months, versus fifteen months expected by those still piloting (Deloitte, Automation with intelligence).
The three ways automation gets bought
| Option | Typical cost | What you get |
|---|---|---|
| DIY with no-code tools | $20 to $150 per month, plus your hours | Zapier, Make, or n8n wired up yourself. Cheap in cash, expensive in founder time, and fragile once workflows pass a handful of steps or need error handling. |
| Agency or consultancy | $5,000 to $50,000+, often retained monthly | Discovery phases, hourly billing, and a team. Right for enterprise integrations across many departments. Overkill and overpriced for a single broken process. |
| Fixed-price build | $750 to $7,500 per build | A defined scope, a quoted price, a working system demonstrated on your real data before you commit. You own the result; no retainer required. |
The failure mode of DIY is not the tool cost, it is the maintenance. The failure mode of agencies is incentive: when billing is hourly, a longer project is a better project for the vendor. Fixed pricing puts the scope risk on the builder, which is where it belongs.
The payback math for a small team
Ignore the survey averages and run your own numbers, because the math is short. Take one process: an operations hire spends six hours a week moving data between a form, a spreadsheet, and an invoicing tool. At a fully loaded cost of $40 per hour, that is $240 a week, roughly $12,500 a year. A $2,500 build that removes five of those six hours pays for itself in about three months and then keeps paying. That is the boring, checkable version of ROI, and it is the calculation worth doing before any purchase.
Two adjustments keep it honest. First, count only hours that actually get redeployed; time saved that evaporates into slack is not a return. Second, add something for error reduction: manual copy-paste processes generate mistakes, and mistakes in invoicing or customer data have costs that never appear on a timesheet.
Why so many projects can't prove ROI
The uncomfortable finding in the Deloitte survey is that over half of organizations had not calculated the cost reduction from their automation programs at all. The projects may be working; nobody measured. This is a buying lesson, not just a management lesson: if a vendor cannot tell you, before the build, which metric will move and how you will check it, the ROI conversation is decoration.
The other common failure is automating a process nobody has written down. If the process only exists in one employee's head, the automation will encode their workarounds and their mistakes. An hour spent documenting the current process, exceptions included, is the cheapest de-risking step available.
How to buy it well
- Price the manual process first. Hours per week times loaded hourly cost. If the annual figure is under the quote, don't automate it yet.
- Demand a demo on your data before you pay. A working slice of the real workflow beats any proposal document.
- Insist on ownership. The workflows, code, and documentation should be yours at handover, running on your accounts, so you are not renting your own operations back.
- Agree the success metric up front. Hours saved, error rate, turnaround time: pick one and measure it before and after.
This is the model behind VerifiedDesk's fixed-price automation builds: scopes from $750 to $7,500, a demo on your real data before commitment, and full ownership at handover. Whoever you hire, run the payback math above first and hold them to the metric.
Sources: McKinsey Global Institute, Jobs lost, jobs gained (mckinsey.com); Deloitte, Automation with intelligence survey (deloitte.com); Zapier, State of business automation, 2,000 SMB knowledge workers (zapier.com); Zapier, business resiliency report (zapier.com); HubSpot, State of AI report (blog.hubspot.com). Price ranges for tools, agencies, and builds are indicative market ranges as of mid 2026, not quotes.