A calendar invite is not the handoff. Context is the handoff
Booked meetings feel like pipeline. Most aren't. Qualification defines what has to be true before a meeting counts, and the handoff decides whether everything the SDR learned actually reaches the AE.
SD Lab framework · C.A.R.E.S. lineage from the Kustomer engagement · expanded for SD Lab V2
What this guide covers
- A booked meeting is an activity metric. Qualified pipeline is a judgment with criteria.
- C.A.R.E.S. = Company + Access to Buying Committee + Roadblocks + Event + Set-Backs.
- Qualify in three parts: the company, the person, the Hero's Journey.
- The handoff is four steps: CRM fields, context, the calendar set, the reminder sequence.
- The buyer should never have to repeat everything the SDR already learned.
A booked meeting is not automatically pipeline
Teams that count meetings as pipeline inflate the top of the funnel and poison every forecast downstream. The AE walks in blind, the buyer repeats their story to a second person, and half the 'pipeline' evaporates on contact with discovery.
The fix is not more meetings or fewer meetings. It's a shared, inspectable definition of what has to be true before a meeting counts.
A calendar invite is not the handoff. Context is the handoff.
What C.A.R.E.S. is checking
C.A.R.E.S. is the qualification lens the SD Lab taught inside the Kustomer engagement, preserved here as that lineage, not as a universal BANT replacement. It's a fit check for this kind of motion, not a claim about how all sales works.
- Company: does the account actually fit the target profile?
- Access to Buying Committee: can this person reach, or become, the people who decide?
- Roadblocks: what's standing between the buyer and the outcome they want?
- Event: what happened, or is about to happen, that makes this timely?
- Set-Backs: what has it already cost them that this isn't solved?
The three-part qualification play
Three passes, each one cheaper than a wasted AE hour. A meeting that clears all three is pipeline. A meeting that clears none of them is a calendar event.
- Qualify the company: through the Target Customer Profile and 3x3 Research, before the meeting is ever booked.
- Qualify the person: role, ownership of the problem, and access to the buying committee.
- Qualify the Hero's Journey: the buyer's situation, their goals, and the roadblocks between the two.
The four-step sales handoff play
- Complete qualification fields in CRM: structured, inspectable, not a paragraph in a notes app.
- Record prospect and company context plus the full outreach history. What was sent, what landed, what they reacted to.
- Set the Discovery Call directly in the AE's calendar, ownership transfers with the meeting, not after it.
- Run the Reminder Sequence: no-show prevention as a process step, not a hope.
If the AE's first question is 'so, tell me about your situation,' the handoff failed. The buyer should feel like the second conversation continues the first.
What useful CRM context looks like
Useful context is short, structured and written for the reader. The AE should be able to prep in three minutes:
- Why this account, why now: the trigger and its source.
- Who this person is: role, problem ownership, committee access.
- Their situation in their words: goals, roadblocks, set-backs.
- What they responded to: the angle, asset or message that got the meeting.
- What was promised: anything the SDR committed to sending or covering.
Warm introduction, set expectations
The SDR introduces the AE to the buyer, by name, with role and relevance, and sets the agenda for the discovery call before stepping back. The buyer knows who's coming and why; the AE enters with credibility borrowed from a relationship that already exists.
This is also where the Reminder Sequence does its work: confirmation touches before the call, owned as a process, so attendance doesn't depend on the prospect's memory. We treat reminder cadence as hygiene, not a benchmark. The claim is that process beats hope, not a number.
Stage exit criteria: the Queryon evolution
In the Queryon engagement, qualification matured from a meeting-level check into explicit stage exit criteria. A deal doesn't advance because time passed. It advances because the criteria are met:
- ICP fit confirmed.
- Mobilizer / champion identified.
- Primary persona mapped.
- Use-case summary captured.
- Risk flags named.
- Next steps agreed and dated.
SDR qualification is not AE discovery
The SDR qualifies the meeting: right company, right person, real situation, credible timing. The AE qualifies the deal: budget, decision process, evaluation, close plan. Collapsing the two either overburdens the SDR or underfeeds the AE. The handoff criteria exist precisely at the seam between them.
What this looks like in live engagements
- Kustomer: qualification and handoff discipline installed and reinforced as part of a documented capability build; C.A.R.E.S. lineage originates here.
- Queryon: stage exit criteria documented above, evolved live inside the engagement.
- FusionAuth: qualification fields and handoff context built into the CRM spine as part of the live system install.
Where qualification sits
Everything upstream: aim, relevance, research, conversations, exists to produce this moment. Qualification is where outbound either becomes pipeline or gets exposed as activity. It's the seam the whole system is judged on.
Related reading
Make 'qualified pipeline' mean something again
The Revenue Rebuild defines what a qualified meeting is, what must transfer at handoff, and how the whole seam becomes an inspectable operating system instead of a weekly argument.