Closing the loop between the quote and the cut
Lee Herron·Jun 5, 2026·2 min readAsk where a manufacturer loses margin and everyone points at pricing. But the quietest leak isn't the price you quoted — it's the distance between what you quoted and what actually happened on the floor.
You quoted 20 minutes of setup. It took 45. You quoted one grade; the shop swapped it for what was in stock. Nobody logs it, nobody tells the estimator, and next quarter you quote the same job at the same wrong number.
The loop that isn't closed
Most quoting systems are one-directional. Inputs go in, a number comes out, the job ships. The floor's reality — real times, real substitutions, real scrap — never flows back to the model that made the estimate. So the estimate never learns.
Closing that loop doesn't take a new ERP. It takes a channel:
- Capture what actually happened — job times, material used, rework — at the point it happens, not in a month-end reconciliation.
- Route it back to the estimate that job came from, so the two can be compared.
- Surface the gaps where quoted and actual diverge consistently. Those are your mispriced product lines, hiding in plain sight.
Why agents help here
This is exactly the kind of dull, cross-system plumbing that never gets built because no one has a spare week for it. An agent with the right hands — read the job status, match it to the spec, flag the variance — can run it continuously in the background instead.
It's not glamorous. There's no clever model. It's a machine patiently noticing that the "quick" bracket takes twice as long as you think, every single time.
Start with one number
You don't need the whole loop on day one. Pick the single number you least trust — setup time is a good bet — and just start comparing quoted vs. actual for it. One honest number, fed back consistently, will pay for the effort before you've closed anything else.
The tools for the plumbing — the MCP servers that read the floor, the skills that reconcile it against the quote — are the same ones in the marketplace. The hard part was never the technology. It's deciding to look.
Get new posts by email
Occasional field notes on design automation and AI. No spam.
