Author: Next

The finance director of a food distribution company looked exhausted when we met. Every month, the ritual was the same: 15 days of spreadsheet gymnastics, phone calls hunting for invoices, and a board meeting where the numbers were already stale by the time they were presented. She said something I’ll never forget: “We’re always driving the car looking through the rear view mirror.”

Her team of five accountants spent nearly half their month just assembling data. The actual analyzing—the part humans are good at—came last, and got rushed.

Why it was slow, and it wasn’t their Excel skills

The invoices lived in one system. The bank statements sat in another, downloaded manually. Sales data was in a third. Every month, someone re-keyed the same numbers by hand, and every month, the same three reconciliation errors appeared.

Nobody was lazy. The structure forced them to be slow.

Here’s the pattern I see everywhere: the accounting team doesn’t create the delay; the handoff between departments does. Sales doesn’t log a deal until the end of the week. Warehouse records arrive three days after the month ends. So finance can’t start until everyone else finally cooperates.

When I map this in an ERP Consulting engagement, the close is the first thing I look at—it exposes every broken handoff in the company.

What we changed in the first 30 days

1. Set a hard deadline: every department must submit its data by the 2nd business day of the month, no exceptions, and the CFO sends a reminder on day 1
2. Switched bank statements to an automatic feed so nobody re-keys them—this alone saved roughly 8 hours per month
3. Created a one-page close checklist so the entire team can see where each task stands instead of asking each other by email

None of this was fancy. It was discipline plus one integrated place to look at the numbers. By month three, the close took seven days. By month six, three days.

The benefit nobody predicted

Once the books closed fast, salespeople stopped booking revenue in the wrong month just to make targets look better. The sales manager admitted they’d been “optimistic” with timing in the past. With real-time visibility, that game ended. The company also found $60,000 of duplicate vendor payments, hidden for years because invoices were paid before anyone matched them properly.

If your close takes more than a week, don’t assume you need a bigger accounting team. Map the slowest handoff between departments and fix that single handoff first—that usually delivers half the improvement. When the organizational piece is in place, ERP Consulting can build the integrated reporting on top. But the team habits have to come first, or the software just makes bad data flow faster.

A mid-sized furniture maker once told me a maddening story. Their warehouse had enough raw wood to build for six weeks. Yet twice a month, a truck would arrive to pick up a customer order, and a key component would be missing. The purchasing manager’s answer was always the same: “we have plenty on order.”

Plenty on order isn’t the same as plenty on the shelf. That phrase alone was costing them $18,000 per month in express shipping and partial deliveries. ERP Consulting started by asking one uncomfortable question: what do we actually sell, in what combination, and how fast do we truly use each material?

The mistake most inventory teams make

They treat every item the same. This company bought hinges in huge batches because a supplier gave a 5% discount. But hinges were cheap to store and slow to move. Meanwhile, they bought specialty leather in tiny lots because it was expensive, and ran out every other week when a rush order came in.

It was backwards. The expensive, hard-to-replace materials were the ones they should have stocked deepest, and the bulky cheap stuff should have been trimmed down.

• List your top 20 materials by how much they disrupt operations when missing, not by purchase cost—those are two different lists
• Set a minimum stock level for each critical material based on your supplier’s actual lead time, including weekends and holidays
• Run a simple count twice a week for the top ten problem items; a 20-minute task that catches 90% of stockout surprises

What the numbers showed after one month of tracking

They discovered that 70% of their stockouts came from just seven materials. And the supplier for those seven had a 12-day lead time, not the 5 days everyone assumed. See the gap? For seven critical items, they were reordering nearly a week too late, every single time.

Once they adjusted reorder points to match real lead times, stockouts dropped by half in the first month. They also freed up $28,000 in cash by cutting the unnecessary hinge inventory they’d been hoarding for that 5% discount.

Why the system matters more than the spreadsheet

A spreadsheet can record a reorder point. But it won’t tell you that a slow-moving item is tying up your cash, or that lead times just stretched because your supplier changed their production schedule. That’s where a proper system earns its keep.

Here’s the honest truth: inventory problems are almost never about lazy people. They’re about people making decisions with bad or outdated information. When I work on these engagements, ERP Consulting always starts with the trust issue—do your people actually believe the numbers on the screen? If not, fix the data first, then the rules. Set your reorder points from real lead times, not gut feel, and review them every quarter because suppliers change faster than you’d think.

I sat in a meeting with a 120-person factory that made metal enclosures. The owner was furious. Orders were going out three weeks late, overtime was eating 14% of payroll, and when he asked the production manager why, the answer was always “the schedule is tight.”

But the schedule wasn’t the problem. The real problem was they were planning with a whiteboard and a gut feeling. ERP Consulting got involved, and the first thing we did was map how long each job actually spent in each machine center.

What we found made the owner go quiet

One press machine sat idle 6 hours a day because the operator had to chase down materials. Another machine ran 22 hours straight because everyone “knew” it was the bottleneck. The gap between what they thought was happening and what was real cost them roughly $40,000 a month in late penalties and rush freight.

I’ve seen this pattern in at least a dozen plants. The fix isn’t buying better forklifts. It’s having a system that shows every order against every machine’s real capacity.

• Pick your three busiest machines and write down how many hours they actually run per day—not what the schedule says, what the clock says
• List your top ten overdue orders and trace where each one stalled; most shops find the same two or three choke points
• Track how much time operators spend walking or waiting—anything above 15% is a planning gap, not a labor problem

What changed when we set real capacity numbers

We rebuilt the production plan with honest capacity numbers: the bottleneck machine got scheduled first, and everything else was pulled around it. Within six weeks, on-time delivery went from 43% to 78%. Overtime dropped because jobs stopped bouncing between machines in random order.

Here’s the part managers miss—the schedule is a contract between sales and production. If the planner commits to a date that ignores real capacity, the whole company is lying to the customer. ERP Consulting doesn’t magically give you more hours in a day. It forces you to face the truth about the hours you have.

The one change that mattered most

The owner started a 10-minute daily meeting at 8:05 AM, standing by the bottleneck machine, not in a conference room. Every department head had to state what was coming to the bottleneck that day and what was missing. That tiny habit created more accountability than any software feature.

If your delivery dates are slipping, start there. Measure the bottleneck honestly for one week before you even talk about software. When you’re ready for the system piece, bring ERP Consulting into the conversation early—not after you’ve already bought something that runs on made-up numbers.

It’s the most common complaint a consultant hears. I once sat through a long Tuesday meeting where the sales director said revenue was $2.4 million for the quarter, the operations manager said $2.1 million, and the finance controller argued it was $2.2 million. All three were looking at the same company. All three were right.

Why three people can be right at once

Those reports came from different sources. The sales director counted what was ordered. Operations counted what was shipped. Finance counted what was invoiced. For a services business, the gaps come from timing — a job billed in February for work done in January, a credit note that hasn’t landed anywhere yet. This is a reporting design problem, and it’s solved before anyone touches the system.

ERP Consulting always starts with a favorite exercise: write down five key metrics and define each one in writing. No screens. A company that says “gross margin” but doesn’t specify whether freight is included has a definition problem, not a data problem. Until the definitions line up, every dashboard is a story written by different authors.

• Define your top five metrics in 50 words or fewer; if it takes more, the term is too vague
• Set one authoritative report per metric — not one per department
• Pick a single time basis (“shipped in January” or “invoiced in January”) and never mix them in the same table

The math that convinced the CFO to act

That same company, before any system change, ran a visibility exercise. It asked all three managers to compare notes on a single big customer. The mismatch on that one account was $178,000. Nothing was wrong with the accounting. The report timestamps just didn’t align. An ERP Consulting blueprint effort that took 90 minutes gave the CFO the pattern, and more importantly, a decision rule she could enforce.

She adopted one simple convention: every report tracks sales by the date of invoice and cost by the date of shipment. Within a month, roughly 70% of the disagreements in management meetings disappeared.

Test it this week: ask three of your managers to each pull one number — say, accounts receivable over 60 days — then compare what they bring back. If the answers differ by more than 2%, you don’t have a software problem; you have an authority problem. The value of ERP Consulting doesn’t start after implementation. It starts with these tiny definitions that everyone can agree on today.

You run a small clinic. Your doctors are excellent. Your front desk is drowning. Every afternoon, a nurse calls five different suppliers to check if the sanitizer order shipped. The booking system works, but it can’t tell you which physician is 45 minutes behind schedule. And the accountant spends two full days a month reconciling patient invoices that don’t match the appointment list. Does any of this sound familiar?

Where the 12 hours were hiding

A three-doctor family practice handed ERP Consulting a complaint: the front desk staff were working through lunch and still taking work home. We tracked every administrative task for two weeks. The shocking part: staff spent 22 hours a week on tasks that could be automated or done in one-third of the time.

The four changes that freed the time

• Supplies with a minimum stock level get reordered automatically when the count drops below a two-week buffer
• Patient invoices generate automatically from the appointment and procedure log, so billing matches reality
• The front desk sees live wait times and calls the next patient 10 minutes before the doctor is actually ready
• Daily supply counts on five critical items take two minutes per morning instead of 30 minutes of phone calls

What the reclaimed time bought

The 12 hours per week went straight back into front desk interactions with patients. The clinic started answering the phone on the second ring instead of sending callers to voicemail. Patient satisfaction scores went up, and the accountant’s monthly reconciliation went from two days to three hours. The doctors noticed the difference in their own stress levels within the first month.

The clinic did not cut a single person. That’s worth repeating: no layoffs, no pay cuts, just better flow of information. The front desk staff finally stopped acting as the middleman between suppliers, the doctors, and the accountant. If your clinic is running on sticky notes and phone calls, start by listing the five most repeated questions your front desk answers each week. Those are your automation targets. ERP Consulting will tell you to tackle those five before you even think about bigger systems.

Let’s start with the before. A regional retailer with three warehouses — two small ones and a big one — shipped 410 orders a week. Almost none of them went out complete. The big warehouse’s manager claimed the small ones were hoarding stock; the small ones said the big one didn’t trust them. There was no data to settle it, just an argument that had been running for 18 months.

The insight hiding in plain sight: your warehouses are competing on the wrong metric

Across the three sites, the same SKU sat in two buildings in 43% of cases. In theory, that’s a safety buffer. In practice, it meant nobody could trust their own counts, so each warehouse ordered extra stock to protect itself.

ERP Consulting didn’t begin with a grand integration plan. It began with agreeing on one thing: which warehouse ships a given SKU by default. That single rule untangled half the duplication.

• Assign a primary warehouse for every SKU; others can hold overflow but must label it as such
• Set standard transfer triggers: if the primary site drops below six days of cover, request a move in one click
• Report a single set of numbers each Monday: on-hand total, committed, available, and days of cover

When the numbers settle, people stop pointing fingers

The change took about 60 days to measure. By the end of the year, the same 23 people were shipping 820 orders a week. The big warehouse manager stopped accusing the small ones because the report showed exactly where stock moved. The two small warehouses started doing 38% of the picking, not because anyone asked nicely but because the primary-assignment logic distributed the work.

Try this yourself: take your top 50 SKUs and run the dual-location test. If more than a fifth of those SKUs live in two warehouses at once, your reorder numbers are lying to you. Fix that alone and you’ll see the difference. If you can’t fix it without help, that’s exactly the problem an ERP Consulting engagement should be asked to solve.

It’s 11 p.m. and you’re a founder with 200 orders to ship by Friday. Your spreadsheet says you have 60 of the best-selling dress in stock, but the warehouse person just texted “only 12 left.” A customer emails demanding a refund for an item you were sure you sent. Welcome to the stage where spreadsheets quietly turn from helper to saboteur.

The crossover moment we see most

An online fashion boutique selling 150 SKUs across three marketplaces hit this wall. Returns were running at 18%, which is normal for fashion, but they were handling returns with the same spreadsheet they used for fresh stock. The result: items sat in a “returns” box for two weeks while the website kept selling them as available. That mismatch alone cost the boutique about $6,000 a month in cancelled orders and angry reviews.

Making returns a first-class process

ERP Consulting started by separating returned inventory visually in the workspace and in the system. Every return got a status: restockable, damaged, or refund-only.

• Restockable items are inspected and photographed within 24 hours, then made available online with the original photos
• Damaged items moved to a discount list automatically, instead of hiding in a drawer for weeks
• Refund-only items trigger the refund the same day, which stopped the “where is my money?” emails

Buying decisions improved too

Once returns were tracked accurately, the boutique could see which colours and sizes actually came back. That sounds niche, but it was gold. Their return rate on a certain floral dress was 31%, mostly because the fabric ran small. They changed the size chart, and returns on that item dropped to 12%. Good return data tells you what to fix before customers decide to stop buying.

Now the founder runs the whole business on a single screen: stock by location, orders in flight, and return status per item. The spreadsheet still exists, but only for planning next season’s styles, which is what it’s actually good for. If your marketplace order volume has grown 30% three years in a row, that’s a sign you outgrew the spreadsheet. ERP Consulting will tell you to make the switch in the off-season, not with 200 orders on your desk tomorrow morning.

Here’s a mistake small distributors make: they think order management problems are about visibility. A sales rep discovers the warehouse never picked a customer’s 36 pallets when the customer calls at 4:47 PM asking where the truck is. The rep checks the system, sees the order sitting in “picking,” and has to decide in seconds whether to blame the warehouse, the system, or the traffic.

Who gets the bad news first matters more than having all the data

ERP Consulting does change screens, yes. But the bigger shift is about which role is accountable for catching problems early. In one 30-person wholesale operation, the rule became simple: the warehouse lead sends a status to the sales rep twice a day, at 11 AM and 4 PM, even when everything is fine. Doesn’t sound glamorous, yet the number of “where’s my truck” calls dropped by half in three weeks.

That distributor had another quirk. Orders were typed manually, so a customer ordering “3 cases of 12” and “2 cases of 24” of the same product created two lines that looked like one product to the warehouse. The result was a constant stream of partial picks.

• Set one standard unit for every product and refuse to accept an order entered any other way
• Freeze order changes after 2 PM unless a manager approves — the warehouse can’t ship what it couldn’t see
• Make the status field mandatory on every work order: waiting, picked, loaded, shipped. No blanks allowed

The ripple effect on customer trust

Sales teams resist these rules because they want flexibility. But when the distributor implemented those three items, its on-time shipment rate for promised deliveries went from 68% to 91% in two months. The sales rep no longer needed an angry call to find out something was wrong.

Here’s a simpler way to think about it: your ERP Consulting project is on track if the person closest to the customer hears about a problem before the customer does. If you’re still hearing about it from the customer, no dashboard will save you.

You can be a brilliant lawyer and still lose money on a $300-an-hour case. How? By doing 40 hours of work and billing for 28. By fixing a partner’s draft three times because the file version kept changing. By forgetting that a client told you in a phone call to drop the research request. Small firms bleed cash in these invisible ways every month.

The billing audit that stung

A 15-person law firm came to ERP Consulting because their realization rate, the share of billable hours that actually became client invoices, had slipped under 70%. Partners were furious with associates, associates were afraid of partners, and the firm was leaving $50,000 a month on the table. The problem was not lazy work. It was that time entries happened at the end of the week, when memories faded and nobody wrote down the important details.

Mistake number one: billing from memory

The first fix was to make everyone log time the moment they finished a task. Not three hours later, not after lunch. Entries made the same hour are 20% longer than entries made three days later, because you remember what you actually did. This one change added 4 billable hours per associate per week.

Three more fixes that paid for themselves

• Every non-billable task gets a code, so partners can see which admin work is eating the team’s capacity
• All client communication about scope changes goes into the matter file within 24 hours, no exceptions
• Write-offs require a named person to approve them, which cut “friendly discounts” by more than half

What changed in a quarter

Within 90 days, the firm’s realization rate climbed from 68% to 82%. That is roughly $35,000 more collected every month without taking on a single new client. The associates actually preferred the new system, because they could finally prove how much value they were producing. The last thing ERP Consulting recommended was a monthly invoice review with every timekeeper, so people see exactly where time disappears instead of guessing.

If you run a professional services firm, here’s your first step. Look at your last twenty invoices. Count the hours you billed and divide by the hours your team honestly logged. If that number is under 80%, you don’t have a lazy team, you have a leaky process. That number will not fix itself.

A food manufacturer with roughly $25 million in annual purchases ran on urgent POs. Their buyer processed 40 purchase orders a day, and at least six of them were emergency orders placed because someone forgot a component. The purchasing manager and the production supervisor had a loud shouting match in the hallway over a missing spice blend. The production supervisor won — mostly by being louder.

The 2 AM question: are you buying on demand or buying on panic?

Here’s what’s predictable: if more than 10% of your POs qualify as “urgent,” your planning process is the problem, not your buyers. ERP Consulting for this company started by tagging every purchase order with a reason code — rushed, planned, or forecast-driven. The data took four weeks to mean anything because people had to trust that the tag wouldn’t get them in trouble.

Why do companies hit 60% emergency orders? Because nobody reconciles what’s in stock with what’s in the pipeline. Buyers act on what they remember from yesterday’s rush, not on a single source of truth.

• Tag every PO with a code: planned, forecast, or emergency — no exceptions
• Run a weekly “stock-to-commit” report: what’s on hand, what’s on order, what’s promised
• Set a two-week minimum on all non-perishable reorder points so there’s always a buffer that absorbs one miss

Give buyers time to actually buy

The manufacturer realized its top buyer was spending 40% of the day answering chat messages and matching invoices. ERP Consulting redirected those tasks to a simpler rule: invoices go to the system, the system flags mismatches, and buyers only look at exceptions. That freed up seven hours of buyer time per week.

By month four, emergency POs fell from 15% of orders to 4%. The shouting match stopped, not because people got nicer, but because the production supervisor found inventory appearing on a routine schedule instead of a crisis.

If you’re not tagging your emergency orders, start tomorrow. You can’t improve what you can’t count.