The first real conversation. SPRINT's situation and problem feed PLAN's P directly. The question it answers: “Do I understand their world better than they expected me to?”
Discovery is a conversation the buyer finds valuable, not a form the seller completes out loud. Here is what that feels like from each seat.
You ran the demo they asked for, and the deal died politely six weeks later. Discovery was the funeral. You just did not know it yet.
You listen to calls where the rep talks 70%, and the only coaching tool you have is ask better questions.
Deals keep dying at the close that were actually lost in discovery, so every fix keeps landing on the wrong stage.
An illustrative first call with a VP of Sales at a fourteen-AE org, written up the way the rep documents it while the call is still warm. The buyer talked for most of the hour; these notes are in the buyer's words.
The current landscape and process, in their words. You cannot diagnose what you have not seen.
Fourteen AEs in a two-stage motion, and the forecast built by hand in a spreadsheet every Thursday night. Opened with the business, not the pain: how they make money came first, the process second.
The specific pain points and how they show up day to day. Symptoms first, then the disease.
Deals stall after the demo. The third why landed the real one: nobody agrees on what a qualified deal is, so the pipeline is full of hope. Their words: half of this pipeline is not real.
The cost of keeping the status quo. If nothing changes, what breaks, and when?
The board built the hiring plan off the forecast. Miss it two more quarters and the plan gets reset without the VP in the room. That is what standing still costs.
The outcomes of change: which metrics improve, by how much, and who feels it.
A forecast they trust means hiring on time and a credible number upstairs. Asked what that would mean for them personally, the VP paused, then said: this is the difference in how the CEO sees me.
The path forward and who else needs to be involved. Discovery that ends without a next step was a chat.
A thirty-minute working session Thursday with the RevOps lead, agenda agreed: walk the current stage definitions against real deals.
The decision timeframe and the milestones inside it. Urgency is discovered, not manufactured.
Planning for the new fiscal year starts in eight weeks, so a decision needs to land inside four. Their date, not ours.
“Do I understand their world better than they expected me to?”
The talk ratio told the story: the buyer spoke for most of the call, the 5 Whys did the digging, and every note above is something the buyer said, not something the rep inferred. That is what makes the PLAN read possible later: P and L are already sitting in these notes, in the buyer's own words.
Good discovery starts wide on purpose. Spend the first 20% on their business, because the context is what makes the other 80% land ten times harder.
Tell me about your email problems. You sound like every other vendor in their inbox.
Tell me about your business. How do you make money? Then work inward, layer by layer, until the problem sits inside its real context.
So the current process is not ideal?
With a 15% forecast error, what happens to resource allocation when the deals you counted on do not close?
Would improving this help?
If forecast accuracy went from 85 to 95%, what would that mean for planning, and for your team's credibility with leadership?
Our response rate is 20%. On its own: so what?
70% of revenue comes from outbound, so that same 20% is the difference of millions a month. Context is what turns a stat into a problem.
THE CHECK
The talk ratio is the tell. The buyer speaks 70% to 80% of the call, the 5 Whys do the digging, and every session gets documented in the SPRINT structure while it is still warm. Discovery that ends without a dated next step was a pleasant chat.
The first real conversation. SPRINT's situation and problem feed PLAN's P directly. The whole chain, in deal order; every one has its own page.
Three places on the site: the playbook and skill for this one, the library the rest live in, and how to put AI on the prep so the conversation stays human.
The playbook and the skill, in one place: what the machine preps and scores, what stays yours. Install it in one line.
Open the playbookEvery operator-built skill, grouped by the outcome it moves. The deal review, the pipeline review and the rep scorecard inspect this one every week.
Open the libraryHow to put AI on the prep, the notes and the scoring so the rep's time goes to the conversation, which stays human.
Start hereOne story a week, plus the runnable playbook and skill behind each framework in the chain.