Author: Next

Walk into any services firm — IT services, engineering, marketing agencies — and you’ll find the same pattern. Consultants finish the work, jot down their hours “later,” and the invoice finally goes out after a project milestone, or after someone asks about the money. One 30-person engineering firm billed clients an average of 12 days after the work was delivered. That doesn’t sound terrible until you see what it really costs.

Every late invoice is a sales problem, not an accounting problem. When a client sees an invoice 12 days after the work, the work is old news. The project is emotionally closed for them, and “what’s this for?” replaces “great, where do I sign?” Disputes take longer, payments drag on, and cash flow starts leaking slowly.

Why the timesheet is the true starting line

The ERP Consulting review at this engineering firm found something surprising: hours were collected, but nobody trusted them. Project managers adjusted the reports based on feel, and billing was rebuilt from scratch by a finance person interpreting messy notes. The timesheet wasn’t a business document — it was a suggestion.

We changed the rule at the first meeting: a timesheet entry with no project code doesn’t exist. If a consultant can’t pick a project, the system blocks the entry until it’s fixed. It felt harsh for about one week, then everyone adapted.

The invoicing rhythm that cut billing time from 12 days to 2

1. Timesheets close every Friday at 3 pm — no exceptions, no “I’ll remember Monday morning” games.
2. Project managers approve their teams’ hours by Monday noon; anything unapproved is not billable, and the consultant hears about it directly.
3. Invoices generate automatically on Tuesday morning for all approved hours, with one quality review — not re-typing.

Within one quarter, the average invoice went out 2 days after the work. Payment time shrank too, because clients stopped questioning line items that were once vague. That slow spiral of disputes simply ended.

The finance manager told me the ERP Consulting engagement paid for itself in the first three weeks. Not because of fancy software — because of a Monday noon deadline and a screen that refused to accept laziness. The discipline was the system.

You know the feeling: a customer calls and asks, “do you have this in stock?” You say “let me check” — while secretly hoping nobody asks about the other two channels. A 25-person outdoor gear company lived that reality for two years. They sold on their own website, on a big marketplace, and through two retail partners, all from one warehouse, with three separate spreadsheets and a growing pile of backorders nobody could explain.

Here’s the mess they called normal: the marketplace showed 40 units of a camping stove, because the website team forgot to subtract the 25 units reserved for retail partners. A marketplace order came in, the warehouse picked it, and the website ran out of stock — causing 38 canceled orders in a single month. Customer service stopped answering the phone.

Spreadsheets are fine — until three people touch them

The real problem wasn’t the marketplace or the warehouse. It was that stock levels lived in four different places: the website platform, the marketplace dashboard, a retail partner’s portal, and a purchasing spreadsheet on someone’s laptop. The ERP Consulting conversation started with one simple rule: one master inventory number, visible to everyone, updated in real time.

What changed when stock became a single number

• Orders from any channel deduct from the same inventory pool, so a sale on the marketplace reduces website stock instantly — no manual subtraction, no forgotten reservation.
• Each product has an allocation rule: retail partners reserve a fixed quantity, and anything above that is sellable online. The rule is set once in the system, not scribbled on a whiteboard.
• Reorder alerts fire when available stock drops below the combined 30-day forecast across all channels.

Within two months, backorders fell from 142 open lines to 19. Canceled orders dropped by 87%. The warehouse manager put it simply: “I used to guess what to pick. Now I just read the screen.”

The ERP Consulting work didn’t end at launch. The team revisited the allocation rules twice in the first quarter as sales patterns shifted, and each tweak took an afternoon instead of a week. That’s the payoff of a system where everyone looks at the same number.

Here’s a familiar scene: a restaurant group with 14 locations and a central kitchen has food cost hovering near 31%. The chef swears the recipes haven’t changed. The purchasing manager swears vendors raised prices. Everyone points at someone else, and the margin keeps slipping a point every year.

We ran a 90-day ERP Consulting review for a group exactly like this, and the finding was blunt: the recipes in the computer were 18 months old.

Old recipes leak money even with good cooks

Flour went up 11% in that period. The portion size for the signature chicken dish quietly grew, because a newer cook scooped a little fuller. The “standard” recipe said 140 grams of rice; the plate actually carried closer to 165. Multiply a 25-gram difference across 4,000 covers a week and you’ve lost roughly $21,000 a year on rice alone.

The ERP Consulting diagnostics compared purchase receipts against recipe math. For every menu item, the system calculated what the kitchen should have consumed, then matched that against what was actually bought. The variance told us exactly which items were leaking.

How to find your own leak in three steps

1. Lock every recipe in the system with exact weights, and re-verify each one quarterly — a cook’s “generous scoop” is not a measurement.
2. Run a monthly check comparing actual purchase quantities to theoretical recipe usage; any variance above 3% gets reviewed with the kitchen manager.
3. Tie vendor price updates to recipe costing, so a supplier increase recalculates the true cost of every menu item the same day.

The group’s food cost went from 31% to 27.8% within five months. No menu price increase. No portion cut that customers noticed. Just accurate recipes and a measurement routine that people actually follow.

If your food cost is drifting, the answer isn’t a new menu. It’s a more honest look at what’s really on the plate — and a system that catches the drift before it reaches your bottom line.

A roofing contractor with 60 employees finished seven commercial projects in one year. The accounting team said all seven were profitable. The owner sold the business six months later and discovered the truth: two jobs had actually lost money, and the combined losses totaled $92,000. Where did the numbers go wrong?

The uncomfortable part is that the job logs looked fine — because labor hours were being charged to the wrong jobs. Crews moved between sites constantly, but the foreman recorded hours at the end of the week from memory. A crew that spent Tuesday on the Smith building and Wednesday on the Lee building often had both days logged to whichever job came to mind first.

Why weekly memory never adds up to profit

I’ve sat with foremen who genuinely believed their records were close. They weren’t lying — they were guessing. A company that charges $1,400 per hour of crew time, across twelve crew members, can misallocate $5,000 in a single week without anyone noticing, because the total payroll still adds up. No red flags appear when the total is right.

The ERP Consulting assessment asked one direct question: can we trace every hour of every crew member to a specific job, day by day? The answer was no. So we built a routine, not just a report.

The five-minute habit that protected the next year’s margins

• Each foreman enters crew hours on a tablet before leaving the site — five minutes, tied to the actual job worked that day.
• Change orders get logged within 24 hours of verbal approval, with the name of the person who authorized it.
• Equipment hours follow the same rule: the excavator belongs to a job, and idle time is a line item, not an overhead guess.

The next year, the same company finished eleven jobs. Eight came in at or under budget, and the three overruns were caught early enough to renegotiate before completion. Real-time job cost visibility turned out to be more valuable than any forecast the accountant ever produced.

When I checked back at month eight, the foremen had stopped complaining about the tablet routine. One said it actually saved him from arguing over hours every week — a benefit nobody predicted. The ERP Consulting team confirmed the habit had stuck in their month-nine check-in, and that’s the part business owners underestimate: a good process survives because it makes people’s jobs easier, not harder.

Here’s a number that should scare any distributor: 214. That’s how many wrong shipments a 40-person plumbing supply company sent out in one year. Customers received the wrong valve, the wrong thread size, or the wrong quantity — and the company only found out about 61 of those mistakes because someone complained. The rest surfaced months later as lost reorders.

When the general manager finally studied the return data, the errors clustered around one thing: order entry, not picking. Pickers pulled the right products off the shelf every time. The mistake was happening at the computer screen, and that’s where the ERP Consulting engagement began.

One wrong digit was behind most of the damage

The sales team typed part numbers from memory. A 1/2-inch brass adapter and a 3/4-inch adapter differ by a single digit, and the dropdown list didn’t show the dimension unless you clicked deeper into the screen. Multiply that by ten sales reps, four thousand products, and a target of 60 seconds per order, and you get 214.

I’ve walked through this exact scene in other businesses. The fix is not retraining people to type more carefully. Careful people still make typos under pressure. The fix is building guardrails into the order screen, and those guardrails don’t cost a dime in new software.

Three small screen changes that cut errors by 85%

1. When a sales rep selects a part, the full description plus a photo appears before the order can be saved — one extra click, zero extra typing.
2. The system warns if the customer ordered the same item in the past six months and the new quantity differs by more than 30%.
3. High-return SKUs carry a visible flag on the order line, so the rep double-checks before confirming.

Within 60 days, the wrong-shipment rate fell from 2.6% of orders to 0.4%. The owner estimated the change saved $47,000 a year in freight, restocking labor, and refunds — plus the customers he stopped losing to angry follow-up calls.

The ERP Consulting follow-up call at month three checked one thing: were the guardrails still slowing anyone down? Nobody complained. The team had one question for the system — “is this the right part?” — answered at the moment it mattered most, instead of when a customer found the problem for them.

On a Friday afternoon, the production manager at a 70-person precision machining shop opened the stockroom door and couldn’t find 300 brass fittings the system said were on the shelf. He checked again — same screen, same number. The fittings were simply not there. That moment started a six-week ERP Consulting engagement that changed how this shop runs.

Why the inventory numbers kept lying to us

Three root causes surfaced quickly. The receiving team counted parts by hand and entered numbers hours later, so the system and the shelf never matched. Second, the shop used three different naming conventions for the same part — one for purchasing, one for the lathe operators, one for shipping.

And third, nobody ever did cycle counts. The annual physical count happened in December, and by February the numbers were fiction again.

The ERP Consulting team asked a blunt question: if you can’t trust your stock count, how do you know which jobs to schedule next week? The answer was, we didn’t. We were buying parts we already owned and stalling jobs that had plenty of material.

The fix cost $0 in software and took 30 days

We didn’t buy anything new. We changed four processes and stuck to them.

• Receiving counts at the shelf, not the desk — within 30 minutes of delivery, not end of day.
• One part number per part, enforced everywhere, with the ERP Consulting team mapping the old codes to the new ones.
• Cycle count 20 SKUs every Friday, rotating through the full list six times a year.
• A “material hold” flag for any part with a count variance over 2%, so nobody plans around a bad number.

What 30 days of discipline changed

After one month, inventory accuracy went from 88% to 96%. After three months it hit 99.1% and stayed there. We stopped an estimated $38,000 in duplicate purchases over that quarter, and job scheduling became calm. The production manager now checks Friday cycle-count results like he used to check sports scores.

The lesson worth passing on: inventory accuracy is a behavior problem, not a software problem. But good ERP Consulting gives you the exact routine to make that behavior stick. If your stock numbers feel shaky, run one cycle count next Friday and watch what turns up. I suspect you’ll be surprised too.

Let me tell you a terrifyingly ordinary story. A $12 million industrial parts distributor had used the same Excel workbook for a decade. Sales orders, purchase orders, shipping schedules, all in one massive file with 14 tabs. It worked, mostly.

Then one Tuesday afternoon, someone typed 5,000 units of bearing instead of 500, and the mistake cascaded through six weeks of purchase orders before anyone noticed.

What happened next is the part I want you to remember. The wrong quantity triggered a huge rush order from the supplier. The supplier shipped it. The warehouse ran out of space.

The customer’s actual order was delayed three weeks while the company tried to unload the extra bearings. One keystroke, and three departments spun in circles for a month.

Why this wasn’t really about the typo

The typo was just a symptom. The disease was that nobody could see the full picture. The sales order lived in one tab; the purchase order was born in another, referencing a different row. The receiving team used a third file entirely.

When the numbers disagreed—and they always disagreed somewhere—there was no single source of truth. Just three versions of “the same” information.

Here’s a hard truth from years of consulting: if your critical business numbers live in a file that only one person understands, you don’t have a system, you have a hostage situation. If that person wins the lottery or gets sick, your entire operation is paralyzed.

The scary list of what breaks quietly

• Version confusion: you email the spreadsheet to a colleague, they save a copy, edit it, email it back, and now nobody knows which file is current
• Hiding errors: Excel can’t tell you when a cell formula was accidentally overwritten, it just quietly shows the wrong number
• No alarms: in a proper system, an order that needs approval sits in a queue and someone gets notified; in a spreadsheet, it just sits there until someone remembers to ask

What a real system changes about Monday mornings

With one integrated system, the order flows from sales to purchasing to receiving to shipping without anyone re-keying it. The mistake scenario changes too: if a quantity looks abnormal, the system flags it against that customer’s history. One of our manufacturing clients caught a would-be $47,000 over-purchase before it even hit the supplier because the system questioned a quantity that was 8 times the historical average. When we map this during an ERP Consulting engagement, we always start with the question: which decision, if wrong, hurts most?

Software isn’t magic. But the difference between a spreadsheet and a structured system is the difference between guessing and knowing. A structured system shows you the full consequences of a single change before you commit to it.

If you’re still on spreadsheets, here’s tonight’s homework: open your main file and look for all the places where a number is typed by hand that could instead be calculated. Find the five cells that, if wrong, would hurt you the most, and put a visible warning color on them.

That’s step one. Step two is having an honest conversation about what your business would do for a month if that file vanished. If that thought scares you, it’s time to talk to someone like ERP Consulting about introducing real structure before disaster introduces itself—not after.

A specialty food company with 40 employees and $8 million in revenue called me with a surprising question. They’d just turned down a big new retail contract because they were terrified they couldn’t handle the paperwork. The owner said, “We’re too small for a real system, aren’t we?” My honest answer surprised them: it depends on what the growth is doing to your margins.

The warning signs were all there. They were paying a bookkeeper 30 hours a week just to enter orders and chase down purchase records. Customer service reps were keeping order details in their email inboxes. And two large customers had already complained about being billed twice in the same month.

The real cost of staying small

People think ERP Consulting is only for big factories with hundreds of employees. That’s outdated thinking. The real question is complexity, not headcount.

This company had 14 raw ingredients, 22 finished products, and only about 30 suppliers. That’s simple enough to run well. But they also had tight food-safety traceability requirements and a retailer demanding electronic packing slips.

The honest threshold is around $5 million in revenue, when order volume and compliance demands start multiplying the manual work. Below that, a well-organized spreadsheet plus good discipline might hold up. Above it, the cracks appear fast.

What we did instead of jumping into a big project

1. First, we built a two-week “cost of chaos” log: every time someone re-typed data, searched for a document, or fixed a double billing, they wrote it down with a time estimate
2. Then we totaled it: the log showed 41 hours per week of pure waste, roughly one full-time salary every single week
3. That number changed the conversation from “is this worth it” to “how did we survive this long”

With that evidence, the owner stopped debating and started planning. We implemented a system sized for their actual complexity, not a bloated enterprise package. The implementation took nine weeks, not nine months.

What changed in the first quarter after go-live

The bookkeeper’s order entry time dropped from 30 hours a week to 6. The double billing complaints stopped completely. And the food-safety audit that used to take two days of gathering paper records? It now takes about two hours because everything is traceable from one screen.

The proudest moment was the retail contract they’d turned down. They renegotiated it, signed it, and shipped the first order without a single error. All because they stopped treating “small business” as an excuse for chaos.

If you’re in the $4–8 million range and feeling stretched, do the two-week waste log before you buy anything. Show the CFO the math in dollars, not hours, because hours feel abstract to some owners. And when you’re ready, find a partner who starts by documenting your workflow, not by showing you product demos. That’s exactly the conversation we have at ERP Consulting: we start with your numbers, your bottlenecks, and your actual paperwork mess, not with a features list.

A plumbing supplies distributor with locations in three cities called me in a panic. Sales were up 35% year over year, but net profit was flat. Nobody could explain why.

Each warehouse ordered its own stock, kept its own records, and answered to its own manager. The owner had to phone three people to find out how much total inventory they held. Even then, the answers didn’t quite add up.

Here’s the thing about growth: it hides disorder. When you’re small, you can keep everything in your head. Add a second and third location, and suddenly the left hand doesn’t know what the right hand is buying.

The specific mess we uncovered

One warehouse was sitting on 90 days of a certain copper fitting. Another warehouse, 400 miles away, was paying a premium for a rush order of the exact same fitting. That waste alone was roughly $15,000 a year.

And it wasn’t the only one. I counted eleven items where two locations were both overstocked while occasionally emergency-shipping from each other.

The root cause was simple: each location was measured on its own inventory and its own sales. There was no incentive to share or to think about the company’s total cash. This fragmented thinking is the first thing ERP Consulting challenges, because software can’t fix a culture that rewards hiding.

• Stop measuring each warehouse’s inventory accuracy in isolation—measure the company’s total stock value and the number of inter-warehouse transfers that actually happened
• Make one person responsible for “slow-moving capital,” the dollars sitting on shelves that haven’t moved in 90 days, and review that number every Monday
• Before any purchase order above $5,000, require a quick check of stock levels at all other locations

What happens when the numbers finally line up

We put all three locations on one connected view. For the first time, the owner could see total company stock across all sites with one log-in. Within two months, they found $190,000 in unnecessary inventory. They sold off the excess, used the cash to pay down their credit line, and stopped the premium freight nonsense almost entirely.

But the quieter win was even bigger. The warehouse managers started talking to each other. One discovered the other had a crew with spare capacity, and they started swapping labor instead of both paying overtime. That’s the kind of collaboration that can’t be forced by an email from headquarters; it only happens when everyone’s looking at the same numbers.

When to call for help

The signal that you’ve outgrown your spreadsheets is simple: it takes you more than ten minutes to answer “how much total inventory do we own right now, in dollars, across all locations?” If you can’t answer that instantly, you’re flying blind.

I’ve seen this scenario play out in food, hardware, apparel, auto parts, you name it. The solution always involves the same two steps: standardize how every location counts and categorizes its stock, then put the numbers in one shared place. That’s precisely where ERP Consulting earns its keep—not in teaching you software, but in forcing the discipline to make the data comparable. Start by making all your locations use identical product names and units; you’d be shocked how often “1 box” in one warehouse means “12 units” in another.

Picture this: a company spends eight months and a lot of money implementing a new system. Go-live day arrives. Three weeks later, half the sales team is still working from their personal notebooks, whispering “I’ll input it tonight” and then forgetting. The warehouse supervisor is hiding the old paper forms in a drawer.

You can buy the best software in the world and it will fail if people refuse to touch it.

I walked into this exact situation at a window manufacturer with 90 employees. The owner’s first instinct was more training sessions. But the problem was trust, not understanding. Senior staff had seen three “new systems” come and go in ten years, and each one was abandoned within a year.

I’ve watched this pattern repeat in dozens of companies. That’s why ERP Consulting looks at people before it looks at screens.

The real reason people resist

It wasn’t laziness. Older warehouse staff worried the system would make their experience useless. Sales reps worried management would finally see exactly how long they spent on each account. And honestly? Some of those worries were justified.

The system did expose inefficiencies. The trick was framing that exposure as a tool for them, not a weapon against them.

The turning point came when we let the loudest critic of the system help design the daily workflow. He was a warehouse lead with 22 years of experience. Within a week, he found a way to cut two hours of scanning time per shift. After that, he became the system’s biggest champion.

• Find the most vocal skeptic and give them a real role in configuring how their team uses the system
• Put the old paper forms in clear physical view but require a brief explanation in writing whenever someone uses them
• Publish a weekly “wins” board listing specific numbers, like “order entry time dropped from 9 minutes to 4”

How fast can attitudes actually change

Faster than you’d think, if the evidence is concrete. By day 45, the warehouse lead was showing new hires how to scan. By day 60, the sales team was logging in on their own before their morning coffee because they discovered the system showed them their commission status in real time. Nobody had to nag them.

Here’s the principle that mattered: people accept a new system when it solves a problem they personally feel, not when it solves a problem the CEO describes. Also, you can’t out-train a trust problem—giving people ownership beats another slideshow every time.

What I’d tell any owner before go-live

Set aside 30% of your implementation energy for the human side before you even pick software. When you’re stuck and the rollout is going badly, that’s exactly when to bring in an outside pair of eyes. ERP Consulting often gets called in after a failed launch, and in nine cases out of ten, the fix is simpler than the owners feared: stop defending the system, start listening to the critics, and redesign the workflow together.

Your next step is small but real: schedule a 30-minute private conversation with the one person most opposed to the change and ask them what the system makes worse for them personally. Write down their answer. That one conversation tells you more than any vendor demo ever will.