How to run a QBR at early stage (and make it worth everyone's time)
Not every customer needs a QBR, how to get them to show up, and keep showing up
Hi friends! This article wraps up our customer success series for now — next month we’re shifting gears into marketing and sales, and there’s a lot of good stuff coming. We’ll circle back to CS later in the year with more frameworks and playbooks, so stay tuned for that.
Before we dive in this week, I want to leave you with a reminder that I think is worth a call out: it’s easy to get caught up chasing new logos. New logos, new leads, new people — it’s exciting, it’s visible, and it tends to be where founders focus most of their energy.
But for many companies, the fastest path to growth isn’t new logo acquisition. It’s retaining and expanding the customers you already have. They already trust you. They’ve already seen value. The cost to grow them is a fraction of what it costs to replace them.
Don’t lose sight of that. And if there’s one practice that anchors a strong retention and expansion motion, particularly with larger more complex or enterprise customers, it’s the QBR — when it’s done right.
Here’s how to do it right.
How to run a QBR at early stage (and make it worth everyone’s time)
The quarterly business review has a reputation problem. Mainly because the ones many of us have experienced were 45-minute slide decks summarizing data we could have read in an email.
However - done right, a QBR is one of the highest-leverage touchpoints in your entire customer journey. It’s where you reinforce value, surface risk before it becomes churn, and open expansion conversations in a way that feels like helping rather than selling. Done wrong, it’s a calendar invite your customer dreads and starts declining.
Here’s how to do it right — including when it actually makes sense to do it at all.
Not every customer needs a QBR
A QBR is a significant investment — in prep time for you, in the customer’s calendar, in the relationship capital required to get senior stakeholders in the room. It only makes sense for the customers where that investment is proportionate to the commercial value or opportunity.
The way to think about this isn’t a hard ACV threshold. It’s your tier one customers — whoever is commercially most important to your business. For most early-stage companies, that’s roughly the top 30% of your customer base by revenue or strategic value. Those are the accounts that warrant a structured quarterly conversation. The rest of your book can be served with lighter-touch check-ins, standard reporting, automated health score monitoring, and reactive support.
If you sell exclusively to enterprise organizations, this calculus changes — nearly every customer is likely tier one, and QBRs should be a standard part of your CS motion for all of them.
But if you have a mixed book spanning SMB through mid-market, be deliberate. Running a formal QBR with a customer on a small contract is usually not the right use of anyone’s time.
A few variables that could pull a customer into QBR territory regardless of ACV: they’re a strong reference or expansion candidate; they’re coming up for renewal and the relationship is frayed; or there’s a risk signal that warrants a more structured conversation.
What a QBR is not
Before getting into the agenda, it’s worth being clear on what you’re not trying to do...
A QBR is not a status update. If the customer wanted a usage report, you could have emailed it.
It’s not a product demo of features they haven’t adopted yet — that feels like a sales call in disguise.
And it’s not a support ticket retrospective, which signals that the relationship is reactive rather than strategic.
The posture you want going in is: we’re here to talk about your business, review whether we’re delivering the value we committed to, and make sure the next quarter sets you up for the outcomes you care about.
That’s a different conversation than “here’s your dashboard from the last 90 days.”
Who should be in the room
On the customer side, you want their day-to-day champion — the person who uses the product and can speak to the operational reality — and ideally their manager or economic buyer.
Also, getting a senior stakeholder back in the conversation at least once a year is one of the most important things CS can do for retention and expansion. They were in the room when the decision was made. They remember what was promised. And they’re the ones who will sign the renewal. Make sure they aren’t completely out of the loop before that renewal hits their inbox.
On your side, the CS lead should typically own the QBR. But if there’s an active expansion opportunity or the renewal is coming up, having an AE or Account Manager join the call is a good move — it signals investment in the account and keeps the commercial relationship warm without making the whole conversation feel like a sales call.
Getting the customer to actually show up
The invite is the first impression of the QBR, and most of them are bad. A calendar hold that says “Q3 Business Review” with no context gives the customer nothing to look forward to and every reason to reschedule when something else comes up.
Getting the right people in the room — especially a senior stakeholder who isn’t part of the day-to-day usage — requires a bit more intentionality than a generic calendar invite.
Consider renaming it. “QBR” is internal language that means nothing to most customers, and for some it carries baggage from bureaucratic enterprise relationships they’ve been through before. “Strategy session,” “quarterly growth review,” or simply “[Your company] + [Their company] — Q3 review” all land warmer and signal that this is a conversation, not a presentation.
Lead the invite with a TLDR of why they should care. Before the customer even decides whether to accept, give them a reason to be excited. A short note alongside the calendar invite that surfaces two or three concrete wins from the quarter — in their language, not yours — immediately reframes the QBR from obligation to opportunity.
Something like: “Your team hit [X milestone] this quarter, and [cost/time savings] are estimated to be [X]. I also want to share a couple of developments on our end that are directly relevant to [their stated goal]. Would appreciate 45 minutes to walk through it together — I’ll send an agenda in advance.”
Specific, forward-looking, and clearly about them. If there’s a meaningful product update that applies to their use case, call it out by name. Customers are much more likely to accept an invite when they feel like there’s something in it for them before they even get on the call.
Send the agenda ahead of time. Following up with a brief agenda a few days or even a week before the call does two things: it helps the customer prepare any context, data, or questions they want to bring, and it removes the anxiety of not knowing what they’re walking into. It also signals that you’ve prepared — which raises their confidence that the time will be well spent. The downloadable agenda template linked at the end of this article is designed to serve this purpose.
Make the ask for the senior stakeholder personal. If you want the economic buyer in the room, don’t leave that to the day-to-day champion to sort out. CS or the AE should reach out directly:
“We’d appreciate the opportunity to reconnect with [exec name] for this one — it’s been a few quarters since we’ve had a chance to connect, and I want to make sure we’re aligned on where things are headed.”
A direct, personal ask is much harder to deflect than a generic calendar invite sent through a gatekeeper.
Get it on the calendar early. Don’t send a QBR invite two weeks out and expect to get a senior stakeholder. Four to six weeks of lead time is reasonable to coordinate across multiple calendars and senior execs — it signals that this is a planned, intentional touchpoint, not a reactive check-in. Build the scheduling trigger into your CS calendar so it’s not something you have to remember.
If a customer consistently declines or reschedules QBRs, that’s a health signal in itself — and worth addressing directly rather than just rescheduling again. Sometimes the right move is a softer conversation first:
“I want to make sure we’re making this time valuable for your team — is there anything we should do differently for this next session?”
The agenda that actually works
A QBR should run 45 to 60 minutes. Any shorter and it’s hard to have a real conversation; any longer and you’re testing their patience. The downloadable agenda template gives you a timed structure you can adapt — here’s the logic behind each section.
Open with their world, not yours. The first five minutes should be a genuine check-in: what’s changed for them since you last spoke? New priorities, leadership changes, upcoming initiatives? This does two things — it shows you’re interested in their business beyond the contract, and it surfaces context that shapes everything else in the call.
Tip: Do your homework to attempt to identify these things before the call, too. If you can locate any of this type of news beforehand, reframe your opener accordingly:
“We saw that you have a new CFO / announced an expansion into EMEA / [insert any other news you found]. We'd love to learn more about that. Any other updates we might not have seen?”
Review progress against their goals. This is the heart of the QBR and the section that requires the most prep. Go back to what was documented at kickoff — or in the sales-to-CS handoff — and hold the conversation against those original commitments. What did they say success looked like in 90 days? In 12 months? What’s been achieved, what’s behind, and why? Use their metrics where possible.
Cover product usage and value delivered. Walk through the numbers, but translate them into business language. “You processed 4,200 events this quarter” means less than “your team is handling roughly 350 more events a month than when you started — here’s what that represents in time saved.” Frame the value in terms that connect to the outcomes they told you they cared about.
Share what’s new or coming on your end. A brief section on relevant product enhancements or roadmap items — emphasis on relevant. Not a full product roadmap dump, but a targeted look at what you’ve delivered or what’s coming that applies to their use case. This is also a good moment to point them to your help library and any new documentation or resources that can support their team.
Have the forward-looking conversation. This is where expansion lives, and the key is that it has to emerge from the goals conversation rather than feeling like a pivot to sales mode. If they said at kickoff that they wanted to expand to three teams and they’re only on one, that’s not a sales conversation — that’s you helping them get the value they told you they wanted. The downloadable template includes specific prompts for common expansion scenarios.
Close with clear actions. Before you leave the call, recap who owns what and by when — on both sides. This is what makes the follow-up email useful rather than performative, and it sets the tone for the next quarter.
The expansion conversation
The biggest mistake CS teams make in QBRs is either skipping the expansion conversation entirely — leaving money on the table — or tacking it on at the end in a way that feels like a gear shift.
The setup is everything. If you’ve spent 40 minutes genuinely reviewing their business, discussing their goals, and demonstrating value in their language, the expansion conversation is a natural extension, not a mood change. “You mentioned wanting to roll this out to your operations team — is that still on the roadmap for you this half?” doesn’t feel like a sales pitch when it’s rooted in something they told you months ago.
The expansion prompts in the agenda template cover the most common scenarios: a goal they set that they haven’t yet achieved, a feature they’re not using that would clearly benefit them, an adjacent team or use case that’s come up in conversation, and the renewal conversation itself.
None of them require hard selling. They require good notes from the kickoff call and the discipline to bring the customer’s own words back into the room.
Preparing without it taking all day
The prep is what separates a QBR that feels sharp from one that feels generic — and it doesn’t have to take hours. If your CRM is well-maintained, you’re using call recording software, and you’re tracking usage data, most of what you need is already somewhere findable.
Pull your usage data and support ticket summary. Review the original goals from the kickoff or last QBR call recording. Check for any open action items from the previous conversation. Note the renewal date and any commercial context worth being aware of. If you’ve collected an NPS score this period, have it ready.
Use AI to help synthesize the narrative. Drop all your files into Claude or ChatGPT and ask it to identify the key themes — what’s going well, what’s at risk, what hasn’t moved. What comes back is a useful first draft of the story you want to tell on the call, which you then refine with your own judgment about the relationship.
After the call
Send a follow-up email within 24 hours summarizing key wins, any outstanding challenges, and all agreed action items with owners and dates. This is not optional — it’s what makes the QBR feel like a professional, structured touchpoint rather than a nice chat.
Update your CRM with notes, any expansion flags, and the current renewal outlook. And set a reminder for the next QBR before you close the record. The cadence compounds: customers who experience a consistent, well-run quarterly conversation are meaningfully less likely to churn than those who only hear from CS when something goes wrong.
👉 Download the QBR agenda template — includes a pre-call prep checklist, timed agenda with facilitator prompts, expansion conversation guide, and post-call follow-up checklist.
With love and gratitude -
If you want to learn more about working with me directly…
For B2B startups I serve as a Fractional GTM executive or advisor. Learn more about-
When you’re ready, let’s connect to discuss your specific growth goals and challenges.
Subscribe for weekly education, ideas, and frameworks
In this newsletter I share the exact tips, playbooks, and GTM multi-vitamins I’ve used to help 30+ B2B startups scale their revenue 150-590% YoY.