Illustrative composite: a quarterly business review reaches the slide nobody likes. Marketing reports 640 qualified leads delivered. Sales development reports 210 meetings booked. The account executives report 58 new opportunities. Everyone's number is accurate, and nobody can explain the gaps between them. Marketing says sales ignored good leads. The SDR lead says half were students and competitors. The AEs say many booked meetings arrived with no notes. The CRO asks: of the leads that disappeared, how many did someone actively reject, how many were never touched, and how many were touched too late? The room goes quiet, because the CRM cannot answer it.
That silence is the handoff problem. The deals did not die inside any team. They died between teams, when one believed it had passed something on and the next did not yet believe it had received it.
The buying side has become harder to hand off, not easier. Forrester's State of Business Buying 2024 found that 86% of B2B purchases stall during the buying process, that an average of 13 people take part in a purchase decision, and that 89% of purchases involve two or more departments. Every internal transfer on the seller's side is another place where a stalled deal quietly becomes a lost one.
The selling side is stretched as well. Salesforce's sixth State of Sales report, a survey of 5,500 sales professionals in 27 countries published in 2024, found that reps spend 70% of their time on non-selling tasks, and that only 35% completely trust the accuracy of their organization's data. A rep with little time and low trust in the record works the obvious leads and lets the ambiguous ones age.
The friction is felt, even when it is not measured. In a December 2025 survey of 500 go-to-market professionals by Unbounce and Ascend2, 28% said marketing-sales misalignment had caused delayed or inconsistent lead follow-up. Mutiny's 2025 survey of 500 sales and marketing leaders found only 24% describing their teams as completely aligned. That is a lot of energy spent on blame that a timestamp could settle.
The standard advice is to hold a weekly handoff meeting, write a service-level agreement, and ask everyone to communicate more. All three help; none tells you where deals actually stall. An SLA without instrumentation is a promise nobody can check. The fix is to treat each handoff as an event the system records, so the gaps become visible before the quarterly review.
Diagnosis: why handoffs fail without anyone noticing
At $3M to $30M ARR companies, handoff failures tend to fall into a small number of patterns. None is about effort; all are about what the system records.
Assignment is mistaken for acceptance
When a lead is routed, the owner field changes and every report treats the lead as "with sales." But a changed owner only means the system made a decision. It says nothing about whether the SDR saw the lead or agreed to work it. Without a separate acceptance moment, a lead can sit with a named owner for weeks and look healthy on a dashboard. The gap between assigned and accepted is where most untouched leads hide, however good the assignment rules are.
The status field overwrites its own history
Most teams track the funnel with a single status or lifecycle field. Each change overwrites the last, and unless field history is switched on and actually reported, the record only shows where the lead is now. You cannot tell how long it waited or whether it bounced between teams. A lead that went from qualified to rejected to nurture to qualified again looks identical to one that arrived yesterday.
Rejections disappear into a void
When an SDR disqualifies a lead or an AE declines a meeting, the record usually goes to a generic "unqualified" or "closed" status with no structured reason. Marketing never learns which campaigns produce the rejects, and the SDR never learns why the AE turned a meeting away. The argument repeats every quarter because neither side has evidence.
Context does not travel with the deal
An SDR spends twenty minutes learning the buyer's situation, then books a meeting and moves on. The AE opens the record and finds a name, a title and a calendar slot. The buyer explains everything again. Notes live in emails, call recordings and chat threads, not in fields the next owner is required to read. A handoff that drops context is a handoff the buyer can feel.
The handoff meeting is the only control
Handoff meetings are useful for judgment calls, but they review what people bring to them. They cannot surface the lead that nobody remembered, the meeting that never got a follow-up, or the pattern where Friday-afternoon leads routinely wait until Tuesday. A meeting is a review step; it is not a measurement system.
The framework: the Handoff Clock
The Handoff Clock is a simple model: every transfer of responsibility between teams is recorded as an event with four moments and measured the same way, whichever teams sit on either side.
The four moments. Offered is when the sending team marks the lead, meeting or opportunity as ready for the next team. Accepted is when a named person on the receiving team explicitly takes it, or rejects it with a reason. First action is the first real piece of work by the receiver: a call, a personal email, a held meeting, a created opportunity. Outcome is where it ended up: progressed, returned with a reason, or still open.
The handoffs to clock. In a typical B2B SaaS motion there are three internal transfers before a deal is in an AE's forecast. Marketing to SDR, when a lead crosses the qualification threshold. SDR to AE, when a meeting is booked. And the AE's first meeting to a qualified opportunity, when the AE decides the conversation is worth forecasting. Demo requests routed straight to an AE skip the first.
The five measures. For each handoff, report the same five numbers every week:
Time to accept, from offered to accepted, at the median and the 90th percentile. Time to first action, from accepted to the first real piece of work. Rejection rate with reasons, the share returned or disqualified, broken down by a short list of reason codes both teams agreed in advance. Orphan rate, the share of handoffs with no acceptance or rejection within the agreed window. Context completeness, the share of handoffs where the required fields (for the SDR to AE handoff, for example: pain, current tool, timing, and who else is involved) were filled at the moment of transfer.
The service-level targets come from your own baseline. A suggested starting point, not a benchmark: for high-intent inbound leads, acceptance within one business hour and first action within four; for SDR-booked meetings, AE acceptance within one business day and a held meeting within ten; for every handoff, an orphan rate close to zero. The urgency on inbound is supported by Harvard Business Review's 2011 article on the short life of online sales leads. Its authors audited 2,241 US companies and found wide variation in how quickly they answered a web lead, and in a separate study of 1.25 million leads at 42 US companies they found that firms that tried to contact a lead within an hour were nearly seven times as likely to qualify it as those that tried even an hour later.
Implementation: six steps to an instrumented handoff
This needs a few fields, a few automations and agreement on what each moment means, not a new platform. Do it in this order.
Map the handoffs as they actually happen
Trace who owned each lead and opportunity over the last 90 days. Many teams find handoffs they did not know they had, such as meetings reassigned between AEs. The diagnose-before-you-build playbook covers how to do this read-only. Check: you can name every handoff, its sender, its receiver and how often it occurs.
Agree the four moments and the reason codes
Get marketing, sales development and the AEs to agree what counts as offered, accepted, first action and outcome for each handoff, plus five to eight rejection reasons each side can choose from. If the qualification criteria behind those reasons are still gut feel, settle them first with a structured qualification framework. Check: each team leader has signed off on the definitions in writing.
Record each handoff as an event, not a status
Add a timestamp for each moment on the record, or better, a dedicated handoff record that logs sender, receiver, the four timestamps, the reason code and which required fields were filled. Timestamps are written once, never overwritten. A lead-to-cash data model gives these records a stable home, and an event-driven architecture lets other systems react to them. Check: for any lead or opportunity, you can see every handoff it went through and how long each took.
Make acceptance explicit and context mandatory
Give receivers a one-click accept or reject where they already work, and require the agreed context fields before the sender can mark a handoff as offered. Check: context completeness on the SDR to AE handoff is above 90% for two consecutive weeks.
Test the rules on your own past handoffs before switching them on
Replay a set of recent handoffs through the new logic and confirm each would have been flagged, escalated or passed correctly. We hold every system to the same bar: tested on around 20 of the client's own past cases, and 85 percent correct or it does not ship. Check: the alerts match what the team agrees should have happened, and every miss has a written reason.
Alert on breaches and publish the Handoff Clock weekly
Notify the receiver's manager when a handoff passes its acceptance or first-action target, and publish the five measures for each handoff every week, by segment and source. Check: every breach in the first month has an owner and an explanation.
Workflow: the instrumented handoff, stage by stage
A suggested design for the three common handoffs plus an escalation layer. Adapt the details; keep the four moments and the owners.
What happens: a lead or account crosses the qualification threshold and is offered to sales development with its source, its recent activity and the reason it qualified.
System role: timestamp the offer, route to an active owner, start the acceptance clock, and capture the reject reason if the SDR returns it.
Owner: marketing operations owns the threshold and the context sent; the SDR manager owns acceptance time.
What happens: the SDR books a meeting and offers it to an AE with the required discovery fields filled. The AE accepts or declines with a reason before the meeting.
System role: block the offer until context is complete, notify the AE where they work, and flag meetings not accepted within the agreed window.
Owner: the SDR owns context; the AE owns acceptance; the sales manager owns breaches.
What happens: after the first meeting, the AE either creates a qualified opportunity, returns the account to nurture with a reason, or schedules a defined next step.
System role: prompt for an outcome within a set time after the meeting ends, and record whether the opportunity came from the SDR handoff so the source gets credit.
Owner: the AE records the outcome; RevOps owns the reporting.
What happens: any handoff without acceptance or first action inside its window is escalated to the receiving manager. Timings and reason codes feed the weekly report.
System role: make sure no handoff goes orphaned unnoticed, and show each team which sources and segments generate the most rejections.
Owner: RevOps runs the report; the heads of marketing and sales review it together.
The board narrative
Instrumented handoffs replace the marketing-versus-sales argument with three statements a board can follow.
We now record every transfer between marketing, sales development and account executives as an event, with when it was offered, accepted, first acted on and resolved. Each team has a target, and rejections carry a reason.
B2B purchases already involve large buying groups and stall often. Every hour a lead waits between our own teams adds to that delay. Fixing the gaps between teams protects demand we have already paid to create.
We report acceptance and first-action time at the median and 90th percentile, rejection rates by reason and source, orphan rates and context completeness for each handoff, and conversion from handoff to qualified opportunity, every week.
After a quarter of clean data, the conversion effect becomes visible in your own records. Illustrative example, with made-up round numbers: a $15M ARR company whose SDRs book 200 meetings a month might find that meetings accepted by the AE within one business day turn into qualified opportunities at 35%, while meetings accepted later convert at 20%. If half of meetings are currently accepted late, closing that gap would be worth roughly 15 extra qualified opportunities a month in that example. Your numbers will differ; once the clock exists, the value of a faster handoff stops being opinion.
Cross-domain: where the handoff connects to the other systems
Handoffs are where revenue systems connect or fall apart, which is why the Handoff Orchestrator tracks handovers with a named owner, carries context and escalates stalls. It does not reassign accounts or change owners on its own. The Handoff Clock acceptance and reason-code workflow above is a proposed implementation, not a statement of every shipped installation.
It sits directly after Speed-to-Lead, which gets the first touch right (the speed-to-lead benchmarks by ARR band show what "fast" means in practice); the Handoff Orchestrator makes sure the second and third touches do not undo it. Downstream, the Pipeline Hygiene Sentinel watches opportunities that were handed off cleanly and then went quiet, and the Forecast Assistant becomes more reliable when every opportunity carries a known source and a clean first-meeting outcome. The same four moments apply to the post-sale transfer from AE to customer success. The wider picture sits on the GTM Operations page.
For who should own this work once it is instrumented, see the GTM engineer vs. RevOps manager vs. growth engineer decision tree. Our approach is forward-deployed engineering: build inside your existing CRM, test against your own past handoffs, and switch each change on only when it proves itself.
Sources: Forrester, "The State Of Business Buying, 2024" (press release, December 4, 2024) and the accompanying Forrester blog (more than 16,000 global business buyers). Salesforce, State of Sales, sixth edition (July 2024; 5,500 sales professionals in 27 countries, surveyed March to April 2024). Unbounce and Ascend2, marketing-sales misalignment survey, as reported by MarketingProfs (December 2025; 500 go-to-market professionals). Mutiny, marketing and sales alignment study, as reported by MarketingProfs (2025; 500 sales and marketing leaders). James B. Oldroyd, Kristina McElheran and David Elkington, "The Short Life of Online Sales Leads," Harvard Business Review (March 2011; an audit of 2,241 US companies and a separate study of 1.25 million leads at 42 US companies). The Handoff Clock targets and the conversion example are suggested starting points and illustrative figures, not benchmarks.
