Customer Success Managers who need QBR content fast. Copy these prompts into ChatGPT, fill in your account details, and get polished quarterly review materials in seconds. No starting from scratch, no writer’s block.
These prompts pair well with Jasper AI for Customer Success-specific tone control, or Copy.ai for fast iteration.
Executive Summary Creation
You are a Customer Success Manager writing an executive summary for a quarterly business review.
Client: {client_company_name} Relationship length: {months_or_years_as_customer} Primary stakeholder: {main_contact_name_and_title} Quarter performance: {exceeds_expectations / meets_expectations / below_expectations} Key wins this quarter: {three_to_four_wins_in_bullets} Main challenges faced: {two_challenges_with_context} Revenue impact: {dollar_figure_or_percentage} Contract status: {renewal_date_and_value}
Write a 250-300 word executive summary that opens with the biggest business impact, addresses challenges as opportunities, and closes with next quarter priorities. Use confident, data-driven language that positions our partnership as strategic.
When to use it: When you need the opening section of your QBR deck and want to lead with impact, not features.
Pro tip: If your client had a rough quarter, lead with usage growth or engagement metrics instead of pure ROI numbers.
You are preparing a QBR executive summary for a high-growth client considering expansion.
Client: {client_company_name} Industry: {client_industry} Growth stage: {startup / scale-up / enterprise} Current ARR with us: {annual_recurring_revenue} Usage growth: {percentage_increase_this_quarter} Team growth: {new_users_added_or_percentage} Expansion opportunity: {upsell_product_or_seats} Potential expansion value: {dollar_amount} Decision maker: {expansion_decision_maker_name}
Write a 200-250 word executive summary focused on scaling impact. Highlight how increased usage correlates with their growth. Position expansion as inevitable next step. End with specific expansion recommendation and timeline.
When to use it: During QBRs where upselling is the primary goal and the client is in growth mode.
Pro tip: Reference their hiring plans or funding rounds if you know them—shows you understand their business context.
You are writing a QBR executive summary for a client with mixed performance this quarter.
Client: {client_company_name} Contract size: {annual_contract_value} Adoption rate: {percentage_of_licensed_users_active} Performance vs goal: {behind / on-track / ahead} Biggest win: {most_significant_success_story} Main blocker: {primary_obstacle_to_success} Internal champion: {key_advocate_name_and_role} Risk level: {low / medium / high_churn_risk}
Write a 300-350 word balanced executive summary using the “Challenge-Action-Result” structure. Acknowledge the mixed results upfront, detail specific actions taken, and demonstrate measurable progress. Close with concrete next-quarter commitments.
When to use it: When you need to address underperformance honestly while maintaining confidence in the partnership.
Pro tip: Include a specific metric that improved, even if overall performance was mixed—shows momentum.
You are creating a QBR executive summary for a long-term strategic client.
Client: {client_company_name} Relationship duration: {number_of_years} Total contract value: {cumulative_revenue} Year-over-year growth: {percentage_growth} Strategic initiatives supported: {major_client_projects_we_enabled} Executive sponsor: {c_level_champion_name} Competitive landscape: {key_competitors_they_mention} Industry trends: {relevant_market_changes}
Write a 280-320 word strategic executive summary that positions our relationship as business-critical. Reference industry trends and competitive advantages. Include specific examples of strategic value delivered. Frame next quarter around innovation and market leadership.
When to use it: For enterprise clients where the relationship transcends vendor-customer into strategic partnership.
Pro tip: Mention industry benchmarks or peer comparisons to reinforce their competitive advantage through your solution.
You are writing an executive summary for a QBR with multiple stakeholders from different departments.
Client: {client_company_name} Attending departments: {departments_represented} Primary use cases: {different_ways_each_team_uses_product} Cross-team collaboration metrics: {sharing_or_workflow_data} Department-specific wins: {wins_for_each_team_in_bullets} Integration success: {tools_connected_or_processes_automated} Overall efficiency gain: {time_saved_or_cost_reduced}
Write a 320-370 word executive summary that speaks to multiple audiences. Open with company-wide impact, then highlight department-specific value. Use language that resonates across functions. Close with vision for deeper cross-team integration.
When to use it: When your QBR includes stakeholders from sales, marketing, operations, or other departments beyond your main contact.
Pro tip: Use metrics each department cares about—marketers want conversion rates, sales wants pipeline velocity, ops wants efficiency.
Performance Analysis and Metrics
You are analyzing quarterly performance data for a customer success QBR presentation.
Client: {client_company_name} Baseline period: {previous_quarter_or_year} Current usage metrics: {key_performance_indicators} Goal achievement: {percentage_of_targets_met} User engagement: {login_frequency_or_feature_adoption} Business outcome: {revenue_growth_or_cost_savings} Benchmark comparison: {industry_average_or_peer_performance} Data confidence: {high / medium / low_data_quality}
Write a 400-450 word performance analysis that tells a story with the data. Structure as Problem-Solution-Impact-Proof. Include specific metrics but explain what they mean for business outcomes. Address any data limitations transparently. End with clear trajectory for next quarter.
When to use it: When you have strong data and need to build a compelling narrative around measurable success.
Pro tip: Lead with the metric that improved most dramatically—even if it’s not the most important one, it creates positive momentum.
You are creating a performance comparison analysis for a QBR with a competitive client.
Client: {client_company_name} Industry: {specific_industry_or_vertical} Company size: {employee_count_or_revenue_range} Our performance: {key_metrics_achieved} Industry benchmark: {average_performance_data} Top performer benchmark: {best_in_class_numbers} Competitive advantage: {unique_capabilities_or_results} Improvement opportunity: {biggest_gap_to_close}
Write a 350-400 word competitive performance analysis using the “Good-Better-Best” framework. Position their current performance as good, industry-leading as better, and our enhanced partnership as best. Include specific percentiles and rankings. Close with roadmap to top-tier performance.
When to use it: For competitive clients who respond to benchmarking and want to lead their industry.
Pro tip: If they’re already top-performing, compare them to companies one size tier up instead of same-size peers.
You are presenting quarterly metrics for a client who struggles with data interpretation.
Client: {client_company_name} Stakeholder background: {technical / business / executive} Key metric 1: {most_important_number} What it means: {business_impact_in_plain_language} Key metric 2: {second_priority_number} Success story: {specific_example_or_case_study} Trend direction: {improving / stable / declining} Next milestone: {specific_target_for_next_quarter}
Write a 250-300 word metrics explanation using simple, jargon-free language. Start each metric with “This means…” statements. Use analogies if helpful. Focus on business impact over technical details. Include one concrete success story that illustrates the numbers.
When to use it: When presenting to executives or stakeholders who want insights, not raw data.
Pro tip: Use percentage changes instead of absolute numbers when the baseline might not be familiar to them.
You are documenting unexpected performance outcomes for a QBR discussion.
Client: {client_company_name} Expected outcome: {original_goal_or_prediction} Actual result: {what_really_happened} Variance: {percentage_difference} Root cause analysis: {why_results_differed} Learning captured: {insight_gained} Adjusted strategy: {how_approach_will_change} Confidence level: {high / medium / low_for_new_approach}
Write a 300-350 word performance variance analysis using the “Hypothesis-Test-Learn-Adapt” structure. Frame unexpected results as valuable learning, not failure. Include specific actions to capitalize on insights. Close with updated expectations and methodology.
When to use it: When actual results significantly differed from projections and you need to maintain credibility while adjusting course.
Pro tip: If results exceeded expectations, explore what you can replicate. If they fell short, focus on controllable factors going forward.
You are creating a quarterly ROI calculation for budget justification discussions.
Client: {client_company_name} Investment amount: {annual_or_quarterly_contract_value} Time period: {months_of_usage_measured} Hard savings: {quantifiable_cost_reductions} Soft benefits: {efficiency_gains_or_time_saved} Revenue impact: {new_revenue_or_growth_attributed} Avoided costs: {problems_or_risks_prevented} Total quantified value: {dollar_amount_of_all_benefits}
Write a 350-400 word ROI analysis that builds a conservative business case. Structure as Investment-Returns-Methodology-Confidence. Show math clearly but don’t over-engineer the calculation. Include both quantified and strategic value. End with ROI multiple and payback period.
When to use it: During budget planning season or when renewal decision makers need financial justification.
Pro tip: Include “avoided cost” scenarios like prevented downtime or compliance risks—they’re often larger than direct savings.
Stakeholder Communication
You are drafting a QBR follow-up email to an executive sponsor who missed the meeting.
Executive: {executive_name_and_title} Relationship: {how_long_they_ve_been_sponsor} Meeting attendees: {who_represented_their_company} Key outcome: {most_important_decision_or_result} Action items: {specific_next_steps_agreed} Executive decision needed: {what_requires_their_input} Timeline: {when_decision_or_action_is_needed} Attachment: {qbr_deck_or_summary_document}
Write a 200-250 word executive follow-up email that gets to the point immediately. Lead with the business outcome, summarize key decisions, and include one clear ask. Use confident, peer-level language. Close with specific next contact timeline.
When to use it: When your main sponsor couldn’t attend but needs to stay informed and potentially approve next steps.
Pro tip: Put the specific ask in bold or a separate line—executives scan emails quickly and need clear action items.
You are sending a pre-QBR preparation email to ensure productive discussion.
Meeting date: {qbr_scheduled_date_and_time} Attendees: {confirmed_participant_names_and_roles} Agenda focus: {primary_topics_to_cover} Data needed: {information_you_need_them_to_bring} Questions to consider: {strategic_topics_for_discussion} Success metrics: {what_good_outcomes_look_like} Time allocation: {how_meeting_time_will_be_spent} Preparation time: {how_long_their_prep_should_take}
Write a 300-350 word pre-meeting email that sets expectations and ensures preparation. Frame as partnership in making the meeting valuable. Include specific prep requests with rationale. Close with enthusiasm about the strategic discussion ahead.
When to use it: One week before your QBR when you need stakeholders to come prepared for strategic conversation, not just a presentation.
Pro tip: Send this on Tuesday for the following week’s meeting—gives them time to prepare without it getting buried in their inbox.
You are writing to a new stakeholder joining their first QBR with your team.
New attendee: {name_and_role_of_new_person} Their background: {how_they_relate_to_your_solution} Meeting context: {why_they_ve_been_included_now} Relationship history: {brief_partnership_overview} Current status: {where_things_stand_today} Their interest area: {what_they_likely_care_about_most} Meeting format: {how_qbr_typically_runs} Preparation needed: {what_they_should_review_beforehand}
Write a 250-300 word welcome email that brings them up to speed efficiently. Explain the QBR value and format. Highlight aspects most relevant to their role. Include brief relationship context. Close with offer to discuss their specific interests before the meeting.
When to use it: When a new decision maker, department head, or team member joins an established QBR rhythm.
Pro tip: Ask your main contact what this person’s hot buttons are—budget concerns, competitive threats, growth priorities—and reference them.
You are following up on action items committed during the QBR discussion.
Meeting date: {when_qbr_took_place} Attendees: {who_participated} Your commitments: {specific_things_you_promised_to_deliver} Their commitments: {actions_they_agreed_to_take} Shared commitments: {joint_initiatives_or_projects} Timeline: {when_each_item_is_due} Next check-in: {when_you_ll_follow_up_on_progress} Escalation path: {who_to_contact_if_issues_arise}
Write a 280-320 word action item follow-up email using clear accountability structure. Organize by owner and due date. Include context for why each item matters. Frame as shared commitment to success. Close with proactive check-in schedule.
When to use it: Within 24 hours of your QBR when you need to cement commitments and maintain momentum.
Pro tip: Include one “quick win” action item you can complete within days to demonstrate immediate follow-through.
You are requesting additional stakeholders for the next quarterly review cycle.
Current stakeholders: {who_currently_attends_qbrs} Missing perspective: {department_or_role_not_represented} Business case: {why_their_input_would_be_valuable} Specific value: {decisions_they_could_help_make} Meeting impact: {how_agenda_would_improve} Time commitment: {what_you_re_asking_of_new_person} Alternative options: {other_ways_to_get_their_input} Next QBR date: {when_you_d_like_them_to_join}
Write a 250-300 word stakeholder expansion request that makes the business case