How to Structure an SDR-to-AE Discovery Dossier

Most SDR-to-AE handoffs fail because they are written as activity reports, not buyer diagnoses. The AE receives notes that list how many touchpoints the SDR made, a few CRM checkboxes, and a vague problem statement such as "interested in efficiency." The AE walks into the first meeting with little more than a name and a category-level problem. The buyer can feel the difference.

A useful discovery dossier does something different. It gives the AE the context to lead a sharper first conversation without asking the buyer to repeat what the SDR already heard. I first started building this structure while coaching SDR teams; you can read more about my background on the About page.

An SDR-to-AE discovery dossier should be a one-page structured handoff that gives the AE a buyer-level diagnosis before the first meeting. It should include four elements in order: the verifiable trigger or change at the account, the stated problem and its impact in the buyer's words, the specific process where that problem occurs, and a one-sentence hypothesis about why the problem matters now. The AE uses this to confirm and go deeper instead of re-discovering the account.

Why most discovery handoffs do not prepare the AE

The most common failure is the activity report. It records six touchpoints, two sequences, and one call, but no leverage. A second failure is the abstract use case: "workflow challenges" or "managing documents manually" without naming the process. This is the same pattern Lavender's operations email benchmark found in cold outreach: ops buyers respond to emails that name a specific process, not a category. A dossier that says "month-end close depends on three manual exports" is more useful than one that says "efficiency improvement opportunity."

The four-part discovery dossier format

Everything the AE needs fits into four fields. If the SDR fills them in order, the AE can open the meeting with the buyer's context already in hand.

1. The trigger: what changed, and why now

The trigger is a verifiable change a prospect company has made: a fundraise, a new office, a new market, or a new business line. For instance, imagine an SDR selling finance automation software notices a target company just opened a third office. The trigger is not "they are growing"; it is "they announced a third office this quarter." Pairing this with a pre-call account research workflow keeps the trigger evidence-based.

2. The stated problem and its impact

This is the buyer's own language, not the SDR's summary. If the buyer said "we are spending five extra hours a month reconciling across the new office," that exact phrase goes in the dossier, with the speaker's name and date. A paraphrase loses the texture the AE needs. The SDR may also note the impact the buyer described: late close, missed approvals, or a controller working Friday evenings.

3. The specific process

This is the workflow where the problem appears: the month-end close, the AP approval chain, the onboarding checklist, the demo scheduling process. Naming the process turns a category into a path the AE can walk with the buyer. Without it, the AE has to ask the buyer to do the work the SDR should have done.

4. The hypothesis

The SDR finishes with a one-sentence prediction. It should answer the same filters discussed in the Pavilion Boston event on deal health: what is the buyer's situation, what problem are they trying to solve, and what is the impact of that problem? For example: "I think the bottleneck is the manual export in quote-to-cash, because the CFO mentioned spending Friday afternoons re-keying numbers." This gives the AE something to confirm or correct. For turning a trigger into that kind of commercial insight, see how to construct commercial insights that reframe buyer thinking.

How SDRs should write the dossier

Most SDRs write handoff notes the way they were taught to write follow-up emails: question, answer, summary. The dossier should instead sound like an SDR explaining an account to a colleague walking into the meeting. I have found three practices work.

Write the trigger before the call. The dossier starts as a hypothesis before the first dial, then gets corrected or confirmed during the conversation.
Turn every "yes" into a "why." If the buyer acknowledged a problem, capture the reason behind the acknowledgment. That is the evidence the AE will use.
Name the human. "Sarah from procurement said her VP keeps asking why projected headcount is still 20 percent over last quarter" is more usable than "procurement mentioned competitive pressure."

What the AE does with the dossier in the first meeting

The AE should read the dossier in order, then use it as the opening agenda: confirm the trigger, check the stated problem, ask about the process, and test the hypothesis. If the SDR captured the buyer's own words, the AE can say, "You mentioned month-end close is taking three extra days. I'd like to test why that is happening now." This avoids re-discovery and keeps the buyer from repeating themselves. For more on keeping that first conversation moving, see how to overcome buyer indecision in early SDR discovery calls.

I learned the opposite lesson early. A rep I coached once told me he liked sounding like a salesperson and was not going to change because it "qualified" prospects. He failed. The handoff equivalent is an SDR who writes only activity and opinion. The AE is then forced back into a seller-led interrogation rather than a buyer-led conversation.

Adapting the dossier by buyer seniority

Different executives read the same four fields through different filters. A CFO wants cost, risk, and time; a COO wants systems and execution. Lavender's finance email benchmark found finance buyers respond to numbers, precision, and clarity. For a CFO, the hypothesis should include a cost or risk line: "The controller is spending five extra hours a month on reconciliation." For a COO, name the process: "The onboarding checklist is being edited three different ways."

Making the dossier stick in the CRM

If the dossier lives in a separate document the AE can't find, it has no value. Build the structure into the CRM activity form: three fields for Trigger, Stated problem, and Hypothesis, with the process named in the meeting abstract. The AE can then filter the most recent SDR activity before the meeting and read the dossier in place.

Don't start with the fields. Salesloft's build vs. buy guide notes that AI deployed without a clear business problem or workflow context produces output in isolation. The same applies to a handoff template: define what "ready to meet" means first, then add the CRM structure. You can also align that definition in an SDR-to-AE lead handoff service level agreement.

How the dossier compounds across the team

One dossier is a note. Twenty dossiers are a signal. When every SDR uses the same four fields, the sales manager can see where meetings stall. If the hypothesis section is always empty, reps are not pausing to think. If the process section is always a category, training needs to fix it. The Bridge Group's 2025 SDR research found median pipeline sourced per SDR of $3.78M and a median of 4.1 Quality Conversations per day. A better dossier does not guarantee either number, but it protects the work behind them by making every conversation more usable downstream.

I saw this on a team where I made reps read three dossiers aloud in a weekly meeting, then open a mock first meeting using only the notes. The practice exposed weak process and hypothesis fields instantly. For KPIs that hold the team accountable to this habit, see implementing effective sales development KPIs.

Frequently asked questions

What should SDRs include in an SDR-to-AE discovery dossier?

An SDR-to-AE discovery dossier should include the trigger or change at the account, a specific stated problem and its impact, the actual business process where that problem shows up, and a one-sentence hypothesis about why the problem matters now. Keep it focused on the buyer's language, not the SDR's activity log.

How can an AE use discovery handoff notes to avoid re-discovery in the first meeting?

AEs should read the dossier in order and treat the trigger, stated problem, specific process, and hypothesis as the conversation's opening structure. If the SDR captured the buyer's own words, the AE can confirm the problem's reality and move straight to examining the hypothesis with the buyer, rather than asking questions the SDR already answered.

What's the difference between a generic handoff note and a discovery dossier?

A generic handoff note records activity, such as the number of calls or emails a prospect opened. A discovery dossier records named evidence: what changed at the account, the problem the buyer described in their own words, the specific process the problem is stuck in, and the SDR's hypothesis about why it is urgent now. The difference is the amount of re-discovery the AE must do.