What a VP of Growth Should Actually Own

A VP of Growth should own one number: the probability that the revenue the company has already told the board to expect will actually land. Not lead volume. Not website traffic. Not how many meetings got booked this week. Every other line on the job description is instrumentation built to serve that one number.

I watched the alternative up close before I had language for what was wrong with it. A VP of Growth I'll call Desmond ran growth at a 150-person logistics software company I'll call Northlane, selling dispatch and routing software to regional trucking fleets. His board measured him the way most boards still measure growth leaders: marketing qualified leads, sales meetings booked, campaigns shipped, content published. Every one of those numbers climbed for three straight quarters. Bookings stayed flat.

When the CFO pulled the forecast apart, more than half the "qualified" pipeline had no economic buyer and no forcing function attached. It had been counted as progress because it existed, not because anyone had assessed how likely it was to close. Desmond wasn't lying about his numbers. He was accountable for the wrong number, and nobody above him had noticed the gap until the miss showed up in a board deck.

Key takeaways

• A VP of Growth's real job is a probability call, not an activity report. The forecast should be the sum of assessed probabilities on real opportunities, not a rollup of CRM stages or lead counts.
• Activity metrics and revenue probability move independently. Leads, meetings, and content output can all rise for quarters while the probability-weighted forecast stays flat or falls.
• Owning probability means owning decision rights, not just reporting. The job includes killing low-probability activity on purpose, not logging it as progress.
• The honest trade-off: probability-first management produces quiet-looking weeks. Fewer meetings, lower email volume, and a flatter activity chart, on dashboards built to reward busyness.
• The data backs the shift. McKinsey found 72% of the fastest-growing B2B companies call their analytics effective for sales planning, versus 50% of the slowest, and the chief revenue officer's average 25-month tenure is itself evidence of what happens when accountability sits on the wrong number.

The business problem: a forecast nobody can defend

Most revenue forecasts are not probability models. They are optimism rollups, a stage-weighted guess built from whatever a rep typed into a CRM field, aggregated up through a sales manager with every incentive to round up, and handed to a growth or marketing leader with no visibility into whether the number underneath is real. Nobody owns the probability. Everybody owns a piece of the activity that produced it.

The cost of that gap is not abstract. Research published in Harvard Business Review found the average chief revenue officer tenure is just 25 months, among the shortest of any C-suite role. Revenue growth goes flat or declines in 62% of companies during the fiscal year that follows a CRO transition. That is not a story about individually bad hires. It is a story about a role that keeps getting measured on the wrong inputs until the forecast misses badly enough that someone has to be replaced.

I've written about the layer of this problem one level down, where lead volume climbs while pipeline quality quietly rots underneath it. The forecast problem sits a layer above that. It's possible to have a defensible pipeline definition and still forecast badly, because nobody has been assigned to own the probability that the whole thing closes on time.

Why the usual fix, better dashboards, fails

When a forecast misses, the standard response is to add more visibility: more activity fields in the CRM, more granular MQL scoring, a new dashboard that slices the same lead and meeting counts three more ways. Northlane's board did exactly this with Desmond. They asked for weekly activity reports broken down by rep, channel, and campaign. The reports got longer. The forecast didn't get more accurate, because every new metric was still measuring the same thing: how much activity happened, not how likely any of it was to turn into revenue.

More dashboards fix a visibility problem. They don't fix an ownership problem. Nobody at Northlane had been asked to look at an individual opportunity and say, out loud, with a number attached: this closes at 30% probability, not 70%, and here's why. Without that judgment call, made opportunity by opportunity and defended weekly, more data just means more precisely measured noise.

What a VP of Growth should actually own

I run five ownership tests against any growth or revenue role I'm evaluating, including my own seat at ViitorCloud. A VP of Growth owns all five, or the title is mostly decorative.

• The probability-weighted forecast, not the top-line pipeline total. Every open opportunity gets an assessed probability the owner can defend in one sentence, and the forecast is the sum of those, not a stage-based multiplier applied to the whole list.
• Decision rights over where effort goes. The job is deciding which accounts get more investment and which get killed this week, not producing a longer list for reps to work through.
• The definition of a real signal. If a lead, meeting, or pipeline stage doesn't move the probability number, it isn't a result. It's activity that happened.
• The cadence that surfaces probability changes early. A weekly review built around what changed in probability and why, not a monthly readout of what activity occurred.
• The miss, when it happens. When the forecast is wrong, the VP of Growth explains which probability assessment was wrong and why, not how hard the team worked.

Here's the trade-off I'd rather name than hide. A week run on probability discipline can look quiet on a dashboard built to reward busyness. Fewer meetings get booked, because low-probability activity gets killed on purpose instead of logged as progress. Fewer emails go out, because a sequence that isn't moving a real account's probability gets paused instead of run to completion for volume's sake.

Executives used to watching an activity chart climb every week will ask why it flattened. The honest answer is that the team stopped doing the wrong things faster than it started doing new ones.

What the evidence says

This isn't just an operating preference. The Growth Institute's own research on the role makes the same distinction structurally: a VP of Growth owns the growth constraint, not a channel or a department. That constraint shifts every quarter, which makes diagnosing it a continuous job, not a quarterly planning exercise. The same research recommends replacing single-number forecasting with probabilistic planning outright, independent confirmation of the same claim from outside my own operating experience.

The market-level data points the same direction. McKinsey's analysis of B2B sales-growth outperformance found 72% of the fastest-growing B2B companies say their analytics are effective for sales planning, against 50% of the slowest-growing ones. That gap isn't explained by who has more dashboards. It's explained by who has built a real probability model underneath the dashboard, and who is still reporting stage counts and calling it a forecast.

The ViitorCloud perspective: the machine scores probability, judgment owns the call

This is the same argument I make about engineering work, applied to growth. I've written before about why value migrates to whoever can tell good output from bad once production gets cheap, and a revenue forecast is exactly that kind of output. Enrichment tools, intent data, and forecasting models can now compute a probability estimate on every open opportunity continuously, at a scale no revenue team could recompute by hand.

As VP of Growth at ViitorCloud, after 14 years moving from an individual contributor seat through CTO and COO before this one, I run the same five-test audit against our own funnel before I'd recommend it to anyone else's. Every open opportunity on my forecast has a probability I can defend out loud, and accounts that can't clear that bar get deprioritized instead of counted. You can see the kind of delivery accountability that discipline is meant to protect in our case studies.

We now run this as a working engagement for growth and revenue leaders we call the Growth Operating System Review: we pull your current forecast, test it opportunity by opportunity against a real probability model instead of CRM stage, and hand back a rebuilt cadence built around what predicts revenue instead of what's easy to count. If your board is watching an activity chart climb and nobody can say with confidence what it predicts, ViitorCloud's technology consulting team runs the Growth Operating System Review as a working engagement, not a slide deck you file away.

An ownership audit you can run this week

This takes an afternoon against your current forecast and last board deck, not a quarter of new tooling.

• Pull your last board deck and count how many metrics are activity, meetings, MQLs, emails sent, versus probability, forecast movement you can explain opportunity by opportunity. If activity outnumbers probability three to one or worse, the dashboard is measuring the wrong thing.
• For your ten largest open opportunities, ask whoever owns growth to name why the probability moved up or down this week. "It's in late stage" is not an answer. A specific reason tied to the buyer is.
• Check who has the authority to kill a low-probability account outright, today, without a committee. If the honest answer is nobody, or an individual rep, growth ownership hasn't actually been assigned to anyone.
• Pull the postmortem from your last significant forecast miss and check whether it discussed probability assessment or activity volume. If it's activity, the wrong lesson got drawn from it.
• Recompute this quarter's forecast weighting every open opportunity by a probability you can defend in one sentence, not by its CRM stage, and compare it to the number in the current board deck. The gap is the size of your ownership problem.

Frequently asked questions

What does it mean for a VP of Growth to own revenue probability?

It means the VP of Growth is accountable for how likely the company's committed revenue is to actually close, assessed opportunity by opportunity, rather than for the volume of leads, meetings, or campaigns their team produces. The forecast becomes the sum of real, defensible probabilities instead of a rollup of CRM stages.

Isn't pipeline volume still important for a growth leader?

Volume still matters as a raw input, but it isn't the job. A VP of Growth who tracks volume alone can watch every activity number rise for quarters while the probability-weighted forecast stays flat, because volume says nothing about whether the accounts behind it can actually close.

How is this different from what a CRO or VP of Sales already owns?

Titles vary by company, and the lines blur in practice. What doesn't change is the principle: whoever is accountable for growth in an organization should be judged on the probability of committed revenue landing, not on their department's activity count. If that accountability isn't assigned to anyone by name, the forecast will keep missing regardless of what the org chart says.

What's the first change to make if our metrics are mostly activity today?

Replace one metric in your next board deck with a probability-weighted number you can defend line by line, and stop presenting the activity metric beside it as if the two measure the same thing. That single substitution usually surfaces which parts of the current pipeline were never real to begin with.