Your Discovery Call Is a Product Walkthrough

It is Tuesday at 10 AM. Your senior AE is on a 30-minute discovery call with a director of operations at a Series B logistics company. The booking came from an inbound demo request the night before. The AE opened the meeting with two minutes of small talk, asked the buyer what brought him in, listened for ninety seconds, then shared his screen at minute four and ran the standard product walkthrough for twenty-two minutes.

The buyer asked two questions in those twenty-two minutes. The AE answered both with a feature. At minute 28 the buyer asked about pricing. The AE gave a range. The buyer said he would talk to his team and circle back. The next-step email went out at 11:14 with a link to a case study and a Calendly slot for a technical deep-dive next week. The buyer never replied.

That call is in your CRM as a stage-two opportunity at $84K ACV with a 30 percent win probability. The forecast call on Friday will roll it into the quarter. The deal will sit in stage two for fifty-one days and close-lost in week eight. The closed-lost reason in HubSpot will read "no decision." Nobody on the team will go back and listen to minute four.

Discovery is a function. Most Series A and B sales teams have not staffed it. The function lives in the gap between the SDR who booked the meeting, the AE who runs it, the sales engineer who joins from minute fifteen, and the CRM field nobody fills in. On the org chart, it sits inside sales. In the calendar, it eats one hour per AE per opportunity and produces a notes field with three bullet points and a feature request.

The 30-minute demo masquerading as discovery

Pull the last fifty stage-two opportunities your team booked from inbound demo requests. For each one, log the time the AE first shared his screen, the count of qualifying questions asked before the screen share, and the closed-lost reason if it never advanced. Most teams see the screen share land between minute three and minute six. The qualifying-question count sits at one to three. The closed-lost reason reads "no decision" or "went with incumbent" on six in ten.

Walk the call. Minute one, hello. Minute three, what brought you in. Minute four, screen share. Minute six, the dashboard view. Minute twelve, the integration page.

Minute eighteen, the reporting module. Minute twenty-two, the admin console. Minute twenty-five, a question about SSO. Minute twenty-eight, the pricing range. Minute thirty, the next-step email teed up. Nothing about the buyer's budget cycle, his decision committee, the incumbent's renewal date, or the integration his data team has been begging for.

The team that should own this knows it is broken. The CRO asks for cleaner stage-two qualification. The AEs ship calls that look like webinars. The VP of Sales runs call coaching every Friday on three random recordings and tags the same three issues every week. The sales engineer joins the technical call next week with no brief because the discovery notes have three bullet points. The deal moves into stage three on a calendar booking, not on a qualified pain.

The cost shows up as a win rate that sits five to nine points below industry benchmark and a cycle time that runs forty to seventy percent longer than it should. The CRO writes it off as a tough market. The forecast call burns ninety minutes a week on opportunities that were never qualified. The real read is that discovery is the highest-impact hour in the funnel, and your AEs are spending it on a feature walkthrough. Same shape the CRM update problem takes on the pipeline side.

Hiring a sales coach is the slow answer

The textbook fix is a sales enablement manager or a director of sales coaching. Loaded comp in the US runs $160K to $220K a year. Months one through three go to building the discovery framework, picking a call-recording tool, and writing the new MEDDPICC or Command of the Message variant the team is going to adopt. Months four through six are when the framework gets rolled out in a two-day offsite and half the team starts using it on calls.

The output is good on the AEs who already ran clean discovery. The other six on the team revert to the demo-first pattern by week ten. The coaching cadence runs at three calls reviewed per AE per quarter. Each AE runs forty to sixty discovery calls a quarter. The coverage is five percent. The framework lives in a Notion page nobody opens between offsites.

The fractional version is faster to start and stops at the same wall. Eight to twelve thousand a month buys a fractional sales coach with twenty hours of senior time. The top two reps get weekly call reviews and tighten up. The bottom six get a monthly group session and a Loom. The discovery quality lifts on the top of the team and stays flat on the bottom. The forecast call still rolls in unqualified stage-two deals.

Both versions assume the work is human bottleneck work. Listen to the call, score the discovery against a framework, write the brief for the next meeting, pull the buyer's company signal from the web, pull the incumbent contract status from CRM enrichment, draft the multi-thread plan, write the AE coaching note, log the qualified pain into the CRM, brief the sales engineer, draft the follow-up email tied to the buyer's metric. On forty AEs running fifty discovery calls each per quarter, that is 2,000 calls to score and 2,000 briefs to write. No two-person enablement team clears that pile and also runs onboarding.

What a fractional AI discovery function does

Hand the call recordings, the CRM, the firmographic enrichment, the buyer-intent data, the product feature library, the discovery framework, the pricing logic, and the win-loss archive to an agent that runs the prep, the scoring, and the follow-up on a fixed cadence. The agent does the work a sales coach and a sales operations analyst would do together. The cadence is per-call on scoring, per-opportunity on briefs, weekly on coaching loops. The AE stops being the bottleneck on call quality.

Pre-call brief drafted off live signal. Forty-eight hours before every booked discovery, the agent reads the buyer's LinkedIn, his company's last earnings call or funding round, the incumbent's renewal cycle if public, the buyer's hiring posts, and the CRM enrichment. It drafts a one-page brief with the three pains worth probing, the two metrics the buyer's role is measured on, the likely incumbent, and the four qualifying questions the AE should land before minute ten. The AE reads it on the way to the call.

Real-time scoring against the framework. The call recording feeds the agent inside the hour. The agent scores the call against the discovery framework on time-to-first-question, count of qualifying questions, depth on budget and decision process, multi-thread coverage, and metric capture. The score lands in the CRM with the call notes auto-filled. The VP of Sales sees a roll-up across forty AEs every Monday, not three recordings she happened to listen to on Friday.

Coaching note written for the AE. Every call produces a 200-word coaching note tied to the framework. The note names the two minutes the AE handled well and the one moment he switched into demo mode. It links to the timestamp on the recording. The AE reads it in three minutes between calls. The VP of Sales runs her Friday session on the patterns the agent flagged across the team.

Next-step email tied to the buyer's metric. The follow-up email is drafted off the actual call. It opens with the buyer's metric, names the integration his data team has been waiting on, and books the technical session with a brief for the sales engineer attached. The AE edits it in four minutes. The buyer reads an email written to him, not a templated case study link.

Sales engineer brief that closes the gap. When the technical call gets booked, the sales engineer opens a two-page brief drafted off the discovery transcript, the buyer's stack, the integration history with similar accounts, and the two questions the buyer asked on the first call. He runs the technical session prepared. The AE stops re-explaining the buyer's pain on minute three of every follow-up call.

The unit economics of a demo-shaped discovery

A team of forty AEs running fifty discovery calls per quarter is producing 8,000 calls a year. At an average call cost of $180 in loaded AE time plus $40 of overhead, that is $1.76M of sales time spent on discovery. Six in ten of those calls produce a stage-two opportunity that closes-lost on "no decision." The forecast burn alone runs ninety minutes a week of CRO and VP time across the year. The win rate sits five to nine points below benchmark.

Layer in the direct spend most companies add to plug the gap. A sales enablement director at $200K loaded, a call-recording and coaching platform at $60K to $120K a year, a sales methodology license at $40K to $80K. Call it $320K to $420K a year of run rate against a coverage rate of five percent of calls reviewed. The CRO sees the spend, the CFO sees the line item, and neither one connects them to the demo that starts at minute four.

A 14-day sprint to stand up the agent runs in the low to mid five figures. Ongoing cost lands closer to one senior contractor than an enablement team. Pre-call briefs land on every opportunity, scoring covers every call, coaching notes ship within the hour. A two-point win-rate lift on a $40M pipeline is $800K of closed-won. Same shape we ran for the SDR motion. Function, not headcount.

The harder number to price is the CRO forecast trust line. A CRO who can open the Friday forecast call with a discovery score on every stage-two deal, the qualifying questions the AE asked, and the metric the buyer named, runs a different forecast than one who is reading three-bullet notes. The stage-two-to-closed-won rate moves because the deals in stage two were qualified, not booked. That is the part of sales that pays for the function five times over, and it only works when every call gets scored, not the three the VP listened to on Friday.

What changes after the sprint

Picture the same Tuesday 10 AM call, fourteen days after the 14-day sprint ships. The AE opened his laptop at 9:45 and read the one-page brief. He knows the buyer's CFO is on a six-week budget freeze, the incumbent contract renews in eleven weeks, and the data team has been asking for the same integration the AE's product shipped in March. At minute three he asks the buyer how his VP measures his quarter. At minute seven he asks who else has to sign off. At minute twelve he names the integration. The screen share opens at minute fifteen and runs eight minutes against the buyer's metric.

The call ends at minute 29. The follow-up email goes out at 10:36 with the buyer's metric in the subject line, the integration named in the first paragraph, and a slot booked for the technical session next Tuesday. The sales engineer gets the brief that afternoon. The deal moves to stage three at the end of week one with three qualified pains, a named economic buyer, and the incumbent's renewal date logged in the CRM.

If your discovery calls open the screen share at minute four and close-lost on "no decision" at week eight, the version where every call gets scored and every brief gets written inside two weeks is fourteen days away. Discovery is a function. You can hire against it, you can buy another coaching tool for it, or you can scope a sprint and have it running this month. The work is the same. The math is not.