Working with a VP of Growth

What this role actually does

The VP of Growth runs the cross functional growth team under the CMO, the CGO, or the CEO depending on the org shape. The seat is where product led motions meet performance marketing, and where experiments meet the P and L. In a product led company the VP of Growth often owns activation, onboarding, monetization, and lifecycle. In a sales led company the seat sits closer to demand generation and paid acquisition.

A working VP of Growth spends real hours with product on the roadmap items that move activation and conversion, real hours with the performance marketing team on channel efficiency, real hours with the analytics team on the growth model, and real hours with the CFO on payback and unit economics. The seat carries a mixed team, usually growth product managers, growth engineers, performance marketing managers, and lifecycle marketers. The scope is smaller than the CGO scope by one layer and heavier on execution.

The VP of Growth owns the experiment portfolio, meaning what the team is testing this quarter and what got killed last quarter. They also own the growth model in operational form, meaning they are the person who tells the CFO which segment is compounding and which one is leaking.

What a functioning VP of Growth does not do: run the ad account personally, code the experiments themselves, or write every email. They do not own the demand generation number if the org has a separate demand VP. They do not own the product roadmap. They influence both. A VP of Growth who is writing SQL at eleven at night has an analyst problem two layers down.

The VP also carries the operating discipline that makes experiments believable. Pre registration on hypotheses, defined sample sizes, and a post ship audit that verifies the lift held for thirty days. Without that discipline the growth team ships wins that reverse. Finance stops trusting the model inside two quarters and the VP loses the political room to expand the team.

How to brief them well

You brief a VP of Growth on the growth constraint. Here is the metric the model needs to move. Here is the segment where the constraint lives. Here is the resource envelope. Here is what falls outside your scope. The VP comes back inside two to three weeks with a portfolio of bets, a hypothesis on which one moves the number, and a resource ask that RevOps and engineering can plan around.

Bad briefs to a VP of Growth look like a channel or feature request. Please improve paid social. Please launch a referral program. Please rebuild the onboarding flow. Any one of those may be the right answer and none of them is a diagnosis. The VP who executes a tactic brief either ships the wrong thing well or spends the quarter rebuilding what the CMO or CGO actually wanted.

Context the VP needs on arrival includes the current experiment velocity, the data warehouse hygiene, the engineering capacity commitment for growth work, the state of the attribution model, and which product areas the head of product considers off limits. A VP of Growth who does not know the off limits areas is going to burn a quarter proposing changes engineering will refuse to build.

The strongest brief pairs a metric target with a defended capacity commitment. Move activation from thirty four percent to fifty percent inside two quarters. You have three growth engineers, two growth PMs, and defined access to two product surfaces. Any change to pricing runs through the CGO or CMO. Named capacity saves the VP from spending the year negotiating for engineering time in one off requests.

The strong brief also names the segment where growth is going to run. A growth motion in SMB is different from a growth motion in enterprise. The VP who accepts a brief that lets the segment stay vague ships experiments that never compound because the population is heterogeneous.

Review cadence + operating rhythm

Weekly at the VP level is the growth review and the pipeline of experiments. A Monday of about an hour with the growth team covering experiments in flight, decisions to ship or kill, and blockers that need escalation. A Wednesday sync with product on shared roadmap items. A Friday one on one with the CMO or CGO. Numbers reviewed weekly are experiment ship rate, active experiment win rate, and the top of funnel metrics the team is testing against.

Monthly is the operating review with the CMO or CGO. Growth model actuals versus plan, cohort behavior, blended CAC by segment, activation trend, and the proposed next month portfolio. The VP walks in with a reallocation proposal and defends it. Monthly is where the VP earns or loses the political room to ask for more engineering capacity.

Quarterly is the retrospective and the plan. The VP presents every experiment shipped, the outcome, the median lift, and the current state of the model. This is where entire experiment tracks get killed and new ones get greenlit. If the QBR does not name at least one abandoned track, the VP is padding.

Annual planning at the VP level is the operational half of the CGO or CMO plan. The VP sizes engineering and analytics headcount, forecasts the yield from the experiment portfolio, and negotiates against product for capacity. A VP who arrives at January without a written portfolio plan is going to lose engineering time to product's own roadmap.

Between the standing cadences the VP also runs a monthly review with product management on the shared roadmap. When product ships a feature the growth team did not brief, growth loses a quarter. When growth runs an experiment that touches a product surface without product involvement, product resists the next ask. The monthly forum is the coordination discipline that keeps both teams shipping.

Measurement (real KPIs, not vanity)

Four numbers matter at the VP of Growth level.

First, blended payback period. Same as at the CGO level but the VP owns the operational movement of the number. When payback stretches out, the VP is the person who diagnoses whether the cause is CAC, activation, or expansion.

Second, activation rate. The percentage of new signups that reach the product moment that predicts retention. This is the number the VP most often owns end to end. A VP who cannot pull activation trailing thirty days from memory is not close enough to the work.

Third, experiment velocity and win rate. Ships per quarter, percent that produce a statistically clean lift, and the median lift size. The VP owns the operational discipline of the experiment program. Weak sample sizes, missing pre registration, and cherry picked windows are the failure modes the VP eliminates.

Fourth, growth model attainment. The gap between the growth model forecast and the actual number, cut by segment. When the gap opens, the VP has thirty days to diagnose the cause and produce a written plan. A VP who cannot narrate the gap is not going to earn the room to expand the team.

Vanity metrics that mislead include gross signup volume, session count, social engagement, and generic clickthrough numbers. A VP who reports gross signups without activation is hiding a funnel problem. A VP who reports channel efficiency without payback is defending a local metric while the model leaks.

The diagnostic layer under blended payback is the segment cut of CAC, average deal size, and churn. When payback stretches, the VP is the person who names which of the three inputs moved. Without a segment level cut, every payback conversation is a discussion about the average, and the average hides the segment that is quietly leaking.

Compensation + career path (honest ranges)

VP of Growth comp splits into three market bands.

Mid market

Mid market. Series B, ten to thirty million ARR. Base 200 to 260 thousand. Bonus 20 to 35 percent. Equity 0.15 to 0.50 percent. Total cash 240 to 340 thousand. Team size four to eight. Often a player coach VP who still writes SQL and reads experiment results themselves.

Tech metro

Tech metro. Series C onward, fifty to two hundred million ARR. Base 250 to 340 thousand. Bonus 25 to 45 percent. Equity 0.08 to 0.30 percent. Total cash 320 to 470 thousand. Team size six to fifteen. Cross functional leadership across product, engineering, and marketing is expected.

Coastal enterprise

Coastal enterprise. Public or late private. Base 300 to 420 thousand. Bonus 35 to 55 percent. Equity or RSUs 400 thousand to 1.2 million a year. Total comp 700 thousand to 1.7 million. Team size ten to twenty. This band expects prior public company experience and comfort presenting to public market investors.

The typical next step is CGO at a smaller company, CMO at a growth stage company, or a lateral to a larger VP of Growth seat. The move to CEO happens rarely and usually requires the VP to have owned a segment P and L in a prior role.

Common departures. The two year exit when the growth model does not compound. The eighteen month exit when the VP cannot get engineering capacity and burns out. The clean three year run when the VP moves activation or payback substantially and takes a bigger seat elsewhere. A healthy VP of Growth tenure is two to four years.

The negotiation moment for a VP of Growth is the capacity commitment on engineering and analytics. A VP with three engineers is a different seat from a VP with eight. The offer that treats capacity as a soft ask produces a VP who spends the year negotiating for people rather than running experiments.

Common ways this seat fails

The VP who cannot get engineering time. Growth needs engineers. When the head of product does not commit capacity, every experiment cycle stretches. Ship rate drops, win rate drops, and the model stalls. The VP who does not push for a written engineering commitment in the first sixty days is going to lose every prioritization argument for the rest of the tenure.

The VP who runs experiments without a growth model. The team ships experiments, some produce lifts, and none of them connect to the P and L. The CFO stops attending growth reviews. The pattern signals a VP who is running experiment theater. The right fix is a written growth model in month one that traces every input to the revenue line.

The VP who confuses local optimization with growth. The team optimizes button colors and headline copy on the pricing page. Conversion moves one point. Payback does not. A VP who does not push into pricing, packaging, and product changes is running a landing page function, not a growth function.

The VP who cannot manage the tension with product. Every growth experiment overlaps with the product roadmap. The head of product resists, the VP escalates too often, and the CEO gets tired of the pattern. The right move is a defined boundary and a weekly sync. The VP who does not build the working relationship early is going to lose scope inside two quarters.

The VP who ships gross signups without activation. Top of funnel volume climbs, activation flat, retention drops. The CFO catches it in the payback number and the VP loses the seat inside a year. The VP who ties every acquisition experiment to the activation and retention downstream is the VP who compounds.

The seat also fails when the VP ships too many small wins and cannot show a compounding move on the model. Ten wins that lift local metrics by two points each do not add to a twenty point move on payback because the wins overlap or interact. The VP who does not stack rank experiments by expected payback impact is running experiment theater.