Category: ERP

Twelve months after go-live, a general manager asked me a simple question: “Is this thing done?” Nobody on the team could answer. They’d been so focused on getting live that nobody had defined what “working” meant.

If you can’t measure it, you can’t claim it. Here’s how to run that check honestly.

Four numbers to pull before anyone declares victory

Don’t start with a satisfaction survey. Start with these, and compare them to the numbers you recorded before the project began. If you never recorded a baseline, use your best estimate and label it as one.

• Order-to-invoice cycle time: how many hours from customer order to an invoice that’s actually correct.
• Month-end close days: the count, not the feeling.
• Inventory record accuracy: sample 50 SKUs and count them.
• Manual workarounds: how many offline spreadsheets are still supporting core processes. This one is the honest one.

If those four aren’t better than when you started, you have a project, not an improvement.

The 90-day value review, run properly

Most companies do a go-live celebration and never schedule a follow-up. That’s why so much of the promised value never shows up.

1. At day 30, list every workaround that’s been created since go-live. No judgment, just inventory.
2. At day 60, pick the three workarounds that cost the most time and assign an owner to each.
3. At day 90, re-measure the four numbers above and present them to the leadership team, good or bad.
4. At day 180, decide what to retire: which legacy reports, spreadsheets or approval steps can be switched off entirely.

Go-live is roughly the halfway point

In most implementations I’ve seen, about 60% of the real benefit arrives between month three and month twelve. Early on, everyone’s just trying not to break anything. The gains come later, when people start simplifying instead of just coping.

A retail business we worked with cut 40 days of annual effort out of its reorder process — not at go-live, but in month seven, when a store manager pointed out that three approval steps existed to catch a problem that had never once occurred.

That’s the work of ERP Consulting after the consultants have mostly gone home: finding the rules nobody remembers choosing and asking whether they still earn their keep. Book your 90-day review on the calendar today. If it isn’t scheduled, it won’t happen.

Warehouse A had it figured out in nine days. Warehouse B, with the identical setup and the same training materials, was still fighting it three months later. Same company. Same software. Different outcome.

This is the part of implementation work that gets blamed on software and almost never is.

What Warehouse A did differently on day one

The supervisor in Warehouse A did something his counterpart didn’t: he asked his team what would make the new process slower, and then he changed two things before training started.

He moved the scanning station closer to the dock doors, saving about 40 feet of walking per pallet. And he let the two fastest pickers test the sequence first, so the rest of the crew heard it from them, not from management.

Training took one day instead of three. Adoption was basically automatic, because the people doing the work had already shaped it.

Warehouse B’s quiet rebellion

In Warehouse B, the process was designed in a meeting room, printed, and handed down. Nothing was wrong with it on paper. On the floor, it added 11 seconds per pick and required walking back and forth across the aisle.

What happened next is predictable. People kept a paper list in their pocket and entered transactions in batches at the end of the shift. The system was “live.” The data was fiction. Error rates on inventory went up 18%.

Nobody was being difficult. People don’t resist new systems; they resist processes that make their day harder.

What we did when we came back

1. Spent a full shift watching, not talking. Two observers, one aisle, no clipboards.
2. Asked the crew to name the top three annoyances. They named five in under ten minutes.
3. Changed the pick sequence and moved one printer. Total cost: about $400.
4. Gave the crew a scoreboard they could see — picks per hour and error rate, updated daily.
5. Made two experienced pickers the go-to people for questions, with a small pay differential.

Six weeks later, Warehouse B matched Warehouse A on accuracy and beat it on throughput. The change had nothing to do with configuration and everything to do with who got to have an opinion.

Any ERP Consulting effort that treats floor staff as an audience instead of a design team is planning to lose six months. Budget the observation time. It’s the cheapest insurance you’ll ever buy.

Before your next rollout, spend one shift standing next to the people doing the work, saying nothing. You’ll redesign half the process before lunch.

Friday, 6 p.m. The cutover begins. Everyone’s optimistic, pizza is ordered, and the project manager is quietly terrified. This is the part of ERP Consulting nobody puts in the brochure.

Saturday, 2 a.m.: the first sign of trouble

Customer records loaded, but 4,100 of them had missing credit limits. That meant every order would stop at the credit check on Monday morning. Nobody had flagged it, because the field was optional in the old system and mandatory in the new one.

By 9 a.m. Saturday, they’d found three more of the same problem: two dozen supplier payment terms set to default, a warehouse location code that hadn’t transferred, and opening inventory balances that were off by $180,000.

What actually saved the Monday

They didn’t push the date. They froze two critical decisions instead: no new orders processed without manual credit approval, and only five order-entry staff worked Monday instead of eighteen. Slower, but nothing shipped wrong.

That company survived because they had three things ready before the weekend started:

• A written list of the 12 checks that had to pass before anyone could transact.
• Two people on call who knew the old data well enough to spot nonsense.
• A pre-agreed fallback: manual approval for anything that would otherwise block a customer.

The second go-live, eight months later

For the next site, they did something simple and unglamorous. They ran the entire cutover twice into a test environment, using a full copy of live data, three weeks before the real thing.

1. Rehearsal one: load everything, log every failure, fix nothing. Takes about 14 hours.
2. Two weeks of cleaning data based on what broke.
3. Rehearsal two: same steps, same people, same clock. Target under 10 hours with zero blockers.
4. Real cutover: Friday 6 p.m. start, Saturday 1 p.m. finish, Sunday off.

The second go-live wasn’t flawless. Three reports came out wrong and one integration ran two hours late. But Monday morning, 96% of orders processed without anyone touching them — versus a number nobody wants to admit from the first attempt.

The lesson isn’t “test more.” It’s that a rehearsal with real data finds the problems that meetings never will. Two dry runs cost three weeks of effort and saved a month of chaos.

If your go-live is more than six weeks out, book the first rehearsal today. If it’s closer than that, write your 12 checks and your fallback plan this week.

The most expensive sentence in manufacturing is “the system will handle it.” I’ve heard it from plant managers, operations directors, and once from a CEO who had never walked the shop floor on a Thursday afternoon.

Here’s what that sentence usually means: we don’t trust our own data, so we’re hoping software will somehow fix that. It won’t.

Your bill of materials is probably fiction

A $32 million job shop we worked with had 1,900 active assemblies. When we checked, roughly 60% had at least one error — a component that hadn’t been used in two years, a quantity that reflected an old design revision, or a phantom part that existed only in the system.

Scheduling on top of that data doesn’t produce a plan. It produces a confident-looking document that everyone ignores by Wednesday.

Fix the 20% that drives the schedule

You don’t need to correct every assembly before you see results. You need the ones that actually constrain your week.

• Pick the top 30 assemblies by revenue or by hours consumed. That’s usually 15–20% of the list.
• Walk each one on the floor with the supervisor and the person who builds it. Ask what they actually take off the shelf.
• Record real scrap percentages instead of the 2% default nobody has questioned since 2019.
• Set lead times from what suppliers actually deliver, not what they promised when you signed the contract.
• Lock routings so two people don’t run the same job two different ways.

Two numbers tell you whether it’s working

Track schedule adherence and unplanned overtime. The job shop started at 61% adherence with 340 hours of unplanned overtime a month. Eight months later: 88% adherence and 190 hours.

Notice what didn’t change. Same system. Same machines. Same headcount. What changed was that the plan was finally built on data that matched the building.

This is where ERP Consulting earns its keep: not in configuring modules, but in forcing the uncomfortable conversation about which numbers are real. A plan built on assumptions is worse than no plan, because it creates false confidence across the whole business.

Pick one assembly tomorrow. Walk it with the supervisor and write down every difference between the paperwork and the parts. Do five of those and you’ll know exactly what needs fixing.

Twelve days. That’s how long it took one $45 million distribution business to close a month. Nine people, six spreadsheets, and a controller who hadn’t taken a full week off in three years.

When we broke the 12 days into pieces, the surprise wasn’t the volume of work. It was how little of it was real accounting.

Where 12 days actually disappears

• 4 days waiting for inventory valuation because receipts weren’t matched to invoices.
• 3 days reconciling purchase orders against what actually arrived at the dock.
• 2 days chasing approval signatures from two managers who travel constantly.
• 2 days re-keying what was already in the system into a consolidation spreadsheet.
• 1 day redoing all of the above after someone found an error.

Only about two of those days involved genuine judgment calls. The rest was cleanup.

Set a three-day rule and hold it

The rule we introduced was blunt: no transaction sits unposted for more than three business days. Receipts matched within 48 hours. Invoices coded the day they arrive. If something is stuck, it gets a name next to it, not a note in a shared inbox.

That single rule moved the close from 12 days to 7. Not because the team got faster at typing, but because month-end stopped absorbing work that should have been done on the 8th, 14th and 21st.

What the finance team stopped doing

1. Stopped re-keying data that already existed. One report, pulled from the system, replaced three spreadsheets.
2. Stopped waiting for signatures. Approval limits were raised for anyone below $5,000, with a monthly review instead of a pre-approval.
3. Stopped treating reconciliation as a month-end event. It became a 20-minute daily task.
4. Stopped closing on day 12. The target became day 4, and they hit it in the fifth month.

Why the controller cared more than anyone

A four-day close doesn’t just feel better. It changes what decisions get made. When numbers are nine days old, you’re steering a business with a rear-view mirror. When they’re two days old, you can actually stop a bad month while it’s still happening.

The team that did this also found $340,000 of duplicate payments in the first quarter, simply because reconciliation stopped being a monthly panic. That’s the return nobody puts in the business case for ERP Consulting, and it’s often bigger than the efficiency savings.

Pick the single biggest bottleneck in your close, and set one rule about it this week. Then time the next close and see what moved.

“I lost another one,” the sales manager said, dropping a printed email on my desk. A customer had asked for pricing on 30 SKUs on Monday morning. The quote went out Thursday at 3 p.m. The competitor’s quote landed Wednesday.

Nobody in that 20-person wholesale team was lazy. Every single person was busy. That’s exactly what made the problem invisible.

We timed every handoff on one real quote

Total elapsed time: 4 days and 6 hours. Actual working time: 3 hours and 20 minutes. The other 90% was people waiting on other people.

• Rep emails the SKU list to the sales manager, who is in meetings until 4 p.m.
• Sales manager checks stock in one place, pulls cost from a spreadsheet that was last refreshed in March.
• Finance director has to approve anything under 22% margin, and he was traveling Tuesday.
• Two of the 30 SKUs had no cost loaded at all, so someone had to call purchasing.
• The final quote sat in a draft folder until the rep remembered to send it.

The waiting was the problem, not the work

You don’t need a new system to fix 90% of this. You need to decide in advance what nobody should have to ask about. That’s the part most ERP Consulting projects skip because everyone is busy arguing about screens.

Four decisions cut that team’s quote time to under a day:

1. Pre-approved margin bands. Reps quote down to 18% without asking anyone. Below that, it goes to finance, and finance has a four-hour response clock.
2. One source of truth for cost. If a cost isn’t loaded, the quote tool flags the SKU instead of letting someone guess.
3. A stock freshness rule. Available quantity is shown with the time it was last updated. Anything older than four hours is marked as an estimate.
4. A 24-hour default. Every open quote gets a status every morning. No quote sits untouched for more than one business day.

What 60 days of change produced

Average quote turnaround fell from 4.1 days to 9 hours. Win rate on quotes went from 31% to 44%. The team didn’t hire anyone and didn’t work weekends.

The uncomfortable truth is that speed in quoting is rarely a technology gap. It’s a decision-rights gap. Who is allowed to say yes without asking is the single most powerful lever in a sales operation, and it costs nothing to define.

Here’s your first move. Take the last quote you sent out and write down the timestamp of every handoff. You’ll find your bottleneck in about 20 minutes, and it almost certainly won’t be the software.

Picture a 60,000-square-foot warehouse at 6 a.m. Forty people with clipboards, two days of counting, and a Monday morning where the system says 340 units of a fast-moving part and the shelf holds 212. That gap isn’t a computer problem. It’s a process problem wearing a computer’s costume.

The distributor I worked with had $18 million in revenue, 4,200 active SKUs, and a system that had been running for two years. Their finance team had quietly given up on inventory reports and was doing manual write-offs every Friday afternoon.

Measure one number before you change anything

Most managers want to jump straight to handheld scanners and new modules. Don’t. Start by measuring inventory record accuracy: pick 50 SKUs at random, count them by hand, compare against the system. If fewer than 48 match, you have a counting problem, not a technology problem.

That distributor scored 71%. Which means roughly one in three times a salesperson promised a delivery date, they were guessing. Customers noticed before management did.

The five places errors are actually born

• Receiving before paperwork: goods hit the shelf at 2 p.m., the receipt gets typed at 5 p.m., and someone sells three of them at 3 p.m.
• Returns parked by the door: a customer sends back 12 units, nobody posts them, and the system keeps selling stock that’s physically back in the building.
• Damage never written down: a forklift clips a pallet, the note goes on a scrap of paper, the write-off never gets entered.
• Substitutions at pick time: the picker grabs the 6-inch version because the 8-inch is buried, ships it, and the system still thinks the 8-inch is gone.
• Unit-of-measure confusion: buying in cases of 24, selling in singles, and someone picking the wrong one at 4:45 on a Friday.

Run a 15-minute count every single morning

Forget the annual wall-to-wall count. It costs you two days of shipping and buys you accuracy for about one afternoon.

1. Pick 15 SKUs each morning: ten high-value or fast-moving, five completely random.
2. Freeze only those 15 locations. Everything else keeps moving and shipping.
3. Have a second person count independently. Two counts, no discussion, then compare.
4. Log every mismatch with a reason code: receiving, picking, damage, return, unit of measure.
5. Fix the process behind the number. If three mismatches in one week trace back to unposted returns, the count was just the messenger.

What 90 days actually bought them

Accuracy went from 71% to 96%. Pick errors fell from 4.1% of orders to 0.6%. Expedited freight — the money you burn when you promise a date you can’t hit — dropped by $11,000 a month.

Nobody bought new software. They changed who counts, when they count, and what happens after a mismatch. This is the unglamorous half of ERP Consulting that rarely makes a slide deck, because process discipline doesn’t come with a license fee attached.

Tomorrow morning, pull the 20 SKUs with the highest annual usage and count them by hand. Whatever you find, write down the reason. That one habit is where the recovery starts.

The founder of a food service distribution company with 23 employees still checked the bank balance every morning before his first coffee. Every morning, he felt the same panic: the account looked strong on Tuesday and dangerously low on Friday, and he could not quickly tell which customers were paying on time and which were quietly stretching beyond 60 days. He was the only person at the company who saw the whole financial picture, and he admitted he did not actually understand it until four different spreadsheets had been aligned by hand.

The Owner Was the Bottleneck, and That Was Nobody’s Fault

His salesman closed a large deal with a restaurant group, and the order looked fantastic in the revenue column. What nobody translated into weekly visibility was that the contract allowed that customer 75 days to pay. The distributor had to buy the inventory, store it, and deliver it for more than two months before seeing a dollar in return, all while continuing to pay its own invoices on 30-day terms.

ERP Consulting‘s role here was not to redesign the whole company. It was to give the owner a single weekly review that let him spot cash flow patterns before they bit him. The first meeting took 90 minutes, and the most important question was simply: which ten orders currently in the backlog require us to spend money before our customers pay us?

A Weekly Cash Review That Fits on One Page

1. List open orders older than 45 days, with the number of days since the invoice date next to each customer name.
2. List every confirmed purchase order that requires inventory to be bought before the customer’s deposit arrives.
3. Compare the next two weeks of expected cash collections against the next two weeks of required supplier payments, and only then decide whether the company can accept fast-growth orders without taking on a short-term loan.

This looks painfully obvious on paper, but the owner later admitted he had grown so fast that he managed his cash by memory. His memory was wrong at least twice a month. After eight weeks of the daily cash sheet and weekly review, he told me the single most useful change was dialoguing with his sales team about financing terms, not just selling price.

When the Growth Question Becomes a Financing Question

By the end of the quarter, he had shifted his best customers toward a 50 percent deposit for first-time orders and standard 14-day payment terms for repeat business. The bank line of credit stopped being used as a permanent float, and instead was reserved for true seasonal peaks. The answer to his old question, “where is the cash,” turned into a one-page view that even a vacationing owner could hand to his operations manager on Friday afternoon.

Run your own version of this review tomorrow. Print the accounts receivable aging, the open purchase orders, and the bank balance, and place the three pages side by side for ten unbroken minutes. Draw a circle around any order where you must spend money before the customer pays. If the circles cover more than a third of the page, your company is growing faster than its cash cycle allows, and no extra sales effort will solve that tension. A methodical review, where ERP Consulting helps you turn scattered numbers into a single rhythm, beats the owner’s instinct to simply watch the bank balance more anxiously each morning.

One Tuesday in January, a heating and plumbing service company had 20 vans on the road and a warehouse full of parts. A technician arrived at a customer’s house to fix a broken heating system, opened the back of his van, and discovered he had been carrying a new circulator pump for six months without ever knowing it was there. His van was so cluttered that he had bought another unit with the company credit card two days earlier. When the owner checked all vans that night, he found duplicates worth about $12,000 sitting in plain sight.

The Cheap Shot: Blaming the Technicians

It would have been easy to introduce a rule demanding that every van be organized and scanned weekly. But the problem was not laziness. The same van would be assigned to a different technician every week depending on who was on call, and each new driver rearranged the shelves to match his own habits. There was no fixed agreement about what belonged on each van or in the warehouse, and nobody had ever measured how often a technician skipped a job because the right part was sitting somewhere off-site.

What ERP Consulting Suggested Instead

• Define one standard layout for every van, with the top 15 high-turnover parts assigned to exact labeled shelves that never change position.
• Create a two-bin system for those top parts. When the working bin is emptied, the empty bin itself acts as the signal to replenish from the warehouse.
• Count every van’s inventory once per week at the same time and by the same person, rather than waiting for an annual stocktake that nobody really trusts.

The company also realized that its service software treated vans as just transportation assets. In reality, each van held $9,000 of working inventory, and nobody was accountable for it. The owner’s role changed from buying more stock when a part was missing to tracing why the system said a part was on a van that no one could find.

The Figure That Changed the Conversation

During the first month of the new layout, the team recovered enough duplicate part inventory to cover the entire two months of onboarding cost. Same-day fix rates improved from 61 percent to 79 percent over ten weeks, and the customer service manager stopped hearing the phrase “I think I have one of those under the shelf in the back.” Visible, standard stock rotation became a profit lever instead of an endless source of emergency purchases.

Walk your own parking lot tomorrow morning with a simple clipboard. Ask three field employees to show you the part they replace most often, and watch how long it takes each of them to find it. If even one of them cannot locate it in under two minutes, the issue is not the technician or the van size. You have a stock location trust problem, and until the support team stops buying parts on credit cards to cover missing inventory, every additional purchase only deepens the chaos. That is the exact moment when a structured consultation model from ERP Consulting becomes far more useful than another piece of rugged hardware attached to a windshield.

Two regional packaging manufacturers merged, and for the first six months they operated as one company with two completely different pricing lists. The same corrugated box design was quoted at $18.40 by plant A and at $16.90 by plant B. Customers noticed. Salespeople lost deals arguing about which division was allowed to honor whose discount, and the finance team could not calculate combined margins without building two separate spreadsheets side by side.

A Merger in Name Only

The new owner assumed the big challenge would be integrating computer systems. In reality, the biggest mess was that plant A used a $5 markup on a particular material while plant B used a $1.20 markup plus a separate handling fee. Both plants were profitable under their own rules, but now they were sharing customers and both still used different cost definitions for freight.

ERP Consulting assembled six people from purchasing, production, sales, and finance for a single working session. The goal was not to choose one price list over the other. It was to agree on exactly what went into the cost of a box, right down to whether the glue in the recipe was a shared raw material or a factory consumable charged to the customer.

The Three Decisions That Made the Price Book Work

• One cost definition. Every plant now includes freight, tooling, and a fixed overhead rate in the same way, so comparing quotes at any of the three sites feels apples to apples.
• One discount ladder. A customer who orders $200,000 a year gets the same discount no matter which plant produces the order.
• One exception log. Any price that does not fit the standard formulas is written on a shared exception sheet that gets reviewed every Friday. Nobody simply memorizes a special deal anymore.

The project took ten weeks, and less than one-third of that time involved software configuration. The hard part was getting the production teams to agree that the cost of an hour of machine time should be calculated identically at both sites. Once the cost definition was settled, everything else became an administrative task.

What the New Owner Noticed Afterward

The biggest benefit was not having a prettier price list. It was that salespeople finally argued with competitors instead of with each other, and quote response time dropped from three days to one. Margin analysis also exposed that one of the merged plants had been quoting freight charges significantly below its actual delivery cost for years.

If you are heading into any kind of merger or acquisition this year, start by printing the last ten quotes from each site and highlighting every line where the same item costs a different amount. If you circle more than three differences, what makes a shared system work is not better software reports but the uncomfortable discussions about cost and discount definitions that your leadership team has been avoiding. ERP Consulting can offer the neutral room, but the honesty has to come from inside your own team.