Working with a Chief Growth Officer (CGO)

What this role actually does

The Chief Growth Officer is the person accountable for compounding revenue across the whole funnel. The seat exists when the CEO believes the growth problem is bigger than marketing and bigger than sales. Most weeks the CGO is running experiments across acquisition, onboarding, monetization, and retention, and defending which experiments deserve engineering time. The seat lives at the intersection of marketing, product, sales, and finance, and the person in it either earns that four way trust or loses the seat.

A working CGO spends real hours with product on activation and time to value, real hours with sales on segment expansion and pricing tests, real hours with finance on payback and LTV to CAC, and real hours with the CEO on the growth story the next raise or the next board meeting needs to tell. The CGO owns a growth model, meaning a spreadsheet the CFO can defend, that ties acquisition volume, conversion, expansion, and churn into one revenue projection. When the model breaks, growth stops being a discipline and starts being an argument.

The CGO carries the growth team, which usually includes performance marketing, lifecycle, growth product management, and growth engineering. In a product led company the seat also owns onboarding and monetization. In a sales led company the seat sits closer to demand generation and partners with the CRO on pipeline. The exact scope changes by company. The accountability for a revenue number and a payback number does not.

What a functioning CGO does not do: own the brand, own the product roadmap end to end, or run every channel personally. They do not own the number the CRO owns and they do not own product itself. They own the mechanisms that connect the two. A CGO who is optimizing ad copy has an operator problem two layers down. A CGO who is fighting the head of product on the roadmap has a scope problem the CEO has to resolve.

The seat also carries the political weight of translating growth into a language each function trusts. Finance wants a growth model with defensible input assumptions. Product wants a shipping partner, not a request queue. Marketing wants budget clarity across brand and performance. The CGO who is fluent in each of those languages earns the political room to run experiments. The CGO who speaks only the language of dashboards ends the year defending numbers nobody trusts.

How to brief them well

You do not brief a CGO with a channel wish list. You brief them on the growth constraint, meaning the specific place where the model breaks. If activation is 34 percent and needs to be 55 percent to make LTV work, that is the brief. If mid market payback is 22 months and the board wants 14, that is the brief. The CGO comes back inside three weeks with a portfolio of bets, a hypothesis on which one moves the number, and the engineering and marketing resources each bet requires.

Bad briefs look like a request to grow faster. Please double top of funnel. Please improve conversion. Please launch this partner channel. Every one of those may be correct and every one is a tactic without a diagnosis. The CGO who accepts a tactic brief either executes the wrong thing well or spends three months undoing the framing. Both cost the same amount of runway.

Context the CGO needs on arrival includes the real state of the data warehouse, the actual attribution model in use, which product changes are already committed for the next two quarters, and which of the CEO's public commitments cannot move. A CGO who does not know the roadmap constraint spends the first quarter designing experiments that engineering will refuse to build.

The strongest brief pairs a constraint with a hard boundary. Fix activation for the SMB segment inside two quarters. You have four growth engineers and no additional headcount until the next funding milestone. Any change to pricing runs through the CFO and the CEO before it ships. Named constraints save the CGO from running experiments that finance will kill in the QBR anyway.

The good brief also includes a written record of what the CEO believes and what the board believes. When those diverge, the CGO is going to end up in the middle of the disagreement inside two quarters. Naming the divergence in month one is how a CGO turns political risk into a manageable input.

Review cadence + operating rhythm

Weekly rhythm

Weekly at the CGO level is a growth review of thirty to sixty minutes. Active experiments, statistical significance, decisions to ship or kill, and any blocker that needs an escalation. The CGO does not decide the roadmap on the weekly. The weekly surfaces which experiments are ready to be decided at the monthly. The rest of the week is one on ones with direct reports, a Wednesday sync with product, and a Friday check in with the CEO.

Monthly and quarterly reviews

Monthly is where the CGO shows a growth operating review to the CEO and the CFO. Growth model actuals versus plan, cohort behavior on the last two quarters, blended CAC by segment, LTV to CAC by segment, and payback trajectory. The CGO also proposes the next month's experiment portfolio and the resource allocation. Monthly is when the CGO negotiates for engineering time against product's own roadmap. That negotiation usually decides which quarter the growth number will hit or miss.

Quarterly is the honest one. The CGO owns a QBR that documents every experiment shipped, the outcome, and what the team learned. It also names what the CGO is killing and where the next quarter's bets are concentrated. Board members read this QBR. If the QBR does not name at least one dead program and one abandoned hypothesis, the CGO is padding. A CGO who defends every prior bet is not learning fast enough to justify the seat.

Annual planning

Annual planning at the CGO level starts in September for a January year. The CGO builds the growth model with finance, negotiates headcount and equity against product, and produces the top of funnel and expansion numbers the CFO carries to the board. A CGO who arrives at January without an October draft has already given the CFO permission to write the model without them.

Between the standing cadences the CGO also runs a monthly forum with product, sales, and finance where the growth model is the artifact everyone edits. When the model has a single owner and the inputs are contested weekly, the model earns trust. When the model has no forum, the CFO writes their own version and the CGO loses control of the narrative.

Measurement (real KPIs, not vanity)

Five numbers matter at the CGO level and everything else is diagnostic.

First, blended payback period. New revenue divided by fully loaded acquisition cost, tracked as a rolling window by cohort. This is the number the board asks about. It survives attribution vendor changes and it is honest about paid, organic, and product led motions all at once.

Second, LTV to CAC by segment. The CGO reports this by SMB, mid market, and enterprise, and defends the input assumptions on churn and expansion. When the ratio is above three the segment funds itself. When it drops below two the CGO has ninety days to diagnose and act.

Third, activation rate. The percentage of new signups or new accounts that reach the product moment that predicts retention. Activation is the number the CGO most often owns end to end, because it is the metric the growth team can move without asking finance for more budget. A CGO who cannot pull activation trailing thirty days from memory is not close enough to the product.

Fourth, net revenue retention. Some CGOs own this directly and some influence it through lifecycle and expansion programs. Either way, the number tells the board whether the company is compounding on the installed base. NRR under 100 percent forces every acquisition dollar to work harder. NRR above 115 percent is the number that opens category conversations with the board.

Fifth, experiment velocity and win rate. Ships per quarter, percent that produce a statistically clean lift, and the median lift size. Velocity without win rate is churn dressed as motion. Win rate without velocity is a team afraid to ship. The CGO who reports both keeps the CEO honest about whether growth is a machine or a slogan.

Vanity metrics that mislead include impressions, clicks, MQL count divorced from activation, session count, and gross signup volume. A CGO who reports gross signups without activation is hiding a funnel problem. The CFO catches this inside two quarters and the seat loses political capital that does not come back.

The CGO also carries a diagnostic layer under the top numbers: the segment where activation stalls, the channel where CAC drifts up, the pricing tier where expansion pauses. When a top metric moves, the CGO points at the diagnostic that explains it. When the top metric moves and the CGO cannot point at the driver, the seat has stopped operating and started reporting.

Compensation + career path (honest ranges)

CGO comp splits into three market bands and the ranges are honest about the scope.

Compensation bands by market

Mid market. Series B to early C, ten to fifty million ARR. Base 260 to 330 thousand. Bonus 25 to 40 percent of base. Equity 0.35 to 1.0 percent depending on stage. Total cash 320 to 460 thousand. This band skews toward operator CGOs who still write SQL and read cohort tables. The role often reports to the CEO and sits between product and marketing on the org chart.

Tech metro. Series C onward, fifty to two hundred million ARR, based in Austin, Denver, Chicago, Atlanta, or hybrid to those hubs. Base 330 to 430 thousand. Bonus 30 to 50 percent. Equity 0.20 to 0.60 percent. Total cash 430 to 640 thousand. This band expects a functional leader with four to seven direct reports and prior category experience.

Coastal enterprise. Public or late private, San Francisco, New York, or Boston based. Base 400 to 560 thousand. Bonus 50 to 80 percent. Equity or RSUs valued at 800 thousand to 2.5 million a year. Total comp routinely lands between 1.2 and 3 million. This band expects public company readiness, board level narrative, and prior success turning a growth model into an earnings call story.

The typical next step is CEO of a smaller company, President or COO at the current company, or general partner at a growth fund. CGOs who move sideways into a CMO role usually do it because the company changes shape and marketing becomes the constraint. The move to CEO is more common for CGOs than for CMOs because the seat already carries a revenue number.

Common departures. The two year exit when the growth model does not compound and the CEO changes the framing. The eighteen month exit when the CGO and the head of product cannot align on the roadmap. The four year run when the CGO builds a compounding model, hires a strong successor, and moves to a bigger seat or a fund. A healthy CGO tenure is three to five years.

The negotiation moment when a CGO takes the seat is the split between what the CGO owns and what the CRO owns. If the seat also carries a piece of the pipeline number, comp reflects it. If the seat is a P and L role in a product led company, comp reflects that. The offer that pretends the accountability question does not exist is the offer that produces the two year exit.

Common ways this seat fails

The CGO who inherits a broken growth model and treats it as a marketing problem. Activation is bad because onboarding is confusing, and the CGO spends the first quarter on paid channels because that is what they know. Two quarters later the model is worse and the CEO changes the framing. The CGO who does not diagnose the constraint before they act loses the seat inside a year.

The CGO who cannot get engineering time. Growth needs engineers and engineers report to product. When the CGO cannot negotiate a reliable capacity commitment from the head of product, every experiment cycle stretches from four weeks to twelve. Ship rate drops, learning rate drops, and the CFO stops trusting the model. The right move is a written capacity commitment ratified by the CEO. The CGO who does not push for that in the first sixty days is going to lose every prioritization argument that follows.

The CGO who confuses experiment count with learning. The team ships thirty experiments a quarter and none of them move the model. Velocity without win rate is a team optimizing for their own dashboard. The CGO who does not audit hypothesis quality, sample size discipline, and post ship measurement is running a theater of growth. The board sees this pattern inside two quarters.

The CGO who wrestles the CMO. Category creation and demand generation both influence CAC and both need budget. A CGO who does not negotiate a clean boundary with the CMO on brand versus performance spend spends the year fighting for scope instead of moving numbers. The right boundary is negotiated with the CEO in month one. The CGO who postpones that conversation loses political capital every quarter.

The CGO who cannot ship on payback. Every experiment lifts a mid funnel metric and payback stays flat. The pattern is common in product led companies where the growth team is optimizing for activation while pricing and packaging are broken upstream. The CGO who does not name that gap and force the pricing conversation with the CFO and the CEO is going to spend two years running experiments on the wrong lever.

The seat also fails quietly when the CGO wins a few big experiments early and then stops running the small ones. Growth is compounding on the base rate of shipping. The team that produces one big win a year and thirty small wins builds a moat. The team that produces two big wins a year and no small wins builds a headline that ages badly.