Chief Growth Officer (CGO)
.png)
A Chief Growth Officer (CGO) is a C-suite executive who owns the full arc from market positioning to signed contract, holding accountability for pipeline health, win rates, and the integration of business development and marketing into a single revenue-generating function.
How the CGO Role Differs from a CMO or BD Director in AEC
Most AEC firms historically split growth functions between a marketing director who managed proposals and a BD director who managed client relationships, with neither owning revenue accountability end to end. The CGO role closes that gap. Where a CMO typically oversees brand, content, and proposal production, the CGO owns the number: total contract value pursued, hit rate by market sector, and the strategic decision of which clients and project types the firm should be chasing three years from now. At firms between 500 and 2,000 people, the CGO often inherits both functions and has to rebuild coordination between teams that developed separate workflows, separate data, and sometimes separate CRM instances. The non-obvious friction point is that proposal coordinators and BD managers rarely report through the same chain before a CGO arrives, which means pursuit data is fragmented by design.
Where the CGO Shows Up in the Pursuit Cycle
A CGO rarely writes a single line of proposal copy, but their decisions shape every pursuit from go/no-go through debrief. They set the go/no-go criteria that filter which RFPs the team responds to, define the win themes that should run through every SF-330 Section H, and are often the executive who reviews debrief notes to recalibrate sector strategy. In QBS-governed public procurements under the Brooks Act, where price is off the table and qualifications carry everything, the CGO's job is to ensure the firm's positioning work happens before the RFQ drops, not after. They also own the relationship with practice area leaders and principals whose project work feeds the win rate data the CGO reports to the board or ownership group.
What Breaks When the CGO Lacks Institutional Knowledge Infrastructure
The most common failure mode for a newly installed CGO is inheriting a growth function with no reliable data underneath it: win rates calculated inconsistently, project experience scattered across individual hard drives, and pursuit histories that live in the heads of people who have since left the firm. Without a structured record of what was pursued, who worked on it, and why the firm won or lost, strategic decisions default to instinct and seniority rather than pattern. A CGO trying to make a data-backed case for entering a new market sector, or for dropping a sector where hit rate has been poor for four years, needs verified pursuit history, not anecdote. Kantiv gives CGOs that foundation by capturing pursuit context, outcome data, and personnel contributions across the full pursuit cycle, so growth strategy is built from what actually happened rather than what the team remembers. The firms that get the most out of a CGO hire are the ones that treat institutional knowledge as infrastructure, not an afterthought.
Related terms