Why this matters. Searching "ERP for small companies" returns licence prices — not who decides on the system, runs it, and replaces it. The segment here covers firms of one to twenty staff with no IT function, where the owner-operator carries selection, budget and operations alone. Selection logic, budget discipline and partner dependency differ at the root from the Mittelstand — Germany funds adoption through go-digital and the Mittelstand-Digital network.
When this view fits — and when it does not
This view fits when:
-
Your headcount is below twenty and no internal IT role is filled;
-
The owner-operator carries selection, budget and operations alone;
-
Your seven-year budget stays under half a million euros.
This view does not fit when:
-
You have an internal IT function with named accountability — that is the small Mittelstand and follows different logic;
-
You operate in a regulated industry with its own validation obligations;
-
A group-mandated tenant system is already in place.
The four differentiation criteria
-
Partner matters more than vendor: Without an internal architect you live with the implementation partner's decisions. Their sector experience and data-migration practice outweigh the logo on the licence. Methodology comes before the module.
-
Real TCO, not list price: Implementation costs one to three times the licence sum across seven years. Master-data clean-up and training are systematically understated in comparison tables.
-
Cloud-first with a lock-in clause: Subscription ERPs lower the entry barrier but raise the switching cost. Export formats, data sovereignty and notice periods belong in the contract before signature.
-
Methodology before feature list: Mapping three core decisions cleanly — order release, purchase approval, month-end close — beats one hundred checkboxes on a specification sheet.
A common mistake and how to avoid it
A trades business in North Rhine-Westphalia, twelve staff, picked a cloud ERP on licence price and demo impression. Eighteen months later the switch was unavoidable: the implementation partner had wound down the business, the master data sat in a proprietary format, and no successor partner would take it on. The owner carried selection, contract and consequences alone.
In small firms the owner-operator usually decides without an internal challenger. That is exactly where an external second opinion belongs — before contract signature, not after.
What to do next
-
Name three daily decisions the ERP must carry.
-
Call the implementation partner's references — not the vendor's — and ask about projects in your size class.
-
Have the draft contract reviewed for exit clauses, export formats and data sovereignty.
We review your proposal as an independent second opinion — before you sign.
FAQ
At around twenty staff and a named IT role. Below that, the owner-operator carries the decision alone; above it, a steering committee shapes the choice. The two worlds follow different selection logic, budget discipline and partner dependency.
Across seven years, implementation costs one to three times the licence sum. Master-data clean-up and training add to the bill. Comparing list price alone misses about two thirds of total cost of ownership.
Cloud is usually the right choice on entry cost and automatic updates. The trade-off is vendor lock-in. Export formats, data sovereignty and termination clauses belong in the contract before signature.
