Before you pitch anything, prove you were listening. The discovery recap is the page that does this, a concise, specific mirror of what the buyer told you about their situation, written back to them before you offer a single recommendation. It’s the page that separates consultants from vendors.
Why This Page Changes Everything
Gap Selling teaches that buyers don’t trust proposals from consultants who haven’t demonstrated they understand the current state. Understanding the problem is table stakes. But demonstrating that understanding in writing, using the buyer’s own metrics, language, and concerns, is something most proposals never do.
The typical proposal jumps from “here’s who we are” directly to “here’s what we’ll do.” The discovery recap adds a critical intermediate step: “here’s what we heard from you.” That step does three things simultaneously:
First, it proves attentiveness. A buyer who reads their own situation accurately described in a proposal knows you were listening, not just presenting.
Second, it validates the problem. Seeing the situation written down in a document elevates its urgency. Problems that live in a person’s head can be rationalized or minimized. Problems that appear in a formal document feel real and solvable.
Third, it builds the logical bridge to your solution. When the solution section follows a well-constructed discovery recap, the recommendation feels inevitable, like the natural response to a documented problem, rather than arbitrary.
The Five-Bullet Structure
The discovery recap is exactly five bullets. Not four, not seven. Five creates the impression of thoroughness without padding; fewer than five feels like you didn’t dig deep enough.
Each bullet follows this pattern: [specific observation] + [specific detail] + [why it matters].
Bullet 1, The Primary Problem The main reason they’re looking for help, with numbers where available. “Your trial-to-paid conversion rate sits at 13%, roughly half the 24% benchmark for B2B SaaS tools at your price point, and has been flat for three quarters.”
Bullet 2, The Root Cause or Contributing Factor Something specific you identified that explains or amplifies the primary problem. “Your onboarding sequence has seven steps, but analytics show 58% of trial users never complete step 3, the first point where the product’s value becomes clear.”
Bullet 3, The Internal Constraint A resource, process, or organizational factor making the problem harder to solve internally. “Your product team is running a six-sprint backlog with no bandwidth for onboarding redesign, which means this initiative has been waiting 11 months for internal capacity.”
Bullet 4, The Consequence of Inaction What continues to happen if nothing changes. “At the current conversion rate, you’re leaving approximately $18,000 in monthly recurring revenue on the table from trial users who intend to convert but drop off before activation.”
Bullet 5, The Goal The specific outcome they articulated as success. “Your target for Q3 is to reach 22% trial-to-paid conversion, which would put you inside the top-quartile range for your category and generate the MRR needed to hit your Series A metrics.”
The most powerful discovery recap bullet is the one that names something the buyer said, something specific, perhaps something they said casually, and treats it as a central diagnostic insight. When a buyer sees a throwaway comment from the call treated as a key data point, they feel deeply understood.
Getting the Language Right
The discovery recap uses the buyer’s words, not yours. This is the most important discipline in writing it.
If the buyer said “our sales team keeps getting ghosted after the first demo,” your recap bullet says “your sales team loses contact with prospects after the first demo call”, not “your post-demo follow-up process is underperforming.” The first version is their language. The second is your analysis. The first creates recognition. The second creates evaluation.
The test: could you hand this page to someone who wasn’t on the discovery call and have them understand exactly what the buyer told you? If yes, the recap is specific enough. If not, it’s still in consultant language rather than buyer language.
Common Mistakes in the Discovery Recap
Vagueness. “You mentioned some challenges with your current process” is useless. Every bullet needs a number, a name, a date, a percentage, or a specific condition.
Editorializing. “Your team seems to struggle with…” inserts your judgment. Keep it factual: “Your team reported that…”
Leading with your solution. “Your main challenge, which we will address through our methodology, is…” The recap is not the pitch. Keep them separate.
Using internal jargon the buyer didn’t use. If they said “our conversion is bad,” don’t write “sub-optimal funnel performance.” Write what they said.
Sending the Recap Before the Proposal
For high-value engagements, consider sending the discovery recap as a standalone document 24 hours before the full proposal, as a “here’s what we’re working on” preview. Subject line: “Here’s what we heard, full proposal follows tomorrow.”
This technique does two things: it gives the buyer a chance to correct any misunderstandings before you’ve committed to a full solution, and it creates a second touchpoint that keeps the proposal top of mind. Buyers who receive a pre-proposal recap report feeling more invested in the solution when the full proposal arrives, because they’ve already confirmed the problem framing is accurate.
Placement and Format
In a 3-page proposal: the discovery recap is page 1, immediately after the title block, before the methodology. In a longer proposal: it’s section 2, after the executive summary. It should be visually distinct, a bulleted list with clear spacing, no table format, no decorative elements. The content is doing the work. The formatting should step aside and let it.
Ready to send stronger proposals?
Build, send, and track proposals in one place so follow-up is easier.
Start your free trial →
