Sales-to-Ops Handoff in Manufacturing: Where Margin Goes to Die

The deal is closed. The spec is agreed. The delivery date is set. And then the details start dying.

Somewhere between WhatsApp, the shared inbox, and the ERP, the non-standard finish disappears. The adjusted delivery window gets forgotten. The revised spec that the customer mentioned in the car park on the way out ("Oh, one more thing, can we change the fitting to the 12mm version?") never reaches production.

Three weeks later, the wrong product arrives on site. Your customer calls. Your ops team scrambles. Your margin on the deal gets eaten by rework. And nobody can quite pinpoint where it went wrong, because the information travelled through six different channels and four different people before it reached the system that actually matters.

This is the sales-to-ops handoff problem. Every field sales company has it. Almost none of them measure it.

The 23-step information journey nobody maps

I once sat with an operations manager at a manufacturing company and mapped every information handoff between the field sales team and the operations team on a typical deal. We expected 8 or 10 distinct transfers. We counted 23.

Customer requirements: from the site visit conversation to the rep's notes. Rep's notes: from memory to a WhatsApp message to the internal sales coordinator. Sales coordinator: from the WhatsApp message to an email to operations. Spec details: from the email to a shared spreadsheet. Pricing: from the spreadsheet to the ERP. Delivery date: from the initial conversation to the project plan. Changed delivery date: from a follow-up phone call to a voicemail that may or may not get listened to.

Of the 23 handoff points, only 4 were fully captured in a system with audit trail and version control. The other 19 relied on human memory, email searching, or Karen's spreadsheet. (Every company has a Karen. The operations person who's been there for years and maintains the spreadsheet that nobody else fully understands.)

Each handoff point is a potential failure point. Information doesn't just get lost at handoffs. It degrades. Numbers get rounded. Spec details get simplified. Qualifications get dropped. "The customer said they'd prefer the 12mm but the 10mm would work in a pinch" becomes "10mm" by the time it reaches production, because someone along the chain made a reasonable judgment call without the full context.

What actually gets lost

The information losses fall into predictable categories. Knowing them helps, because once you can name the pattern, you can measure it.

Spec changes after the initial quote. The customer mentions a modification during a site visit or follow-up call. The rep makes a mental note. Sometimes it gets captured. Often it doesn't. The order proceeds with the original spec. Wrong product gets manufactured.

Estimated cost per incident: depends on the product, but rework typically runs 20% to 40% of the original order value. For a £10,000 order, that's £2,000 to £4,000 in rework cost, plus the damage to the customer relationship which is harder to quantify.

Timeline shifts that don't propagate. The customer's project gets pushed back two weeks. The rep hears this in a corridor conversation and doesn't think it's worth logging because it's "only two weeks." Operations has already scheduled production against the original date. Materials ordered. Capacity allocated. Now everything needs rescheduling, and the customer whose timeline didn't change gets bumped because the slot is taken.

Contact changes. The person your rep was dealing with gets promoted, leaves, or goes on long-term leave. Their replacement has different priorities, different authority levels, and no knowledge of the ongoing conversation. This information sits in the rep's head for days or weeks before the office discovers it during a follow-up call that goes badly.

Custom terms and conditions. Special payment terms agreed during negotiation. Non-standard warranty arrangements. Delivery conditions specific to the site. These verbal agreements sometimes make it into the contract, sometimes don't, and almost never reach the person responsible for fulfilment in a clear, actionable format.

Competitive intelligence. The customer mentions a competitor's offer during the sales process. Pricing, lead times, warranty terms, product quality observations. This is exactly the kind of intelligence that should shape how you compete on the next deal, but it stays in the rep's memory, mentioned in passing to their manager, and never reaches a system where it can be analysed or acted on.

The cost nobody tracks

Companies don't measure the cost of bad handoffs because the costs are distributed across departments and disguised as other problems.

The wrong product ships. It shows up as a returns cost, attributed to "order error." Nobody traces it back to a spec change during a field visit three weeks earlier.

A deal stalls because the office team followed up with the old contact. It shows up as a lost deal, attributed to "timing" or "competition." Nobody traces it back to a personnel change the rep knew about but didn't log.

Production gets rescheduled because a timeline changed. It shows up as a planning variance, attributed to "customer delay." Nobody traces it back to a conversation that never made it into the system.

From the companies I've worked with, the aggregate cost of information losses between sales and operations typically runs between 3% and 7% of revenue. For a £30 million manufacturer, that's somewhere between £900,000 and £2.1 million per year. In one case, a manufacturer reclaimed 351,000 hours per year by systematically addressing these handoff failures alongside their quoting and CRM problems. The same pattern shows up across hidden manual processes in UK manufacturing and the ghost workflows nobody documents. Not from bad products. Not from bad people. From information that started in one place and didn't arrive in another. Make UK and McKinsey both flag this operational drag as one of the largest unmeasured productivity gaps in mid-market manufacturing.

The Ell Advisory website estimates rework costs for a typical field sales company at around £60,000 per year. That's a conservative figure for smaller companies. For mid-market manufacturers doing complex configured work, it's often significantly higher.

Why WhatsApp runs your manufacturing operations

Here's something I've noticed at every field sales company I've worked with: WhatsApp is the de facto business communication system.

Reps send photos of site conditions to the office via WhatsApp. Spec changes get communicated in group chats. Delivery confirmations come as text messages with photos. Customer complaints get forwarded as screenshots.

This isn't a technology failure. It's a pragmatism success. WhatsApp works on site, in the van, with poor connectivity. It handles photos, voice notes, and documents. Everyone already has it. Nobody needs training. The barrier to use is zero.

The problem is that WhatsApp is a communication tool, not a system of record. Information that travels through WhatsApp is unsearchable, unstructured, and invisible to every other business system. When the ops team receives a spec change via WhatsApp, they need to manually transfer that information into the ERP. If they're busy (they're always busy), it waits. If they miss it (these things happen), the spec change doesn't reach production.

The solution isn't banning WhatsApp. Reps will use it anyway because it works. The solution is building bridges between the informal channels where information naturally flows and the formal systems where it needs to end up. AI-powered data extraction from messages, automated routing to the right system, confirmation workflows that catch missing updates before they become problems.

The three types of handoff company

After working with dozens of field sales businesses, I've noticed they cluster into three groups based on how they manage the sales-to-ops transition. Recognising which one you are helps decide where to start fixing things.

The "hero" company. Relies on one or two experienced ops people who hold the whole process together through personal knowledge and effort. Karen's spreadsheet is the backbone. When deals go smoothly, it's because Karen caught the discrepancy. When they go wrong, it's because Karen was on holiday. The process is a person, not a system. This works until it doesn't, and it usually doesn't at about the 15-rep mark.

The "process" company. Has documented workflows, standard templates, and defined handoff stages. The CRM has mandatory fields. There's a handoff checklist. It looks good on paper. The problem is that the formal process is too slow or too rigid for field reality, so reps work around it. The documented process and the actual process are two different things, and management only sees the documented one.

The "instrumented" company. Captures information at the point of origin using the tools reps naturally use. Voice notes that auto-populate CRM fields. Photo capture that tags into the order. Mobile forms that take 30 seconds instead of 5 minutes. The system adapts to how people actually work rather than demanding people adapt to how the system was designed. These companies are rare, but they exist, and their error rates are typically 60 to 80% lower than the other two types.

Most companies are type one or two. The goal isn't to jump straight to type three. It's to identify which type you are and take the next practical step.

The handoff audit checklist

Before you fix the problem, you need to see it clearly. Here's how to map your sales-to-ops handoffs.

Pick a recent deal that had a problem. Returns, rework, customer complaint, delivery error. Trace the information backwards from the error to the original conversation. Document every handoff point: who told whom, through what channel, when, and what was (or wasn't) captured in a system.

Then do the same exercise for a deal that went smoothly. Compare the two. The difference will show you exactly where your process is vulnerable.

Questions to ask at each handoff point: Is this step captured in a system with an audit trail? If the person responsible is on holiday, would someone else know to do it? Is there a verification step that catches errors before they reach the next stage? How long does information typically sit at this point before moving forward?

Most companies find that their smooth deals succeed despite the process, not because of it. They succeed because experienced people fill in the gaps through memory, relationships, and informal communication. That works until someone leaves, takes holiday, or handles too many deals at once.

A typical handoff lifecycle: where the leaks happen

How to fix the sales-to-ops handoff

The companies that handle handoffs well share a few approaches.

Reduce the number of human intermediaries. Every time information passes from one person to another, it degrades. The fewer people between the field conversation and the operating system, the better the data quality. Voice-to-CRM capture. Automated data routing. Direct field-to-ERP pipelines.

Capture at the point of origin. The best time to capture a spec change is when the customer mentions it, not three handoffs later. Mobile tools that let reps log changes in the moment (voice notes, quick-capture forms, photo annotation) mean the information enters the system at its most accurate.

Build verification loops. Before an order moves from sales to production, an automated check compares the current spec against the original quote, flags any discrepancies, and requires confirmation. This catches the spec changes that fell through the cracks before they become manufacturing errors.

Kill the spreadsheet by making it unnecessary. Karen's spreadsheet exists because the official systems failed her. If the CRM, ERP, and project management tools actually handled the data in the way the business needs, nobody would maintain a workaround. But killing the spreadsheet requires understanding the business logic it encodes first. The conditional formatting. The custom formulas. The institutional knowledge baked into cell references.

The compounding cost of waiting

This problem gets worse over time. As your business grows, the number of handoff points increases. More products. More customers. More customisation. More people in the chain. The informal processes that worked when you had 5 reps and 50 customers don't scale to 20 reps and 500 customers. But they persist because nobody formally replaced them.

The real cost of slow quoting compounds with handoff failures — a quote that arrives late AND contains spec errors from a broken handoff is a deal you've already lost.

Meanwhile, your competitors who fix this get compounding benefits. Better data means fewer errors. Fewer errors mean higher margins. Higher margins fund further improvement. The gap widens — and as sales capacity planning and CRM data quality become measured metrics, the laggards' problem becomes board-visible. Modern Machine Shop has documented this widening gap across US shops; the UK pattern is identical.

The sales-to-ops handoff isn't a glamorous problem. It doesn't make for exciting board presentations or conference talks. But it's where a measurable percentage of your margin goes to die, every week, in predictable and preventable ways.

Related Reading

• AI Quoting for UK Manufacturers: What Works, What Doesn't, What It Costs
• The Real Cost of Slow Quoting in UK Manufacturing
• CPQ vs Custom AI Quoting for UK Manufacturers
• How One Manufacturer Reclaimed 351,000 Hours
• Ghost Workflows: The Hidden Manual Tasks Eating Your Margin
• Hidden Cost of Manual Processes in UK Manufacturing
• Sales Capacity Planning: The Metric UK Manufacturers Miss
• Why AI Projects Fail Without Process Redesign

Frequently Asked Questions

How much revenue do UK manufacturers lose at the sales-to-ops handoff?

Across mid-market manufacturers we've worked with, aggregate handoff information losses run between 3% and 7% of revenue. For a £30 million manufacturer, that's £900,000 to £2.1 million per year, distributed across rework costs, late-delivery penalties, lost deals from contact-change failures, and goodwill credits to retain customers after errors.

Why does the handoff problem hide in the financials?

Because the costs are distributed across departments and disguised as other categories. Wrong-product shipments show up as "order error." Stalled deals show up as "lost to competition." Production reschedules show up as "customer delay." Nobody traces these back to the original handoff failure three weeks earlier, so the root cause never reaches the P&L narrative.

How many handoff points exist in a typical deal?

When mapped end-to-end, a typical mid-market manufacturing deal contains around 23 distinct information transfers between field sales and operations. In the case we audited, only 4 of those 23 were captured in a system with audit trail and version control. The other 19 relied on human memory, email searches, or a maintained spreadsheet.

Should we ban WhatsApp to fix this?

No. Reps will use WhatsApp anyway because it works in vans, on sites, and with poor connectivity. The fix is building bridges between the informal channels where information flows naturally and the formal systems where it needs to land — AI extraction from messages, automated routing to CRM/ERP, and confirmation workflows that catch missing updates.

What's the difference between a "hero" company and an "instrumented" company?

A hero company runs on one or two experienced ops people who hold the process together through personal knowledge — Karen's spreadsheet is the backbone. An instrumented company captures information at the point of origin using tools reps already use (voice notes, photo capture, mobile forms). Error rates at instrumented companies are typically 60% to 80% lower.

How quickly can a handoff fix pay back?

For mid-market manufacturers, the dominant ROI driver is rework reduction. Rework typically runs 20% to 40% of order value, so eliminating even half of spec-change failures pays back the intervention within 3 to 6 months on most pipelines. The compounding gain — better data leading to better forecasting, planning, and capacity allocation — accrues over the next 12 to 18 months.

Where should we start if we want to fix this?

Run a handoff audit on one recent problem deal and one smooth deal. Trace every information transfer between field and factory. Document who told whom, through what channel, and what was captured in a system. The gap between the two deals shows you exactly where to instrument first. The Hidden Waste Audit does this systematically.

Want to see where your handoffs are leaking? Our Hidden Waste Audit maps your field-to-office information flow and identifies the gaps costing you margin. Five minutes. No pitch. Or book a 15-minute call to walk through the maths with one of our advisers.

Sources: Manufacturing and construction operational analysis, Ell Advisory client data, SPOTIO Field Sales Report 2026, Make UK, McKinsey, BCG, Modern Machine Shop, Industry Week, Gartner.