What a deal handoff brief should actually contain

I've lost two deals during handoffs that I'm still annoyed about. An SDR qualifies a prospect and passes it to an AE who asks the same discovery questions. A rep goes on parental leave and their colleague picks up mid-negotiation with zero context. A founder hires a VP Sales and hands over thirty deals with the context stored exclusively in their own memory.

The deal doesn't die because the next person is bad at selling. It dies because the context — the specific words the prospect used, the objection that came up in meeting two, the internal champion who went quiet after the reorg — didn't transfer with the account. The new rep starts from ignorance and the prospect can feel it immediately.

Most teams try to solve this with a handoff document. A Notion page or Google Doc with bullet points: deal value, current stage, next steps, key contacts. Better than nothing, worse than useful. It captures the what without the why. It tells you the deal is in Negotiation without telling you the CFO pushed back on the annual commitment and the champion suggested a six-month pilot that hasn't been formally proposed yet.

Here's what actually belongs in a handoff brief. Not a template with fifteen required fields — a narrative document that gives the next person the same contextual understanding the previous person had.

The five things a brief needs

First: the stakeholder map. Not just names and titles. Who is the economic buyer and have they been in a meeting? Who is the internal champion and what motivates them? Is there a blocker — someone skeptical whose approval is needed? Who's been in the room versus conspicuously absent?

Second: open objections, stated and unstated. The handoff brief needs both, with specific language. 'We need to think about budget' means something different from 'This isn't in this quarter's budget but I'm working on getting it into next quarter's.' That nuance is the first thing that gets lost.

Third: commitments made, by both sides. What did your team promise? A custom demo? A reference call? A pilot by a specific date? What did the prospect commit to? An internal review? Sharing the proposal? A follow-up with their CTO? These commitments are the scaffolding of the deal.

Fourth: relationship texture. Does the champion prefer email or phone? Do they respond faster in the morning or after 4pm? Did they mention a personal detail — a kid's football game, an upcoming conference — that creates a natural re-engagement point? ('Don't call me, I'm in back-to-back meetings all day — email is better.') These details are what make a relationship feel continuous.

Fifth: the deal narrative. Not the stage progression. The story. Why did this prospect take the first meeting? What problem are they solving, in their own words? What was the moment the deal gained momentum, and what caused the last stall? That two-minute-coffee explanation — with its emphasis on causality, not data points — is what the next rep actually needs.

Why this shouldn't be a document

We're building this into Agent07 because we don't think it should be a document someone writes. It should assemble automatically from the emails, meetings, and conversations that already happened. The stakeholder map from attendees and email threads. The objections from transcripts. The commitments from action items.

A handoff should feel like picking up a book someone left open to the right page, with the important passages highlighted.