If you bought an ERP tomorrow, which parts of it would you actually use?

Most growing businesses reach a point where someone says “we need a proper system.” Usually that means an ERP like Odoo, NetSuite or SAP Business One. It also means a project that touches accounting, inventory, purchasing, sales and HR all at once. For a business of 20 or 50 people, that's a big change to make for what are often 3 specific problems.

“Most SMBs don't need an ERP. They need the 3 parts of one that hurt right now.”

The part I pay attention to

When a business tells me it needs an ERP, I ask what went wrong last month. The answer is rarely “our general ledger isn't good enough.” It's closer to this. We sold stock we didn't have. Purchase orders don't match what arrived. Nobody can see a job's cost until it's finished. Those are inventory, procurement and job-costing problems. The accounting platform is usually fine.

WHAT'S ACTUALLY HAPPENING
The accounting system works
Stock, purchasing and jobs live in spreadsheets around it
An ERP would replace all of it to fix the middle

What I'd do before buying an ERP

Keep the accounting platform you already trust. Fix the operations around it first:

Then connect those to accounting so nothing gets retyped.

That's the part of an ERP you'd actually use, without migrating your books. We build it on AnyDB because we can start with one area and add the next when it's needed. If you still genuinely need a full ERP after that, you'll know exactly why, and you'll go in with clean data.

Fix the parts that hurt. Keep the parts that work.

Where AI fits

The same goes for AI. You don't need an AI strategy, or an AI version of an ERP. You need AI doing one of the parts that hurt, on records you trust, with someone checking the result.

Give AI its first job →

Our CFO still handles full sets of accounts for local SMBs, and would rather you didn't replace a working ledger to fix a stock problem. Show us the workaround →