Sales Conversation Script & Discovery Framework
Create a consultative sales conversation system that uncovers buyer problems and builds trust. Includes discovery questions, qualification, and presentation approach.
Use This When
Landing pages, product pages, CRO audits, funnel fixes, FAQs.
Inputs Needed
Website/store URL, product/service, audience, funnel stage, analytics, conversion goal, current blocker.
Expected Output
Conversion diagnosis, prioritized fixes, copy/UX recommendations, test plan, KPI impact.
The Workflow Prompt
You are a CRO strategist and eCommerce revenue operator. Objective: Sales Conversation Script & Discovery Framework Context: Create a consultative sales conversation system that uncovers buyer problems and builds trust. Includes discovery questions, qualification, and presentation approach. Original task: **You are a sales methodology expert specializing in consultative selling and discovery conversations. I sell [PRODUCT/SERVICE] to [TARGET CUSTOMER] and my sales cycle is [LENGTH]. My current conversion rate is [METRIC].Create a comprehensive sales conversation system including:(1) A discovery framework identifying key buyer problems, business impact, current approach, and buying criteria(2) Opening statements that establish credibility and create curiosity(3) Question sequences that uncover root problems and implications(4) Active listening protocols showing how to understand what's really being said(5) A qualification framework determining fit and timeline(6) Presentation approach connecting solution features to prospect's specific problems(7) Trial close and objection handling for end of conversation(8) Call recap and next steps protocol. Include sample scripts for different scenarios—[PROSPECT TYPE A], [PROSPECT TYPE B]—and conversation flowcharts showing decision points. Include specific language to build rapport and trust.** Inputs I may provide: Website/store URL, product/service, audience, funnel stage, analytics, conversion goal, current blocker. Operating instructions: - First, restate the objective in one clear sentence. - If critical information is missing, ask up to 5 focused questions. If there is enough information to proceed, make practical assumptions and label them. - Use a Exhaustive response style. - Be specific to the business, audience, channel, and constraints provided. - Avoid generic AI advice. Give concrete recommendations, examples, templates, copy, or steps I can use. - When current facts, competitors, laws, prices, policies, or market claims matter, use current research and cite sources. - Do not expose hidden chain-of-thought. Provide a concise rationale or decision summary instead. - End with a short QA checklist that helps me verify the output. Required output: Conversion diagnosis, prioritized fixes, copy/UX recommendations, test plan, KPI impact. Caution: Use live web research or source documents before finalizing claims.
QA Follow-Up Checklist
After the AI returns its output, verify against:
- Output is specific to the provided business/context.
- Assumptions are clearly labeled.
- No unsupported claims without source checks.
- Next actions are clear and usable.
Follow-Up Prompt
Now turn the result for 'Sales Conversation Script & Discovery Framework' into a client-ready version: tighten wording, remove fluff, add missing assumptions, and provide the next 3 actions.
Avoid / Cautions
Use live web research or source documents before finalizing claims.
How Different Verticals Use This Workflow
Restaurant & Hospitality
A POS company with 12 AEs builds a discovery script for restaurant owners. Output: opening that establishes credibility in restaurant-specific language, 8 questions sequenced from operational to financial to strategic, mandatory quantification of labor cost. Demo-to-close lifts from 18% to 28% in 90 days.
Retail & E-commerce
A Shopify app with 6 AEs builds discovery scripts for DTC ops managers and CMOs. Output: role-specific opening, 6 questions per role probing attribution clarity and team workflow. Average deal size moves from $4.2K to $6.8K as bigger problems surface.
Professional Services & B2B
A fractional CFO firm with 4 partners builds discovery scripts for Series A and B founders. Output: 7 question sequence anchored to specific SaaS metrics (CAC payback, gross margin, burn multiple). Discovery-to-close lifts from 22% to 41% and average ACV moves from $4K/mo to $7.5K/mo.
Beauty & Personal Care
A medspa consulting firm with 3 sales reps builds discovery scripts for owners. Output: 6 questions sequenced from revenue mix to staff retention to growth ambition, with mandatory probe on owner's hours per week. Demo-to-engagement lifts from 14% to 32%.
Local & Trade Services
A field service software vendor with 8 AEs builds discovery scripts for residential service company owners. Output: 7-question sequence probing dispatch efficiency, tech retention, and cash flow. Close rate lifts from 19% to 31% and sales cycle compresses from 62 to 41 days.
Frequently Asked
What inputs actually move the needle for a real discovery script vs leading questions?
Three things: the buyer's role and the 3 metrics they're judged on (CFO is judged on cash, not features), 5 verbatim quotes from past discovery calls where prospects revealed real pain, and your current conversion rate from discovery to next step. Discovery scripts fail when questions are generic ('what's your biggest challenge?'). They work when questions probe specific metrics the buyer owns. Without buyer-specific framing, you're running an FAQ session, not discovery.
How is this different from using SPIN, Sandler, or MEDDIC?
Those are methodologies for the full sales cycle. The discovery framework is the front end where most cycles win or lose. The methodologies tell you what to ask in concept; the framework gives you scripts adapted to your specific product, buyer, and motion. Use both: methodology for principles, scripts for execution. Reps who study methodology and skip scripting either freelance the discovery (inconsistent) or read methodology questions verbatim (wooden). Scripts in your voice and product context are the bridge.
What's the most common failure mode in discovery?
Selling during discovery. The prospect mentions a pain, the rep jumps in with 'oh we solve that, here's how' — and the conversation collapses into a demo. Discovery's job is to uncover pain, quantify impact, identify decision criteria. Selling happens after. The discipline is asking 3 follow-up questions before saying anything about your product. Most reps can't tolerate the silence and pitch on the first pain. That single habit cuts close rates by 30-50% across SaaS sales orgs.
When is this the wrong tool to reach for?
Skip building discovery scripts for transactional sales under $500 — the time investment doesn't pay back. Skip for inbound demo-on-demand motions where prospects already know what they want. Skip if your sales team is under 3 reps — manual coaching is faster than scripting. Build discovery scripts when you have 5+ reps, an ACV over $5K, and a sales cycle over 30 days where deeper discovery actually changes deal outcomes.