Picture a company of forty people. It runs on spreadsheets, an accounting package, a shared drive, and a few WhatsApp groups that have quietly become the operations department. It works, mostly. But something breaks most weeks, nobody can say with real confidence what is sitting on the shelf, and when the person who knows how everything actually works took two weeks off in July, everybody noticed.
This is a good problem to have. It is the problem of having grown.
So you start looking for a solution, and within about an hour of looking, every road leads to the same place. You probably need an ERP.
What That Decision Actually Means
Here is the part that rarely gets said plainly.
You are not buying an operations system. You are replacing your accounting system.
That is what an ERP is. The entire premise is a single integrated set of books that everything else posts into — inventory, purchasing, sales, payroll, all of it reconciling to one general ledger. You cannot adopt the operations half and leave the financial half alone, because the financial half is the product. The integration is the whole point, and the integration runs through the accounts.
Now think about what that means on an ordinary Tuesday in September.
Accounting is the one system in your business where being wrong does not cost you a bad afternoon. It costs you your auditor, your tax filing, your lender’s covenant reporting, and possibly payroll. It is the system your bookkeeper has known for fifteen years and can navigate half asleep. It is, by a wide margin, the thing you least want anybody touching.
And you are being asked to replace it mid-year, during growth, because you wanted better visibility on inventory.
Most companies, presented with that trade honestly, would find it terrifying. They would be right to. It is a genuinely large risk, taken in exchange for a benefit that lives somewhere else entirely.
The Cost Nobody Puts On The Quote
Even setting the accounting question aside, there is a second cost, and it is quieter.
An ERP is not software you install. It is a process model you adopt. It arrives with opinions already formed about how a quote becomes an order, how an order becomes a shipment, how a shipment becomes an invoice. Implementing it means mapping your company onto that model, and everywhere the two disagree you have two options. You can pay to bend the software, which is expensive, brittle, and makes every future upgrade your problem. Or you can bend the company.
In practice, you bend the company.
This matters more than it sounds, because of what actually sits in those gaps. The places where you do not fit the model are not defects. They are, disproportionately, your advantage.
It is the judgment that lets somebody say yes to an unusual request on a Friday afternoon. The workaround that turns a job around in three days when your competitors are quoting three weeks. The unwritten rule that everybody in the building understands: we look after that customer, whatever it takes. None of it is written down anywhere. All of it is why customers choose you over somebody larger.
And none of it survives contact with a process model, because standardising exactly that kind of variation is what the model is for.
So the real trade is this. You give up the characteristics that got you to forty people, in exchange for the predictability you would need at four hundred. Some companies genuinely need to make that trade, and they should. Many more are asked to make it a decade too early — at precisely the age when they have not finished discovering what they are, freezing into a shape somebody else chose on their behalf.
The Place Good Companies Get Stuck
Faced with all of that, the rational response is very often to do nothing.
Too big to keep running the way you are. Too small to seriously consider SAP, or NetSuite, or the year of consulting effort required to get there. So you stay where you are, add another spreadsheet, and hire another person to hold the gaps together.
That is an uncomfortable place to live, and a great many capable companies live there for years. Not because they cannot afford software, and not because they do not understand their own problems. Because the only thing on offer asked them to bet the business.
Separating The Books From The Work
The two options presented are rarely the only two available.
Look carefully at what you actually wanted on the day you started looking. Knowing what is on the shelf and what is on order. Knowing why something is needed and when it is genuinely needed by. Knowing who picked it, who approved it, what it cost, and where it went. Being able to answer a customer’s question without making three phone calls first.
Almost none of that is accounting. It is operations. And your accounting system was never going to tell you any of it — which is not a criticism of your accounting system. Telling you what is on the shelf is simply not what it is for.
Once you separate those two concerns, the frightening part of the decision disappears entirely. Your books stay exactly where they are. Your bookkeeper carries on doing precisely what they do today, in the software they already know, with the same controls and the same audit trail they have always had. Nothing about your financial reporting changes, because nothing about your financial system changes.
You simply stop guessing about everything else.
What We Do, And What We Don’t
This is where Opterion-IT sits, and the boundary is worth stating explicitly rather than leaving somebody to discover it later.
We do not do your accounting. We do not want to. Your general ledger is not a place we belong, and the day we claimed otherwise we would be asking you to take on exactly the risk that stopped you in the first place.
What we do is run the operation. Quotes and orders, from first draft through to delivery. Products, kits and suppliers. Purchasing that tells you not merely what is running low, but why it is needed and when it is needed by. Receiving, stock counts, adjustments, picking and shipping — with every movement of stock traceable back to the event that caused it. It is built for organisations of roughly twenty to two hundred and fifty people, where the person managing inventory is also managing three other things and has no appetite for a year-long implementation.
Your bookkeeper keeps the books. We keep the business honest about what it is actually doing.
If you have been stuck in that no-man’s-land for a while, it is worth asking yourself honestly which of the three things actually held you back — the price, the disruption, or the accounting. In our experience it is almost always the third, and almost nobody says it out loud.
Purchasing is one of the clearest examples of operational work that never needed to touch your general ledger — knowing what to buy, why, and when it is genuinely needed. See how orders drive purchasing automatically →
Keep reading
- Opterion-IT vs. Odoo: Built for Gears, or Built for People?
Odoo is a serious ERP platform. But when your organization runs on relationships rather than production runs, its feature list becomes an obstacle course.
- Your Quotes Already Know What You Need to Buy
When a quote is accepted, most businesses start a second, disconnected process to work out what to buy. Here is what changes when they share a system.