ERP comparisons, including the ones we are not in

How to read the positioning map

The chart above plots each product by the size of company it genuinely serves against how much work it takes to get live. Both axes are our assessment, drawn from implementation engagements rather than from vendor materials, and the method is published.

The useful thing about plotting it this way is that it makes the actual trade-off visible. Capability and implementation burden are strongly correlated across this category — the systems that handle a $200M multinational are the systems that take nine months to deploy. That correlation is not an accident or a failure; it reflects genuine configurability that a complex business needs.

The interesting territory is the gap below the diagonal: mid-market capability without mid-market implementation burden. That is the space we are trying to occupy, and it is fair to be sceptical about whether any product can hold it. The way we try is by not requiring you to replace your ledger to get most of the value, which moves the effort axis without pretending the capability axis is easier than it is.

What the map does not show

• Industry fit. A manufacturer and an agency at the same revenue have entirely different requirements, and a two-axis chart cannot express that. Use the industry guides for it.
• Quality of the partner you get. For NetSuite, Acumatica, Sage, and Dynamics this is often more predictive of outcome than the software. The same product implemented by two firms produces two different experiences.
• Total cost. Effort correlates with cost but is not the same thing, particularly where licensing is per-seat and headcount is growing. The TCO tool models that properly.
• Where a product is heading. Every vendor here is shipping AI features and several are moving. The map is reviewed quarterly and dated for that reason.