The Four Handoffs

Open your funnel report. It will tell you, precisely, how many accounts sit in each stage. It will not tell you the thing that decides the quarter: what happens to an account while it is between stages, when it belongs to nobody.

Conversion is not five stages. It is four handoffs.

The four handoffs

Lead to prospect: an anonymous flicker becomes a named conversation, or doesn't.

Prospect to trial: a conversation becomes hands on the product, or doesn't.

Trial to customer: usage becomes a contract, or doesn't.

Customer to revenue: a signature becomes expansion, renewal, and advocacy, or quietly doesn't.

Every stage has an owner, a dashboard, and a meeting. The handoffs have none of the three.

Gap anatomy

Each gap has its own cause of death.

Lead to prospect dies on response time. The account read your pricing page Tuesday morning; the SDR queue got to it Thursday. Thursday's note covered the research: the window where a response reads as attention is measured in minutes, and most teams miss it by days.

Prospect to trial dies on no reason to start now. The call went well, the follow-up said "let us know when you'd like to kick off a trial," and the prospect returned to a job that is not evaluating your product.

Trial to customer dies on activation silence. The user signed up, poked twice, and went quiet on day five. Nobody noticed until the trial expiry email fired, which is a receipt, not a rescue.

Customer to revenue dies on unwatched expansion. Three new teammates joined the workspace last month. The usage cap is close. Renewal is in ninety days. Each of those is a signal; none of them reached a human while it mattered.

Gap 1, lead to prospect. Dies on response time. The Play: answer the pricing-page flicker in minutes with the answer the behavior implies (example: inbound-answer-v2).

Gap 2, prospect to trial. Dies on no reason to start now. The Play: turn the good call into a trial with a concrete first step (example: trial-start-v1).

Gap 3, trial to customer. Dies on activation silence. The Play: catch the day-five silence and route the activation nudge (example: activation-nudge-v2).

Gap 4, customer to revenue. Dies on unwatched expansion. The Play: watch seats, caps, and renewal windows so expansion stops being an accident (example: expansion-flag-v1). Play names illustrative.

Click a gap, or use arrow keys. Every stage has an owner. The gaps have Plays.

The number your CRM doesn't show

Stage reports measure time-in-stage. The predictive number is time-in-gap: how long an account sits between one owned state and the next, unwatched.

Time-in-stage is a pipeline-review artifact. Time-in-gap is where the compounding happens, because a gap, unlike a stage, has no owner to notice it growing.

Handoff	Time in stage (reported)	Time in gap (unreported)
Lead to prospect	2 days as "new lead"	2.5 days unanswered
Prospect to trial	3 weeks as "qualified"	11 days since the good call
Trial to customer	14-day trial window	6 days of silence inside it
Customer to revenue	12 months as "active"	90 days of unwatched expansion signals

Select a handoff, or use arrow keys. The second bar predicts the outcome. All values illustrative, not a benchmark. Time-in-gap is the bar your CRM does not draw.

Running the gap

The fix is not another dashboard, because a dashboard is one more thing to watch and the gap exists precisely because nobody is watching.

Bryn is not another dashboard to watch. It is the governed execution layer that runs Plays through your stack. For each handoff, the growth owner defines and approves a Play: what fires it, what it does, where its output lands. Bryn watches the signals the company already owns, scores what fired against that company's definition of a good account, and runs the matching Play while the signal is warm.

A gap-1 Play answers the pricing-page flicker in minutes, not days. A gap-2 Play turns the good call into a trial with a concrete first step. A gap-3 Play catches the day-five silence and routes the activation nudge. A gap-4 Play watches seats, caps, and renewal windows so expansion stops being an accident.

The operator's authority lives at Play definition and approval, not per-instance execution. What Bryn actually does, mechanically, is covered elsewhere; the point here is where it does it: in the four places your org chart has no name for.

The record

Every run writes its receipts as it works: the signal that fired, the score, the Play that matched, who approved it, what action was taken, and what happened next. Which means the four handoffs, historically the least visible part of the funnel, become the best documented.

When the quarter closes, the question "who moved this account?" has an answer with timestamps. And when the buyer's clock comes for your own stack, the record is already there.

Name your gaps

The do-it-Monday version: write the four handoffs on a whiteboard and put a name next to each one. Who, or what, notices an account sitting in that gap today? Most teams find at least two gaps owned by nobody. That is not a staffing insult. It is the shape of every org chart that was drawn around stages.

The gaps were never a people problem. They were a watching problem, and watching is now a solved category. Running is the open one.

Bryn starts at $49 a month with a 7-day trial. Pricing is public at civic.com/bryn/pricing.

---

Further reading

• The {FirstName} Fallacy (Civic Field Notes): part 1 of the personalization series, on moments and why they expire.
• What Bryn Actually Does (Civic Field Notes): the mechanics.
• You Already Paid for This Pipeline, Why Aren't You Converting? (Civic Field Notes): the case for running what you already bought.
• The EU AI Trust Deadline Moved. The Buyer Didn't. (Civic Field Notes): the buyer's clock, and why the record matters on your own deals.