When you've outgrown QuickBooks, every ERP vendor promises to be your perfect next step. But most of them aren't actually built for mid-market companies like yours. Here's how to tell if a system is truly right-sized for your business.

The Questions That Matter

After years of helping companies move from legacy systems to modern ERPs, I've learned which questions actually predict success. Not the ones vendors want you to ask. The ones that reveal whether you'll still be happy with this choice three years from now.

What to Ask

"Can you show me how to add a custom field to an order?"
Custom fields and custom reports are part of what I do. But a simple field shouldn't take weeks or cost a fortune.

"What happens when we need a report that doesn't exist yet?"
Custom reports are part of any good implementation. They get scoped and quoted as part of the project. The question is whether the system makes that reasonable or whether every new report becomes a major expense.

"How many of your clients our size use all the modules we're buying?"
Nobody admits they're only using 30% of what they bought. But most are.

"What's the real monthly cost including hosting, support, and the add-ons we'll actually need?"
The quote is never the real number. Budget for 40% more. And if you're getting a steep discount for years one and two, ask what the price looks like in year three. That's the number you'll be living with.

"Can my warehouse manager learn this in a week?"
If the answer involves "comprehensive training programs," your people will be in Excel within a month.

"When something breaks at month-end, who do I call and how fast will they answer?"
Support matters more than features. Bad support ruins good software.

"Which of these features do you think we won't use?"
An honest vendor will tell you. A salesperson will insist you need everything.

The Bottom Line

The right next step should feel like relief, not a bigger version of the problem you already have.

These questions have saved my clients from expensive mistakes. Use them.

Need help figuring out if your current system is right-sized, or what to look for next? Let's talk. A 45-minute conversation can save you years of frustration.

~Audrey Quick, Founder of AGS Enterprises Consulting LLC

Audrey has spent 35+ years helping businesses manage ERP implementations and accounting software transitions.  If you're evaluating your options, we can book a free 15-minute call

.A few months ago, I was working with a client and noticed something odd. Their AR person was out on leave, and the person filling in was creating invoices in Microsoft Word.

Not exporting from the system. Creating them from scratch. In Word.

She'd type up the invoice, email it to the customer, then manually key the details into the AR module afterward. When I asked why, she shrugged. "I wasn't really trained on the invoicing side. This was easier."

The system had a perfectly functional invoicing module. But she didn't know it well enough to trust it, so she built her own process. Two steps instead of one. Double the effort. No one flagged it because the invoices still went out.

That's the thing about systems that "still work." Orders get processed. Invoices go out. Month-end happens eventually. Nobody's in crisis.

But somewhere in the operation, a warehouse manager has a spreadsheet open next to the ERP. A CSR is calling the warehouse to answer a question a customer asked ten minutes ago. Finance is running a month-end close that takes nine days.

The system isn't broken. It's just not doing the job anymore.

This post isn't about whether your software is technically functional. It's about the hidden system costs. Whether it's quietly costing you money, time, and people, and whether those costs have just become normal. I've talked about this before. It's a pattern I keep seeing.

The Workaround Problem

The most common pattern we see: the system technically works because the people around it have figured out how to compensate for what it can't do.

• Finance opens QuickBooks plus ten to fifteen spreadsheets every morning just to have a usable picture of the business
• The warehouse manager keeps a parallel inventory sheet because the system numbers can't be trusted in real time
• Customer service reps maintain their own tracking files because the ERP doesn't show them what they need
• Purchasing exports to Excel every morning to calculate reorder needs because the system's forecasting isn't reliable

The organizational tell is when the workarounds get names. "The Tuesday export." "Karen's spreadsheet." "The master pricing file." When informal processes become standard operating procedure with their own nicknames, the workaround is the system.

Here's a story that still gets me.

I've worked with one client for decades. Took them from paper records to DOS accounting to their current system. Over the years, I trained a lot of their staff. But one director preferred to keep things close to the vest. She didn't like to let on when she didn't know something.

When she retired, she trained her replacement on what she knew. Which didn't include the system's financial reporting capabilities. He trained his replacement the same way. For nine years, quarterly financial reports were built by exporting data and manually creating spreadsheets. Ten to fifteen hours a quarter, minimum.

The cycle broke when a new director insisted I train her staff from scratch. During that training, I asked who handled the financial reports. Her second-in-command said the director did, manually, every quarter.

They didn't even know to ask if the system could do it.

Turned out it could. The whole time. Nine years of manual work, not because the system couldn't handle it, but because the knowledge never got passed down.

The question we ask when we first talk to a company: when a new employee asks "why do we do it this way," what's the honest answer?

What "Reports Take Too Long" Actually Means

A month-end close that takes five to ten days is common in distribution companies running legacy systems. Finance works late. "Close week" becomes a department-wide emergency. Data gets pulled from multiple places, exported to Excel, reconciled manually, and even after all that, the numbers aren't fully trusted.

I've seen companies get this down to three or four days with the right systems. The gap between a spreadsheet-heavy manual process and a system where the data is clean and centralized can be that stark.

The same problem shows up in smaller ways every day. A CFO who can't answer "what's our margin by product line?" without a half-day of pulling. A warehouse manager who spends two hours every morning generating pick lists manually. That's over five hundred hours a year on a single preventable task. An owner who gets the question "what's in stock at the other location?" and has to make a phone call to find out.

When reporting is a project rather than a conversation, decisions either slow down or get made without the data.

The Roles That Notice First

Different people in a distribution company feel the limits of the system differently.

The warehouse manager usually notices first. The inventory discrepancies. The time spent on manual counts. The gap between what the system shows and what's actually on the shelf. They stop trusting the numbers.

The controller or CFO notices it at month-end. They can pull accurate top-line numbers, but a margin breakdown by product line, a customer profitability report, an inventory valuation by location, those require a process, not a click.

The owner is often last. They see it when growth stalls, when headcount keeps increasing without a revenue bump, or when a customer complaint escalates past the ops team for the first time.

The one we don't talk about enough: customer service. A CSR who can't answer "when does my order ship?" without calling the warehouse is doing two jobs, one of which the system should do for them. High turnover in that role is often a systems symptom dressed up as a hiring problem. According to SHRM (Society for Human Resource Management), replacing a single employee typically costs between 50% to 200%  of their annual salary.

There's another pattern I see, mostly with manufacturers. The accounting system handles the P&L, tracks customers, maybe even sales commissions. But the heavy lifting, inventory, production costs, profit by order, lives somewhere else. A separate inventory package. Spreadsheets. The order entry handles the sale. Payables tracks the supplier bills. Payroll tracks labor. But none of it connects at the order level.

Big picture, yes, everything makes it to the ledger eventually. Micro picture? That's where the spreadsheets live. And that's where the reconciling happens, quietly, in the background, by whoever drew the short straw.

What It's Actually Costing

This is the section that tends to surprise people, because the current system feels free. It's paid for. The staff knows it. No invoice arrives every month that says "cost of workarounds."

But the costs are real. Here's how we'd run the numbers for a typical client.

A distributor with $1M in inventory carrying 15 percent excess stock due to poor visibility has $150,000 in capital sitting idle, not generating returns, accumulating holding costs. For a $10M distributor, inventory errors alone, stockouts, overstock, emergency orders, and expedited shipping, can run $100,000 to $300,000 annually.

Manual workarounds have a payroll cost, too. Thirty minutes per person per day across a 15-person team is roughly 1,950 hours a year. At a loaded cost of $40 per hour, that's $78,000 annually in labor performing tasks a modern system automates.

And then there are the harder-to-quantify costs: the customer you couldn't promise accurate stock to because you didn't trust the inventory numbers. The supplier quote you couldn't pull without making them wait. The contract you hesitated to take because you weren't sure the systems could handle the volume.

These hidden system costs don't send an invoice. But they're billing you anyway.

The Objection We Hear Most

The most common reason companies stay: "We're not ready."

There's always a reason. Q4 is coming. A new hire is starting. It'll be calmer next year.

It's rarely calmer next year. Distribution is operationally intense by design. The companies that wait for a clean window are often still waiting, while the cost of the current system keeps compounding quietly.

The other common one: "It still works." And that's true in the narrowest sense. Orders get processed. Invoices go out. But "still works" and "working well" are different things. When the system works only because the people around it have built a workaround infrastructure to compensate for what it can't do, the real question is: how long do you want to maintain that?

And then there's the honest one: "We can't spend the money right now."

Cash flow is real. I have a client right now who knows their system needs to change, but they're in a crunch. That's not an excuse, it's a constraint. I'm not here to tell anyone to spend money they don't have. But if cash flow is the barrier, it's worth exploring rent-to-own options. It's slightly more expensive at the end of the day, but it lets you delay the large purchase until the cash is there.

Seasonality is real too. If your business has a quiet stretch, that's a natural window for go-live. A good implementation plan can work around your calendar, not against it.

If several of these hidden system costs sound familiar, it might be worth a conversation.

Not a sales call. A practical look at what's actually happening in your operation and whether a change makes sense. That's what I do.

~Audrey Quick, Founder of AGS Enterprises Consulting LLC

Audrey has spent 35+ years helping businesses manage ERP implementations and accounting software transitions.  If you're evaluating your options, we can book a free 15-minute call 

Most companies imagine  ERP go-live day as a stressful, all-hands scramble. Systems crashing. Panic in the conference room. Late nights and everyone bracing for impact.

It makes for a good story. It's also a sign that something went wrong long before launch day.

A good ERP go-live day should feel calm. Not boring. But controlled. Yes, there's always a little last-minute energy. It's like moving day: no matter how prepared you are, you're still packing a few boxes the morning the truck arrives. But the big decisions are made. The system is tested. You're not solving problems. You're executing a plan.

You check the boxes, run the first real transactions, confirm the numbers tie out, and go home at a reasonable hour.

If that sounds anticlimactic, good. That's the goal.

The difference between a chaotic go-live and a calm one isn't luck. It's what happens in the weeks before anyone flips the switch.

 

What Has Already Happened Before ERP Go-Live

 By the time go-live day arrives, most of the real work is already done. That's the point.

Here's what should be complete before anyone enters a live transaction:

Test conversion completed.
Your data has already been moved into a test environment at least once. This is where you catch the surprises: duplicate records, missing fields, formatting issues. Better to find them here than in production.

Sandbox validated.
Someone has actually clicked through the system. Created a test order. Run a report. This isn't a demo; it's a dress rehearsal. And it needs to include the people who'll use the system daily, not just leadership. I've seen go-lives where the owner and accountant tested everything thoroughly, but staff never touched it until day one. They were fine because leadership knew the product well enough to answer questions on the fly. But that's not a plan. That's luck.

Workflow questions resolved.
How will you handle returns? Who approves purchase orders? Where does this report live? These conversations are boring. They're also the ones that stall a go-live when they happen too late.

 Custom forms finalized.
Invoices, packing slips, purchase orders. Anything client-facing should already match your branding and include the fields you need. You don't want to discover a missing column the first time you send a real invoice.

User permissions configured.
Everyone has access to what they need and nothing they don't. This sounds simple until you realize someone can't post a payment and the owner is out of the office.

Training done in the real environment.
Not slides. Not a video from the software company. Hands-on time in the system they'll actually use, with their actual data. By go-live, the basics shouldn't feel new.

 If any of this sounds like a lot, it is. But it's the kind of work that happens over weeks, in manageable pieces. Go-live day is just the moment all that preparation becomes official.

 

What Actually Happens on a Well-Run ERP Go-Live Day

Go-live day has a rhythm. If the preparation was done right, it feels methodical, not frantic.

Here's what happens, step by step:

Final data backup.
One last snapshot of the old system before anything changes. If something goes sideways, this is your safety net.

Controlled cut-off from the legacy system.
The client finishes entering their last transactions in the old system. After this point, the old system is for lookup only. No new orders, no new invoices, no new payments. The books are closed.

Data conversion or import.
This is where the data moves. If there's a conversion tool, I run the conversion. If not, we import from the spreadsheets the client has already cleaned up. Either way, the data lands in the live system.

Data integrity checks.
Now we verify. Did everything come through? Are there obvious errors, missing records, or duplicates? This is a quick scan before we get into the detailed comparisons.

Balance comparisons.
We run reports in both systems and compare:

• Vendor balances (AP)
• Customer balances (AR)
• Inventory valuation
• General ledger balances

Old system to new system. Line by line. If something doesn't match, we stop and figure out why before moving forward.

 

What We Confirm Before Going Live

 Before we move to live transactions, three things must be true:

1. Financial totals tie out.
   The core balances in the new system match what we expect from the old system. No unexplained differences. No "we'll figure that out later."
2. Inventory makes sense.
   Counts and valuations are directionally right. Nothing is missing, duplicated, or valued at zero when it shouldn't be.
3. The system is ready for a real transaction.
   Not a test. A real order, a real invoice, a real payment. We're confident the workflow will hold.

Only when all three are confirmed do we move to the next step.

 

The First Live Transaction

This is the moment everything has been building toward. And if you've done the work, it's almost anticlimactic.

The balances tie. The data is verified. The old system is locked down. Now it's time to see the new system do what it's supposed to do.

Pick something real.
Not a test order with fake data. A real customer, a real invoice, a real workflow. This is where you find out if the system works the way everyone expects.

Walk it through end to end.
Enter the order. Check inventory allocation. Generate the invoice. Post it. Send it. Every step that will happen a hundred times next week should happen once, right now, with someone watching.

Confirm it lands correctly.
Does the invoice hit the right GL accounts? Does inventory decrement properly? Does the customer balance update? This isn't about trusting the software. It's about trusting your setup.

If the first transaction runs clean, you're live. Not "sort of live" or "live but still figuring things out." Actually live.

If something breaks, you catch it now, with one transaction to fix, not fifty.

This is why the preparation matters. A clean first transaction isn't luck. It's the result of everything that came before it.

 

What Does Not Happen on a Good ERP Go-Live

A good go-live is defined as much by what doesn't happen as by what does.

On go-live day, you should not be:

Figuring out your chart of accounts structure.
That conversation happens weeks earlier. If you're debating account numbers while trying to convert data, you're not ready.

Debating workflow decisions.
Who approves what? How do returns work? Where do these transactions post? These questions are fine in discovery. On go-live day, they're a red flag.

Designing forms from scratch.
Invoices, packing slips, purchase orders. If you're building these on go-live day, you're going to be sending ugly documents to real customers while you figure it out.

Teaching basic navigation.
Users should already know where to click. Go-live day is for answering "what do I do in this specific situation," not "how do I create an invoice."

Migrating 30 years of messy history at the last minute.
You don't need every transaction from 2003. You need clean opening balances and enough history to operate. Deciding what to bring over is a planning conversation, not a go-live conversation.

If any of these are happening on go-live day, it's a sign that something got skipped earlier. The day itself isn't the problem. The preparation was.

 

Why ERP Go-Live Should Not Feel Dramatic

There's a certain mythology around go-live. The all-nighter. The war room. The heroic scramble to fix something at the last minute.

That makes for a good story. It does not make for a good implementation.

ERP success is not about a dramatic launch. It's about a stable transition.

When go-live is calm:

Teams adopt faster.
People learn better when they're not stressed. A quiet go-live gives users space to get comfortable instead of just survive.

Fewer errors occur.
Rushed decisions lead to mistakes. When there's no panic, people take the time to do things right the first time.

Confidence builds immediately.
The first few days set the tone. If those days feel controlled, users trust the system. If those days feel chaotic, they start looking for workarounds.

Support requests stay manageable.
A calm go-live means questions trickle in instead of flooding in. That gives you time to answer thoughtfully instead of just putting out fires.

This is why the phased approach matters. Every decision made earlier, every workflow tested in the sandbox, every form reviewed before go-live day, all of it exists to make the actual transition feel almost boring.

Boring is the goal. Boring means it worked.

 

Common ERP Go-Live Mistakes I've Seen

I've seen a lot of go-lives. The ones that struggle tend to share the same patterns.

Skipping sandbox testing.
"We'll figure it out in production." This sounds efficient until you're fixing live data in front of real customers. The sandbox exists for a reason. Use it.

Underestimating cleanup time.
Data cleanup always takes longer than anyone expects. Old duplicates, inconsistent naming, customers who haven't ordered in a decade. Cleaning this up is tedious work, and it can't be rushed. Build more time into the schedule than you think you need.

Waiting to train until after launch.
The logic seems reasonable: why train people on a system that isn't live yet? But users who see the system for the first time on go-live day are learning and working at the same time. That's a recipe for mistakes and frustration. Training happens before go-live, not during.

Over-customizing to match the old system.
"Can we make it look like what we had before?" Sometimes, yes. But chasing the old system's quirks often means fighting the new system's strengths. The goal isn't to replicate what you had. It's to work the way the new system was designed to work.

None of these mistakes are fatal on their own. But stack a few together, and a go-live that should have been smooth turns into a scramble.

 

The Bigger Message

A good ERP go-live day is not the finish line. It's the starting point.

The system is live. The data is clean. Transactions are flowing. But that doesn't mean the work is done. It means the real work is beginning.

Post-go-live optimization.
The first few weeks will reveal things you couldn't see before. Reports that need tweaking. Workflows that could be smoother. Small friction points that only show up when people are using the system every day. This is normal. Plan for it.

Gradual adoption of advanced features.
You don't need to use everything on day one. Start with the core workflows. Get comfortable. Then layer in the more advanced capabilities when the team is ready. Trying to do too much too fast is how systems get abandoned.

Continuous refinement.
A good ERP isn't something you set up once and forget. It evolves with your business. New products, new processes, new reporting needs. The companies that get the most value from their systems are the ones that keep refining them over time.

Go-live is a milestone, not a destination. The goal was never just to get the system running. The goal is disciplined operations, and that's a practice, not an event.

Where to Start

If your current implementation plan relies on figuring things out during go-live, it's not a plan.

A real plan means decisions are made before go-live day. Workflows are tested. Data is clean. Users know what to do. The day itself is just execution.

If that's not where you are, there's still time to fix it.

If you're mid-project and something feels off, let's talk. An implementation review can spot what's been missed before it becomes a go-live day problem.

If you're still in the planning stages, start with my Migration Readiness Checklist. It walks through what to expect and how to prepare before moving to a new system, from data cleanup to team preparation to cutover planning.

Either way, the goal is the same: a go-live day that feels boring. Because boring means it worked.

 

~Audrey Quick, Founder of AGS Enterprises Consulting LLC

Audrey has spent 35+ years helping businesses manage ERP implementations and accounting software transitions.  If you're evaluating your options, we can book a free 15-minute call