The Growth Review — Complete Guide
Written by Alex Raymond, founder of AMplify and author of The Growth Department.
A Growth Review is a scheduled, strategic meeting with a customer where their senior decision maker attends for the whole meeting, the conversation is about their business rather than your product, they do roughly two-thirds of the talking, and you leave with five evidenced answers about the account's future instead of a guess in the CRM. It is the same meeting slot as a Quarterly Business Review and the same customers. It is a different meeting with a different job. Vendors run QBRs. Partners run Growth Reviews.
Why the name changed
The Quarterly Business Review is not a designed meeting. Most Account Managers inherited it from a manager who inherited it from their manager, and every other vendor the customer works with runs the same one, so the customer arrives expecting exactly what you brought. Nobody sat down and designed it. It arrived.
What it produces is the problem. You send the invite six weeks out, build the agenda with your champion, get your own leadership on the calendar. Forty-eight hours out the executive sponsor gets pulled into something with their chief executive. Twenty-four hours out somebody has a dentist appointment. Seven minutes into the meeting one person joins and says "just me today." You run the deck anyway, because you are polite. Then you open the CRM and type 70%.
Renaming the meeting is not cosmetic, because the old name sets the customer's expectation before anyone walks in. "Quarterly Business Review" tells a senior person they are about to watch a vendor present ninety days of history. "Growth Review" tells them something about their business is on the table. The rename is the smallest part of the change and the part that makes the rest possible, which is why it comes first.
Everything structural about the meeting stays: scheduled in advance, senior people, strategic, forward-looking, prepared for. The name changes, the design changes, and the energy behind it changes. The mechanics of running the meeting itself are covered in the complete guide to Quarterly Business Reviews, and everything there still applies. What follows is what makes a Growth Review a different instrument.
The four differences between a Growth Review and an old-school QBR
Four tells separate the two meetings. You can score any meeting on your calendar against them in under a minute.
Who attends
The old meeting gets whoever accepts the invite, plus six silent people from the vendor's side. A Growth Review gets the person who controls budget, timelines, and resources, on the customer's side, for the whole meeting. On your side it gets a peer and no wallflowers, which means everyone present has a job.
What it is about
The old meeting is about you: your slides, your dashboards, your roadmap, your support tickets. A Growth Review is about them: their year, their priorities, their business, and what they need to decide.
Who does the talking
In the old meeting you talk for fifty-nine minutes and thirty seconds of an hour. In a Growth Review the customer talks for roughly two-thirds of it. You facilitate: ask, probe, and listen for the difference between an answer and a non-answer.
What it produces
The old meeting produces notes and a 70% in the CRM. A Growth Review produces five evidenced answers about the account's future, a written read, and a renewal number you can defend, while there is still time to act.
Two things sit beside that table and get mistaken for items on it. Engagement is not a fifth difference; it is the readout of the other four. When the right people attend, the meeting is about them, and they do the talking, engagement is what you see. When they ghost, delegate down, or sit with arms crossed, that is the old meeting's readout. Frequency is not a difference either; it is the earning rule, covered further down.
The five questions a Growth Review has to answer
The meeting exists to answer five questions about a single account. They map to priority, position, economic support, structural risk, and process.
- Priority. Does the problem we solve, or propose to solve, still matter to them next year, in a funded way?
- Position. Does everyone agree we are visibly the answer to it?
- Economic support. Does somebody who controls the budget believe it is worth the money?
- Structural risk. Is anything structural in the way, like a reorganization, an acquisition, a consolidation, or a competitive evaluation?
- Process. How does this renewal get decided, by whom, and when?
You will not answer all five in every meeting, and that is fine, because these run on a regular rhythm and you build toward them. What matters is that these are the questions the meeting is for, rather than a satisfaction score or a usage report.
The discipline that makes the answers usable is knowing what a non-answer sounds like, because most Account Managers accept one and write it down as evidence. "This is really important to us" is present tense and says nothing about next year. "The team loves working with you" is likeability. "We have no plans to change anything" is inertia. "Not that I'm aware of," from somebody who would not be aware, is nothing at all. Standardize the evidence your team has to come back with. Never standardize the conclusion they draw from it.
The Meeting Card: how to run one
The format is portable and the rule behind it is one line: all about them. Short, about their business, in their language.
The deck. If a slide does not help them decide something about their business, it does not make the deck. No dashboards, no roadmap, no company update. Three slides. If you must do more, five, and no more than that.
The questions. The ones only this person can answer, about their priorities, their budget reality, and how the decision actually gets made. Three of them.
The agenda. A short list, three points, each line a question about their business, written in their language. The test for every line: is this about them, or about us? About us gets rewritten or cut.
Two rules govern your own side of the table. Bring a peer, because peers attract peers and an Account Manager alone has only so much standing with a customer's executive. And no wallflowers: nobody attends just to listen, and everyone present owns something, whether a question, a probe, or an expertise moment.
AMplify members have the format as a printable Meeting Card inside the Growth Review Toolkit, along with a three-slide advocacy deck for presenting the change internally. The meeting runs forty-five minutes. Aim to talk a third of the time or less. And the ask that gets a yes is exactly as small as it sounds: forty-five minutes, a short agenda, questions about your business.
How to get senior people to attend
This is the hardest part and there is no magic wand. Three things make the difference.
Bring your own senior people. Your ability as an Account Manager to attract a customer's chief executive into a meeting with you alone is not zero, but it is not high either. Bring someone with a title from your side and make it a peer-level discussion. If your company has no executive sponsor program, this is the moment to start asking for one.
Make it about them. Not your roadmap, your offices, your awards, your new hires, your escalations, or your tickets. Their results, their business, their challenges.
Make the invitation about something they want. Compare two asks. "I want to show you our roadmap and how you have been using our tool" gets delegated. "I want to share three things we noticed about how you are solving this problem that could limit your results next year," or "I want to walk you through two opportunities we found that could roughly double your return next year," gets accepted. Speak in the language of making money, saving money, saving time, or being more efficient, and note that you already know what this customer cares about, because your sales team wrote it down when they bought and your onboarding team wrote it down again.
The first time, you may only get one level higher, from a manager to a director. Try again next quarter and you may get the vice president. That is the work.
The red rule
One rule in this system looks like a formula, and it is worth keeping because it runs in the opposite direction from most formulas. If no senior decision maker attends, the account goes red. If the senior person leaves ten minutes in and tells you to proceed without them, the account goes red. Not yellow, not 70%.
The reason is not punitive. A rule like this turns a missing conversation into a recorded unknown instead of a hopeful guess, which means it lands on the Risk Register where somebody can work it. The mechanics of the Register sit inside the Commitment phase of the Growth Department Method.
The reason to trust the rule is that attendance is the message. If a senior person still cares about the problem you solve and still believes you are part of the solution, they will make time. If they have stopped believing that, or have already decided to go elsewhere, they delegate to someone junior with no authority to answer your questions. Do not congratulate yourself on a flawless meeting run with a marketing manager. Do not explain away the absence either. Unless the customer tells you why it is not red, it is red.
Which accounts earn a Growth Review
Nobody can run a Growth Review with thirty accounts, and the attempt is how the practice dies. Old-school QBRs go to every account because the calendar says so. Growth Reviews go to the accounts that earn one. Doing fewer of them, better, is the design rather than a compromise.
The same rule that governs account plans governs these: do them well for the top 20% rather than badly for all of them. Start with one account and one excellent Growth Review before expanding. The account planning guide covers how that 20% gets chosen on potential rather than on current revenue alone.
For this meeting specifically there is a sharper filter. Plot your accounts on two axes: your confidence they will renew, and the impact if they left. The accounts that earn a Growth Review sit in the low-confidence, high-impact quadrant, the ones where you are not certain and being wrong costs the most. The accounts you are sure about and the accounts that barely matter are not where this meeting pays.
Why the Growth Review is a forecasting instrument
This is the part that makes the meeting a leadership concern rather than an Account Manager's preference.
Look at what most Account Managers read to build a forecast: product usage, health scores built from that same usage, satisfaction scores describing how someone felt three weeks ago, and CRM notes recording what they already knew. All four come from inside your own company. The customer never has to say a word. And none of them answers the only question the forecast needs answered, which is whether the person controlling the budget intends to keep paying you. A customer can be in the product daily while procurement builds a consolidation case. A health score can be green a month after finance decided the budget does not survive next year.
So the Account Manager guesses, and because they like their customers they guess high, and they type 70% against a renewal that is going to be a yes or a no. One person doing that is uncertainty. Ten people doing it for the same reason is a forecast that was voted on rather than measured.
Here is the arithmetic that makes it a portfolio problem. Take ten Account Managers, each 90% accurate, each with a million dollars of renewals. If they are wrong about different things, portfolio variance lands near 3.2%. If half of what they get wrong is shared, it is 7.4%. If they are all wrong about the same thing, it is 10%, exactly as wrong as any one of them with more zeroes on it. Same ten people, same individual accuracy, and only the first version clears a 5% tolerance. The full model, including the arithmetic behind those figures, is in The Missing Variable in Renewal Forecasting. Headcount cannot fix this, because shared error does not average away. Standardization makes it worse when it standardizes the conclusion, because training ten people to read the same four internal signals writes the blind spot into the operating model.
The Growth Review is where that shared blind spot gets broken, one account at a time, because each of those five answers belongs to a single account and comes from outside your company. An Account Manager who gets that conversation stops typing 70%. They type 90%, or they type 10%. A 10% typed in June is worth more to your company than a 70% typed in November, because you can still work a 10%. You cannot work a surprise. That is the No Surprises discipline in practice, and the renewal side of it is covered in the guide to running renewals.
What this looks like in practice
Guy Rubin, who founded Ebsta and is now at Fullcast, analyzed thousands of deals and billions of dollars of renewals and shared the result on the Account Management Secrets podcast. When the last two business reviews before a renewal were with C-suite executives, companies were seven times more likely to open a cross-sell or upsell opportunity. When those same two meetings were with someone more junior, they were four times more likely to churn the customer. That is an association rather than a proven cause, and it is measured on outcomes rather than on forecast quality. It still tells you which of those two Account Managers knows where they stand. The full conversation is in Relationships Drive Revenue.
Anthony DeShazor rebuilt the executive review process at a donation platform where any customer could leave on any day, with no contract and no notice period. Over eight quarters the pattern was close to binary. In his words, they did not lose a single customer who had an Executive Business Review, and if a customer had one, he knew they were not going to leave. He also did not offer the meeting to everybody, which is the earning rule showing up in the field. His episode is Value Is the New Contract.
Jason Scott had a three million dollar information technology services account that was going nowhere, stagnant enough that he was bored of it, with a sense the customer was drifting away. He asked for a short meeting with a senior person, and what he heard was that the customer saw him as a vendor, more transactional than a strategic partner. He accepted that rather than arguing with it, opened a notebook, and asked what was going on in the business. The customer started naming challenges, most of which his company could solve. Over the following year he more than doubled the account. He calls his version a growth roundtable, because a roundtable is a meeting where everyone talks. His episode is Your QBR Is Probably Killing Your Client Relationship.
What the four differences buy you
Run this way and you understand where you actually stand, rather than reporting a number you hope is true. You see risks and opportunities early, while there is still time to act on them. You know your customer instead of guessing at them. Relationships get broader and more senior. And you are perceived, and treated, as a partner instead of a vendor.
For a leader, the change shows up as three things: attendance becomes a leading indicator you can manage before any dashboard reflects it, forecasts arrive with reasoning attached account by account, and risk surfaces while it can still be worked. A concern heard in a Growth Review this quarter is a save. The same concern discovered at renewal is a churn. None of it requires new headcount or new tooling. It is a meeting already on the calendar, run differently.
Where to start
Take one account, ideally one in the low-confidence, high-impact quadrant. Build three slides, three questions, and a three-point agenda, with nothing in any of them about you. No office photo, no map, no roadmap. Send it as a forty-five minute invitation to a senior person, framed around something they want to know about their own business. Then run the meeting, write the read, and put whatever surfaced on the Risk Register with an owner and a date. If no senior decision maker attends, mark the account red and work it as a risk. Then do the next one.
The Growth Department is the post-sale revenue operating standard for B2B companies. Take the ten-minute Post-Sale Stress Test to see where your function stands across Clarity, Commitment, and Cadence. Or download the free audiobook of The Growth Department and read the manifesto.
About the author Alex Raymond is the founder of AMplify and the author of The Growth Department, the operating standard for the function that delivers most of a company's revenue. He spent a decade building Account Management and Customer Success systems with B2B companies before founding AMplify, where he works with Post-Sale leaders on installing the Growth Department Method. He hosts the Account Management Secrets podcast.
