Your Floor Didn't Have a Workflow Problem Until Your Software Did
Every year between Christmas and New Year's, we shut down and spent a full week counting inventory.
Not because we wanted to. Because the numbers were so far off from reality that the only way to get them close was to stop everything, bring in the whole team, and physically count every roll, every box, every bag of material on the shelves. For a week. During the holidays.
And at the end of it, after all that time, we'd still write off a significant chunk in missing inventory. Then the accounting side of the business would spend another two or three weeks doing forensic work — trying to figure out what was actually a loss versus what just got miscategorized somewhere. Most of the time there was no clean answer.
This was a real operation. Solid revenue, substantial inventory, good customers. And almost completely in the dark about what it actually had on the shelves.
The root of most of it traced back to one thing: there was no real Bill of Materials.
The Recipe Nobody Wrote Down
Converting tape sounds simple. You start with a roll, cut it into pieces, ship the pieces. The math isn't complicated — a 36-inch roll yields 1,296 linear inches, so a one-inch piece yields 1,296 cuts. That part everyone knew.
What nobody had written down in any reliable way was everything else. The secondary materials. The liner. The waste percentage on a difficult cut. The labor time per piece. Those things lived in people's heads, got recalculated by hand every time a job ran, and got forgotten about during inventory because tracking them felt like more trouble than it was worth.
The warehouse would get a handwritten note on a clipboard. They'd do their own math to figure out how many rolls to pull. Meanwhile the office was doing the same math separately to build the quote. Nobody was working from the same document. Every job was a mild improvisation.
"Without a BOM that accounted for every material going into a job, including the cheap stuff and the waste, the numbers were always going to be a guess."
The result was years of underquoting converted items. Not because anyone was being careless — because nobody had ever built the actual recipe. Without a BOM that accounted for every material going into a job, including the cheap stuff and the waste, the numbers were always going to be a guess.
We eventually got there with the right system. Set up all the parts, registered the unit of measure conversions once, built out the BOMs properly. And the first time the system printed a clean job summary — every material, every quantity, every cost, laid out like a recipe card — people loved it. That one printout replaced a clipboard, a calculator, and three separate conversations that used to happen every single time a job ran.
The Band-Aid Problem
Here's what I've learned about putting any new system in place, whether it's an ERP, a compliance requirement, or even just a better spreadsheet: it doesn't create problems. It exposes them.
When we tried to set up a proper BOM structure early on, we realized fast how little we actually understood about our own process. We thought we had a handle on it. Turns out we had a collection of workarounds held together for years by one or two people who kept things running through institutional knowledge and manual adjustments. The software couldn't run on institutional knowledge. It needed clean inputs.
"The places where systems break down are almost always the places where the process was already broken and someone was quietly patching it."
The places where systems break down are almost always the places where the process was already broken and someone was quietly patching it. The system just makes the patch visible. That's uncomfortable, but it's actually the most useful thing a new implementation does — it tells you exactly where the real work is.
The fix isn't always technical. Sometimes it's process. Sometimes it's documenting a handoff that two people have been doing informally for years and never written down. Sometimes it's as simple as deciding who touches the data and who doesn't, and then holding that line.
The Map You've Never Drawn
The other thing that consistently surprises shop owners — and I've seen this play out enough times to call it a rule — is how many steps are actually in their process.
A shop with five people thinks it operates simply. But when you sit down and map it out step by step, you usually find 15 to 18 distinct steps and six or seven handoffs. In a shop with five people. The complexity is there. It just hasn't been visible because everyone's been running on habit.
"You can't make that call until you can see it."
The map also shows you which steps are adding value and which ones exist because nobody ever questioned them. Some are required — quality, safety, compliance. Some are waste that crept in over time and stayed because the process was never written down. You can't make that call until you can see it.
Two Tools, One Conversation
The ClearBridge BOM Tracker and the Operational Process Mapper address two sides of the same problem.
The BOM Tracker gives you the recipe. Register your materials and their unit of measure conversions once. For each job, enter your quantities, waste percentage, and labor rate. The tool calculates exactly how much material to order, what the job actually costs per piece, and produces a clean summary you can use to quote, order, and track against. The liner doesn't get forgotten. The waste gets accounted for. The number is real.
The Process Mapper gives you the workflow. Add your steps, classify each one as value-added, non-value-added, or required non-value-added, and render the map. What comes back is a visual process flow with a waste analysis — how much of your process time is producing output versus moving paper around.
Both tools are free. Both take less than an hour to get meaningful output from. And both tend to show you something you didn't expect to see.
If what they surface points to a deeper structural problem — a process that needs a real rebuild, a BOM architecture that needs to connect to your ERP, a workflow that's been running on band-aids long enough that fixing it requires actual floor time — that's where the consulting work starts. When you're ready for that conversation, we're here.
Map Your Process. See the Waste.
Ready to map it out?
ClearBridge Operating Solutions provides fractional operations consulting to small industrial manufacturers and machine shops in Connecticut and Western Massachusetts. Let's dig into what's actually happening in your operation.
