CSPulse Business Review
A business review is the one recurring meeting where the people who can end the contract are in the room and have already agreed to hear you justify the spend. That access is scarce, it does not carry over, and it is spent once whether or not you use it. Most reviews spend it on a usage readout. That is why the format has the reputation it has, and it is a reputation suppliers earned rather than one the meeting deserves.
So the bar is not "did we present". It is whether the customer leaves more confident, having made a decision, in a meeting where they spoke more than you did.
The failure this exists to prevent: fifty-five slides of usage data when the customer asked for four charts.
What this needs
Minimum: the account and the date. It will build the structure, the questions and the ask from what you know, and mark what it could not verify.
Better with the customer's stated goals from the last review or the original business case, usage and outcome data, the history since the last meeting, and the attendee list.
Best with a documented success measure agreed earlier, because that is the difference between confirming value and arguing for it.
Step 0: Decide whether to run one at all
Run this check before building anything. A business review held to satisfy a cadence, in the wrong conditions, burns the format's credibility for later.
Do not run a business review when:
- There is no value story yet and no baseline to measure against. Run a success-planning session instead
- There is a live unresolved escalation. Run the remediation call. A value review while the customer is angry reads as tone-deaf
- The decision-maker will not be in the room and the purpose was to reach them. Reschedule or change the purpose
- Nothing has changed since the last one. Send a written update
Cadence is not automatically quarterly. Match it to contract value, the customer's decision cycle, and how fast their own metrics move. Slow-moving operational deployments may warrant two a year; a high-risk or fast-changing one may need monthly. The simplest correction is the one most suppliers skip: ask the customer what cadence they want.
Step 1: Answer the one question that sets the whole meeting
What does this customer need to walk away believing?
Write it in one sentence before you gather a single data point. Everything that does not serve that sentence is a candidate for the appendix. If you cannot write it, you are not ready to prepare, and the meeting probably should not happen yet.
Step 2: Reconstruct their world, not your account record
Gather before you build, three to four weeks out for a significant review:
- The goals they stated at purchase or at the last review, and whether those goals have since changed. Ask - do not assume they are stable
- Their own public signals - results announcements, strategic initiatives, leadership changes, reorganisations. An executive notices when you have read them
- Everything they raised since the last review, with current status. The review opens by closing those loops
- Your outcome data, and deliberately more of it than you will present, so you can answer questions the deck does not carry
- Who is attending and why, including whether the person who signs will be there
Step 3: Build the value case to a standard finance would accept
Most reviews die here, by presenting activity and calling it value.
The ladder:
- Activity - logins, seats, feature usage, tickets. Evidence that a mechanism is running. Belongs in an appendix or a single line, never the headline
- Outcome - the operational result in the customer's units: cycle time, error rate, hours per case, tickets deflected
- Business impact - that outcome converted into money or risk: cost avoided, revenue enabled, headcount redeployed, exposure reduced
What makes a number survive being forwarded to their CFO:
- The baseline, and where it came from
- The full cost, not just licence fees - implementation, integration, training, their own people's time. A model showing only benefits reads as a sales pitch
- The attribution assumption, stated conservatively and out loud: "we are attributing 40% of this to the workflow, the rest to the process change your team ran"
- Arithmetic the customer can reproduce. A number they cannot rebuild dies the moment they forward it
When value cannot be proven numerically, and often it cannot, use these in order:
- Have the customer say it. Arrange in advance for the champion to present their own result. A customer-stated benefit needs no attribution defence
- Document testimony instead of measurement. Has an executive said, in the last quarter, that they are achieving what they set out to achieve? Record the answer either way
- Frame it net of their cost - what working with you has cost them in effort, change management and learning curve, alongside the benefit. More honest and more credible than a one-sided claim
- Say the gap out loud and propose the instrumentation as a next-quarter action. That converts a weakness into an ask
The deeper mechanic: value is agreed in advance and confirmed at the review, not proved at the review. If no success measure was set, the meeting has nothing to measure against and will degrade into usage reporting no matter how well you build it. Fix that for next time by setting one now.
Step 4: Sequence it so the customer's business comes first
A structure that consistently works:
- Their business - what has changed for them, what they are being measured on now. Not your company update
- Goals restated, and confirmed as still current
- Progress against those goals, with the value case from Step 3. This is where adoption data finally appears, now that it has something to be measured against
- What is not working, raised by you before they raise it
- Recommendations and the ask - the largest block, not the leftover
Hold to three to five themes, not comprehensive coverage. Aim for roughly a third presentation and two thirds discussion. Keep it to an hour; for smaller accounts, half that.
Cut on sight: long introductions, full ticket recaps, feature-by-feature walkthroughs, generic roadmap decks, and your company's news. Roadmap content earns its place only when it answers a gap the customer has named - otherwise it is filler standing in for a value story you do not have.
Step 5: Shape it for who is actually in the room
- Economic buyer or executive. Open with one line: where we are against the goal you set, what I recommend, what I need from you. Business impact, risk, and a decision. Not adoption percentages
- Champion. They need ammunition to defend the investment internally, recognition, and help removing blockers. They must never be surprised in front of their own executive
- Operational users. Workflow, training, responsiveness, and roadmap that touches their actual pain
Seniority is a permission structure, not just an audience. The more senior the room, the more strategic the conversation is allowed to be - which is an argument for getting the right people there rather than for presenting differently to the wrong ones.
Where the executive is joining for a slice of the meeting rather than the whole of it, exec-conversation shapes that slice: one ask, one number they recognise, and questions only they can answer.
Bring fewer of your own people than feels natural. A vendor delegation outnumbering the customer changes the meeting.
Step 6: Pre-brief the champion
This single step prevents most of the failures below at once.
A review where the customer presents their own results is also the strongest advocacy moment you will get. advocacy-ask covers what to do with it, and the answer is not to ask in the room.
Walk the champion through the data and the narrative before the meeting. Collect their agenda items. Ask what they want out of it. Arrange for them to present their own wins. Confirm attendees and hard stops around 48 hours ahead. Send a one-page pre-read so the meeting can be spent deciding rather than absorbing.
A champion blindsided in front of their executive stops being a champion.
Step 7: Name the ask
If you cannot say what you are asking the customer to decide, do, or fund, the meeting has no reason to exist.
The ask does not have to be commercial. An introduction, a data feed, an executive sponsor, a pilot, a decision to stop doing something - all legitimate. What is not legitimate is the expansion conversation disguised as a value review. Customers do not punish the upsell; they punish the disguise.
Where the review does establish that more scope is warranted, expansion-case builds the document the champion carries into the budget conversation afterwards, which is a separate meeting on purpose. For the leave-behind that the sponsor forwards upward after the meeting, one-pager is the format.
Open the meeting by agreeing the agenda, the time, and what both sides want out of it - explicitly including that "no" is an acceptable answer.
Step 8: Close the loop
Within 24 hours: a summary with decisions, owners, dates, and the next meeting already booked. Ending a good review without follow-through wastes everyone's time in it.
Output
- The one sentence from Step 1
- A sequenced agenda with time per section
- The value case, with baseline, cost, assumption and arithmetic shown
- Three to five themes, and what you deliberately cut
- The ask, in one line
- The champion pre-brief - what to walk them through and what to ask for
- Open loops from last time, with status
- What you could not evidence, stated plainly rather than padded with activity metrics
Failure modes
- No ask. The most common structural failure. A review that informs but decides nothing
- No next step, and no meeting booked before people leave
- Surprising the customer, especially the champion, especially in front of their boss
- Re-presenting problems they already raised as if new. This reads as proof you have not been listening
- Vanity metrics disconnected from their goals, and industry benchmarks standing in for their own numbers
- The monologue. No questions asked, no silence left for them to fill
- Getting defensive when criticised - and its mirror, dwelling so long on problems that the meeting becomes an apology
- Last quarter's deck with the date changed
- Running one at all when the conditions in Step 0 said not to
What good looks like
- The customer talked more than you did
- A decision was made in the room
- The customer presented part of it
- Everything in the deck survived "so what?"
- Problems were on the agenda, and you raised them
- The value number is one they could rebuild themselves
- The next meeting was booked before anyone left