Chief Growth Officer vs VP of Growth
Chief growth officer vs vp growth is not a title debate, it is a question of altitude. One owns the whole revenue engine from the C-suite. The other executes a growth motion inside one function. Here are the five gaps that decide which one your stage actually needs.
One owns revenue, one runs a function
A chief growth officer and a VP of growth both live and breathe growth, but they are not the same hire. One is a C-suite revenue owner. The other is a functional growth lead. The gap between them is altitude, authority, and scope, and getting it wrong costs you either money or momentum.
I have run growth at executive altitude and I have managed VP-level growth leads under me, so I will be blunt about where the line sits. A VP of growth is an exceptional doer. Hand them a clear thesis and a defined funnel and they will out-execute almost anyone: ship experiments weekly, raise activation, squeeze a channel until it gives. That is real, valuable work. But their authority stops at the boundary of their function. When growth stalls because marketing and sales are misaligned, or because nobody owns expansion revenue, a VP of growth cannot fix it. They do not have the org-chart reach. A chief growth officer does, because the CEO handed them the whole engine and a seat on the exec team. At Elementor I owned that full scope and took the growth function through a $200K-to-$20M ARR arc, which is a different job than optimizing one funnel stage.

Where the two roles actually diverge
| Dimension | VP of Growth | Chief Growth Officer |
|---|---|---|
| Scope | One growth function or motion | The entire revenue engine end to end |
| Authority | Executes the strategy | Sets the strategy and owns the number |
| Reports to | CMO, CRO, or COO | CEO, sits on the exec team |
| Mandate | Hit channel and funnel targets | Re-architect how the company grows |
| Accountability | Pipeline, activation, a funnel stage | Net new revenue and net revenue retention |
| Comp | $180K-$260K base plus equity | $250K-$400K-plus plus C-suite equity |
Altitude is the whole story
Where a VP of Growth sits
Mid-tier on the org chart, one or two levels below the C-suite. They report into a CMO, CRO, or COO and usually manage a growth pod: a few growth marketers, a product-led-growth engineer, a data analyst. Their authority stops at the edge of their function. They own execution, not the company’s growth thesis.
Where a Chief Growth Officer sits
On the executive team, reporting to the CEO with a seat at the board table. A CGO does not manage one pod, they coordinate the leaders of marketing, sales, and customer success around a single revenue plan. The authority is horizontal across functions, not vertical inside one. That altitude is the whole point of the title.
Why altitude changes the work
A VP of Growth optimizes the machine they are handed. A CGO decides what the machine should be. When growth stalls in the seams between functions, a VP cannot reach across the org chart to fix it, they lack the authority. A CGO can, because the CEO gave them the whole engine. Same growth fluency, different altitude and mandate.
Match the hire to where growth is stuck
Strategy vs execution
A VP of Growth runs the playbook. A CGO writes it. If you already know the growth thesis and need someone to execute relentlessly inside a function, hire a VP. If nobody owns the thesis and growth is leaking between functions, you need the altitude of a CGO.
Functional vs cross-functional
A VP of Growth has authority inside one function and influence everywhere else. A CGO has authority across marketing, sales, and retention because they sit at the exec level and report to the CEO. Cross-functional problems need cross-functional authority, not just a strong opinion.
A motion vs the whole engine
A VP of Growth owns a motion: acquisition, activation, or a PLG funnel. A CGO owns the entire revenue engine including the handoffs a VP cannot touch. When the bottleneck is a single channel, scope a VP. When it spans the whole funnel, scope a CGO.
Hiring the wrong altitude costs you
The decision is not about seniority for its own sake, it is about where your growth problem actually lives. Framed plainly, chief growth officer vs vp growth is a question of which gap you are filling, ownership or execution. If you already have a working growth thesis and you need someone to execute it inside a defined function, a VP of growth is the right and cheaper hire. They will run the playbook harder and faster than a CGO ever would, because execution at depth is the job they signed up for.
You need a chief growth officer when the problem is structural rather than functional. Growth has plateaued and nobody can name the real bottleneck. Marketing generates leads sales never works. A product-led motion has no commercial owner. Expansion revenue is everyone’s job and therefore no one’s. These are seam problems, and seams sit between functions where a VP of growth has no authority. A CGO operates at the altitude where those seams are visible and reports to the CEO with the mandate to fix them. This is also why a fractional CGO works so well at growth stage: you get C-suite revenue ownership and the authority that comes with it, at the bandwidth the problem needs, without committing to a permanent $300K-plus salary before you know the shape of the work. If your gap is execution, hire a VP. If your gap is ownership of the whole revenue engine, hire a CGO. Many companies that think they need a VP of growth actually have a CGO-shaped hole, which is also the distinction between a virtual CMO and a true cross-functional revenue owner.
Everything you need to evaluate the role
Tell me where growth is stuck and I will tell you the altitude you need
What has stalled, what the funnel looks like, who owns the number today. I will tell you whether your gap is execution inside a function or ownership of the whole engine, and whether a VP of growth or a fractional CGO is the right call.
Sources: Chief growth officer (Wikipedia)