본문으로 건너뛰기
cccskills
무료GitHub에 공개

qbr-deck

Build a structured Quarterly Business Review deck for a customer account. Use when user says "QBR", "quarterly business review", "prep my QBR", "build the deck", "renewal prep", "executive check-in", "90-day review", or "customer business review" - even if they don't use the acronym. Applies to CSMs preparing for executive-level customer meetings focused on value delivered, health, and next quarter alignment.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

설치 방법 보기

포함된 파일(1)

  • SKILL.md5.9 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Overview

A QBR is a structured executive conversation, not a product demo or status update. Based on "Customer Success" by Mehta, Steinman & Murphy, the QBR's purpose is to demonstrate realized value, align on goals, and earn continued investment. The meeting fails when it looks backward without a forward commitment.

The core insight: every slide must answer "so what?" from the customer's perspective. Data without context is noise. Health scores without recommended actions are incomplete.

Workflow

Step 1: Gather inputs before building anything

Collect the following before touching the deck:

  • Goals from last QBR: What did [customer name] say they wanted to achieve this quarter?
  • Usage data: Logins, feature adoption rate, active users vs. licensed seats
  • Health score: Current score and 90-day trend (improving, stable, declining)
  • Support tickets: Volume, average resolution time, any unresolved critical issues
  • Outcomes achieved: Measurable business results tied to your product
  • Renewal timeline: Months until renewal, ARR at stake
  • Expansion signals: New use cases, headcount growth, adjacent teams not yet using product

If you don't have all inputs, note explicitly what is estimated vs. confirmed.

Step 2: Structure the deck in this sequence

Slide 1 - Partnership Summary One-line: "[Your company] x [Customer name] - Q[X] [Year] Review" Include: CSM name, executive sponsor (customer side), renewal date, ARR.

Slide 2 - Goals We Agreed On Last Quarter List 2-4 goals verbatim from prior QBR or success plan. Use the customer's language, not yours. Mark each: Achieved / Partially Achieved / Missed.

Slide 3 - Value Delivered Lead with business outcomes, not product features.

OutcomeMetricLast QuarterThis QuarterChange
[business result][measure][value][value][delta]

Example row: "Reduced onboarding time | Hours per new hire | 8h | 3h | -63%"

Slide 4 - Usage and Adoption Health

MetricTargetActualStatus
MAU / licensed seats>80%[X]%Green/Yellow/Red
Feature adoption (core)>70%[X]%
Support ticket volume<[N]/mo[X]

Include a 90-day trend if available.

Slide 5 - Health Score Summary Show composite health score and breakdown by dimension (usage, engagement, NPS, support, financial). Flag any dimension scoring Yellow or Red with the specific risk named.

Do not hide Red scores. Customers respect transparency. Hiding problems erodes trust before renewal.

Slide 6 - Goals for Next 90 Days List 2-4 specific, measurable goals for next quarter:

  • Goal: [specific outcome]
  • Owner: [customer name / your CSM team]
  • Measure: [how you will know it is done]
  • Target date: [month]

Slide 7 - Open Items and Asks Outstanding product requests, blockers, and anything you need from the customer. Name owner and due date for each item.

Slide 8 - Roadmap Preview (optional, only if directly tied to customer goals) Show 1-2 upcoming features that address goals the customer stated in their own words. Padding with irrelevant features weakens credibility.

Step 3: Apply the "so what?" test to every slide

After drafting, ask for each slide: "Why does this matter to [customer name]'s business?" If you cannot answer in one sentence, rewrite or cut the slide.

Step 4: Prepare for likely objections

Anticipate the three most common concerns before the meeting:

  1. "We're not seeing the ROI we expected" - have outcome data and a remediation plan ready
  2. "Adoption is lower than we'd like" - have a specific activation plan, not just acknowledgment
  3. "We're evaluating alternatives at renewal" - have a retention offer or executive escalation path

Anti-Patterns

1. Activity report masquerading as a QBR Bad: "This quarter we ran 4 training sessions, resolved 12 tickets, and shipped 3 updates." Good: "Onboarding time dropped 60% this quarter. Here's what drove it and what we're targeting next."

2. Hiding health problems Bad: Only showing green metrics. Glossing over low adoption. Good: "Active users are at 52% of licenses - below our 80% target. Here's the remediation plan."

3. No forward commitment Bad: Deck ends at "here's what happened." No goals, no owners, no dates. Good: Every QBR closes with 2-4 signed-off goals for next quarter with named owners.

4. Generic roadmap slides Bad: Showing the full product roadmap as a feature list. Good: Selecting 1-2 items that directly address goals the customer stated in their own words.

5. Vendor language instead of customer language Bad: "We improved platform engagement scores by 14 points." Good: "Your goal was to reduce rep ramp time. We cut it from 8 weeks to 5."

Quality Checklist

  • Every metric is tied to a goal stated in a prior QBR or success plan
  • No metric appears without context (target, trend, or "so what")
  • Health score shows dimension breakdown - no composite-only slides
  • Red and Yellow items named explicitly with a remediation plan
  • Next 90-day goals are specific, measurable, and have named owners
  • Customer's own language used for goals and outcomes
  • Deck is 8 slides or fewer - no padding
  • Renewal date and ARR visible on slide 1
  • Open items have owners and due dates
  • No personal names, internal tool names, or company-specific references in template

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Rate any product, feature, or experience on the 11-star scale (Brian Chesky's Airbnb thought experiment). Use when user says "rate this experience", "11-star", "star rating", "experience audit", "how good is this", "experience rating", "product audit", "quality assessment", or wants to evaluate product quality and identify improvement paths. Also trigger when user wants to benchmark a feature, assess where a product stands, or map out what "great" looks like - even if they don't explicitly say "11-star".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

qa-aman/claude-skills212026년 10월 19일 업데이트

Generate A/B copy variants grounded in Eugene Schwartz's awareness and market-sophistication stages and John Caples' tested-headline discipline. Every variant declares its angle, the awareness stage it targets, and a falsifiable hypothesis, and the skill recommends which pair to test first and what delta counts as signal. Use when the user says "A/B test this", "write variants", "give me options", "test different angles", "copy variants", "ab copy", "test this headline", "multiple versions", "which version is better", or wants to test copy before publishing. For reviewing copy that already exists, see copy-review. For sample size and stopping rules, see growth-experiment. For diagnosing a page rather than its words, see page-cro. For full paid ad sets by platform, see ad-campaign-writer.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

qa-aman/claude-skills212026년 10월 19일 업데이트

Design statistically rigorous experiments to test data science hypotheses. Use when the user says "design an A/B test", "run an experiment", "test this hypothesis", "is this difference significant", "how many samples do I need", "randomized controlled trial", "causal inference", "uplift test", "holdout group", "significance test", "power calculation", "avoid p-hacking", or needs to determine whether an observed effect is real before making a product or model decision. For lean build-measure-learn product experiments without the statistics, use experiment-design instead.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

qa-aman/claude-skills212026년 10월 19일 업데이트

Write measurable acceptance criteria for requirements or user stories. Use when the user says "write acceptance criteria", "definition of done", "how do we test this", "fit criteria", "given when then", "Gherkin scenarios", "what does done look like", "testable conditions", "how will we know this works" - even if they don't explicitly say "acceptance criteria".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

qa-aman/claude-skills212026년 10월 19일 업데이트

Build a strategic account plan for winning, retaining, or expanding a named account. Use when the user says "build an account plan", "strategic account planning", "how do I grow this account", "account expansion strategy", "whitespace analysis", "QBR prep", "key account review", "map the stakeholders in this account", "land and expand plan", "how do I break into [company]", or wants a structured strategy for a specific account.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

qa-aman/claude-skills212026년 10월 19일 업데이트

Write paid ad copy for LinkedIn, Google, Meta, and YouTube. Produces multiple variants per platform, each targeting a different Eugene Schwartz awareness level and Cialdini persuasion principle. Use when the user asks for ad copy, ad variants, "write LinkedIn ads", Google ads, Meta ads, paid social copy, ad headlines, or wants creative for a paid campaign. Reads brand voice, ICP, and positioning from knowledge/. For organic social posts, see linkedin-post or social-calendar. For the landing page the ad points at, see landing-page-writer. For testing variants, see ab-copy-writer.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

qa-aman/claude-skills212026년 10월 19일 업데이트

qa-aman의 스킬 모두 보기

이 스킬의 문제 신고