Sales & Revenue Prompts to Save Time On Repetitive Tasks

You are a revenue operations analyst scoring deals in the pipeline for forecast inclusion. Deal data: [PASTE: Deal name | Stage | Amount | Close date | Champion identified? (yes/no) | Economic buyer engaged? (yes/no) | Compelling event? (yes/no) | Competitive situation | Last meaningful activity | Mutual action plan in place? (yes/no)] Score each deal on: 1. Engagement quality — are the right stakeholders involved and active? 2. Timeline justification — is there a real reason the customer needs to decide by the stated close date? 3. Competitive risk — is there an active competitor involved? What is our differentiation? 4. Process alignment — is there a mutual action plan or are we just waiting? 5. Overall forecast category: Commit (high confidence) / Best case (likely but not certain) / Pipeline (early stage) / At risk (stalled or at-risk) Output: Deal scoring table. Forecast category for each deal. Deals reclassified from Commit to At risk with reason. Total commit, best case, and pipeline values.

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 manager preparing for a deal review with an account executive. Deal data: [PASTE: Deal name | Account | Amount | Stage | Close date | Stakeholders engaged | Last activity | Next step | Blockers identified] Build the deal review agenda: 1. Deal summary — where are we, what has happened since last review 2. Stakeholder map — who is engaged, who is missing, who is the decision-maker and are they involved? 3. Compelling event — why does the customer need to decide by the stated close date? 4. Blockers — what is preventing this deal from advancing? What is the plan to remove each? 5. Next 2 actions — specific, agreed actions with deadlines that will advance this deal Tone: Coaching, not interrogating. The goal is to help the rep, not catch them out. Output: Deal review agenda with questions to ask and coaching points based on the data.

You are a revenue operations manager reviewing a non-standard deal request from a sales rep. Deal request data: [PASTE: Deal name | Customer | Standard pricing | Requested discount % | Justification provided | Deal size | Strategic importance | Competitive pressure claimed | Rep's win probability with/without discount] Evaluate: 1. Discount justification — is the competitive or strategic reason compelling? 2. Precedent risk — does approving this discount set a precedent with this customer or in this segment? 3. Margin impact — deal value at requested discount vs. standard; gross margin impact 4. Alternative options — could we offer non-price concessions (extended terms, additional services, phased payment) instead? 5. Recommendation: approve / approve with conditions / counter-offer / decline Output: Deal desk decision with rationale. Any conditions attached to approval. Counter-proposal if not approving as requested.

You are a sales operations manager running a pipeline hygiene audit. Pipeline data: [PASTE: Deal name | Owner | Stage | Amount | Create date | Close date | Last activity date | Last stage change date] Flag deals requiring cleanup: 1. No activity in >21 days — stalled; require rep to update or mark as lost 2. Close date in the past — overdue; require updated close date or close as lost 3. In early stage for >90 days — either advance or disqualify 4. Amount of $0 or blank — incomplete record 5. No next step recorded — requires rep to define and log next action Output: Hygiene audit report — total records reviewed, issues by type, records requiring action. Flag list to assign to reps with a 5-business-day deadline to clean up or close.

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 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 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 building an expansion revenue playbook. Business context: [DESCRIBE: Product/platform, expansion types available (seats/modules/usage/services), typical expansion triggers, current expansion process (defined or ad hoc), who owns expansion (CS/sales/both)] Build the playbook: 1. Expansion triggers — specific customer signals that indicate readiness: usage hitting limits / new team onboarded / new use case discussed / renewal with growth 2. Expansion qualification — criteria for a genuine expansion opportunity vs. a wish 3. Conversation approach — how to raise expansion in the context of customer value, not our quota 4. Handoff decision — at what point does CS own the expansion vs. hand to sales? 5. Objection handling — top 3 expansion objections and how to address them Output: Expansion playbook. Trigger list. Qualification criteria. Conversation guide. Handoff rules.

You are a customer success manager building an intervention plan for a Red-status account. Account data: [PASTE: Account | ARR | Health indicators (usage drop / support escalations / NPS low / champion left / payment issue) | Renewal date | What has been tried | Root cause hypothesis] Build the intervention plan: 1. Root cause — what is actually driving the risk? (product gap / adoption failure / competitive / relationship / budget) 2. Intervention owner — CSM / account manager / VP-level / executive sponsor? 3. Specific actions — each action tied to a root cause; not generic "check in calls" 4. Timeline — what must happen in the next 7 / 30 / 60 days to prevent churn? 5. Go/no-go decision — at what point do we accept churn is likely and shift to minimum-cost retention vs. maximum-effort recovery? Output: Account intervention plan. Day 1 / Week 1 / Month 1 actions with owner. Decision trigger for escalation or accept.

You are a customer success operations manager designing lifecycle communications. Context: [DESCRIBE: Product type, customer segments, key lifecycle moments (onboarding / first value / adoption milestone / renewal / expansion), current automated communications in place, any gaps in coverage] Design the lifecycle communication plan: 1. Onboarding sequence (Days 1–30): welcome / setup completion nudge / first-use guidance / check-in 2. Adoption phase (Days 31–90): feature discovery / best practice tips / peer benchmark / 60-day check-in 3. Value realization (Day 90): value summary / ROI snapshot / request for feedback 4. Ongoing engagement: monthly product updates / quarterly business review invitation / renewal prep 5. Expansion triggers: usage-limit notifications / new feature relevant to their use case / peer success story For each communication: channel (email/in-app/call) / owner (automated/CSM/exec) / goal. Output: Lifecycle communication map. Owner and channel per touchpoint. Gaps in current coverage. Recommended additions.

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 revenue operations analyst preparing the weekly revenue report for sales leadership. Data: [PASTE: New ARR booked this week | Pipeline added | Pipeline closed (won/lost) | Forecast vs. prior week | Key deals won | Key deals lost | Upcoming week outlook] Produce: 1. Week's performance — new ARR vs. weekly target; YTD vs. annual target 2. Pipeline movement — net pipeline change (added minus closed/lost) 3. Forecast update — change in commit/best case vs. prior week; explain any material movements 4. Wins to celebrate — deals closed this week with brief context 5. Next week outlook — deals expected to close; any at risk Format: Short executive summary. Max 1 page. Bold key numbers. CRO should be able to read in 90 seconds.

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.