How to choose an ERP for a small business

Here’s a sign worth paying attention to. You bought software to run the business, or you’re still running it on QuickBooks and a stack of spreadsheets, and yet every department has its own secret spreadsheet on the side. The one they actually trust. The one that has the real numbers. When that’s happening across the company, you’ve usually outgrown what you have, and someone has probably said the word ERP.

Before you go shopping, let’s talk about what an ERP will and won’t do, because the single most expensive misunderstanding starts right here.

An ERP will not fix your broken processes

This is the thing we wish more people heard before they signed anything. An ERP is not magic. If a process is a mess today, done by hand or held together by one person’s memory, it will be a mess inside the new system too. Software doesn’t clean up a broken workflow. It just runs it faster and makes the mess more expensive.

So the real work of an ERP project isn’t the software. It’s understanding how your business actually runs first, deciding what should change, and then choosing a system that fits the good parts and helps you fix the bad ones. Skip that, and you’ve paid a lot of money to automate your problems.

With that said, here’s what an ERP actually is, and when it’s worth it.

What an ERP actually is, in plain words

An ERP is software that manages all the different processes you run to operate your business, in one place. Sales, purchasing, inventory, invoicing, payroll, the works.

Two things happen when it’s all in one system instead of scattered across separate tools and spreadsheets.

First, you finally see what things cost. Every process in your business has a financial side to it. When they all live in one system, you can see what each part actually costs you and where you could do better. That’s hard to do when the numbers are spread across five different tools and nobody’s are quite the same.

Second, everyone can see across the business. When purchasing, sales, and the front office are all working in the same system, one department can see what another is doing instead of guessing. That cross-department visibility is where a lot of the real value is, better cooperation, fewer surprises, less work falling through the cracks between teams.

How to know you’re actually ready

There’s a simple tell, and you’ll recognize it when you hear it. As a business grows, people across teams start saying some version of the same thing:

“I wasn’t aware.” “I didn’t know.” “I forgot.” “How did we miss that?”

When you’re hearing that regularly, from good people who are trying, it usually isn’t a people problem. It’s an information problem. The business has gotten big enough that no one can hold the whole picture in their head or in a spreadsheet anymore, and things are falling into the gaps. That’s the moment an ERP starts to earn its cost.

The three things that actually decide it

Once you’re looking, it’s easy to get lost in feature lists. Here’s what actually matters, in order.

Can it show you the data you need? This is the whole point. Sit down and get specific about the questions you can’t easily answer today, what’s my true cost per job, which customers are actually profitable, what’s sitting in inventory. Then make each system you’re considering show you exactly that. If it can’t surface the numbers you need to run the business, nothing else about it matters.

Will it fit how you work, and can you adapt where it won’t? Every system makes assumptions about how a business runs. Some of those will match how you already do things well; some won’t. Where the software’s way is better than yours, you want to adopt it. Where your way is better, you want the system to bend. The balance between those two is the hardest and most important judgment in the whole project. Which brings up the trap.

Who’s on your side of the table? More on this below, because it’s the factor almost nobody weighs and the one that decides whether the project works.

Cost and the look and feel of the system matter too, of course. A system your team finds clunky is a system they’ll avoid, and price obviously has to fit. But those come after the three above. A cheap, good-looking ERP that can’t show you your numbers is still the wrong ERP.

The customization trap: too much and too little

Here’s where projects quietly go wrong, and it cuts both ways.

Customize too much, and you’ve built a fragile, one-of-a-kind system that’s hard to update, hard to support, and expensive to change. Every upgrade becomes a project. You’ve painted yourself into a corner.

Customize too little, and the system doesn’t fit how you actually work, so people quietly go back to their spreadsheets, and you’re right back where you started, except now you’re also paying for an ERP nobody fully uses.

The right amount is somewhere in between, and finding it takes someone who deeply understands both how your business works and what the software can reasonably do. That someone is the most important person in the whole project.

The champion: the person who makes or breaks it

Implementation is a huge part of an ERP project. But the bigger factor is having someone on your side, inside your business, who truly understands how every department gets things done today.

That person, the champion, does the job the software vendor can’t. They know which of your current processes are working well and should be protected, and which are broken and should be fixed. When the system is good enough to keep your process as-is, they recognize it. When your process is the problem, they know how to adapt your team to the better way the software suggests. Without that person, you’re either forcing expensive customizations to preserve bad habits, or letting a vendor who doesn’t understand your business make decisions they’re not equipped to make.

A great implementation partner matters. A great champion on your side matters more.

The honest part

Two things are true about every ERP project, and you should hear them plainly.

It will take longer and cost more than the quote. This is almost never because anyone lied to you. Estimating an ERP implementation is genuinely, deeply hard. So much of the timeline depends on you, getting the partner your data, holding the internal meetings, answering the questions, making the decisions. The implementation partner only controls their half. It’s not like a construction project with a fixed scope and a crew that shows up; a huge amount is out of their hands and in yours. Plan for more time and more money than the number on the proposal. (You’re not alone in this: one 2026 industry report found more than a quarter of ERP projects went over budget, most often because of technology the business hadn’t planned for.)

And your team will complain. No matter what you pick, no matter how good it is, people don’t love change to the tools they use every day. That’s normal, it’s not a sign you chose wrong, and it passes. Knowing it’s coming makes it easier to lead through.

None of this is a reason not to do it. It’s a reason to go in with your eyes open, which is exactly what makes these projects succeed.

A few of the common systems, and how we think about them

We’re not going to hand you a ranked list, because the right ERP depends entirely on your business. But here’s how we tend to think about a few of the ones you’ll run into. Treat this as our opinion, not gospel.

Acumatica is what we lean toward for a lot of small and mid-sized businesses. It was built for the cloud from the start, it comes in a range of editions tuned to different industries, and it doesn’t charge per user, so cost is based on how much you use it, not how many people log in. That’s a real advantage if you have a lot of occasional or light users. It’s highly customizable, has genuinely powerful built-in reporting, and has a strong, active community behind it.

NetSuite is worth a look if e-commerce is central to your business; its online-selling capabilities are strong.

Salesforce is, in our view, not a full ERP, but it’s a powerful customer-management system, and with add-ons it can handle basic inventory, quoting, and more. It’s often run alongside a real ERP rather than as one. If your world revolves around managing customer relationships and sales, it’s worth understanding where it fits.

Odoo is open-source, very inexpensive, and endlessly customizable, you can shape it into almost anything. The catch is support: there isn’t much hand-holding, so you’re either doing a lot yourself or paying someone to. For a technically comfortable business on a tight budget, it can be a great fit. For most, the do-it-yourself burden is the thing to weigh.

The point isn’t to pick from this list. It’s to go into the conversation knowing that these systems are genuinely different from each other, and the right one is the one that fits how your business actually works.