Most SMEs decide whether to automate a task by looking at the tool’s price tag. But that number only tells one third of the story. The real cost includes review time, the impact of a mistake, and the hours your team spends adapting. This article gives you a 4-variable formula to decide whether a task is worth automating — with concrete examples for accounting firms, auto repair shops, and dental clinics. No hype, no “AI will solve everything.”
The problem isn’t the tool’s price
When an SME owner considers automating a task, the conversation usually starts — and ends — with the price. “How much does this tool cost per month?” It’s a logical question, but incomplete. It’s like buying a car by looking only at the sticker price and forgetting insurance, maintenance, and fuel.
A few days ago, the technical community around Llama.cpp — the engine that runs AI models directly on a regular computer, without relying on external servers — reported an 11 to 16× improvement in inference speed on Apple Silicon chips. Translation: tasks that once needed a cloud server can now run on a Mac Mini under a desk.
For an SME, that technical news has a practical and non-obvious consequence: the cost per automated task is dropping faster than most people realize. But the tool’s price is only one of the four pieces that determine whether it’s worth it.
The 4 variables that actually matter
The framework we’re proposing — let’s call it the 15-Minute Calculation — starts from a simple premise: a task is worth automating when the time saved multiplied by its frequency exceeds the cost of reviewing it plus the cost of getting it wrong.
Four variables, no more:
| Variable | What it measures | Example |
|---|---|---|
| Monthly frequency | How many times the task repeats each month | 120 invoices, 80 appointment reminders, 45 quotes |
| Minutes saved per task | What a human takes today minus what the system would take | 8 minutes (manual) → 30 seconds (automated) = 7.5 min saved |
| Review cost | The minutes someone spends checking that the system didn’t make a mistake | 1 minute per invoice to validate amounts and tax IDs |
| Error cost | What a single undetected mistake costs — in money, time, or reputation | An invoice with the wrong tax ID: ~20 min to find the error, correct it, and notify the client |
The formula is straightforward: (Frequency × Minutes saved) − (Frequency × Review cost) − (Error rate × Error cost). If the result is positive and meaningful — say, more than 2 net hours per month — the task is a candidate. If it’s negative or marginal, it’s better to leave it as is.
Three examples with real numbers
1. Accounting firm: reconciling incoming invoices
A typical accounting firm processes about 200 incoming invoices per month. Each takes roughly 4 minutes between opening the PDF, extracting the data, cross-checking with the bank statement, and filing it. Today’s AI can extract that data in seconds with a 90-95% accuracy rate on clean documents.
| Variable | Value |
|---|---|
| Frequency | 200 invoices/month |
| Minutes saved | 4 → 0.2 = 3.8 min |
| Review cost | 0.5 min per invoice |
| Error cost | 15 min per misregistered invoice |
| Net savings | ~10.5 hours/month (even with a 10% additional review rate) |
With a tool costing €40-80/month and an employee hourly cost of around €18-22/hour, the return is immediate: the first month already saves 3 to 5 times what you pay. This is the clear case where automation makes sense.
2. Auto repair shop: custom quotes
A typical workshop issues about 45 quotes per month. Each requires looking up part numbers in the distributor’s catalog, calculating labour times against standard rates, and drafting the document. A well-made quote takes 15-20 minutes. A bad one — with a wrong part number — can cost a returned part, a customer waiting 3 extra days, and a 1-star Google review.
| Variable | Value |
|---|---|
| Frequency | 45 quotes/month |
| Minutes saved | 17 → 3 = 14 min |
| Review cost | 2 min per quote (verify part numbers) |
| Error cost | 120 min (part return + correction + unhappy customer) |
| Net savings | ~7.5 hours/month (assuming the system gets 42 out of 45 right) |
Here the decision is more nuanced than the accounting case. The net savings are still positive — 7.5 hours a month is nearly two full workdays — but the cost of a single error is high. Automation makes sense if and only if you design it with a mandatory human review step for part numbers. This isn’t about letting go of the wheel — it’s about taking the repetitive part off the mechanic’s plate while keeping the final check.
3. Dental clinic: WhatsApp emergency triage
A dental clinic receives about 80 WhatsApp messages per month from patients with questions: “Is this normal after the implant?”, “Can I take ibuprofen?”, “My bracket came off.” A team member — usually the assistant or receptionist — spends about 3 minutes per message reading, classifying the urgency, and responding or forwarding to the dentist.
| Variable | Value |
|---|---|
| Frequency | 80 messages/month |
| Minutes saved | 3 → 0.5 = 2.5 min |
| Review cost | 0.25 min per message (validate the classification is correct) |
| Error cost | Variable and delicate: misclassifying a real emergency as “non-urgent” can have medical and legal consequences |
| Net savings | ~2.8 hours/month, but with a risk that can’t be measured in minutes alone |
This is the example where the formula says “yes” but common sense says “with conditions.” The net savings are modest — just under 3 hours a month — and the cost of a mistake isn’t financial, it’s clinical. Automation here is only acceptable with three safeguards: (1) the system never decides alone — it always classifies and suggests, (2) any message containing certain keywords (“bleeding,” “fever,” “swelling,” “severe pain”) is automatically escalated to a person without going through the AI, and (3) the dentist receives a daily summary of what was classified. It’s not a bot that replaces — it’s a filter that saves reading time without removing clinical judgment.
The three most common mistakes when doing this calculation
1. Measuring only the tool, not the entire system. Automation isn’t an app — it’s a workflow that includes the tool, initial setup time, maintenance, exceptions, and the person who reviews. If you only look at the license price, you’re counting 30% of the real cost.
2. Assuming AI always gets it right. No system has 100% accuracy. If you design your workflow as if it does — no review step, no fallback plan for failures — the first mistake will cost you more than several months of savings.
3. Automating what shouldn’t be automated. Some tasks are where the “minute saved” doesn’t justify the risk. Medical emergency triage, drafting a termination letter, or communicating a sensitive clinical result fall into this category. The formula gives you a number; judgment decides whether that number is enough.
Your Quick Win for today
Take one repetitive task from your business — the one you hate most — and apply the 4 variables in 5 minutes:
- Frequency: how many times a month does it happen?
- Minutes saved: how long does it take today? How long would it take with help?
- Review cost: who would check the result and how long would it take?
- Error cost: what would happen if 5% of the time it goes wrong?
Multiply and compare. If the net result exceeds 2 hours per month, you’ve got a candidate. If it’s less, save it for later. You don’t need a consultant for this calculation — you need 5 minutes, a piece of paper, and honesty about your business’s numbers.
Have a task you think is worth automating but don’t know where to start? We can run the calculation together in 30 minutes — no commitment, no corporate presentation, just numbers and judgment.
Request a Free Diagnostic