What an ERP actually has to do for a 40-person business
Most ERP evaluations start with a feature list nobody reads twice. The shorter test — can one person answer what we owe, what we are owed and what is on the floor, without opening a spreadsheet — predicts far more.
Every ERP demo we have sat through opens the same way: a grid of two hundred features, most of which exist because some other customer asked for them. It is an impressive slide and a useless one. A forty-person fabricator does not fail at ERP because a module was missing. They fail because the system asked for more discipline than the shop floor had to give, and within four months everyone is back in Excel with the software running as an expensive filing cabinet.
The three-question test
Before the feature list, ask whether one person, at 9am on a Monday, can answer these without opening a spreadsheet:
- What do we owe, and when is it due?
- What are we owed, and how old is it?
- What is physically in the racks right now, and what is committed against it?
If all three live in one system and update themselves as work happens, you have an ERP. If any of them needs someone to reconcile two screens, you have a reporting tool with an ERP's price tag.
Masters kept once
The most common failure is duplicated masters. An item exists under three codes because sales, stores and accounts each created their own. Once that happens every total is arguable, and an arguable total is worse than no total — it costs a meeting to resolve rather than a moment to read.
An ERP earns its name by owning the masters: items, parties, tax rates, locations, ledgers. Billing, inventory, dispatch and payroll then read from them instead of keeping private copies. That is the whole structural claim, and it is why we treat ERP as the spine the other modules hang off rather than as one product among eight.
The cost that is not on the quote
Per-seat licensing quietly prices your growth. The tenth user costs what the second did, so the natural response is to share logins — and the moment two people share a login, the audit trail that justified the purchase stops being evidence of anything.
The system that gets used is the one that costs nothing extra to give to the next person who needs it.
That is the reasoning behind a one-time build fee and a flat access cycle rather than a seat count. It is not generosity; it is the only pricing shape that does not fight the adoption you are trying to buy.
What to do next
Write down your three answers as they stand today, and how long each took to produce. That number is your baseline, and it is the only figure worth comparing any proposal against.
Tell us how your business actually runs.
One conversation about what you count, who touches it and where it breaks. No pitch deck, no discovery fee.