Ask who designed your sales-to-onboarding handoff.
Enjoy the silence. Maybe someone eventually offers a name — a person who left in 2022, or “I think that’s just how Dana and Marcus started doing it.” That’s the answer, actually. That’s how nearly every handoff in your company came to exist: two people worked out a routine between themselves, once, under deadline, and the routine calcified. Then the people changed and the routine survived them, passed down as folklore. Nobody designed it. It just hardened.
Which means the most consequential infrastructure in your revenue engine — the transfer points where every dollar changes hands — is improvised, unwritten, and maintained by oral tradition. (That last phrase gets its own chapter. Soon.)
—
Here’s what an undesigned handoff is missing. Anatomy of the gap, four parts:
**No entry criteria.** What makes a lead “ready” for sales? What makes a deal “ready” for onboarding? Nobody’s defined it, so the sender decides unilaterally — usually under quota pressure — and the receiver inherits whatever arrives. Half the friction between your departments is really an argument about a definition nobody has ever written down.
**No payload.** What information must travel with the transfer? Undefined — so it doesn’t. The receiving team gets a name and a closed-won notification, and everything else the customer already said — their goals, their constraints, the promises made in the sales cycle — stays behind in someone’s head, someone’s inbox, someone’s shadow spreadsheet.
**No acknowledgment.** Did the receiver actually receive? Nobody confirms, so every handoff ends in a small act of faith. The sender assumes it landed. The receiver assumes it’s coming. The customer sits in the gap between two teams, each certain the other one has her.
**No return path.** What happens when the transfer arrives incomplete? Nothing’s defined, so the receiver just… copes. Re-gathers. Re-qualifies. Absorbs — Chapter 5, reporting for duty at every handoff in the building.
—
Track teams understand something businesses don’t.
In a relay, the baton exchange is the most dangerous moment of the race — so it’s the most *practiced* moment of the race. There’s a marked zone. A protocol. A call. Hours of rehearsal for a two-second transfer, because everyone accepts that races are lost in the exchange, not on the straightaways.
Your company practices the running and improvises the baton. Every department rehearses its own leg relentlessly — sales trains on closing, delivery trains on delivering — and the exchanges between them have never been practiced once, by anyone, in the history of the company. Then the baton drops, and leadership reviews the runners.
And your customers feel every drop, personally. Every time a customer has to repeat their story — to the onboarding team, to support, to the account manager who “just wants to get up to speed” — they are experiencing your undesigned handoff from the inside. *Why am I explaining this again?* is not a service failure. It’s an architecture confession.
—
The fix is unglamorous, which is why it’s rare: design the exchange zone.
Entry criteria, agreed by both sides. A defined payload that travels every time. An acknowledgment, so transfer is a fact instead of a hope. A return path for incomplete arrivals. And one owner — not per department, *per handoff*. The white space between the boxes finally gets a name on it.
None of that requires software. It requires two teams, a room, and the admission that the gap between them has been running on luck.
Because here’s the thing about batons: your best runner cannot save a dropped one.
And there’s something even worse than dropping the baton. It’s runners who compete with each other. Next section.