EBR Kit
Prism Customer Success Handbook — Section 4.3
Enterprise quarterly · Mid-Market twice yearly (EBR-lite) · SMB not applicable (2.2 Meeting Standards & Working Norms)
What an EBR is for
Solving the invisible-value problem. The person who renews is frequently the person with the least direct exposure to the product — the practice lead signed the contract, the account managers use it daily, and value accrues where the buyer never sees it. By renewal, nobody has been counting for eleven months (1.5 Customer Journey Map, stage 5).
An EBR is the scheduled mechanism that puts outcomes in front of the buyer while there's still time for that to matter.
Two hard rules:
- The economic buyer attends, or it's rescheduled. An EBR without them doesn't do the job it exists for. Holding it anyway produces a pleasant meeting with the wrong people and a false sense that the renewal is covered.
- It is not a product demo. An EBR that walks through features has failed. It reviews outcomes against the objectives the customer stated, in their language.
The spine is the success plan (4.2 Success Plan Template). An EBR is a live review of it — what was agreed, what landed, what changed, what's next. If the success plan is current, most of the EBR is already written.
Agenda
60 minutes for Enterprise, 30–40 for Mid-Market EBR-lite.
| Time | Section | Purpose |
|---|---|---|
| 5 min | Their update first | What's changed on their side — clients, team, priorities. Ask before presenting. |
| 15 min | Outcomes against objectives | Each success plan objective: what was agreed, where it stands, evidence |
| 10 min | What's working, what isn't | Honest both ways. Includes what we got wrong. |
| 10 min | Feedback loop | What they asked for, what happened to it (2.8 Voice of Customer & Product Feedback) |
| 15 min | Next period objectives | Agree what we're aiming at, with owners and dates |
| 5 min | Logistics | Renewal timing if relevant, actions, next EBR date |
Their update goes first, deliberately. Presenting before asking means building a value story on assumptions that may be months out of date. A client they lost, a reorg, a new priority — all change what "value" means to them, and all are cheap to discover in the first five minutes and expensive to discover in the last five.
Deck outline
Six slides. More than that and it becomes a presentation rather than a conversation.
| # | Slide | Contents |
|---|---|---|
| 1 | Where we started | The objectives they stated, in their words. Sets the frame: this is about their goals, not our product. |
| 2 | What's been delivered | Concrete: clients live on the portal, reports delivered, milestones reached, time saved where quantified. Numbers, not adjectives. |
| 3 | Objective by objective | Each one: agreed / status / evidence. Includes the ones that slipped. |
| 4 | What didn't go well | Escalations, misses, things we said we'd do and didn't. |
| 5 | What you asked for | Feedback routed to Product and its disposition — shipped, planned, declined with reasoning (2.8 Voice of Customer & Product Feedback). |
| 6 | Next period | Proposed objectives, framed as a starting point for discussion rather than a plan to approve. |
Slide 4 is not optional
Naming what went wrong before the customer does is the highest-trust move available in an EBR. It costs a slide and buys credibility for everything on the other five — a review that presents only wins reads as marketing, and the customer discounts the whole thing accordingly.
If genuinely nothing went wrong, say that in one line. Don't manufacture a miss.
Slide 5 is the most under-used
"You asked for X in February; here's what happened to it" — including declined, and here's why — demonstrates that feedback goes somewhere. Customers accept no far better than they accept silence (2.8 Voice of Customer & Product Feedback), and this is the moment they find out which one they got.
Prep checklist
Start two weeks out for Enterprise. An EBR assembled the night before is a status update with slides.
- Buyer's attendance confirmed — if not, reschedule now rather than proceed
- Success plan reviewed and current (4.2 Success Plan Template) — objectives, statuses, blockers
- Value record assembled — what's been delivered since last EBR, in their metrics
- Health and Risk Level reviewed — know what the data says before they tell you
- Support history checked — escalations, patterns, anything unresolved (2.5 Cross-Functional Interfaces)
- Feedback dispositions collected from Product (2.8 Voice of Customer & Product Feedback)
- Misses identified honestly — what we said we'd do and didn't
- Next-period objectives drafted as a proposal, not a decision
- Renewal timing checked — if inside the window, the value conversation from 3.7 Renewal Motion happens here
- Stakeholder map current — who's new, who's gone, who's gone quiet
Running it
Ask before presenting. Their update first, and adjust what you emphasise based on what they say.
Use their numbers, not ours. "Reports delivered: 340" is our metric. "Your team stopped building decks for 14 clients, which was about 30 hours a month" is theirs. Both may be true; only one lands with a buyer.
Let silence happen after the misses slide. The temptation is to fill it with reassurance. What's usually more valuable is what they say next.
Don't close on renewal. If the renewal is in the window, the EBR is where the value conversation happens — but pivoting from outcomes to a contract ask in the last five minutes reframes the whole meeting retroactively as a sales call. Raise timing as logistics; have the commercial conversation separately (3.7 Renewal Motion).
Output
An EBR that produces nothing was a status update. Required outputs:
- Updated success plan with agreed next-period objectives, owners, and dates (4.2 Success Plan Template)
- Anything the buyer committed to — a decision, an introduction, a budget conversation — logged (2.2 Meeting Standards & Working Norms)
- Forecast category reviewed with a stated reason if it moved (2.6 Renewal Forecasting)
- Next EBR scheduled before the meeting ends. Rescheduling from scratch each quarter is how EBR cadence quietly lapses.
Mid-Market EBR-lite
Same spine, compressed:
- 30–40 minutes, twice yearly
- Slides 1–3 and 6 only; misses and feedback covered verbally
- Practice lead rather than a separate economic buyer, usually the same person
- Often folded into a scheduled cadence call rather than booked separately
What doesn't compress: the buyer attending, honesty about misses, and an updated success plan at the end.
Related pages
- 1.5 Customer Journey Map — the invisible-value problem
- 2.2 Meeting Standards & Working Norms — EBR standard, attendance requirement
- 2.3 Operating Rhythm — quarterly scheduling
- 2.8 Voice of Customer & Product Feedback — dispositions for slide 5
- 2.10 Advocacy Program — EBR wins as advocacy moments
- 3.7 Renewal Motion — where the EBR sits in the renewal timeline
- 4.1 Email Template Library — EBR invitation and follow-up
- 4.2 Success Plan Template — the spine of the meeting