Quarterly Business Review Template: A Meeting Your Customer Would Book Again

The typical review opens with a summary of tickets raised, features used and logins recorded. All of that is about you. The customer sat down wanting to know whether the thing they bought is doing what they bought it for, and whether the next quarter will be easier or harder than the last. When the meeting fails to answer those two questions, attendance drops, seniority drops, and eventually the meeting is politely rescheduled into nonexistence.

The fix is structural rather than presentational. Agree what success looks like at the beginning of the relationship, in the customer own words and preferably in their own numbers, then build every review around progress against that. If you never captured those objectives, the honest first review is a conversation to establish them, which is a far better meeting than a deck of statistics.

Send one question to your main contact: what would make this hour worth your time? Whatever comes back becomes the top of the agenda. At the same time, pull the data, list every open issue, and go and close or progress as many of them as possible before the meeting. Then decide your ask, singular, and check internally that you can deliver anything you are about to promise.

Invite deliberately. Your day to day contact, their manager or the budget holder if the account warrants it, and on your side the person who does the work rather than only the account manager. Give the budget holder a specific reason to attend, such as a decision that needs their input, because generic invitations to review meetings are the first thing deleted from a senior calendar.

Notice that their plans come before your plan. This is the section most often cut for time and it is the most valuable one in the meeting, because everything you might sell next quarter is downstream of what they are about to do. Ask what is changing: new sites, new products, hiring, a system being retired, a compliance deadline. Then listen rather than immediately connecting it to your product.

Your champion frequently has to justify the spend to somebody you never meet. Give them the material for that conversation: a small number of figures they can lift straight into an internal update, framed in their language rather than yours. If they measure in enquiries handled, show enquiries handled. If they measure in days to fulfil an order, show days. Resist the temptation to construct an elaborate return on investment claim on their behalf. A modest, defensible number they can stand behind is worth far more than an impressive one they cannot.

Put it early and say it plainly. What happened, what it cost them in their terms, what has been fixed, and what will be different by when, with a name attached. Then stop talking and let them respond, including if the response is unhappy. The instinct to move quickly past the difficult slide is exactly what convinces a customer that you are managing them rather than helping them.

One practical note: never bring a problem without bringing the fix and the date. A review that lists issues without ownership reads as a status report on your own shortcomings, which helps nobody.

Within a day, a short written summary with commitments, owners and dates on both sides. On the account record, the same items as tasks with dates so they exist somewhere other than an email. And a mid quarter check in booked before you close the calendar, because the plan agreed in week one is usually forgotten by week six unless something forces a look.

Keeping the objectives, the issues and the plan on one account record is what makes the next review easy to prepare, which is the real test of whether the practice is sustainable. HelloGrowthCRM holds the account history, open tasks and renewal dates in one place, which mostly saves the two hours usually spent reconstructing what was promised last quarter.

Related reading on accounts and retention: CRM for small business, lead management, features, use cases, sales automation, and book a demo.