← All posts

I spent the first days of a manufacturing engagement on site, sitting with the retail team and then the shop floor. I was not there to build anything yet. I was there to watch an order move.

One order had been in a status called “Needs Clarification” for thirteen days. There was no clarification attached to it. No message, no owner, no note about what was unclear. The dealer thought the manufacturer had it. The manufacturer thought the dealer owed them an answer.

What the audit found

• 1Three competing status systems: the portal, the CRM and a spreadsheet, each telling a different story about the same order.
• 2Dealer messages buried in a system the office staff rarely opened.
• 3Pricing waited for a manual review because the markup rules were in someone’s head.
• 4The fabrication math lived in a protected workbook. On one machine it would not open at all.

“The clarification loop had no clarification in it.”

What the rebuilt system refuses to allow

The MVP shipped in three weeks: a dealer portal and a staff CRM on one shared database, 34 documented markup rules, a formula engine with its derivations written out in plain language, and seven station sheets plus travel tickets generated per order.

The small rule that mattered most: you cannot move an order to “Needs Clarification” without writing what needs clarifying. Not through the form, not by drag and drop. The interface enforces it. Nonstandard requests route to a person rather than through the formula engine.

INBOX AGENT ✓ YOU

Two things I got wrong first

The first screens looked like a portfolio piece. The people using them were on a shop floor, some of them older, reading from a distance. The type got bigger and the interface got plainer. Paper travel tickets stayed, because they worked.

And a required message prevents a silent handoff. It does not prevent every stalled order. I try not to claim more than the system does.

Keep reading