Sales & Revenue Prompts to Communicate More Effectively

You are a sales manager preparing the weekly forecast submission. Pipeline data: [PASTE: Rep | Deal | Stage | Amount | Close date | Forecast category (commit/best case/pipeline) | Rep's confidence note] Build the forecast submission: 1. Roll-up by rep — each rep's commit, best case, and pipeline totals 2. Manager adjustments — deals you'd reclassify based on your knowledge; note reason 3. Coverage analysis — commit + best case as % of remaining quota for the period 4. Risk items — deals in commit that have warning signs; call out specifically 5. Upside items — deals in pipeline that could accelerate; note what would need to happen Output: Forecast submission table by rep. Manager-adjusted totals. Risk and upside narrative for leadership. Confidence level: high / medium / low on hitting number.

You are a sales executive preparing for a first meeting with a prospect account. Account information: [PASTE or DESCRIBE: Company name, industry, size (employees/revenue), known products or tech stack, any recent news (funding/acquisitions/leadership changes/expansions), any mutual connections] Build a pre-call research brief: 1. Business context — what does this company do, how do they make money, what are their current priorities? 2. Likely pain points — based on their industry, size, and recent news, what problems are they likely experiencing that we solve? 3. Stakeholder intelligence — who are the likely buyers for our solution at this company? What do they typically care about? 4. Our relevant proof points — customers like them; similar industry or use case wins 5. Opening questions — 3–5 questions to ask in the first meeting to qualify and understand their situation Output: Pre-call research brief. Opening questions. Hypothesis about their most likely pain point to validate in the meeting.

You are a customer success manager preparing for a quarterly business review with a customer. Account data: [PASTE: Account | ARR | Products in use | Usage metrics (logins/key actions/active users) | Support tickets (last quarter) | Key milestones achieved | Open issues | Goals customer stated at last QBR | Renewal date | Expansion opportunities] Build the QBR agenda: 1. Progress review — what did we commit to last quarter? What did we deliver? 2. Value realized — specific business outcomes the customer achieved using our product; quantify where possible 3. Usage and adoption review — how are they using the product? Where is adoption lagging? 4. Roadmap and what's coming — relevant upcoming features for their use case 5. Next quarter plan — mutual commitments for the next 90 days Output: QBR agenda and pre-read document. Talking points for each section. Questions to ask to uncover expansion needs and confirm satisfaction.

You are a customer success manager escalating a high-risk churn situation. Account data: [PASTE: Account | ARR | Churn signals observed | Timeline (when did signals start) | What has been tried | Current champion status | Economic buyer relationship | Any unresolved issues | Renewal date] Write the escalation brief: 1. Situation summary — what is happening and why this account is at risk 2. Business impact — ARR at risk, reference value, potential expansion lost 3. Root cause — what went wrong? (product gaps / implementation issues / relationship / competitive / budget) 4. What has been tried — actions taken to date; why they haven't resolved the risk 5. Escalation ask — what specific executive or resource support is needed and by when? Output: Escalation brief for VP of Customer Success or CRO. Clear ask. Timeline. Recommended intervention with owner.

You are a sales executive completing the handoff to the customer success team at deal close. Deal data: [PASTE: Account | ARR | Products sold | Close date | Key stakeholders (name/title/role/relationship strength) | Customer's stated goals and success metrics | Any promises made during sales | Known risks or sensitivities | Competitive context | Implementation timeline agreed] Complete the CS handoff document: 1. Why they bought — customer's specific pain points and what they expect our solution to solve 2. What was sold — products, configuration, professional services included; anything non-standard 3. Key people — champion, economic buyer, day-to-day contacts; who to call if there's a problem 4. Commitments made — anything promised during the sales process (custom features, integrations, timelines, pricing terms) 5. Risks to flag — anything that could complicate onboarding or early success Output: CS handoff document. Suitable for the CS team to start their engagement immediately without having to ask sales for context.

You are an SDR completing the handoff of a qualified opportunity to an account executive. Qualification data: [PASTE: Account | Contact (name/title) | How the lead was sourced | Discovery call notes | Pain points identified | BANT or MEDDIC qualification | Next agreed step | Any competitive context | Contact's communication preference] Complete the AE handoff: 1. Why now — what triggered the prospect to engage? What is their compelling event? 2. What they told us — specific pain points in their own words; don't paraphrase 3. Qualification status — what is confirmed vs. assumed; what still needs to be validated 4. The right entry point — which stakeholder is the champion? Who else should be in the first AE meeting? 5. Agreed next step — what was committed to the prospect? AE must honor this commitment Output: Opportunity handoff document. AE can walk into the first meeting informed. No duplicate questioning of the prospect about things we already asked.

You are an implementation manager completing the post-implementation handoff to customer success. Implementation data: [PASTE: Account | Products implemented | Go-live date | Implementation team | What was delivered vs. scope | Any scope changes or issues during implementation | Technical configuration notes | Key customer contacts | Open items post-go-live | Customer satisfaction at go-live] Complete the CS handoff: 1. What was implemented — products, integrations, configurations; anything non-standard 2. How the implementation went — on time / delayed / issues that were resolved / issues still open 3. Customer sentiment — are they happy at go-live or are there lingering frustrations? 4. Open items — anything not completed in implementation scope that CS must track 5. Early adoption risks — any configuration choices or gaps that may create adoption challenges Output: Implementation-to-CS handoff document. CS team can serve the customer immediately without implementation context gaps.

You are a marketing operations manager documenting the MQL-to-SQL handoff process. Current state: [DESCRIBE: How MQLs are currently defined, how they reach sales (CRM alert/email/Slack), current SLA for sales follow-up, lead source and intent data passed to sales, feedback mechanism between sales and marketing] Design the handoff process: 1. MQL definition — specific criteria that trigger handoff; not vague (e.g., "lead score >75 with demo request OR pricing page visit + 2 content downloads in 7 days") 2. Data passed to sales — what information must accompany the MQL (company, title, behavior data, intent signals, previous interactions) 3. Routing — how does the MQL reach the right rep immediately? 4. Response SLA — time from MQL creation to first rep contact; escalation if not met 5. Feedback loop — how sales communicates lead quality back to marketing; how often reviewed Output: MQL-to-SQL handoff process document. Routing logic. SLA definition. Feedback mechanism template.

You are a customer success manager transitioning a renewing account to an expansion conversation. Account data: [PASTE: Account | Renewal ARR | Renewal date | Health score | Expansion opportunities identified | Products they don't have | Champion readiness for expansion conversation | Any timing factors (budget cycle/new initiative)] Plan the handoff: 1. Renewal close confirmation — confirm renewal is secured before pivoting to expansion 2. Expansion trigger — what specific event or need justifies opening an expansion conversation now? 3. Who owns it — does CS own the expansion conversation or does it get handed to sales? Define clearly. 4. Introduction plan — if handing to sales, how is the introduction made? CS must warm the intro. 5. Customer value foundation — what value has been demonstrated that makes the expansion conversation credible? Output: Renewal-to-expansion transition plan. Owner for expansion conversation. Introduction approach if handing off. Talking points for first expansion conversation.

You are a support manager escalating a customer issue to the account management team. Escalation data: [PASTE: Account | ARR | Issue description | Duration of issue | Impact on customer (business disruption level) | Steps already taken | Customer sentiment | Escalation contact at customer | Risk to renewal/relationship] Complete the escalation handoff: 1. Issue summary — what is happening, in plain language, with business impact context 2. Timeline — when it started, what has been tried, where we are now 3. Customer emotional state — frustrated / angry / patient / about to escalate further 4. What is needed from account management — executive call / compensation offer / escalated engineering resources 5. What not to say — any commitments support has made that account management must honor; anything that is off-limits Output: Escalation handoff brief. Recommended account management response. Draft executive outreach message to customer.

You are an account executive briefing a sales engineer before a technical discovery or demo. Opportunity data: [PASTE: Account | Stage | Amount | Key stakeholders (technical and business) | Business pain identified | Technical environment (known systems/integrations/current solution) | Demo goals | Any technical concerns raised | Competitor in play and their technical differentiators] Brief the SE: 1. Business context — why is the customer looking? What outcome are they trying to achieve? 2. Technical environment — what we know about their stack; what we need to learn 3. Demo goals — what must the demo prove to advance the deal? What are the 2–3 moments that must land? 4. Landmines — known technical objections or areas where our solution has gaps vs. their requirements 5. Questions for SE to uncover — technical discovery questions that will qualify or disqualify this deal Output: SE pre-brief document. Demo goals. Technical discovery questions. Landmines to navigate.

You are a customer success manager identifying customers ready to become advocates. Account data: [PASTE: Account | NPS score | Health score | Time as customer | Key achievements/ROI realized | Reference given before? | Executive relationship level | Any public-facing wins (case study/press release) | Willingness to advocate (known or estimated)] For each potential advocate: 1. Advocacy readiness — are they genuinely successful and willing to speak publicly? 2. Best advocacy format — reference call / case study / event speaker / G2/Capterra review / logo use 3. Ask to make — specific, low-effort first ask that matches their willingness level 4. Value exchange — what do we offer the customer for their advocacy time? 5. Internal handoff — who manages the advocacy relationship: CS, marketing, or a dedicated reference program? Output: Customer advocacy pipeline. Recommended ask per customer. Value exchange. Internal owner for each relationship.

You are an account manager completing an upsell and handing off to implementation. Upsell data: [PASTE: Account | New product/module sold | ACV uplift | Customer's goal for the expansion | Key contacts for implementation | Timeline agreed | Any dependencies on existing implementation | Commitments made during upsell | Customer champion for this expansion] Complete the implementation handoff: 1. Why they bought the expansion — specific use case and expected outcome 2. Dependencies — does this expansion require changes to existing configuration or integrations? 3. Timeline commitments — any dates promised to the customer that implementation must hit 4. Key people — who drives this on the customer side? Who has budget authority? 5. Success criteria — how will the customer define success for this expansion at 90 days? Output: Upsell implementation handoff document. Implementation team can scope and plan without needing to re-engage sales for context.

You are a customer success manager preparing a ROI summary for a customer ahead of renewal. Data: [PASTE: Account | Products used | Metrics available (usage volume / time saved / error reduction / revenue impacted / cost avoided) | Customer's stated goals at purchase | Any data the customer has shared about outcomes] Build the ROI report: 1. Before state — what was the customer doing before? What was the cost/pain? 2. After state — what outcomes have they achieved using our solution? 3. Quantified value — calculate ROI where data supports it; express in $ or time saved 4. Attribution — connect specific product usage to specific outcomes 5. Future value — at current usage growth, what additional value is possible? Tone: Evidence-based. Don't overstate. If data is limited, use ranges and clearly label them as estimates. Output: Customer ROI report. 1–2 pages. Suitable for sharing with the economic buyer at renewal.

You are a customer success manager preparing for a customer advisory board meeting. CAB context: [DESCRIBE: Number of customers attending, their industries and sizes, meeting goals (product feedback / roadmap input / relationship building / reference development), agenda topics planned] Build the preparation brief: 1. Attendee profiles — who is coming, what they care about, any relationship sensitivities 2. Discussion guides — specific questions to generate actionable product or go-to-market feedback 3. Roadmap preview — what can we share that demonstrates we're listening to their prior feedback? 4. Facilitation plan — how to ensure all attendees contribute, not just the loudest voices 5. Follow-up commitments — what will we commit to act on based on their input? Output: CAB preparation brief. Discussion guides per topic. Facilitation plan. Follow-up template for post-meeting.

You are a customer success manager preparing for a renewal conversation. Account data: [PASTE: Account | Current ARR | Renewal date | Health score | Key achievements in the contract period | Any open issues | Usage trend | Champion relationship | Economic buyer relationship | Any pricing or product changes in the renewal] Prepare for the renewal conversation: 1. Value summary — 3 specific outcomes the customer achieved; quantify where possible 2. Renewal ask — how to frame the renewal (continuation of value, not "signing paperwork") 3. Anticipated objections — what pushback is likely? Budget / competing priorities / price / product gaps? 4. Expansion opportunity — is there a natural upsell to raise alongside the renewal? 5. Walk-away scenario — if they push hard on price, what is the minimum acceptable outcome vs. churn? Output: Renewal conversation prep brief. Value talking points. Objection responses. Expansion opening. Pricing flexibility guidance.

You are a CRO preparing the board deck revenue section. Financial data: [PASTE: ARR | MRR | New ARR | Expansion ARR | Churned ARR | Net Revenue Retention % | Logo churn % | Pipeline | Win rate | Average deal size | Sales cycle length — vs. prior period and vs. plan] Write the board narrative: 1. Headline — one sentence on the quarter: are we ahead, on track, or behind and why 2. Growth drivers — what is driving new ARR? (new logos / expansion / specific segments) 3. Retention health — NRR and logo churn; are we retaining and growing the base? 4. Pipeline — coverage ratio; quality of pipeline; leading indicator for next quarter 5. Risks and opportunities — honest assessment of what could help or hurt next quarter Format: 300–400 words. Plain English — board members are not all sales experts. Bold headline metrics.

You are a CFO preparing the monthly revenue summary for the board. Revenue data: [PASTE: Recognized revenue (month/QTD/YTD) | ARR | MRR | ARR growth rate | Pipeline (by stage) | Forecast for current quarter | Forecast for next quarter | Key assumptions] Produce: 1. Revenue snapshot — recognized revenue vs. plan vs. prior year; one sentence on performance 2. ARR health — ARR growth rate; NRR; new vs. expansion vs. churn breakdown 3. Forward visibility — current quarter forecast confidence; next quarter early view based on pipeline 4. Key assumptions — what must be true for us to hit the current forecast? 5. Risk and upside — what could materially affect the forecast in either direction? Format: Executive summary, max 1 page. Plain language. Bold headline numbers. Suitable for board pre-read.