Most ERP business case guides are written for organizations with a CFO, a budget committee, an IT department, and a formal capital approval process. If you run a business with 1 to 25 employees, you probably have none of those things. “Getting executive buy-in” usually means convincing yourself, a co-founder, or maybe one business partner who also answers the phones.
That doesn't mean you should skip the thinking behind a business case — it means the process needs to be radically simplified. Below is that same logic, rebuilt for a company where every pound and every hour is felt immediately, where “IT department” means whoever is least afraid of software, and where a bad ERP decision can genuinely sink the business rather than just embarrass a department head.
Why Bother With a Business Case If It's Just You Deciding?
Even when you don't need to convince anyone else, writing a one-page business case before you buy ERP software forces you to answer three questions that are easy to skip when you're busy running the business day-to-day.
First, it makes you prove the problem is real. It's easy to want new software because a demo looked slick, not because your current spreadsheets, QuickBooks, or paper process are actually costing you money. Second, it stops you from buying more than you need. Small businesses are far more likely to over-buy ERP than under-buy it — a system built for a 200-person manufacturer will bury a 10-person shop in setup time and monthly fees for modules nobody will ever touch. Third, it gives you a way to know afterward whether the purchase actually worked, instead of just assuming it did because you're now used to it.
A 5-Step Business Case, Sized for a Very Small Team
The original 8-step framework works well for companies large enough to have separate people handle finance, process, IT, and risk. At your size, several of those steps collapse into one conversation. Here's the condensed version.
Step 1: Write down what's actually broken, in plain language. Not “our systems lack integration” — something concrete like “I re-enter the same order into three different spreadsheets and last month that caused us to ship the wrong quantity twice.” If you can't point to a specific, recent, recurring pain point, you're probably not ready to buy ERP yet — a better invoice template or a shared spreadsheet might solve it for free.
Step 2: Put a rough pound figure on it. You don't need a finance team for this — you need an hour and your own numbers. Estimate the hours per week you or an employee spend on manual work-arounds and multiply by what that time is worth to the business. Add in anything concrete: a late-shipment penalty, a return caused by a stock count error, a late invoice that delayed cash coming in. For a business this size, even a rough number like “this is costing us about £800–1,200 a month in wasted time and mistakes” is enough to compare against the cost of a system.
Step 3: Get a real, all-in cost for at least two options. This is the step small businesses skip most often, and it's the one that causes the most regret. Get the actual monthly cost per user, times the number of people who'll log in, plus setup or onboarding fees, plus a realistic guess at how many hours it'll take you or your team to get running (your time has a cost too, even if no invoice says so). Compare that total to what you calculated in Step 2. If the software costs more per month than the problem is costing you, that's worth knowing before you sign anything, not after.
Step 4: Decide what “good” looks like before you buy, not after. Pick two or three numbers you can actually check in three months — hours spent on manual entry, number of order errors, days to close the books at month-end, whatever matches the pain point from Step 1. Write them down now. It's very easy to feel like new software has “helped” simply because it's new; a concrete before/after number keeps you honest.
Step 5: Give yourself permission to say no, and a deadline to decide. Small businesses lose real money two ways here: buying ERP they didn't need, and delaying a decision for a year while the manual workaround quietly bleeds time every week. Set a decision date. If the numbers from Steps 2–4 don't clearly support moving forward by that date, either the answer is genuinely no for now, or you need a cheaper, smaller option than the one you were evaluating — not more time deliberating on the same option.
Cost Traps That Hit Small Businesses Specifically (and Rarely Show Up in Big-Company Guides)
Per-user pricing is the biggest one. A platform that looks affordable at £30/user/month is a very different number at 3 users than it is once you're paying for 15–20 seats — check whether the vendor has a small-business tier, a flat-fee plan, or a minimum-seat requirement before you fall in love with a feature set.
Implementation time is the second one. Larger companies can absorb a 6-month rollout because they have staff dedicated to it. If you're a 10-person company, every week spent setting up new software is a week that isn't spent running the business — so weight simplicity and fast time-to-value much more heavily than you would if you had a project team.
Module bloat is the third. Many ERP platforms are priced and packaged for companies with separate finance, inventory, HR, and manufacturing needs. At 1–25 employees, you often need two or three of those modules well, not all of them. Buying the “complete” package because it seems like better value usually means paying for capability you'll never configure.
Do You Even Need “ERP,” or Something Smaller?
This is worth asking honestly, because the term “ERP” gets used loosely. If your main pain is inventory and order accuracy, a focused inventory/order tool may solve 90% of the problem for a fraction of the cost and setup time of a full ERP suite. If your pain is mainly financial reporting and cash flow visibility, a strong accounting platform with good add-ons might be enough. True multi-module ERP (finance + inventory + operations + reporting all connected) tends to earn its cost once you're juggling enough moving parts — multiple locations, real manufacturing or assembly steps, or inventory complex enough that spreadsheets are actively causing errors, not just annoyance. If you're not there yet, it's fine — and often smarter — to solve the specific problem first.
Signs It's Actually Time to Replace What You're Using
A handful of signals matter more than any general “10-year replacement cycle” rule (which is really a mid-market and enterprise benchmark, not a small-business one). Watch for: you or an employee are manually re-keying the same data into more than one place every week; you've had a customer-facing mistake (wrong ship quantity, wrong price, missed order) traceable to a system gap rather than human error alone; you're turning down growth — more customers, a new sales channel, a second location — because your current tools can't keep up; or your current software vendor has announced an end-of-life date or stopped supporting the version you're on. One of these is worth investigating. Two or more is worth acting on.
The One-Page Version
If all of this reduces to a single artifact you actually use, it should fit on one page: the specific problem, its estimated monthly cost, the all-in monthly cost of the two leading alternatives (including your own setup time), the two or three numbers you'll check in 90 days, and the date you'll make the call. That's a business case a 5-person company can write in an afternoon — and it will catch the same bad decisions the formal version is designed to catch for a 500-person company, without any of the overhead that doesn't apply at your size.
Talk to our team