"ERP" gets used as a buzzword long before most growing businesses actually need one — and used vaguely enough that it is worth defining plainly before deciding whether you need it at all.
What ERP actually means
Enterprise Resource Planning software is, at its core, one system that departments share instead of each running its own tool: inventory knows what finance knows, HR knows what operations knows, and a stock movement, an invoice and a payroll entry all trace back to the same underlying data instead of three spreadsheets that quietly disagree. The "enterprise" in the name is misleading — the pattern helps a 20-person company just as much as a 2,000-person one, once the spreadsheets start fighting each other.
The signs you actually need one
Not "we have inventory" or "we have an HR system" — most businesses have both and are fine. The real signs: staff manually re-entering the same data in two or three systems every week; month-end close taking days because nobody trusts the numbers until they're reconciled by hand; different departments reporting different totals for what should be the same figure; or a founder who is still the only person who can explain how the numbers actually connect.
Off-the-shelf vs custom: the honest framework
Off-the-shelf platforms (Odoo, NetSuite, SAP Business One, and similar) are the right starting point for most businesses — mature, well-supported, and genuinely fast to deploy. The case for custom ERP software shows up specifically when you're customizing an off-the-shelf suite so extensively that you're paying enterprise license fees for what has functionally become bespoke software anyway, or when your workflow is genuinely unusual enough that no configuration of a generic tool fits it without constant workarounds.
What a first ERP module actually looks like
Nobody sane builds all of finance, HR, inventory and procurement at once. The businesses that succeed with ERP — whether custom or off-the-shelf — start with the single module causing the most pain today, usually inventory or finance, prove it in production for a few months, then expand. A data model built correctly from day one makes that expansion straightforward later; one bolted together module by module without a plan makes it painful.
If you're weighing this decision for your own business, tell us how your departments currently share data — often in fifteen minutes we can tell you honestly whether you need a full platform, one well-built module, or nothing more than fixing how your current tools talk to each other.