Fix the handoff from sales to delivery

What broken handoffs look like

Sales promises a start date that operations learns about on the day. A crew shows up without the right materials because the details were in a text message. A customer explains their problem three times to three people. Billing finds out a job changed scope after the invoice goes out.

• Customers repeat the same information to different people.
• Jobs start late because something was missing at the handoff.
• Teams blame each other and both are partly right.
• Each team uses a different tool, and none of them talk.
• There is no written list of what must be passed at each handoff.

Why handoffs break

Three causes show up again and again:

• No single owner. The person sending thinks the job is done. The person receiving thinks it has not started.
• No standard intake. Each salesperson passes different details in a different format.
• Different tools. Sales lives in the CRM, operations in a scheduling tool and delivery on paper. The handoff is someone retyping.

The problem gets worse at the point where a company adds its first layer of middle management, usually somewhere between 36 and 85 people. That is the band we call The Break Point.

What it costs

Every broken handoff creates rework, delays and unhappy customers. It also burns goodwill between teams, which is hard to measure and easy to see. Searching for missing information is a real cost: Atlassian (2025) found teams spend about a quarter of the workweek searching for information.

A one page handoff protocol

1. Map it. Draw the path a customer takes from first call to final invoice. Mark every point where work changes hands.
2. Pick the worst one. Choose the handoff that causes the most complaints or rework.
3. Define the packet. List exactly what must be passed: fields, documents, photos, promises made.
4. Name owners. One person sends, one person accepts, and acceptance is explicit.
5. Track returns. Count how often work comes back incomplete each week.

What good looks like

A good handoff is boring. The sender fills in a standard form with every required field. The receiver accepts it explicitly or sends it back with a reason. The customer never repeats themselves because the information traveled with the job. And once a week someone looks at how many handoffs came back incomplete and fixes the cause, not the person.

How we fix it

We map the full customer lifecycle, the same first step that stabilized our founding engagement, then redesign the handoffs with your teams in the room.

• Customer lifecycle map with every handoff marked.
• Handoff protocols: what is passed, by whom, by when and where it lives.
• A RACI for the handoffs so ownership is explicit.
• Standard intake forms built inside the tools you already use.
• KPIs for handoff quality, reviewed weekly.

Department level handoffs start in The Blueprint. Cross department governance from Sales to Ops to Delivery is the core of The Ensemble.

Questions owners ask