.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