Turn Client Reviews Into Decisions, Not Status Recaps

Status takes over when nobody defines the decision

Most client reviews start with good intentions. The advisor pulls service data, supplier updates, contract dates, open projects, and a few slides about the relationship. Then the meeting becomes a tour of everything that happened since the last meeting.

The client hears that twelve tickets closed, an order is still pending, and three vendors have product updates. Everybody nods. Nobody commits to anything. The next review starts with the same open issues.

That is a reporting meeting, not an advisory meeting.

A useful client business review gives both sides enough evidence to make a small number of decisions. Some decisions will create opportunities. Others will protect a renewal, correct a delivery problem, or stop work that no longer deserves attention. All of those outcomes are better than filling an hour.

Choose the decisions before you build the deck

Do not start by opening last quarter's presentation. Start with the account.

Review the current client priorities, open commitments, contract events, active projects, service problems, stakeholder changes, and opportunities. Look for decisions that need the client's judgment or approval. A pending supplier task is not automatically a client decision. Neither is an internal follow-up your team should have completed already.

A decision belongs on the agenda when the client needs to choose a direction, confirm a priority, assign an owner, accept a tradeoff, or approve a next step. Write it in plain language:

• Decide whether to renew the current connectivity design or compare alternatives before the notice deadline.
• Confirm who owns the remaining work required to open the new location.
• Choose whether the recurring support issue needs a supplier escalation or a service change.
• Approve, revise, or stop the assessment proposed after the last review.

Limit the meeting to the decisions the client can reasonably handle. Seven weak agenda items do not become strategic because they appear on an executive slide.

Build the review from evidence, not account folklore

Client history gets unreliable when every person brings a different version. Sales remembers the promise. Operations remembers the ticket. The supplier remembers the order. The client remembers the impact.

Prepare one evidence packet before the meeting. It should contain only what helps the current decisions:

• Prior decisions, owners, due dates, and current disposition
• Material service or support patterns, with the source and period identified
• Open project milestones, dependencies, and client commitments
• Contract dates and notice deadlines checked against the signed agreement
• Current spend or service inventory when it changes the decision
• Stakeholder changes and the latest confirmed client priority

Label what is known, what came from a supplier, and what still needs confirmation. "Client wants to replace the platform" is dangerous if one frustrated user said it six months ago. "Operations asked us on August 4 to price two alternatives" is usable.

Your 90-day client account plan should supply the current priorities, dates, stakeholders, and one decision worth advancing. The business review tests that plan with the client. It should not invent a separate account story every quarter.

Send a decision agenda before the meeting

The client should know where judgment is required. Send the agenda early enough for the right people to attend and for missing evidence to surface.

For each proposed decision, include the current state, why it needs attention now, the options being considered, and what evidence will be reviewed. Name the people whose input or approval is needed. If finance needs to approve a commercial change, discovering that at minute forty does not count as executive engagement.

Give the client permission to change the agenda. A priority may have moved. A decision may belong with somebody else. One urgent issue may deserve the whole meeting. Better to learn that before polishing slides nobody needs.

Keep routine status available as a pre-read or appendix. Do not hide bad news. Just stop making routine updates compete with decisions for meeting time.

Run the meeting around five moves

The exact timing will vary, but the operating sequence should stay simple.

1. Confirm what changed. Ask whether the client's priorities, people, timing, or constraints changed since the agenda was prepared.
2. Close prior commitments. Confirm what finished, what did not, and whether an overdue item still matters.
3. Review the evidence. Show only the facts required for the decision. Explain gaps instead of covering them with more slides.
4. Make the decision. Record the choice, including any condition that must be satisfied before work proceeds.
5. Assign the next external action. Name one owner, one due date, and the proof that will close the action.

If the group cannot decide, do not write "continue discussion." Record what is missing, who will get it, and when the decision returns. An unresolved decision still needs an owner.

Do not force a sales opportunity into every review

A client business review is commercially useful because it improves the relationship and reveals real work. That does not mean every meeting needs a pitch.

Sometimes the right recommendation is to keep the current service. Sometimes the client needs to finish an implementation before considering anything else. Sometimes your firm needs to fix a support or billing issue before asking for more business.

When a new opportunity is justified, connect it to a confirmed client decision. Open the opportunity with the problem, owner, timing, evidence, and agreed next action. Do not turn a vague discussion into pipeline because someone said a category sounded interesting.

The technology advisor discovery process still applies. A client review can create the reason for discovery. It does not replace discovery.

Close the loop while the meeting is fresh

Send the decision record shortly after the meeting. Keep it short enough that the client will correct it if something is wrong.

For every decision, record the chosen direction, owner, due date, dependencies, evidence required for completion, and next review point. Separate client commitments from advisor, supplier, and internal tasks. "Team to follow up" is not ownership.

Put those actions in the same operating system as the client, activities, contracts, projects, and opportunities. Advisor OS includes client records, activity history, tasks, contracts, reporting, and a QBR builder. That lets the review pull from the account record and send decisions back into the work instead of leaving the final slide deck in a folder.

The system will not make the meeting useful for you. It will make it much harder to pretend an action was clear when no owner or date was recorded.

Score the review by what moved

Do not judge the meeting by attendance, slide count, or how positive the conversation felt. Check the operating result.

Did the client confirm or change the priorities? Did the group make the decisions on the agenda? Did old commitments close or receive a clear recovery plan? Does every open action have an owner and date? Did any new opportunity enter discovery with a confirmed business reason?

Review those answers before scheduling the next meeting. If the team keeps carrying the same decisions forward, fix the preparation, evidence, attendees, or decision authority. Changing the slide template will not help.

Pick three upcoming client reviews. Replace the status agenda with decision statements. Pull the evidence from your account records, send the decisions in advance, and record the outcome beside the client work. If that requires hunting through inboxes and asking several people what happened, run the free Advisor OS agency scorecard. The review problem probably starts with the operating system behind it.