30 Claude Prompts for QBRs

You are a customer success operations analyst who builds health scores from raw product usage exports. <context> I have raw usage numbers pulled from our product analytics tool and I need them turned into a health score I can present in a QBR without the customer feeling like they are being graded harshly. </context> <inputs> - Account name: [ACCOUNT NAME] - Active users this quarter vs last: [ACTIVE USER NUMBERS] - Feature adoption rates: [LIST OF FEATURES AND ADOPTION PERCENTAGES] - Support ticket volume this quarter: [TICKET COUNT] - NPS or CSAT score if available: [SCORE OR N/A] </inputs> <task> Calculate a simple health score out of 100 using the inputs, showing your weighting logic, then write a one-paragraph plain-language summary of what is driving the score. </task> <constraints> Show the weighting you used for each input category so it can be checked against our internal rubric. Do not present the score as precise to the decimal, round to the nearest 5. Avoid alarmist language even if the score is low. </constraints> <format> Return a table of Metric, Weight, Raw Value, Score Contribution, then the final score, then the summary paragraph below it. </format>

You are a customer success manager writing an internal briefing for your account owner before a QBR. <context> This account's health score dropped from last quarter and I need to explain why in plain terms before the account owner walks into the review, so they are not caught off guard. </context> <inputs> - Account name: [ACCOUNT NAME] - Health score last quarter: [PREVIOUS SCORE] - Health score this quarter: [CURRENT SCORE] - Metrics that moved: [LIST OF METRICS AND THEIR CHANGES] - Any known context, staff changes, budget cuts, etc: [KNOWN CONTEXT] </inputs> <task> Write a short internal briefing that names the specific metrics driving the decline, ranks them by impact, and suggests one talking point for each that the account owner can raise in the QBR. </task> <constraints> Do not use vague phrases like "engagement is down", name the specific metric and number. Limit to the top 3 drivers even if more metrics moved. Keep the whole briefing under 250 words. </constraints> <format> Return a numbered list of the top 3 drivers, each with the metric, the change, and a one-line suggested talking point. </format>

You are a customer success manager preparing a portfolio review before a batch of QBRs this week. <context> I manage a book of accounts and need to see which ones need the most attention in this week's QBRs before I walk into any of them. </context> <inputs> - List of accounts with their health scores and key metrics: [PASTE ACCOUNT LIST WITH SCORES] - Renewal dates for each: [LIST OF RENEWAL DATES] - Total accounts to review: [NUMBER OF ACCOUNTS] </inputs> <task> Rank the accounts by urgency, combining low health score with near-term renewal date, and produce a short prep note for each of the top 5 most urgent accounts. </task> <constraints> An account with a low score but a renewal date over a year away should rank below one with a moderate score and a renewal next month. Keep each prep note to two sentences. Do not rank more than 5 accounts, the rest can wait. </constraints> <format> Return a ranked numbered list of the top 5 accounts, each with account name, score, renewal date, and the two-sentence prep note. </format>

You are a customer success manager wrapping up a QBR by setting measurable targets for next quarter. <context> We just reviewed this account's health metrics and I want to leave the QBR with specific, agreed targets instead of a vague commitment to "keep improving". </context> <inputs> - Account name: [ACCOUNT NAME] - Current metrics: [LIST OF CURRENT METRIC VALUES] - Areas the customer agreed to focus on: [LIST OF FOCUS AREAS] - Our team's capacity to support these areas: [SUPPORT CAPACITY NOTES] </inputs> <task> Propose specific, numeric targets for next quarter for each focus area, along with what our team will do to help hit them. </task> <constraints> Every target must be a number or a clear binary outcome, not a direction like "increase". Do not propose more than 4 targets. Each target needs one supporting action from our side with an owner marked [OWNER NAME]. </constraints> <format> Return a table with columns: Focus Area, Current Value, Target Value, Our Supporting Action, Owner. </format>

You are a customer success manager building the slide narration for the health metrics section of a QBR deck. <context> I have the health metrics chart ready but need the spoken narrative that goes with it so I am not just reading numbers off the slide during the review. </context> <inputs> - Account name: [ACCOUNT NAME] - Metrics shown on the slide: [LIST OF METRICS AND VALUES] - Trend direction for each: [UP DOWN OR FLAT FOR EACH METRIC] - Time available for this slide: [MINUTES FOR THIS SLIDE] </inputs> <task> Write a spoken narrative script for presenting this slide that interprets the trends rather than reading the numbers, and ends with a transition line into the next agenda item. </task> <constraints> Write it as if spoken aloud, short sentences, no bullet fragments. Keep it to roughly 100 words per minute of time available. Do not editorialize on metrics that are flat, just state them and move on. </constraints> <format> Return the script as plain prose paragraphs, no headers, ending with a single transition sentence in italics using asterisks. </format>

You are a customer success manager who translates product changes into customer-facing value statements. <context> Our product team shipped several features this quarter and I need to turn that release list into a value recap the customer will actually care about, not a changelog. </context> <inputs> - Account name: [ACCOUNT NAME] - Features shipped this quarter: [LIST OF FEATURES SHIPPED] - Which of these the customer has used: [LIST OF FEATURES USED BY CUSTOMER] - Customer's stated goals: [LIST OF CUSTOMER GOALS] </inputs> <task> Write a value recap that connects the features actually used by this customer to their stated goals, and separately lists relevant shipped features they have not tried yet. </task> <constraints> Do not describe features in technical terms, describe them in terms of the outcome for the customer. Keep the used-features section to 3 items maximum, even if more were used. Do not mention features irrelevant to their stated goals. </constraints> <format> Return two sections: "What moved the needle for you" as a short list tying feature to goal, and "Worth exploring next" as a short list of unused relevant features. </format>

You are a customer success manager building a return-on-investment narrative for a QBR value recap. <context> I have some hard numbers on time saved or output produced through our product this quarter and I want to turn that into a clear ROI story instead of just listing usage stats. </context> <inputs> - Account name: [ACCOUNT NAME] - Contract value: [ANNUAL CONTRACT VALUE] - Time saved or output metric: [RAW METRIC SUCH AS HOURS SAVED OR TASKS COMPLETED] - Estimated dollar value of that metric if known: [DOLLAR ESTIMATE OR N/A] - Team size using the product: [TEAM SIZE] </inputs> <task> Write a short ROI narrative that connects the usage metric to a business outcome, and if a dollar estimate is available, express it against the contract value as a ratio. </task> <constraints> If no dollar estimate is available, do not invent one, describe the value in operational terms instead. Do not round the ratio in a way that misrepresents it. Keep the narrative to one short paragraph plus one supporting sentence. </constraints> <format> Return the paragraph first, then a single bolded line stating the ratio or operational summary if no dollar figure exists. </format>

You are a customer success manager preparing a milestone recap for the top of a QBR. <context> I want to open the QBR by celebrating what actually went well this quarter before getting into metrics and risks, so the tone starts positive and grounded in specifics. </context> <inputs> - Account name: [ACCOUNT NAME] - Milestones or wins this quarter: [LIST OF WINS SUCH AS LAUNCHES INTEGRATIONS OR GOALS HIT] - Any public recognition or case study potential: [NOTES ON PUBLIC RECOGNITION] - Team members on the customer side who contributed: [LIST OF NAMES] </inputs> <task> Write a short milestone recap that names specific wins and credits the people involved by name where appropriate. </task> <constraints> Do not inflate a minor win into something it is not. Limit to 4 milestones. If case study potential exists, add one sentence at the end suggesting it as a future conversation, not a request in this meeting. </constraints> <format> Return a short list of up to 4 milestones, each one sentence, followed by an optional closing sentence about case study potential if applicable. </format>

You are a customer success manager preparing for a renewal conversation embedded in a QBR. <context> The customer has questioned pricing before and I want the value recap section of this QBR to make the cost-to-value case clearly, ahead of any renewal pushback. </context> <inputs> - Account name: [ACCOUNT NAME] - Annual contract value: [CONTRACT VALUE] - Key usage stats this quarter: [LIST OF USAGE STATS] - Comparable cost of the alternative, manual process, competitor, or in-house build: [COMPARABLE COST OR N/A] - Prior pricing objections raised: [NOTES ON PRIOR OBJECTIONS] </inputs> <task> Write a value-versus-cost summary that addresses the prior pricing objections directly using this quarter's usage data, without sounding defensive. </task> <constraints> Do not open by mentioning price, lead with usage and outcomes, and only bring in cost comparison after the value is established. If no comparable cost is available, do not invent a competitor price. Keep the whole summary under 200 words. </constraints> <format> Return the summary as two short paragraphs, the first on value delivered, the second on cost context, with no headers. </format>

You are a customer success manager preparing a QBR for an account with disappointing usage this quarter. <context> This account did not use the product much this quarter and I still need to present a value recap section honestly, without either hiding the low usage or sounding like I am making excuses. </context> <inputs> - Account name: [ACCOUNT NAME] - Usage this quarter versus last: [USAGE NUMBERS] - Known reasons for low usage: [KNOWN REASONS SUCH AS STAFF TURNOVER OR COMPETING PRIORITIES] - Any value delivered despite low usage: [ANY VALUE DELIVERED] </inputs> <task> Write a value recap that states the low usage plainly, connects it to the known reasons if any exist, and identifies any real value delivered without overstating it. </task> <constraints> Do not use euphemisms to soften the low usage number, state it directly. Do not blame the customer even if the known reason is on their side, describe it neutrally. If no real value was delivered, say so and pivot straight to a plan rather than manufacturing a win. </constraints> <format> Return one short paragraph stating the usage honestly, followed by one sentence proposing next steps. </format>

You are an account manager looking for genuine expansion signals in usage data before a QBR. <context> I want to identify real expansion opportunities in this account based on how they are actually using the product, not a generic upsell pitch that ignores their behavior. </context> <inputs> - Account name: [ACCOUNT NAME] - Current plan or seats: [CURRENT PLAN OR SEAT COUNT] - Usage patterns that suggest growth, hitting limits, new teams using it, etc: [USAGE PATTERNS] - Available upgrade paths: [LIST OF UPGRADE OPTIONS] </inputs> <task> Identify which upgrade paths are actually supported by the usage patterns described, and reject any upgrade path that has no supporting evidence in the data. </task> <constraints> Do not recommend an upgrade just because it exists, only recommend ones with a clear signal in the usage patterns. If no upgrade path is supported by the data, say so directly instead of forcing one. Limit to 2 recommendations maximum. </constraints> <format> Return a short list of up to 2 recommended upgrade paths, each with the specific usage signal that supports it, or a single sentence stating no expansion is currently supported by the data. </format>

You are an account executive preparing to pitch expanding a product into a new department at an existing customer. <context> This account has had success with our product in one department and I want to pitch expanding to a second department during the QBR, based on the first department's results. </context> <inputs> - Account name: [ACCOUNT NAME] - Department already using the product: [CURRENT DEPARTMENT] - Results achieved there: [RESULTS OR METRICS] - Target department for expansion: [TARGET DEPARTMENT] - Known pain points in the target department: [KNOWN PAIN POINTS] </inputs> <task> Write a short pitch that uses the current department's results as proof and connects them directly to the target department's known pain points. </task> <constraints> Do not assume the target department has identical needs to the current one, adjust the framing to their specific pain points. Keep the pitch to 3 sentences. End with a low-commitment next step, like a short pilot, not a full contract ask. </constraints> <format> Return the pitch as 3 sentences of plain prose, followed by one bolded line naming the suggested next step. </format>

You are a customer success manager preparing a seat expansion recommendation for a QBR. <context> I have adoption data suggesting the current seat count is limiting this team and I want to build a clear business case for adding seats rather than just asking for more. </context> <inputs> - Account name: [ACCOUNT NAME] - Current seats and utilization: [CURRENT SEAT COUNT AND UTILIZATION PERCENT] - Evidence of demand beyond current seats, waitlist, shared logins, requests: [EVIDENCE OF DEMAND] - Cost per additional seat: [COST PER SEAT] </inputs> <task> Build a short business case for adding a specific number of seats, using the utilization and demand evidence to justify the number, and note the added cost plainly. </task> <constraints> Recommend a specific number of seats, not a vague "more seats". Do not recommend more seats than the demand evidence supports. State the added cost in the same sentence as the recommendation, do not bury it. </constraints> <format> Return one paragraph containing the recommended seat count, the supporting evidence, and the added cost, followed by a single closing sentence suggesting how to trial the increase if relevant. </format>

You are an account executive considering whether to propose a multi-year deal during a QBR renewal discussion. <context> This account has a strong growth trajectory and I want to evaluate whether proposing a multi-year deal makes sense, and if so, draft the framing for the QBR conversation. </context> <inputs> - Account name: [ACCOUNT NAME] - Growth trajectory over past renewals: [GROWTH HISTORY SUCH AS SEAT OR SPEND CHANGES] - Current contract length and renewal date: [CONTRACT LENGTH AND RENEWAL DATE] - Known budget cycle or procurement constraints: [BUDGET CONSTRAINTS] - Discount typically offered for multi-year: [DISCOUNT PERCENT OR POLICY] </inputs> <task> Evaluate whether the growth trajectory supports a multi-year proposal, and if it does, draft the framing to raise it in the QBR, including how to present the discount. </task> <constraints> If the trajectory is flat or declining, recommend against proposing multi-year and say why. Do not lead with the discount, lead with the stability and roadmap commitment a multi-year deal buys the customer. Keep the framing to 4 sentences. </constraints> <format> Return a one-line recommendation of yes or no, followed by the 4-sentence framing if yes, or a one-sentence alternative suggestion if no. </format>

You are an account manager sending a follow-up email after a QBR where an expansion opportunity was discussed but not closed. <context> We raised an expansion idea in the QBR, the customer seemed interested but did not commit, and I need a follow-up email that keeps the conversation moving without being pushy. </context> <inputs> - Contact name: [CONTACT NAME] - Expansion idea discussed: [EXPANSION IDEA] - Their stated hesitation or open question: [HESITATION OR OPEN QUESTION] - Proposed next step: [PROPOSED NEXT STEP] - Timeline sensitivity if any: [TIMELINE OR NONE] </inputs> <task> Write a follow-up email that references the specific conversation, directly addresses their stated hesitation, and proposes the next step with a clear but soft deadline if timeline sensitivity exists. </task> <constraints> Do not repeat the full pitch from the QBR, assume they remember it. Address the hesitation head on rather than ignoring it. Keep the email under 120 words. No exclamation points. </constraints> <format> Return a plain email with a subject line, a greeting using [CONTACT NAME], the body, and a sign-off placeholder [YOUR NAME]. </format>

You are a customer success manager doing a risk assessment before a QBR to avoid being blindsided. <context> I want to go into this QBR knowing exactly what churn risk signals exist for this account so I can address them proactively instead of reacting if the customer brings them up. </context> <inputs> - Account name: [ACCOUNT NAME] - Usage trend over the past two quarters: [USAGE TREND] - Support ticket sentiment or escalations: [TICKET NOTES] - Champion status, still employed, engaged, gone quiet: [CHAMPION STATUS] - Contract renewal date: [RENEWAL DATE] </inputs> <task> List the specific churn risk signals present in this data, rank them by severity, and suggest one proactive talking point for the QBR to address the top signal. </task> <constraints> Only list signals actually supported by the inputs, do not invent generic risks like "market conditions" with no basis. Rank strictly by severity, champion loss should outrank a minor usage dip. Limit to 3 signals. </constraints> <format> Return a numbered list of up to 3 signals ranked by severity, each with the signal, why it matters, and the suggested talking point for the top one only. </format>

You are a customer success manager who needs to escalate an at-risk account internally before the QBR, so leadership is not surprised. <context> This account is showing serious risk signals and I need to write an internal escalation note to my manager and the account executive before the QBR happens, not after. </context> <inputs> - Account name: [ACCOUNT NAME] - Annual contract value: [CONTRACT VALUE] - Risk signals identified: [LIST OF RISK SIGNALS] - Actions already taken: [ACTIONS ALREADY TAKEN] - What you need from leadership: [WHAT YOU NEED SUCH AS APPROVAL FOR A CONCESSION OR EXECUTIVE SPONSOR CALL] </inputs> <task> Write a concise internal escalation note that states the risk level plainly, summarizes the signals, lists what has already been tried, and makes a specific ask of leadership. </task> <constraints> Open with the bottom line, do not bury the risk level in a long narrative first. State the ask as a specific action, not "let me know your thoughts". Keep the whole note under 180 words. </constraints> <format> Return the note in four short sections with bold labels: Bottom Line, Signals, Actions Taken, Ask. </format>

You are a customer success manager who needs to raise a difficult risk topic directly with the customer during the QBR. <context> There is a risk signal I need to raise directly with the customer in the QBR itself, and I want to frame it constructively instead of avoiding it or sounding accusatory. </context> <inputs> - Account name: [ACCOUNT NAME] - Risk to raise: [SPECIFIC RISK SUCH AS DECLINING USAGE OR MISSED GOALS] - Relationship context: [RELATIONSHIP CONTEXT SUCH AS LONG STANDING OR NEW CONTACT] - Desired outcome from raising it: [DESIRED OUTCOME] </inputs> <task> Write talking points for raising this risk directly with the customer in a way that opens a real conversation rather than putting them on the defensive. </task> <constraints> Open with a question, not an accusation. Do not soften the risk to the point it is unclear what the actual concern is. Keep it to 3 talking points that build toward the desired outcome. </constraints> <format> Return 3 talking points as short numbered prompts to say aloud, each one or two sentences. </format>

You are a customer success manager building a formal save plan for an account flagged as at risk of not renewing. <context> This account is at real risk of churning and I need a concrete save plan with specific actions and dates, not a vague intention to "improve the relationship". </context> <inputs> - Account name: [ACCOUNT NAME] - Root cause of the risk: [ROOT CAUSE] - Renewal date: [RENEWAL DATE] - Internal resources available, executive sponsor, technical account manager, discount authority: [AVAILABLE RESOURCES] - Customer's stated conditions for staying, if known: [CUSTOMER CONDITIONS OR UNKNOWN] </inputs> <task> Build a save plan with specific actions, owners, and dates that directly addresses the root cause, using the available internal resources. </task> <constraints> Every action must address the stated root cause, do not include generic relationship-building actions unrelated to it. Each action needs a date before the renewal date. Limit to 4 actions. If the root cause cannot realistically be fixed before renewal, say so plainly instead of forcing a plan. </constraints> <format> Return a table with columns: Action, Owner, Date, How it addresses the root cause. If the risk cannot be fixed in time, replace the table with one direct sentence saying so. </format>

You are a customer success manager rolling up risk status across your accounts for a leadership pipeline review ahead of QBR season. <context> Leadership wants a rolled-up view of renewal risk across my accounts before this QBR cycle starts, and I need to summarize it clearly without a long account-by-account narrative. </context> <inputs> - List of accounts with renewal date, contract value, and risk level: [PASTE ACCOUNT LIST] - Total book of business value: [TOTAL BOOK VALUE] - Time period this review covers: [TIME PERIOD] </inputs> <task> Summarize the total renewal value at risk this period, broken down by risk level, and name the specific accounts in the highest risk tier. </task> <constraints> Calculate the dollar value at risk per tier, not just account counts. Name every account in the highest risk tier individually, do not group them as "several accounts". Keep the summary to one screen, no long narrative. </constraints> <format> Return a short summary line with total value at risk, then a table with columns Risk Tier, Number of Accounts, Dollar Value, Account Names (highest tier only listed by name). </format>

You are a customer success manager sending the official recap email after a QBR concludes. <context> The QBR just wrapped and I need to send a recap email to all attendees within a day, summarizing what was covered and what was agreed, before details fade. </context> <inputs> - Account name: [ACCOUNT NAME] - Attendees to include: [LIST OF ATTENDEE NAMES] - Topics covered: [LIST OF TOPICS COVERED] - Decisions or agreements made: [LIST OF DECISIONS] - Action items with owners and dates: [LIST OF ACTION ITEMS WITH OWNERS AND DATES] </inputs> <task> Write a recap email that summarizes the meeting briefly, lists the decisions made, and lists the action items clearly with owners and dates. </task> <constraints> Keep the meeting summary to 3 sentences maximum, the action items are the important part, not the narrative. Every action item must show an owner and a date, if either is missing say [DATE TBD] or [OWNER TBD] rather than omitting it. Do not add new commitments that were not actually discussed. </constraints> <format> Return a plain email with subject line, greeting, a short summary paragraph, then a table of action items with columns Action, Owner, Date. </format>

You are a customer success manager converting QBR notes into a structured CRM update. <context> I took messy notes during the QBR and need them turned into a clean, structured entry for our CRM so the next person who opens this account record understands what happened without reading a wall of text. </context> <inputs> - Account name: [ACCOUNT NAME] - Raw meeting notes: [PASTE RAW NOTES] - Health status discussed: [HEALTH STATUS SUMMARY] - Risk level assigned: [RISK LEVEL] - Next QBR date: [NEXT QBR DATE] </inputs> <task> Convert the raw notes into a structured CRM entry with clearly labeled fields that a colleague could scan in under a minute. </task> <constraints> Use short labeled fields, not paragraphs. Do not editorialize, stick to what was actually discussed or decided. If the raw notes are ambiguous about something, mark it as [NEEDS CLARIFICATION] rather than guessing. </constraints> <format> Return a structured entry with the fields: Summary, Health Status, Risk Level, Key Decisions, Open Items, Next QBR Date, each on its own line with a bold label. </format>

You are a customer success manager turning a list of loosely worded QBR commitments into clear, assignable action items. <context> The QBR produced a list of things people said they would do, but they are worded loosely and I need to turn them into clear action items before I lose track of who owns what. </context> <inputs> - Account name: [ACCOUNT NAME] - Loosely worded commitments from the meeting: [PASTE LOOSE COMMITMENTS] - Internal team members who could own each: [LIST OF INTERNAL TEAM MEMBERS] - Meeting date: [MEETING DATE] </inputs> <task> Rewrite each loose commitment as a specific action item with a clear owner and a suggested due date relative to the meeting date. </task> <constraints> Each action item must start with a verb and describe a single concrete deliverable, not a vague direction. If it is unclear who should own an item from the inputs given, mark it as [OWNER TBD] rather than assigning it arbitrarily. Do not merge two separate commitments into one item. </constraints> <format> Return a numbered list of action items, each showing the rewritten item, the owner, and the suggested due date. </format>

You are a customer success manager who cannot personally attend an upcoming QBR and needs to brief a colleague who will run it instead. <context> I am out for an upcoming QBR and a colleague is covering it for me, so I need to hand off everything they need to run the meeting well without me in the room. </context> <inputs> - Account name: [ACCOUNT NAME] - Colleague covering the meeting: [COLLEAGUE NAME] - Account background they should know: [ACCOUNT BACKGROUND] - Sensitive topics to handle carefully: [SENSITIVE TOPICS] - Planned agenda: [PLANNED AGENDA] </inputs> <task> Write a handoff brief that gives the colleague enough context to run the meeting confidently, with special attention to the sensitive topics. </task> <constraints> Put the sensitive topics section near the top, not buried at the end. Do not assume the colleague knows anything about this account beyond what is given. Keep the whole brief to one page, use headers to make it scannable in under 5 minutes. </constraints> <format> Return the brief with these headers in order: Quick Context, Handle With Care, Agenda, Who's Who. </format>

You are a strategic account manager updating the formal account plan document after a QBR concludes. <context> Our account plan document needs updating after every QBR and I want to fold in what was learned this quarter without rewriting the whole document from scratch. </context> <inputs> - Account name: [ACCOUNT NAME] - Current account plan summary: [PASTE CURRENT PLAN SUMMARY] - New information learned this QBR: [LIST OF NEW INFORMATION] - Updated risk or expansion status: [UPDATED STATUS] </inputs> <task> Update the account plan summary to incorporate the new information, clearly marking what changed from the prior version. </task> <constraints> Do not rewrite sections that have not changed, only touch what the new information affects. Mark every change with [UPDATED] next to it so reviewers can see what moved. Keep the updated summary roughly the same length as the original. </constraints> <format> Return the updated account plan summary as prose with [UPDATED] tags inline next to changed sentences. </format>