The short answer: when managing the data costs more than the work itself
Most small businesses don't need an ERP system on day one. Excel, a shared drive, and a couple of SaaS tools will carry you surprisingly far. But there's a tipping point — typically somewhere between 5 and 20 employees — where disconnected tools quietly start costing more than a real system would.
Here's how to recognize that point, how to choose between off-the-shelf and custom, and what realistic budgets look like.
Five symptoms you've outgrown Excel
- The same data lives in three places. Client details in a spreadsheet, order status in email threads, payments in the accounting tool — and none of them agree.
- Double entry is routine. Someone retypes the same information into invoices, contracts, and reports. Every retype is a chance for an error.
- Nobody has a real-time picture. Answering "how are we doing this month?" means collecting numbers from three people and stitching them together — and the answer is outdated before it's ready.
- Errors reach clients. Wrong amounts on invoices, wrong names in contracts, missed follow-ups. In most cases these aren't people problems — they're process problems.
- The business depends on memory. If one key person left for two weeks, orders would stall because nobody else knows where things stand.
If three or more of these sound familiar, the question isn't whether to move beyond spreadsheets — it's what to move to.
Off-the-shelf ERP vs. custom: the honest comparison
When off-the-shelf wins
If your processes are standard — invoicing, inventory, basic accounting, HR records — an off-the-shelf ERP is usually the right call. It's faster to deploy, cheaper upfront, and battle-tested by thousands of companies.
The trade-offs: you pay a subscription forever, you adapt your processes to the software rather than the other way around, and heavy customization through consultants can quietly cost more than building custom would have.
When custom wins
Custom makes sense when your workflow is your competitive advantage — when the way you operate is something no off-the-shelf tool actually models.
A real example: a Bulgarian real estate agency ran its entire operation on spreadsheets, phone notes, and messaging groups. Preparing the paperwork for one deal meant manually copying data into six Word templates — roughly 30 minutes per transaction, with real error risk. We built them a custom ERP with automated client-property matching and one-click document generation. Contract preparation dropped from 30 minutes to under 60 seconds, and manual transcription errors disappeared entirely.
No packaged real estate product modeled their matching logic or their document flow. That's exactly the situation where custom pays for itself.
The middle path most businesses miss
You don't have to pick one approach for everything. A common pattern: buy standard software for standard functions and build custom only for the part that differentiates you. Our own product Finsense exists for that reason — SMBs use it for expense tracking, invoicing, payroll, and cash flow forecasting across 35+ currencies, while their industry-specific operations run on whatever fits best.
Realistic budgets
Off-the-shelf ERP: typically €20–€150 per user per month, plus implementation and setup that often lands between €3,000 and €20,000 for a small business. Budget extra for training and the occasional consultant.
Custom operational system: most small-business systems we scope fall between €25,000 and €80,000, delivered in 2–5 months. That's a real investment — but there's no per-user fee, no forced upgrades, and the system matches your process exactly.
The honest math: over five years, a 15-person team on an €80/user/month ERP spends around €72,000 in subscriptions alone — before implementation and customization. Custom isn't automatically cheaper, but the gap is rarely as wide as the upfront number suggests.
The migration path (don't skip steps)
- Map your processes first. Write down how orders, documents, and money actually flow today — including the workarounds.
- Clean your data before moving it. Migrating a messy spreadsheet gives you a messy system.
- Phase the rollout. Start with the module that hurts most — usually documents or client tracking — prove it works, then expand.
- Run in parallel briefly. Keep the old spreadsheet alive for a few weeks as a safety net, then retire it deliberately.
- Assign an owner. One person accountable for data quality inside the new system.
Our rule of thumb
If a standard tool covers 80% or more of what you do, buy it. If your core workflow is unique — the thing clients choose you for — build that part, and only that part, custom. Either way, start from the process, not from the software.
We build custom operational systems for exactly these situations — and we'll tell you honestly when an off-the-shelf tool is the better answer.
Not sure which side of the line your business is on? Get in touch — we'll map your processes in a free 30-minute call.