TL;DR
- Paper processes have a fully-loaded cost most businesses have never calculated: staff time, error correction, storage, retrieval, and delay costs typically add up to £38 per transaction.
- At 200 transactions per month with a £4,000 build cost, Year 1 ROI is 2,180%. Year 2 is pure saving — £91,200 per year.
- The financial case alone is enough. Payback is almost always under 3 months for high-volume processes.
- The non-financial case (speed, compliance, employee frustration) is real but rarely needed — the numbers win the argument first.
Nobody budgets for paper processes. They just exist. Somewhere in your organisation right now, someone is printing a form, walking it to another desk, and waiting. That moment has a cost. It happens again an hour later with a different form. And again tomorrow.
Most businesses have never added it up. When we do it for clients as part of a pre-project audit, the number surprises them every time. Not because the per-transaction cost is dramatic on its own — £38 doesn't sound like much. It's when you multiply it by transaction volume that the picture changes.
A process that runs 200 times per month is costing £7,600 per month, or £91,200 per year. For a process most organisations would describe as "just how we do it."
The Full Cost Calculation
Here is how we build the cost model. Use your own numbers — the structure is the same.
We use a fully-loaded hourly rate of £18 for this example. Fully-loaded means base salary plus employer contributions, benefits, and overhead — typically 1.3x to 1.5x base salary divided by 1,760 working hours per year. For a mid-level admin or coordinator on a £25,000 salary, £18/hr is realistic. Adjust for your own staff costs.
| Cost Component | Calculation | Cost Per Transaction |
|---|---|---|
| Staff time — printing, filling, carrying, chasing, filing | 22 min avg × £18/hr | £6.60 |
| Error correction — 23% of transactions have an error, avg 35 min to fix | 0.23 × 35 min × £18/hr | £2.42 |
| Physical storage — filing cabinet cost, floor space, admin to maintain | £0.80 per document per year (annualised per transaction) | £0.80 |
| Document retrieval — finding a specific paper record when needed | 18 min avg × £18/hr (prorated for retrieval frequency) | £5.40 |
| Delay cost — capital tied up, missed opportunities, SLA breaches | Estimated conservative at process level (highly variable) | £22.78 |
| Total estimated cost per paper transaction | ~£38.00 | |
A note on the delay cost: this is the most variable and the hardest to pin down precisely, which is why we put it last. For a £50,000 purchase order sitting in an approval queue for 3 days, the cost-of-capital delay alone is meaningful. For a leave request, the delay cost is lower but still real — a manager making a staffing decision without knowing who's approved for leave that week. We use a conservative £22.78 in this model. For procurement or finance processes, the real number is often 3 to 5 times higher.
The five cost components of a typical paper-based transaction. The delay cost is the largest — and the most often ignored.
The Comparison: Digital Cost Per Transaction
An SPFx form combined with a Power Automate approval flow has zero marginal cost per transaction after the initial build. The Microsoft 365 licences you already pay for cover the compute. The flow runs. The cost is fixed.
Here is the ROI calculation for a mid-complexity process running 200 transactions per month, with a one-time build cost of £4,000:
| Metric | Value |
|---|---|
| Monthly transactions | 200 |
| Cost per paper transaction | £38 |
| Annual paper process cost | £91,200 |
| One-time automation build cost | £4,000 |
| Marginal digital cost per transaction | £0 (after build) |
| Year 1 net saving | £91,200 − £4,000 = £87,200 |
| Year 1 ROI | 2,180% |
Year 2 onwards is £91,200 per year in pure saving, with no additional build cost. The £4,000 investment pays back in 16 days at 200 transactions per month. Even at 50 transactions per month, payback is under 3 months.
Cumulative saving over 24 months at 200 transactions/month with a £4,000 build cost. Break-even occurs in month 1.
How to Build the Business Case for Your Organisation
This is the method we use with every client before any build starts. It takes about 2 hours and produces a number that tends to end the discussion about whether to proceed.
Pick one process
Don't try to cost every process at once. Pick the highest-volume paper-based process in your organisation. Usually that's approvals, leave requests, purchase requisitions, or invoicing. Whichever one someone complains about most is often the right starting point.
Count transactions per month
Pull actual numbers. Look at the last 3 months and average them. If records aren't available (they often aren't for paper processes), count the physical file folders or ask the people doing the work.
Time each step with an actual stopwatch
Sit with the people who do the work. Watch them process one transaction start to finish. Time each step. Add them up. This number is almost always higher than anyone's estimate — people are surprisingly bad at estimating how long routine tasks take.
Multiply by fully-loaded hourly rate
Take the total minutes per transaction and convert to a cost using the fully-loaded hourly rate for the staff involved. Add the error correction cost (ask "how often does something go wrong?" and time a correction). Add storage and retrieval estimates.
Compare against the build cost
Simple flows (single-stage approval, one form, basic routing): £1,500 to £3,000. Mid-complexity (multi-stage, conditional routing, Teams Adaptive Cards, reporting dashboard): £3,000 to £6,000. Complex (multi-department, integrations, escalation logic, Power BI): £5,000 to £8,000. Divide your annual cost by the build cost. That's your Year 1 ROI. If it's below 200%, question the transaction count or error rate estimates — the real number is usually higher.
The Non-Financial Case
The financial case is almost always sufficient on its own. But there are four non-financial arguments worth having on hand when finance directors ask what else they're getting.
Speed to decision. A 72-hour approval cycle doesn't just cost money — it slows down everything downstream. Procurement can't order until the approval clears. Projects can't start. Suppliers don't get paid. Speed has compounding operational value beyond the cost of the wait itself.
Compliance and audit readiness. Paper processes have no inherent audit trail. Approvals happen, but there's no record of who approved what, when, and on what basis. For regulated industries, this is not just inconvenient — it's a compliance risk. Digital flows create a timestamped, immutable audit log by default.
Employee frustration. Paper processes consistently top the list of complaints in employee engagement surveys. Manual, repetitive, error-prone work is demoralising. Removing it is a retention argument as much as an efficiency one. We've had clients tell us that the automation build had more positive feedback in staff surveys than any other initiative that year.
Customer experience. For processes with external-facing components — supplier payments, client approvals, customer onboarding — delays and errors are visible. They communicate something about how professionally the organisation runs. Fixing internal processes often has direct knock-on effects on client relationships.
Non-financial arguments are real, but in most organisations they don't move budget. The number — "this process is costing us £91,200 per year and we can fix it for £4,000" — does. Build the financial case first. Add the non-financial arguments as supporting context once the decision-maker is already nodding.
Common Objections and Honest Answers
Key Takeaways
The £38 figure isn't arbitrary. It's built from five measurable components: staff time, error correction, storage, retrieval, and delay. Run the calculation for your own process with your own hourly rates — the structure is the same, and the total will surprise you.
ROI over 2,000% sounds implausible until you see the maths. The reason it's so high is that the paper cost is ongoing and recurring, while the build cost is one-time. Every month of delay is another month of the full paper cost with no payback.
The business case doesn't need to be complicated. Transaction count × cost per transaction × 12 = annual paper cost. Subtract the build cost. That's Year 1. If that number doesn't justify the investment, either the transaction volume is lower than expected or the process is simpler than typical — in which case the build cost should be lower too.