Sales performance becomes predictable when judgment becomes shared. The highest-performing teams don’t have more meetings or more spreadsheets; they have a small set of questions everyone takes seriously. Those questions create alignment on what “qualified” means, what evidence makes a forecast real, and what trade-offs are acceptable when pressure rises.
17.1 Fact Base and Diagnosis Prompts: What Evidence to Gather, Who to Interview, and How to Cross-check
Most commercial problems arrive with a story attached: “lead quality dropped,” “the product is behind,” or “reps aren’t doing enough.” Stories can be useful starting hypotheses, but they become costly when they replace evidence. A strong diagnostic is the discipline of earning the right to hold a belief.
Minimum viable truth set: the smallest amount of evidence that is sufficient to make the next set of commercial decisions with confidence. The practical test is simple: if a data point or interview will not change a decision, treat it as optional. Speed matters because delayed clarity is lost revenue.
Begin with performance decomposition. If growth is off plan, it is always some combination of pipeline creation, conversion, velocity, retention, or price realization. Your first job is to quantify which two or three explain most of the gap, by segment and motion. Only then should you chase “why.”
Prompts that quickly locate the problem:
- Where is the leak? Is the gap driven by fewer new logos, weak expansion, elevated churn, or lower renewal uplift?
- Where does conversion break? Lead-to-meeting, meeting-to-accepted opportunity, early-stage progression, or late-stage close?
- Where is time being lost? Which stage is stretching, and is the cause customer approvals, internal approvals, or missing early de-risking?
- Where is the margin leaking? Is price realization down, discounting up, or services scope expanding without compensation?
Next, sample real deals. Pick a balanced set of wins, losses, and no-decisions from the last two quarters. Include “ordinary” deals, not only the largest ones; they often reveal systemic issues. For each sampled deal, capture four facts: trigger, buying group, proof path, and friction path. If you can’t capture these, your CRM and handoffs are part of the root cause.
Then use interviews to explain what the data cannot. Keep interviews short and deal-anchored. Ask people to walk you through specific opportunities, not to give general opinions about “the market.” You are searching for repeatable patterns, not compelling anecdotes.
Prompts for internal interviews:
- Winnability: What made a recent win winnable early—trigger clarity, stakeholder access, proof, or commercial flexibility?
- Late surprises: In a recent slip or loss, what did we learn too late—security, integration, budget, procurement posture, or internal scope?
- Proof reality: What do buyers actually believe, and what do they politely ignore?
- Friction: Where do approvals, handoffs, or tooling create waiting time or rework?
Prompts for customer interviews:
- Trigger: What changed that made this initiative real now?
- Decision criteria: What criteria decided the outcome, and which stakeholders weighted them most?
- Risk reduction: What evidence reduced uncertainty enough to move forward?
- No-decision: If you paused, what uncertainty remained unresolved?
Finally, cross-check hard. Cross-checking is how you avoid “single narrative” traps. If a claim shows up only in one place (only in the field, only in leadership, or only in CRM), treat it as a hypothesis until it appears in at least two independent sources.
Cross-check prompts:
- Field vs funnel: If “lead quality is down,” do conversion rates decline by source and segment, or is the issue acceptance standards?
- Product vs process: If “product gaps” are blamed, do losses cluster in specific use cases, or around missing risk events and lane coverage?
- Price vs value: If “price” appears, did we quantify value early and validate assumptions with the buyer?
- Competition vs status quo: Are we losing to a vendor, or to delayed decisions and internal indecision?
End diagnosis with testable hypotheses and a short list of “no-regret” moves. Testable hypothesis: a specific cause tied to a specific mechanism you can deploy, with a leading indicator that should move in weeks. No-regret move: a change that improves quality and economics even if your primary hypothesis is only partially right (for example, tighter qualification gates, clearer discount give-gets, faster handoffs).
Closing prompt: If you could change only three things in the next 30 days, what would they be, and which driver would each move? If you can’t answer that clearly, keep diagnosing until you can.
17.2 ICP and Account Prioritization Prompts: Defining “Fit,” Calibrating Focus, and Avoiding False Precision
ICP discipline is one of the few levers that improves growth and margin at the same time. When you pursue accounts that are likely to buy, succeed, and renew at target economics, everything downstream gets easier: win rates improve, cycles shorten, discount pressure declines, and customer success spends less time saving accounts that never should have been sold.
Define ICP with three lenses. Fit: the customer context matches where your offer reliably delivers outcomes. Value: the magnitude of impact is meaningful and measurable. Buyability: the likelihood of a decision within your planning horizon, given triggers, access, and risk friction. Most teams get fit and value roughly right and ignore buyability, then wonder why the pipeline is large but slow.
Prompts to define ICP in buying language:
- Trigger pattern: What events consistently precede active evaluation in our best deals?
- Baseline availability: What data must exist for value to be quantified credibly?
- Stakeholder structure: What lanes must be engaged early for deals to move (economic, technical, risk, procurement)?
- Delivery feasibility: What integrations, security requirements, or services needs are common, and can we satisfy them in standard scope?
- Profitability: Which account types buy at target price and terms without heavy exceptions?
Calibrate ICP using your own outcomes rather than industry stereotypes. Split your customers into groups: high retention versus low retention; strong expansion versus none; high support burden versus low. Then ask what differs systematically. You are looking for repeatable signals that can be used in qualification, not academic precision.
Calibration prompts:
- Success signature: What do customers who renew and expand have in common that struggling customers do not?
- Failure signature: What early indicators were present in churned accounts at the time of sale?
- Discount signature: Where do we discount most, and what problem is the discount compensating for (value ambiguity, competition, scope, timing)?
Prioritization is where ICP becomes operational. Every company has three scarce resources: seller time, specialist time, and executive time. Prioritization should answer how each is allocated. If it doesn’t change allocation, it is just labeling.
Prompts that turn prioritization into rules:
- Investment: Which accounts deserve proactive planning and multi-threading, and which should be covered programmatically?
- Support: What must be true for a deal to receive specialist attention, and what evidence is required?
- Leadership: When is executive sponsorship warranted—size, strategic value, renewal risk, or competitive intensity?
- Deprioritization: What is the consistent, respectful “no” standard for low-fit pursuits?
Avoid false precision. Elaborate scoring systems often create the illusion of certainty while masking disagreement about priorities. Good prioritization is a portfolio decision under uncertainty. It should be consistent and easy to explain, even if it is imperfect.
Prompts to prevent false precision:
- Disqualifier discipline: What conditions automatically push an account to low-touch coverage, regardless of potential?
- Reallocation discipline: If you had to drop 30% of active pursuits tomorrow, what rule would you use to decide quickly?
- Time-horizon discipline: Which accounts are likely to decide in the next 6–12 months versus “someday”?
Make ICP consistent across functions. Marketing targeting, SDR outreach, partner programs, and sales coverage should reference the same account universe and the same definitions of fit and priority. Misalignment here creates revenue friction and wasted effort.
Alignment prompt: If you randomly pick ten accounts from marketing’s current target list, would your best sales managers want their reps to spend time there? If not, the issue is definition and governance, not rep activity.
17.3 Account and Deal Strategy Prompts: Clarifying Value, Stakeholders, Risk, and the Next Buyer Commitment
Deal strategy is not a document; it is a sequence of choices that increases deal safety. The core choices are: how you frame value, how you build a buying coalition, how you surface and schedule risk, and how you maintain control of the next decision event. When these choices are made well, deals move with fewer surprises and less destructive discounting.
Deal safety: the ability of a deal to survive delay, stakeholder change, competitive pressure, and procurement negotiation without collapsing or forcing uneconomic concessions. Deal safety is built by evidence the buyer accepts, not by seller confidence.
Start with value. Many teams wait until the proposal to quantify ROI, then wonder why procurement anchors on price. Value must be established early enough that price is interpreted through an outcome lens.
Prompts that sharpen a value case:
- Outcome clarity: What will be measurably better, and who will agree that it is better?
- Baseline credibility: What is the current state, and what evidence supports it?
- Impact logic: What specific mechanism creates the improvement in this environment?
- Time-to-value: When does the buyer get their first meaningful result, and what must they do to enable it?
- Cost of inaction: What happens if they delay six months?
Then build the coalition. In complex B2B deals, the seller’s job is often internal alignment more than persuasion. Treat unknown stakeholders as a risk. The safe assumption is that someone you haven’t met can stop the deal.
Prompts to strengthen stakeholder coverage:
- Lane coverage: Do we have active engagement in business/value, technical, risk/security, and procurement lanes?
- Champion strength: Why does our champion care personally, and what do they risk by advocating?
- Internal selling: What can the champion forward that will stand up to finance, security, and procurement scrutiny?
- Introduction logic: For the next stakeholder we need, what is the reason they would accept a meeting?
Make risk operational. Risk is not a feeling; it is uncertainty that can be reduced with the right event. If a risk cannot be reduced by a scheduled action, it is not defined well enough to manage.
Prompts to manage risk like a plan:
- Top risks: What are the three most likely failure modes in this deal?
- Signals: What will we see that tells us each risk is real?
- De-risking events: What review, workshop, reference, or pilot reduces each risk?
- Timing: Are those events early enough that late-stage surprises are unlikely?
- Ownership: Who owns reducing each risk, and by when?
Handle competition by controlling the comparison frame. Buyers rarely choose the “best product” in the abstract; they choose the option that feels safest for their context and fastest to outcomes. Competitive advantage should therefore be expressed as reduced risk, faster time-to-value, or lower total effort, supported by proof.
Prompts to control the competitive frame:
- True alternatives: Who are we competing against, including internal build and status quo?
- Criteria control: Did we help define decision criteria, or are we reacting to someone else’s checklist?
- Proof plan: What evidence will the buyer accept, and when will they see it?
- Procurement posture: What concession requests are most likely, and what give-gets protect economics?
End every deal discussion with the next buyer commitment. “Send a proposal” is vendor work; it is not buyer commitment. Progress is a buyer-owned action with a date.
Prompts that enforce commitment discipline:
- Next decision event: What is the next buyer-owned decision milestone, and what date is on the calendar?
- Definition of done: What must be true after that milestone for the deal to advance?
- Mutual path: Do we have an agreed sequence of milestones through risk reviews, procurement, and kickoff readiness?
- Requalification: If the buyer won’t commit, what does that indicate about urgency or fit?
These prompts become powerful when managers use them consistently in coaching. The manager is not asking for more information; the manager is teaching the rep what “real” looks like. Over time, deal reviews shift from storytelling to evidence, and forecasts become more accurate because they are anchored in buyer behavior.
17.4 Operating Cadence Prompts: Questions That Make Pipeline Reviews, Forecast Calls, QBRs, and Win/Loss Sessions Actionable
Cadence is where strategy is enforced. The meeting itself is not the value; the value is the decision the meeting produces. If your cadence does not repeatedly force requalification, resource reallocation, and learning, it will become performance theater.
Decision focus: the discipline of using live time for choices and commitments, while treating metrics and status as pre-read material.
Weekly pipeline reviews should protect truth and capacity. The goal is to keep the pipeline “clean” enough that managers can coach and forecast without being drowned in dead deals.
Pipeline review prompts that drive action:
- Stage integrity: What evidence proves the deal belongs in this stage today?
- Momentum: What buyer commitment occurred since the last review?
- Stall discipline: Which deals have no buyer commitment in the last 14–21 days, and what is the requalification decision?
- ICP focus: Where are we spending time outside priority fit, and why?
- Interventions: Which deals need specialist help or executive engagement this week, and what is the specific ask?
Forecast calls should be evidence-based and short. The most common failure is treating “commit” as a feeling. “Commit” should be earned by observable proof: scheduled decision events, identified owners, surfaced risk reviews, and a clear path through procurement.
Forecast prompts that reduce surprises:
- Buyer event: What is the next buyer-owned milestone and date?
- Risk events: Have security, integration, and legal steps been surfaced and scheduled?
- Value acceptance: Has the buyer accepted the outcome logic and assumptions as plausible?
- Commercial posture: Are target price and give-get posture aligned internally before negotiation begins?
- Single biggest risk: What risk could still kill the deal, and what action this week reduces it?
Quarterly reviews should reallocate resources based on what is working, not simply celebrate or explain results. The output should be a short list of “more of,” “less of,” and “stop.”
Quarterly review prompts that force reallocations:
- Segment truth: Which segments deliver growth with acceptable retention and margin?
- Play truth: Which plays create accepted opportunities and conversion, not just meetings and activity?
- Capacity truth: Where are we constrained—seller coverage, specialist capacity, delivery capacity, or approvals?
- Stop doing: What work will we remove to fund focus next quarter?
Win/loss sessions should result in shipped changes. If a session ends with “interesting,” it is entertainment. If it ends with a change in a talk track, a proof pack, a stage gate, or a coaching focus, it is a learning loop.
Win/loss prompts that produce change:
- Trigger: Did we anchor on the buyer’s trigger and urgency early?
- Criteria: What criteria decided the outcome, and did we influence them?
- Proof timing: What evidence moved confidence, and did it appear early or late?
- Failure mode: Was the loss to a competitor, to no-decision, or to internal friction like late risk reviews?
- Change: What one adjustment would most improve the next ten deals of this type?
Across all cadences, end with commitments. A simple discipline keeps meetings honest: name the decision, name the owner, name the date, and name the expected impact. If you cannot do that, you did not make a decision—you had a discussion.
17.5 Measurement and Governance Prompts: Defining Metrics Once, Inspecting the Right Signals, and Preventing Data Drift
Sales measurement should reduce debate and accelerate action. When definitions drift, teams create their own spreadsheets, leaders lose trust in dashboards, and the organization responds late. Governance is not a bureaucratic layer; it is the set of owners, rules, and cadences that keep the truth stable enough to act on.
Single source of truth: a governed set of definitions and data sources that produces the same answer to the same question across teams. The aim is consistency, not perfection.
Start with a KPI spine: a small set of outcome metrics and the few drivers that explain them. Most organizations need fewer KPIs than they think. They need more agreement on definitions and more discipline in inspection.
Prompts to design a KPI spine:
- Outcomes: Which outcomes define success for the next 12 months (bookings, net retention, gross margin, cash), and what trade-offs are acceptable?
- Drivers: Which two or three drivers explain most variance (win rate, cycle time, deal size, price realization, churn)?
- Leading indicators: What signals move early enough to intervene (stage progression, stall rate, renewal risk coverage, exception volume)?
Then lock definitions with edge-case clarity. Most metric fights are not about arithmetic; they are about what counts, when it counts, and whether a record is “real” or just entered.
Prompts that harden metric definitions:
- Unit of analysis: Are we measuring at opportunity level, account level, or customer cohort level?
- Timing basis: Are we using created-date cohorts or closed-date totals, and do we label them clearly?
- Qualification standard: What evidence must exist for something to be counted as a pipeline?
- Economic basis: Are we using ARR, ACV, TCV, or recognized revenue, and is it aligned to targets?
Design dashboards to drive behavior. A dashboard should not only show totals; it should point to what needs attention this week. That typically means pairing volume with quality and surfacing exception lists that managers can act on.
Prompts to make dashboards actionable:
- Exception visibility: Does the view surface the specific deals, renewals, or approvals that require action?
- Gaming resistance: For every volume metric, what quality metric prevents optimization of the wrong thing?
- Decision linkage: When a metric moves, is the next decision obvious, or do we still argue about interpretation?
- Ownership: Does each metric have an owner with the authority to change the system, not just report it?
Prevent data drift with workflow and inspection. Data quality improves when CRM is used to run the business and when stage movement requires evidence. It declines when CRM is treated as a reporting chore and exceptions are granted quietly.
Prompts that keep data usable:
- Minimum required evidence: What is the smallest set of fields or artifacts that make a stage meaningful?
- Audit rhythm: How will we sample opportunities monthly for stage integrity, and what happens when evidence is missing?
- Change control: Who approves changes to stages, fields, and routing rules, and how are changes communicated?
- Exception discipline: How do we track and review exceptions so one-off concessions do not become precedent?
Governance becomes real when decision rights are explicit. If “everyone owns data,” no one owns it. Assign owners for definitions, routing, stages, and commercial approvals, and give them a regular forum to resolve conflicts quickly. The output of governance should be fewer exceptions, faster decisions, and earlier truth—because earlier truth is what allows the organization to intervene while there is still time to change outcomes.
