The SE is the only person in a QBR with the credibility and the context to make it genuinely valuable for the customer. The SEs who understand this show up to these meetings differently.
Most companies call them QBRs. Some call them EBRs. The distinction, Quarterly Business Review vs. Executive Business Review, technically matters: a QBR is meant to be operational, a check-in on usage and adoption. An EBR is strategic, a conversation between senior stakeholders about the direction of the partnership. In practice, most teams use the terms interchangeably for the same meeting.
Here's the part that doesn't get talked about enough. The AE owns the business relationship and the commercial conversation. The CSM owns adoption data and renewal health. The executive sponsor manages the room. But the SE is the one who knows what the customer actually built, how well it's working, where the gaps are, and what they should do next. That combination of technical intimacy and business fluency doesn't exist anywhere else on the account team.
What executives are actually trying to figure out
When a CTO or VP of Engineering sits in a business review, they're not there to hear a product update. They attend for one of three reasons: they have a concern they want surfaced, they want to validate that a decision they made is still the right one, or they're being asked by their board or peers to demonstrate that a vendor relationship is generating value.
Every one of those is an SE question.
A concern about technical debt, integration fragility, or organizational capability is something the AE can't answer credibly. Validating the decision means connecting technical outcomes to business results, the kind of translation that requires someone who knows both sides of that equation. And building the case for value to a board means turning what was deployed into what changed, which requires the SE's visibility into how the product is actually being used.
The SEs who walk into these meetings prepared for that conversation have a different experience than the ones who prepared for a product recap.
Outcomes first, always
At Datadog, we call these QBRs. In most of the ones I've been part of over the years, the SE section tends to follow a familiar pattern: here's what we deployed, here's the technical architecture, here's the adoption by team.
Executives don't attend these meetings to hear deployment status. They care about what changed as a result.
"We have 87% agent coverage across your production environment" means nothing to a VP. "Mean time to resolution on your P1 incidents dropped 64% since we completed the Payments team integration" changes the conversation. Those two sentences describe the same reality. The best SE communicators lead with the second one and let the first one live in the appendix.
Every technical fact in a QBR earns its place in the room by having a business outcome attached to it.
Naming a risk is a credibility move
The SEs who stand out in business reviews are the ones who bring a risk to the table proactively. Not as a problem dump, but as evidence that they're paying close enough attention to see what's coming.
The instinct to protect the positive narrative is understandable. QBRs are relationship moments and introducing friction feels counterproductive. But executives have been in enough of these meetings to know that anyone who claims everything is perfect is either not paying close attention or managing perception rather than the account.
An SE who names a real risk, something that's fragile, underutilized, or heading toward a problem, and comes with a mitigation plan earns something in that room that no highlight reel can replicate: trust as someone who's actually watching the account. That trust is what makes the conversation about what happens next feel like a recommendation rather than a pitch.
The expansion story belongs to the SE
Account executives frame expansion in terms of contract value. It's their job. But the most compelling case for expansion rarely comes from the commercial side of the table.
"You have strong coverage in Payments but essentially no visibility into your Infrastructure layer, and based on what your VP of Platform told us about your Q3 reliability goals, that gap is a real risk to outcomes you've already demonstrated" is something only the SE can say convincingly. It comes from knowing the technical landscape, knowing the customer's stated priorities, and connecting the two in a way that reads as advice rather than upsell.
The SE who brings this framing to a QBR positions the commercial conversation that follows as a natural conclusion. The AE closes it, but the SE set it up.
One ask, specific and named
The most memorable QBRs I've been part of ended with a clear next step that came out of the SE's section.
Not "let's stay in touch on how this evolves." A 45-minute technical roadmap session with the infrastructure lead before the end of the quarter. A guided upgrade session for the Security team before their compliance window opens. Something specific enough that the person who needs to schedule it knows exactly what they're agreeing to.
That ask lands differently coming from the SE than from the AE. By the time it's made, the SE has spent 20 minutes demonstrating genuine insight into the account. The ask is a natural conclusion, not a close.
What the preparation actually looks like
None of this happens in the meeting if it doesn't happen beforehand.
The SE who shows up with a shared story, built with the AE well in advance, has a different meeting than the one who sends a slide deck the night before for review. Not because the content is necessarily different, but because the AE has had time to connect it to the commercial narrative and the SE has had time to adjust based on what the AE has heard from the executive sponsor.
When that collaboration happens, the customer doesn't experience the QBR as a vendor visit. They experience it as a conversation with people who know their business.
That's the version of this meeting that renews accounts, expands relationships, and makes SEs genuinely memorable to the executives in the room.
We built an EBR/QBR Builder as part of Field Ready, a free tool that helps SEs structure their business review contributions with opening framing, value wins, risk callouts, expansion narrative, and a specific ask. Try it here.