"Save hours every week." "Eliminate manual work." "Transform your operations."
Every automation vendor leads with phrases like these. And they're not wrong—automation does save time. But vague promises don't help you decide whether to spend £5,000 building a specific workflow. You need actual numbers. A model that tells you whether the ROI justifies the build cost before you commit a penny.
Here's how to build that model.
Step 1: Quantify What You're Currently Spending
Start with a time audit on the specific workflow you're considering automating. Ask three questions: How often does this task happen? How long does it take each time? Who's doing it—and what does their time actually cost?
Here's a real example. Your sales team manually logs every call outcome in the CRM. 15 calls per day × 3 minutes per log = 45 minutes per day. At a fully-loaded cost of £35/hour for a sales rep, that's £26.25 per day, or £550 per month per rep. Across four reps, you're spending £2,200 per month on a task that delivers zero customer value. No revenue generated. No relationship built. Pure overhead.
Most companies have three to five workflows like this hiding in plain sight.
Step 2: Calculate the Real Cost to Build
A standard workflow automation—one to three integrations, linear logic, well-defined inputs and outputs—typically costs £900 to £1,800 to build and test. Monthly management (monitoring, minor updates, troubleshooting) runs £500 to £900.
For the CRM logging example: £1,200 build + £500/month management = £7,200 in Year 1. That's your cost. Now let's look at what you get back.
Step 3: Count the Benefits You're Not Tracking
Time savings are the most visible return. They're not the only one.
Error reduction matters more than most companies realize. Manual data entry carries a significant error rate. In a CRM context, bad data leads to bad reporting, misdirected leads, and missed follow-up. Gartner's research on data quality puts the average cost of poor data at $12.9 million per year across organizations—with most of that flowing directly from manual entry errors in CRMs and ERPs. Even at SMB scale, the waste is real.
Speed is a revenue multiplier. A prospect who submits a form and gets a personalized response within 60 seconds converts at a measurably higher rate than one who waits four hours while someone processes the queue manually. The automation doesn't just save time—it improves the outcome.
Consistency eliminates silent failures. Humans skip steps when they're busy. They forget step four of seven when a call runs long. Automations don't. Every trigger fires the same sequence, every time, regardless of how the week is going.
Freed capacity has a revenue value. Give a sales rep 45 extra minutes per day and they can make three more calls. At your close rate and average deal size, that 45 minutes is worth a specific pound figure—one you can calculate.
Step 4: Run the Payback Math
Back to our example. £2,200/month in savings vs. £7,200 Year 1 cost. Payback period: 3.3 months. From Month 4 onward, the automation generates a net positive of £1,700/month—£2,200 saved minus £500 management fee.
That's a conservative case. For workflows involving multiple team members, senior staff time, or higher-frequency tasks, payback often drops below two months. We've seen simple onboarding automations pay back their build cost in six weeks.
The Question That Matters More Than ROI
The businesses extracting the most value from automation aren't necessarily automating the most. They're automating the right things first.
The profile of a high-value automation candidate: high frequency, low judgment, currently consuming disproportionate team time relative to its actual value. Invoice chasing. CRM data entry. Onboarding task sequences. Weekly reporting. These are the workflows where automation wins every time.
The automation projects that disappoint are the ones that start with the tool—"we bought Make, what do we use it for?"—rather than starting with the audit. What is the single most expensive manual workflow in this business right now? That's where you start.
A good automation partner asks that question first. The tool choice comes after.
If you're spending more than 20 hours a month on manual workflows that follow predictable steps, see which automations we implement first →