Every ERP conversation starts in the same place: someone has outgrown spreadsheets and wants to know whether to buy a product or build one. The honest answer depends on a question most vendors will not ask you.
Is your process an advantage or a habit?
Off-the-shelf ERP encodes one way of working. If your process differs, you either customise the package until it is fragile and expensive to upgrade, or you change how you work to match it.
Changing how you work is not automatically bad. A lot of business process is accident — it exists because someone set it up that way once and nobody revisited it. If that describes your workflow, adopting a well-designed package and dropping your habits is cheaper and faster than rebuilding them in custom code.
But if your process is genuinely how you compete — a pricing model nobody else runs, a fulfilment approach that is faster than the industry norm — forcing it into a package throws away the thing that makes you money.
The costs people forget
Licence fees are visible. These are the ones that surprise people:
- Customisation debt. Every modification to a packaged system has to be revalidated at each upgrade. Heavily customised installations quietly stop upgrading.
- Integration. Whatever you buy has to talk to what you already run. That work is rarely in the quote.
- Data migration. Almost always underestimated, and almost always where a rollout slips.
- Training and adoption. Software that people work around has failed regardless of what it cost.
A practical test
List your top ten workflows. For each, ask whether a competitor doing it your way would gain anything. If eight are generic, buy a package. If four or more are genuinely yours, custom is likely worth it — and a hybrid, where you buy finance and build the operational core, is often the right answer.
Whichever way it goes, insist on owning the data model and having an export path. The system you choose today will not be the one you run in ten years.