Pain documentation prompts

Build Cost-of-Inaction Talking Points for Discovery

This prompt produces talking points that reframe inaction as a business decision with real consequences — not just a delay — for a specific buyer job title and pain area. It identifies what is getting worse while they wait, what opportunity they lose each month, what risk is accumulating, and what will cost more to fix in six to twelve months. It's for AEs and inside sales reps running discovery on deals that have stalled or where urgency is absent. Use it before a discovery call where you expect the prospect to default to 'we'll revisit next quarter.'

Map Non-Obvious Buyer Pain Before Discovery

This prompt helps AEs map the pain a buyer is unlikely to name directly in a discovery call, grouped into workflow friction, political, reporting, and cost-of-inaction categories. For each hidden pain it gives a hypothesis and a question that surfaces it without putting words in the buyer's mouth. Use it while prepping for discovery when you want to go beyond the obvious surface complaints.

Turn Customer Pain Into Value Statements and Hooks

This prompt helps AEs and sales engineers turn customer pain points into value statements, proof-backed benefit statements, and discovery hooks ready for live conversations. For each pain it returns one value statement, one benefit tied to real proof, and one natural hook, plus the strongest three to lead with. Use it after discovery when you have pain documented and need to translate it into language that moves the next conversation.

Discovery Pain Points Bridge Business Case Impact Language Cost Time Risk ROI

This prompt takes pain points surfaced in discovery and translates them into business case language tied to cost, time, risk, and ROI — ready for use in a proposal or executive presentation. It's built for AEs moving from discovery into the proposal stage. Use it when you need to bridge what a prospect told you they care about to the quantified business impact your solution delivers.

Financial Impact Quantification Discovery Questions

This prompt generates discovery questions designed to quantify the financial cost of a prospect's problem and connect it to measurable business outcomes. It's built for AEs, inside sales reps, and founder-led sellers who want to go deeper than surface-level pain and build a credible impact case early. Use it when prepping for a first or second discovery call where you need to move from symptoms to numbers.

Gap Selling Discovery Framework Current To Future

This prompt gives AEs and Inside Sales reps a structured Gap Selling discovery framework to guide conversations from a prospect's current state through the problem gap to a defined future state. It generates sequenced discovery questions designed to surface pain, build the pain chain, and quantify business impact. Use it when preparing for a first or second discovery call where you need to lead a diagnostic conversation rather than pitch.

Conceptual Selling Discovery Big Picture Vision

This prompt builds a bank of big picture vision questions rooted in Conceptual Selling methodology, designed for AEs and founder-led sellers running strategic discovery. It generates questions that get prospects talking about where they want to go, not just where they are, so you can align your solution to their desired future state. Use it before discovery calls where you need to elevate the conversation beyond tactical pain and into business priorities.

Write a Complete Sales Proposal Document

Generates a comprehensive sales proposal document for AEs working a mid-market or enterprise deal. Takes nine inputs spanning the prospect's stated needs, your solution and technical capabilities, business outcomes, pricing, timeline, references, and differentiators and produces a complete proposal structured to address buyer concerns and support a selection decision. Use it when a formal written proposal is required and you need to cover all evaluation criteria in a single document.

Add a Cost-of-Doing-Nothing Section to a Sales Proposal

This prompt writes a 'Cost of Doing Nothing' section for a sales proposal that presents the status quo as a genuine option, quantifies what it is currently costing the client in time, money, and risk, projects that cost forward 12 months, and connects inaction to a specific business deadline or event. It is designed for AEs preparing final-stage proposals where cost of inaction needs to be documented, not implied. Use it when you have specific cost data from discovery and need to make a financially grounded case without manufacturing urgency.

Build a One-Page Champion-Ready Business Case from Discovery

This prompt helps AEs and sales engineers build a business case document a champion can share internally to drive the buying decision forward. It produces a one-page document covering the client's strategic goals, solution-to-priority alignment, quantified outcomes using the prospect's own metrics, a 12-month ROI with stated assumptions, risks of inaction, and a recommended phased approach. Use it after discovery when you have enough inputs to build a credible financial narrative.

Pain Amplification Framework Five Levels

This prompt builds a five-level pain amplification framework starting from an initial pain point and escalating to measurable business impact. It's designed for AEs, SDRs, and inside sales reps running discovery who need to move prospects from recognizing a problem to feeling urgency to solve it. Use it before or after a discovery call to sharpen your pain narrative and connect day-to-day friction to financial or strategic consequences.

So What Probe Questions Prospect Statement Dig Deeper Quantify Dollar Time Impact

This prompt generates probing follow-up questions designed to dig beneath a prospect's stated problem and quantify the business impact in financial or time terms. It's built for AEs and inside sales reps running discovery calls who need to move from 'we have this problem' to 'this problem costs us X per quarter.' Use it before or during discovery when a prospect has named a pain point but hasn't yet connected it to measurable business outcomes.

Feature To Quantified Value For Audience

This prompt takes product features as input and generates audience-specific value statements that frame each capability in terms of the business outcomes most relevant to a given stakeholder persona. It's designed for AEs, Sales Engineers, and CSMs who need to tailor proposal content, demo talk tracks, or business case narratives to different buyer roles. Use it when you're preparing a multi-stakeholder proposal or presentation and need to speak each persona's language without rewriting your pitch from scratch.

SPIN Implication Questions From Acknowledged Problem

This prompt generates SPIN-method implication questions rooted in a specific problem the prospect has already confirmed. It's built for AEs, SDRs, and inside sales reps who need to deepen discovery beyond surface-level pain and connect acknowledged issues to broader business consequences. Use it mid-discovery, after a prospect has validated a problem but before you've established urgency or quantified impact.

Generate Sandler Pain Funnel Discovery Questions

This prompt produces a Sandler Selling Pain Funnel question set across five levels — surface pain, root cause, emotional impact, cost of pain, and payoff — tailored to a specific job title and industry. It's designed for AEs, SDRs, and BDRs who want to run a discovery conversation that goes deeper than symptoms and uncovers the personal stakes behind a business problem. Use it when prepping for a discovery call where you need the prospect to feel the cost of inaction, not just acknowledge that a problem exists.

One-Page Business Case Champion Buy-In Investment Benefit

This prompt produces a one-page business case tailored to your deal's specific ROI drivers, cost of inaction, and stakeholder priorities. It's built for AEs and AMs working deals where the champion needs internal ammunition to get budget approved or build executive support. Use it during the proposal stage, after discovery is complete and you have enough context to quantify value.