Quarterly Business Review

There was a time when a vendor reached out to a customer on exactly two occasions after the contract was signed: when something broke, and when renewal — the decision point at the end of a contract term — was a month away. Customers who seemed fine were left alone, and leaving them alone looked like good manners.

So the renewal call always went the same way. Three weeks out, someone would dial the contact they had been emailing all year, find out that person left the company in August, and end up explaining the product to a successor who had no idea why the team was paying for it. The budget cut, the neighboring team already piloting a competitor — all of it surfaced on that one call, with three weeks left to respond.

None of those facts live in a usage log. A champion changing jobs, next year's budget shrinking, another team wanting in: there is no event for any of it, and no score picks it up. The quarterly business review (QBR) exists to put a conversation where those things can be said on the calendar in advance. You meet because the quarter turned, not because something broke, and the bad news arrives three months out instead of three weeks out.

One review cycle runs in five steps, from pulling the data to opening the next quarter's session.

1. Two weeks out, assemble the material. Last quarter's usage, the account's health score — several usage signals weighted into a single number between 0 and 100 — its support history, and progress against the goals written in the success plan, all on one page.
2. Confirm the attendees and send the agenda ahead of time. An agenda that lands the night before produces a customer with nothing prepared, and the meeting becomes thirty minutes of the vendor talking. An agenda that lands a week early produces a customer who brings their own numbers and their own complaints.
3. Open the meeting with last quarter's results. Put the goal set at signing next to what actually happened. If the plan was to halve document review time and review went from 3.5 days to 2, that number goes up first.
4. Then ask what got stuck. This is the body of the review. You want the feature someone tried and abandoned, the rule each team applies differently, the reason the group next door never came over. If the vendor is talking more than half the time, this is a presentation, not a review.
5. Close by agreeing on next quarter's goals, and send minutes with owners and dates inside two days. The next review opens by walking that list. Break that link and each quarter's meeting starts from zero, which makes it a courtesy call.

On the vendor side the customer success manager (CSM) who owns the account is always in the room. Larger accounts get their manager too, and accounts with a stack of product requests get Mia, so that what is and isn't coming can be answered on the spot. Unlike a business review, which is an internal look at the numbers, a customer is sitting at the table — so nothing gets promised that can't be confirmed.

On the customer side two people are needed: whoever uses the product daily, and whoever controls the budget. With only the daily user you hear every blocker and nothing about next year's spend or the coming reorg. With only the budget owner you get the reverse. Pagedeck pushes the date rather than run a review without the budget owner confirmed.

Once a quarter is the default cadence. A 45-person company cannot hold a session for every account every quarter, so the list is decided in advance. Pagedeck covers its top 20 percent of accounts by revenue plus every red account, meaning any customer flagged as likely to churn. Accounts renewing next quarter go on the list regardless of size, and the list gets rebuilt every quarter rather than fixed once a year.

When something raised in the review won't resolve at the CSM's level, the escalation path — an agreed route for who gets pulled in and when — gets used the same day. Writing it in the minutes and carrying it to the next quarter is not escalation, it's a hold.

"Is the budget owner confirmed for next week's QBR? If not, let's push it two weeks."

A session with only the day-to-day user loses half of what it's for.

"The QBR turned up a team next door that wants access. Let's open the seats conversation."

The meeting is an entry point for expansion, not only a risk check.

"Account was green all quarter and we only learned at the QBR that our champion transfers next month."

The facts that decide renewals often exist nowhere but this conversation.

At Pagedeck, Sofia picks the target accounts in the first week of the quarter and builds the material in the second. The part she works hardest on is talking less. Last quarter's results get five minutes and the rest of the time belongs to the customer. When a transfer or a budget change comes up, she adjusts the account's status that afternoon and reworks the plan for the quarter.

One review on an 82-point account produced the news that the customer was consolidating tools next year. Nothing in the usage data had moved. Sofia escalated to Grace that day, and over the following six months the team built a reason for Pagedeck to survive the consolidation. The account renewed.

The most common assumption is that these meetings are for customers in trouble. Struggling accounts are the ones with obvious things to discuss, so the logic is easy to follow. But the conversations that lead to expansion come from accounts that are doing well — a team next door that wants in, a request to make the current workflow a company standard. A customer who has just hit their goal is also the one most willing to explain how they got there, which is exactly what the next similar account needs to hear. Run reviews only for accounts at risk and the invitation itself becomes a signal, and customers who receive it assume they did something wrong.

Preparing the session as a report on vendor performance is the other common mistake. The phrase "quarterly review" suggests a presentation, so that's what gets built: twenty slides about the product, thirty minutes of the customer listening, and a polite note next quarter that the calendar is tight. What makes the hour worth holding is not what the vendor said but what the customer said, and a presentation format does not produce it.