Why owners say they hate their ERP — the real complaints, and what actually fixes them

Spend an evening reading how business owners talk about their ERP when no vendor is in the room — the long threads on r/ERP and r/Netsuite, the post-mortems on LinkedIn, the "is it just me?" posts on r/smallbusiness — and the striking thing is how little the complaints vary. Different industries, different systems, different countries, the same handful of grievances, almost word for word.

That consistency is the tell. It means the problem usually isn't your ERP, or your team, or your rollout. It's a design the whole category inherited: software built to remember the business and leave the running to you. Below are the complaints that surface again and again, in owners' own words, and the specific thing that actually fixes each — because naming the pain is easy, and most "ERP is broken" takes stop there.

1. "It takes five screens to do one simple thing"

In an r/ERP thread titled, simply, "It seems like everyone hates their ERP — what is the biggest pain?", the most resonant answer described the daily reality as having to "open many CRUD screens and jump back and forth, only to maintain a simple set of data records." Anyone who has lived in a big system recognises it instantly. It is the screen-hopping tax, and it is the complaint underneath most of the others.

What fixes it: not "better training" — fewer screens. When marketing, sales, the storefront, operations, inventory and the books share one record, the data is captured once at the source and there is nothing to jump between. The work that used to take five screens takes a sentence to an assistant that can actually act on it.

2. "We re-key the same data into a second system, just to be sure"

The second-most-common grievance is the spreadsheet kept alongside the ERP — the parallel copy owners maintain because the system of record never quite feels like one. Every duplicated keystroke is a chance to disagree with itself, and month-end becomes a reconciliation exercise between things that should never have been separate.

What fixes it: a single shared record, so a sale at the counter, an order placed online, the stock it draws down and the entry in the accounts are the same event — not five copies you reconcile later. The opposite of a disconnected stack is not a bigger stack with better connectors; it is one place where nothing was ever separate to begin with.

3. "If you can't adapt the ERP, you become the integration layer"

The same r/ERP thread produced the sharpest line of all: "if you can't adapt your ERP, you take on more manual work to fit your system." When the software can't bend to how your trade actually works, the gap doesn't disappear — a person absorbs it by hand, forever. The business ends up serving the software.

What fixes it: a system that arrives shaped for your trade rather than waiting to be configured into existence. A print shop, a hotel, a parts counter and a salon each get the language, the workflow and the defaults of that trade out of the box — as configuration the vendor owns and carries forward, not bespoke code you bolt on and babysit.

4. "We pay enterprise money and hit a wall on something basic"

On r/Netsuite, a recurring shock from owners moving up from QuickBooks is discovering the new, far more expensive system "lacks what seems like basic functionality" — bank reconciliation is the one named most — and that the headline price is really price plus the implementation (or the partner) needed to make it behave. As one put it, the "significant cost difference" buys you a ceiling you have to build the room under yourself.

What fixes it: opinionated defaults shipped, not sold as a configuration project. The basics a small business needs every day should work on day one, without a statement of work — and you should be live in about a week, not a quarter.

5. "The bill grows every time we hire"

Eric Kimberling, who has written more ERP post-mortems than almost anyone, frames the costliest small-business mistake as assuming the per-seat and per-module pricing stays put. You scope the project at today's headcount, then every hire and every add-on quietly re-prices the thing, and the "SME-friendly" quote isn't SME-friendly two years in.

What fixes it: pricing the outcome — the whole business running — rather than the seats. Unlimited users and the AI agent included, no per-seat licence and no AI add-on, so growth doesn't carry a software tax.

6. "The customisation that finally made it usable broke on the next upgrade"

Writing about why ERP customisation promises collapse after go-live, consultant Luke Vickery captures the trap exactly: customisation choices "that felt small turned out very expensive later." The bespoke work that made the system fit is also the thing that breaks on the next update, that nobody remembers the reason for, and that quietly becomes tech debt wearing a nicer name.

What fixes it: the distinction between configuration and customisation. Config that the vendor owns survives upgrades untouched; bespoke code bolted on to fit your process does not. If a "flexibility" feature can't survive an update on its own, it isn't flexibility — it's a liability you'll pay for twice.

The number behind the venting

None of this is fringe complaining. Large surveys and consultancies have long pegged ERP-project disappointment at roughly two-thirds — and usually not because the software was bad, but because the implementation, the customisation, and the change it forced on people were heavier than anyone budgeted for. The smaller the business, the worse the maths: the tools that could run your whole operation quietly assumed you had a team to run the tools. So most owners did the rational thing and stitched together a stack instead.

So what's the actual alternative?

Honestly, it depends on what you're escaping. If you genuinely need the ceiling of a large enterprise suite — multi-entity consolidation at scale, a global supply chain, deep manufacturing — the answer may still be NetSuite, Dynamics or SAP, configured properly. We'd tell you that to your face; pitching a small business a system it doesn't need is how the whole category earned this reputation.

But if the complaints above are your complaints — too many screens, re-keying, a system that won't bend, basics missing at a premium price, a bill that punishes growth — then the fix isn't a better filing cabinet. It is one joined-up system that runs the business and asks before it commits, shaped for your trade, with the AI and the users included. That is the bet PeakSpitz is built on. If you want to see how it stacks up against what you're on now, the honest comparisons and the migration page (we treat moving as "restore from a backup," not a big-bang cutover) are the most useful places to start.

---

Disclosure: PeakSpitz is an AI business management platform for small and mid-sized businesses, so we're biased — we built our whole pitch around removing exactly the friction above. The complaints quoted here are real ones from public threads on r/ERP, r/Netsuite and LinkedIn; we've linked the communities rather than individual posters. If you're weighing your options, our comparisons, migration guides and glossary are written to be useful even if you never become a customer.