DEV Community: Ali Sadhik Shaik

Chapter 9. Stage 4 - Scale

Ali Sadhik Shaik — Sun, 05 Jul 2026 02:17:01 +0000

9.0 What Scale Means
The Scale stage begins when a B2B Enterprise company has built a working engine - a repeatable wedge, a predictable demand system, a sales motion that closes consistently, and a customer base that retains and expands without heroic intervention - and ends when the company has either become a category leader with multi-product depth or has run into a structural ceiling that prevents further compounding. Most companies enter this stage somewhere between $20M and $30M in annual recurring revenue. Most exit it somewhere between $100M and $200M. The exit is not defined by the revenue number. It is defined by whether the company has compounded its engine into a system that can carry the company through the next decade, or has simply scaled the existing engine until its limits became visible.
This is the stage at which the CPMO role is hardest. The reason is structural. At Founding, Wedge, and Engine, the CPMO is operating mostly in greenfield - building things that did not exist before. At Scale, the CPMO is operating in installed terrain - the systems built at Engine are now in production, the team is now large, the customer base is now substantial, and every change has to account for the inertia of what already exists. The work shifts from construction to evolution, and evolution is harder than construction, because the costs of change are higher and the benefits are less immediately visible.
This is also the stage at which most CPMOs fail. The failure rarely looks like incompetence. It looks like a CPMO who is doing the right work for the previous stage in a company that has moved past it. The Engine-stage CPMO who built the demand system continues to focus on demand system optimization at Scale, when the work has shifted to category construction and portfolio strategy. The product-strong CPMO who held the Shape stage tightly at Engine continues to direct individual roadmap calls at Scale, when the work has shifted to platform architecture and ecosystem positioning. The failure is invisible in real time and obvious in retrospect, which is the most dangerous combination of properties any executive failure mode can have.
Section 9.6 of this chapter, on why most CPMOs fail at this stage, is the most important section of the playbook for sitting CPMOs. The five sections that precede it set the context within which the failure becomes legible.

9.1 The CPMO's Job at the Scale Stage
The job at Scale is to compound the engine into a system that can carry the company through the next decade.
The phrasing matters. The Engine stage built the engine. The Scale stage compounds it. Compounding is a different kind of work than building. Building requires engineering instinct, customer intimacy, and the willingness to ship imperfect things. Compounding requires architectural judgment, strategic patience, and the willingness to invest in things that will pay off over years rather than quarters. The CPMOs who built the engine at the previous stage are not always the right CPMOs to compound it at this one, and the question of whether the same executive can make the transition is one of the most consequential personnel decisions a CEO and a board face.
Concretely, the CPMO function at Scale is doing seven things in parallel. Each one is more architectural than its Engine-stage predecessor.
The first is category construction. At Engine, the company sold into an existing category against existing competitors. At Scale, the company has the volume, the reference base, and the analyst standing to define a category - to name the problem space differently, to set the evaluation criteria buyers will use, and to position itself as the natural leader of the category it has named. This work is multi-year, deeply public, and largely irreversible once committed. Companies that successfully construct categories at Scale - Salesforce with CRM in the early 2000s, Snowflake with the data cloud in the late 2010s, HubSpot with inbound marketing across both decades - produce moats that compound for the rest of the company's existence. Companies that fail to construct categories remain features in someone else's category, indistinguishable from cheaper or faster alternatives.
The second is portfolio architecture. At Engine, the company had one product, possibly with editions or modules. At Scale, the question of multi-product strategy becomes live. Should the company expand into adjacent products through internal build, acquisition, or partnership? Should the products be sold separately, bundled, or platformed? How are pricing, packaging, and positioning organized when there is more than one product to manage? These decisions are CPMO-level decisions - too strategic for the VP of Product to make alone, too product-shaped for the CRO to drive, too commercial for the CTO to own. The CPMO is the executive whose remit covers all the surfaces these decisions touch, and the executive whose loop integrates the answers.
The third is the institutionalization of the operating system. The cadences, decision rights, and review mechanisms that emerged organically at Engine become codified at Scale into an executive operating system that is more formal, more documented, and more durable. The reason for the formalization is not bureaucratic instinct but operational necessity. At seventy-person scale, the CPMO can run the system through personal relationships and adjacent management. At three-hundred-person scale, the system has to operate through documented protocols, named decision rights, and explicit review mechanisms - because the CPMO is no longer one or two layers from every person doing the work, and the integration cannot run on personal proximity alone.
The fourth is brand and category investment in compounding surfaces. At Engine, the brand was a downstream consequence of the work. At Scale, the brand has to be invested in directly - through executive points of view that establish category leadership, through analyst relationships that shape Magic Quadrant placement, through public artifacts that compound over years (books, conferences, open-source releases, research reports), and through the deliberate construction of category-defining narratives. This investment is the most important under-funded line item in most Scale-stage companies, because its returns are invisible in the short run and dominant in the long run. The CPMO who under-invests in this layer at Scale produces a company that is operationally healthy and structurally fragile.
The fifth is international expansion. Most B2B Enterprise companies at Scale make their first serious commitments to non-home-market revenue. The work is more than a marketing translation exercise. It involves regional ICP differences, regulatory differences, partner channel differences, pricing localization, language and content production at scale, and the question of how the org structure accommodates regional accountability without fragmenting global coherence. The CPMO is accountable for the product and marketing components of this expansion, with the CRO accountable for the sales components. The boundary management between the two is a recurring source of friction at this stage.
The sixth is the deliberate management of platform and ecosystem dynamics. At Scale, the company's product is increasingly a platform - used by customers, integrated by partners, extended by developers, and surrounded by an ecosystem of complementary products and services. Ecosystem health is a CPMO concern because it shapes the product's gravitational pull, the competitive moat, and the long-term defensibility of the category position. Companies that invest deliberately in ecosystem health - through API maturity, partner programs, developer experience, and marketplace economics - produce moats that pure product investment cannot replicate.
The seventh is the most quietly consequential: the construction of the company's own product and marketing capability as a strategic asset. At Scale, the CPMO function is itself an institutional capability. The processes, talent density, and compounding learning of the function become a competitive advantage that is harder to copy than any individual product feature. Companies that invest in this capability - through deliberate hiring, internal development, talent rotations, and the construction of institutional knowledge - produce CPMO functions that outperform peer companies in ways that are visible in operating metrics but rarely traced back to their source.

9.2 Team Shape: PM, PMM, Growth, Brand, Ops
The team at Scale grows from the seventy-person Engine-stage org into a structured organization of one hundred fifty to three hundred fifty people, depending on the company's size and motion. The shape of that growth is more consequential than at any previous stage, and the org design choices made at Scale will shape the company for the rest of its existence.
The leadership layer below the CPMO expands from the five Engine-stage VPs into a more elaborate structure that accommodates the seven work streams described above.
A Chief Product Officer, accountable for product strategy execution, product management, design, and product operations across the portfolio. The relationship between the CPMO and the CPO at Scale is the most consequential reporting relationship in the company. The CPO runs the product organization. The CPMO sets the strategic frame within which the product organization operates. When the relationship works, the company has both depth in product execution and integration across the loop. When it does not, the company either has a CPMO who is doing the CPO's job (and producing strategic incoherence everywhere else) or a CPO who is operating as a peer rather than a report (and producing the dual-executive dysfunction the role was created to avoid).
A Chief Marketing Officer or VP of Marketing, accountable for brand, demand generation, content, communications, and the public-facing surfaces of the company. The title varies by company. The substance is consistent: this is the leader who runs the marketing organization at scale, with a team of fifty to one hundred fifty marketers across the disciplines. The most common Scale-stage hiring error is bringing in a marketing leader from a Platform-stage company without the operating instincts for a still-compounding business. The right hire is an executive who has personally led a marketing function through the Scale-to-Platform transition, not one who arrived at a Platform-stage company after the transition was complete.
A VP of Product Marketing, often elevated to a more senior title at this stage, accountable for positioning, launch operations, sales enablement, and the cross-functional integration of product into market. Product marketing at Scale is the function most often elevated in title and most often diluted in actual influence. The CPMO's job is to ensure product marketing remains a strategic function rather than a service function - that it sets positioning rather than merely communicating it, that it shapes pricing rather than merely defending it, and that it is in the room when product strategy is set rather than receiving the strategy as a downstream input.
A VP of Growth or Chief Growth Officer, accountable for the systems that drive activation, expansion, and product-led acquisition surfaces. At Scale, growth becomes its own discipline rather than a corner of marketing or product. The leader runs a team of growth product managers, growth engineers, lifecycle marketers, and analysts. The function is responsible for the loops described in Chapter 4 - content loops, sales loops, expansion loops, network loops - and for the instrumentation that makes them measurable.
A Head of Brand and Communications, accountable for the long-term narrative, the executive voice, the analyst relationships, the public relations function, and the compounding brand investments. This role is sometimes a peer to the CMO, sometimes a report. The sometimes-peer-sometimes-report ambiguity is itself a signal: at Scale, the brand investment is large enough and strategic enough that some companies elevate it to its own seat, while others manage it within a marketing organization led by a leader whose remit covers both demand and brand.
A Chief Strategy or Chief of Staff, accountable for the operating system, the strategic planning cadence, the M&A integration when relevant, and the cross-functional projects that span the CPMO's domain. This role is often misunderstood. It is not a junior position. The right occupant is an experienced operator whose work makes the CPMO's other direct reports more effective rather than competing with them.
A VP of Operations, accountable for the data, systems, analytics, and infrastructure that underpin the function. At Scale, this function splits into specialized sub-functions: marketing operations, product operations, analytics, and the platform engineering work that supports both product and growth surfaces.
The international structure at Scale becomes a real org design question. Companies typically choose between three patterns: a fully centralized structure with regional sales overlays (common in product-led companies), a regional structure with local product marketing and demand generation but global product (most common in mid-market enterprise), and a regional structure with local product variations (common in regulated or highly localized markets). The choice is consequential and difficult to reverse. The CPMO is accountable for making it deliberately rather than letting it emerge through tactical hiring decisions.
The total team size at the end of Scale is typically two hundred to four hundred people across product, marketing, growth, and operations. The CPMO at this size has six to nine direct reports, which is the upper bound of effective span of control. Companies that exceed this number are usually in the process of restructuring.

9.3 Cadence: Weekly Ops, Monthly Business Review, Quarterly Planning
The operating rhythm at Scale formalizes the Engine-stage cadence into a structured executive operating system that is documented, repeatable, and durable. The cadence is the same in shape - weekly, monthly, quarterly, annual - but more elaborate in execution.
The weekly cadence has three named meetings. The CPMO leadership team meeting, ninety minutes, with the six to nine direct reports, focused on the state of the loop and the cross-functional decisions of the week. The CPMO-CRO standing meeting, sixty minutes, focused on the shared surface and the operational coordination of pipeline, deals, and customer health. The CPMO-CEO check-in, thirty to sixty minutes, focused on the small number of strategic questions that require executive alignment that week.
A fourth weekly element appears at Scale that did not exist at Engine: the CPMO's own deep work block. The role is structurally vulnerable to becoming a calendar of meetings. CPMOs who do not protect dedicated time for thinking, writing, customer conversations, and direct engagement with the loop produce decisions that are reactive rather than considered. The deep work block is not negotiable. The CPMOs who succeed at Scale all have some version of it, structured differently but functionally equivalent.
The monthly cadence is the monthly business review, three to four hours, attended by the CPMO leadership team, the CRO and key revenue leaders, the CEO, and the CFO. The review is now a formal artifact, with a standardized deck, named accountabilities for each section, and a written follow-up document that captures decisions made and actions assigned. The review is structured around the loop - Sense, Frame, Shape, Ship, Scale - with each section anchored by the leader accountable for that stage and supported by the metrics that measure it.
A second monthly cadence appears at Scale: the cross-functional product and marketing council, two hours, attended by the CPMO leadership team and the senior leaders below them. This is where the operating coordination of the function happens - launch readiness, campaign coordination, segment alignment, and the operational details that the executive review cannot accommodate. The council is what allows the executive review to remain strategic rather than degenerating into a status meeting.
The quarterly cadence is the quarterly planning and review cycle, with two distinct events. The quarterly review at the end of the quarter is an extended monthly business review with a full cumulative view of the quarter. The quarterly planning at the start of the next quarter is the moment at which the company commits to the small number of cross-functional priorities the CPMO function will pursue, and the moment at which the operating plan is documented in writing.
A third quarterly cadence at Scale is the analyst and customer advisory board cycle. Major analyst briefings happen quarterly. Customer advisory board meetings happen quarterly. The cadence is built into the calendar so that strategic input from customers and category influencers is regular rather than reactive.
The annual cadence is the annual strategy reset, the budget cycle, and the annual planning offsite. The strategy reset is now a deliberate multi-week exercise involving deep Sense work, Frame revision, and Shape commitments at the multi-year horizon. The budget cycle is where the CPMO defends the function's investment level against the CFO and the CEO, with the supporting evidence drawn from the year's operating data. The annual planning offsite is where the leadership team commits to the year's priorities in a way that will hold up against the operational pressure of the months that follow.

9.4 Metrics: NRR, Segment Win Rate, Pipeline Coverage
The metrics that matter at Scale are the metrics that became reliable at Engine, now segmented more deeply, accompanied by the leading indicators of category and brand health that did not exist at earlier stages.
Net revenue retention is the central health metric of the company at Scale. The benchmark for healthy B2B Enterprise NRR is typically 110% to 130%, with the industry-leading companies operating above 130% sustainably. NRR below 100% at Scale indicates a structural problem - either product-market fit deterioration, competitive pressure, or pricing power erosion - that no amount of new logo acquisition can compensate for at this stage. The CPMO's job is to maintain NRR through product-led expansion, customer success integration, and pricing discipline, with the CRO as the operating partner.
Segment win rate becomes a primary diagnostic at Scale. The win rate grid - segments by competitors - is the input to almost every strategic decision the CPMO makes. The grid exposes where the company is winning and losing, and the patterns it reveals are usually more useful than any aggregate metric. A company with 60% overall win rate that is actually winning 90% in one segment and losing 80% in another is a company with a segment-specific problem that requires targeted action, not a general performance problem that requires broad effort.
Pipeline coverage and pipeline quality metrics mature into a more sophisticated set at Scale. Coverage is segmented by product, segment, and motion. Quality is measured through stage progression rates, conversion rates, and the distribution of deal sizes. The metric that most often exposes Scale-stage dysfunction is the trend in pipeline quality rather than pipeline volume - companies whose pipeline is growing in volume but degrading in quality are companies whose engine is being optimized for the wrong outcome, and the CPMO who is reporting volume without quality is missing the operating signal the company needs.
Category and brand metrics become measurable at Scale for the first time. Share of voice in analyst reports. Inclusion in evaluation shortlists. Search volume for the company's category-defining terms. Mentions in LLM-generated summaries when buyers research the category. Inbound deal flow attributed to brand and content surfaces. These metrics are leading indicators of category position. They move slowly. They cannot be optimized in a quarter. They are also the metrics that distinguish companies building durable category leadership from companies operating excellent engines without category position. The CPMO who reports them deliberately establishes the case for the brand investment that the CFO is otherwise inclined to cut.
Pricing power metrics - list price realization, average selling price by segment, discount rates, and the trend in deal economics - become operational at Scale. The metric that most directly measures the strength of the CPMO's positioning work is the trend in pricing power. A company whose discounting is increasing over time has a positioning problem, regardless of what the win rate looks like. The CPMO is the executive accountable for that trend.
Three categories of metrics at Scale require active discipline to keep honest. Sourcing metrics - what percentage of pipeline is marketing-sourced versus sales-sourced - are politically sensitive and easily manipulated through definitional changes; the CPMO and the CRO have to agree on the definition once and refuse to litigate it monthly. Cohort metrics - retention, expansion, and behavior by customer cohort - are the most useful operating metrics at Scale and the ones most companies report wrong, usually by averaging across cohorts in ways that hide the underlying dynamics. Forecasted metrics - projected NRR, projected pipeline coverage, projected category position - should be reported with the same discipline as actual metrics, with explicit assumptions and explicit confidence intervals; companies that report forecasts without discipline produce executive decisions that are based on aspirations rather than evidence.

9.5 Traps: Optimizing the Funnel While the Category Shifts
Five traps catch Scale-stage companies more often than any others. Each one is a more advanced version of a trap that began at Engine, and each one is more expensive to recover from at Scale than at any earlier stage.
The first is the central failure mode of the stage and the title of this section: optimizing the funnel while the category shifts. The company's engine is operating well. The metrics are healthy. The team is producing. Meanwhile, the underlying market is changing in ways the operating metrics do not yet detect. A competitor is reframing the category. The buyer's evaluation criteria are shifting. The technology underpinning the product is being disrupted by an AI-native alternative. The CPMO, focused on the operating health of the engine, optimizes what is in front of them and misses what is happening at the periphery. By the time the change becomes visible in the metrics, the lead time required to respond is longer than the time available. This trap has destroyed more category leaders in the past decade than any other, and it will continue to. The defense is the discipline of Sense - sustained investment in market signal, deliberate attention to weak signals, and the willingness to act on patterns before they are statistically significant.
The second is the over-extension of the wedge. The company found a wedge at Founding, made it repeatable at Wedge, and built an engine around it at Engine. At Scale, the temptation is to extend the wedge into segments and use cases where it does not actually fit, on the assumption that the engine that worked in the original segment will work everywhere. It will not. Each segment is a different wedge. Each wedge requires testing, learning, and adjustment. Companies that extend their wedge without that discipline produce expansion revenue that is shallow, churn-prone, and brand-damaging. The CPMO's job is to maintain segment discipline at Scale, even under the pressure of growth targets that demand expansion.
The third is the platform that is not actually a platform. As the company adds products, the temptation is to call the collection a platform - to bundle them, to position them as integrated, to sell them as a unified value proposition. The platform claim is structurally different from the platform reality. A platform is a system in which the components are integrated, the data flows between them, the user experiences them as one product, and the value of using multiple components exceeds the sum of their individual value. A platform claim made in marketing without the underlying integration is a claim that customers will detect, competitors will exploit, and analysts will discount. The CPMO who allows the platform narrative to outpace the platform reality produces a company whose category position becomes brittle.
The fourth is the operating model that does not scale with the team. The cadences, decision rights, and review mechanisms that worked at one hundred people break at three hundred. The CPMO who does not deliberately rebuild the operating system at the transition produces a function that is operationally degraded, in which decisions are slow, accountability is unclear, and the integration that the role is supposed to provide leaks across the gaps between leaders. The rebuild is not a single project. It is a sustained discipline of evolving the operating system as the team grows.
The fifth is the personal trap of the CPMO at Scale: doing the work the previous CPMO would have done. The Engine-stage CPMO ran the function through proximity, personal relationships, and high-intensity engagement with the work. The Scale-stage CPMO has to run the function through delegation, system design, and selective engagement. The CPMOs who fail at Scale are usually the ones who cannot make this transition - who continue to operate in the previous mode, become bottlenecks on every decision, and produce functions that are personally led but institutionally weak. The transition is psychologically difficult and structurally unavoidable.
9.6 The Hardest Stage and Why Most CPMOs Fail Here
Scale is the stage at which most CPMOs fail. The pattern is consistent enough across companies that it is worth describing in detail, because a CPMO who recognizes it in their own work has a chance to correct course before the failure becomes irreversible.
The failure has four distinguishable forms.
The first is the CPMO who built the engine and cannot architect the system. The work that produced success at Engine - operational intensity, customer intimacy, hands-on execution across the loop - does not produce success at Scale. The Scale-stage work requires architectural judgment, strategic patience, and the willingness to invest in things that pay off over years. The CPMO who is comfortable in operational mode, whose identity is built around being the executive who gets things done, often cannot make the transition to architectural mode. They continue to do operational work, become bottlenecks on every decision, and produce a function that is operationally led at a stage where the work is structural.
The second is the CPMO who arrived at Scale from a Platform-stage company and applies the wrong playbook. They were hired because of the size of the company they came from. They bring the structures, processes, and instincts that worked at the larger company. The structures are too elaborate for the current stage. The processes are too formal for the current cadence. The instincts are tuned for stewardship rather than compounding. The result is a function that looks polished and produces less than the leaner Engine-stage version did, because the work the company actually needs is closer to compounding than to stewardship.
The third is the CPMO who optimizes the engine while the category shifts. This is the trap described in 9.5, in its CPMO-personal form. The CPMO is not lazy or incompetent. They are doing excellent operational work. They are also doing it in the wrong direction, because they are not investing the strategic attention required to detect category-level changes early enough to respond. The failure becomes visible when a competitor reframes the category, an analyst report shifts the evaluation criteria, or a new entrant changes the buying conversation - and the company discovers that its CPMO has been running the existing engine while the market that engine was built for has moved underneath them.
The fourth is the CPMO who cannot resist the operating pull. The work at Scale is increasingly architectural, but the operating work is more visible, more rewarding in the short term, and more familiar. The CPMO who cannot resist the pull of the operating work - who continues to weigh in on launch decisions, write positioning documents personally, manage individual product calls, and stay involved in customer escalations - produces a function in which they are personally heroic and institutionally weak. The team beneath them does not develop. The systems that should compound are operated by the CPMO rather than running on their own. When the CPMO leaves, the function collapses, because nothing was actually built.
The defenses against these failures are knowable but not easy.
The first defense is the deliberate choice to architect rather than operate. This requires the CPMO to spend less time in the work and more time in the design of the work. It requires giving up the satisfaction of personally producing outputs in exchange for the longer-term satisfaction of building systems that produce outputs without them. It requires the discipline to refuse meetings the CPMO would have attended at Engine, to push decisions down to the leaders who should be making them, and to invest in the documentation and codification of the operating system in ways that feel bureaucratic but are structural.
The second defense is the deliberate maintenance of category awareness. This requires the CPMO to spend a meaningful portion of their time outside the operating cadence - in customer conversations, analyst briefings, competitive monitoring, and the kind of unstructured market sensing that does not produce immediate operating outputs. The temptation to skip this work, especially when the operating cadence is demanding, is the trap that produces category-shift failures. The defense is the calendar discipline of protecting the time even when the operating pressure is highest.
The third defense is the willingness to redesign the operating model when the team size demands it. The cadence, the decision rights, and the review mechanisms that worked at one hundred people are not the right mechanisms at three hundred. The CPMO who continues to run the previous operating model produces a function whose decisions are slow and whose accountability is unclear. The redesign is a recurring exercise at Scale, not a one-time event.
The fourth defense is intellectual honesty about whether the CPMO is the right person for the next stage of the company. Some CPMOs successfully transition from Engine to Scale to Platform. Many do not. The honest CPMO acknowledges, at some point in the Scale stage, whether they are the right operator for the company they are building, or whether the company will be better served by a different leader for the next stage. This is the hardest conversation the CPMO will have with themselves and with the CEO. It is also the conversation that distinguishes the CPMOs who serve their companies from the ones who serve their tenure.
The Scale stage ends when the company has built durable category leadership in a defined space, has compounded the engine into a system that does not depend on heroic individual effort, and has either committed to a multi-product platform strategy or has positioned itself as a focused leader in a specific category. When that condition is met - typically somewhere between $100M and $200M ARR, though the operating reality matters more than the revenue figure - the company is ready to enter the Platform stage, where the question shifts from "can we compound the engine" to "can we manage a portfolio." That is the subject of the next chapter.

About This Series
This article is part of the The CPMO Playbook series - a chapter-by-chapter serialization of The Chief Product and Marketing Officer: An Operating Playbook for the New Executive Seat in B2B Enterprise by Ali Sadhik Shaik.

Read the full book: Zenodo · Amazon · Google Play · LeanPub · Gumroad

A note on the writing: this article, like the book it draws from, was produced in close collaboration with AI - used for research synthesis, structural framing, and editorial development. The operating logic and editorial judgment are the author's.
Ali Sadhik Shaik is a product executive and operator at Astrikos AI, a DBA candidate at Golden Gate University, and the author of The Algorithmic Monographs and The Chief Product and Marketing Officer. Subscribe to The CPMO Playbook for the next chapter.

Chapter 8. Stage 3 - Engine

Ali Sadhik Shaik — Sat, 04 Jul 2026 01:34:44 +0000

8.0 What Engine Means
The Engine stage begins when a B2B Enterprise company has a repeatable wedge - a defined ICP, a sales motion that closes deals without the founder in every conversation, and a product that delivers value reliably to customers who match the pattern - and ends when the company has built a system that can compound that repeatability across multiple segments, multiple channels, and multiple product lines without the system itself becoming the constraint. Most companies enter this stage somewhere between $3M and $5M in annual recurring revenue. Most exit it somewhere between $20M and $30M. The exit is not defined by the revenue number. It is defined by whether the company has built an actual engine - a set of interlocking systems for product, marketing, sales, and customer success that produce predictable output without heroic individual effort - or has accumulated a large team running on the same founder-driven energy that worked at Wedge.
This is the stage where the CPMO seat genuinely exists for the first time, where the title appears on org charts, and where the structural challenges of the role become visible. It is also the stage where most CPMOs are first hired from outside. The founder-CPMO of the Founding and Wedge stages has either grown into the role and remains accountable for it, or has handed it to a hired executive and stepped back to focus on company-building, capital, and the other CEO functions that now demand full attention. Either path is viable. The path that does not work - the founder who claims to have hired a CPMO but continues to operate as one - produces the failure mode this chapter spends most of its energy describing.
The Engine stage is also the stage at which the loop, in the language of Chapter 4, is operating in all five stages simultaneously for the first time. Sense was the dominant stage at Founding. Frame and Shape were added at Wedge. At Engine, all five stages are active, all five have specialized leaders below the CPMO, and the integration across them is the work the CPMO is paid to do. The org chart that supports this integration is more elaborate than at any previous stage and requires deliberate design, which is the subject of Section 8.2.

8.1 The CPMO's Job at the Engine Stage
The job at Engine is to convert a repeatable wedge into a compounding system.
This phrasing is deliberate. A repeatable wedge produces predictable output as long as the conditions of the wedge hold. A compounding system produces output that grows faster than the inputs grow, because the loops described in Chapter 4 are now real and reinforcing. Repeatability is linear. Compounding is exponential. The Engine stage is the stage at which the company makes the transition from one to the other, and the CPMO is the executive accountable for whether the transition succeeds.
Concretely, the CPMO function at Engine is doing six things in parallel, with each one requiring more deliberate management than at Wedge because each one now involves a specialist leader and a team beneath them.
The first is segment expansion. The company found a wedge in one segment. The Engine stage is when the company tests whether that wedge can be extended to adjacent segments. The discipline is not to spray new segments hoping something works, but to identify the two or three segments most likely to share the same buying triggers, run controlled experiments in those segments, and either commit or retreat based on the evidence. A company that is winning consistently in mid-market financial services has natural adjacencies: mid-market insurance, financial services in larger enterprise, financial services internationally. Each adjacency is a hypothesis. Each hypothesis needs testing with the rigor of the original wedge work. The CPMO function is the discipline of running these tests with the same care the original wedge received.
The second is the construction of a real demand creation system. At Wedge, demand came from the founder's network, from a small content effort, and from the early sales team's outbound work. At Engine, demand has to come from a system - a set of interlocking content, brand, partnership, event, and product-led surfaces that produce pipeline at predictable rates without the founder. The construction of this system is the largest investment the CPMO makes at Engine, and the one most often executed badly. Most Engine-stage companies build the demand system by hiring a senior demand generation leader and asking them to produce pipeline. The CPMO function's job is to ensure the demand system is consistent with the positioning, integrated with the product surfaces, and instrumented well enough that what works can be scaled and what doesn't can be killed.
The third is pricing and packaging maturation. At Wedge, pricing was approximate, packaging was simple, and most deals were negotiated personally. At Engine, the pricing architecture has to support a sales team that can close deals without executive escalation, the packaging has to support multiple buyer profiles within the ICP, and the discount discipline has to be tight enough that the company is not slowly destroying its own price realization. This is the stage at which most B2B Enterprise companies make their first significant pricing error - usually by discounting too aggressively to win deals, which trains the sales team and the market that the list price is fictional. The CPMO function's job is to set the architecture clearly enough that discount discipline is enforceable, and to refuse to be the discount authority in live deals.
The fourth is the institutionalization of competitive intelligence. At Wedge, competitive intelligence was the founder's mental model of a small set of alternatives. At Engine, the competitive set has expanded, the competitors are responding to the company's success, and new entrants are emerging because the category is now visible. The CPMO function builds a competitive intelligence system that produces real-time signal - win/loss patterns by competitor, feature parity tracking, narrative monitoring, analyst commentary, customer perception research - and that integrates this signal into both product and positioning decisions. Most Engine-stage companies do this work badly. They produce competitive battle cards that are out of date within a quarter, win/loss reports that no one reads, and analyst briefings that are reactive rather than strategic.
The fifth is the deliberate construction of the launch system. At Wedge, every launch was a one-off run by the founder and the product marketer. At Engine, launches happen monthly or more often, span multiple product lines and segments, and require coordination across product, marketing, sales, customer success, and partner functions. The launch system - the standardized playbook for tier-one through tier-three launches, the readiness criteria, the post-launch review discipline - has to be built once and then continuously refined. A CPMO who is personally running individual launches at Engine is doing the work of someone two layers below them and producing chaos in everything they are not personally running. The work is to build the system, staff it, and let it run.
The sixth is the establishment of the executive operating cadence - the weekly, monthly, and quarterly rhythm under which the CPMO's team and the CPMO's peer relationships are managed. This is the work that separates Engine-stage CPMOs who succeed from those who survive for eighteen months and burn out. The cadence is not optional. The cadence is what makes the rest of the work tractable. Section 8.3 develops it in detail.

8.2 Team Shape: Building the First Real Org
The team at Engine grows from the lean Wedge-stage cluster of ten to fifteen people into a structured org of thirty-five to seventy. The shape of that growth is more consequential than the absolute size, and most Engine-stage CPMOs design the org wrong on the first attempt and rebuild it within eighteen months.
The standard composition of an Engine-stage CPMO org, in a B2B Enterprise company between $5M and $25M ARR, includes specialized leaders in five functions reporting to the CPMO.
A VP of Product, accountable for product management, design, and product strategy execution. This person manages the PM team that runs individual product lines or major surfaces, and is the CPMO's primary partner on roadmap, packaging, and the Shape stage of the loop. The relationship between the CPMO and the VP of Product is the most consequential reporting relationship in the org. When it works, the CPMO can think about strategy and integration while the VP of Product runs execution. When it does not, the CPMO ends up doing both jobs, the VP of Product becomes a coordinator, and the company under-invests in either strategy or execution.
A VP of Product Marketing, accountable for positioning, launch execution, sales enablement, competitive intelligence, and the translation of product into market. This is the role most often hired wrong at Engine. The temptation is to hire a brand marketer or a content leader for this seat. The right hire is an operator who has personally run product marketing at a B2B Enterprise company through a similar stage transition, who understands the discipline of positioning as a strategic instrument, and who can manage relationships with both the product team and the sales team without becoming captured by either.
A VP of Demand Generation or VP of Growth, accountable for the systems that produce pipeline. The title and the scope vary by the dominant motion. In a sales-led company, this person owns demand gen - paid acquisition, content distribution, events, partnerships, and the early funnel. In a product-led company, this person is more often called Head of Growth and owns activation, in-product conversion, and lifecycle expansion. In hybrid companies, both functions exist with different leaders. The CPMO's job is to ensure the function is matched to the dominant motion and that its leader has authority over the surfaces that actually produce pipeline.
A Head of Brand, Content, or Communications, accountable for the long-term narrative work, the public point of view, the analyst relationships, and the content surfaces that compound over time. This is the function most often under-resourced at Engine, because its outputs do not show up in this quarter's pipeline number. The under-investment is a strategic error that the company will pay for at Scale, when the absence of accumulated brand and category equity will leave the company indistinguishable from cheaper or faster competitors.
A Head of Operations, accountable for the data, systems, and analytics that support the rest of the function. This person owns the marketing automation stack, the product analytics infrastructure, the reporting cadence, and the experimentation discipline. In smaller Engine-stage companies, this role is held by a strong individual contributor rather than a leader with a team. In larger ones, the role splits into separate marketing ops, product ops, and analytics functions.
Below these five leaders sit the teams that do the actual work. Product managers, designers, product marketing managers, content writers, demand gen managers, growth product managers, and operations specialists. The total team size at the end of Engine is typically sixty to ninety people, depending on the company's size and motion.
Three structural choices in this org shape are worth flagging because they are the most contested.
The first is whether product marketing reports to the CPMO directly or through the VP of Product Marketing. At Engine scale, the VP of Product Marketing should manage the team and the CPMO should focus on strategic positioning calls. The CPMO who manages individual PMMs directly is a CPMO who is doing the VP's job and not their own.
The second is whether growth reports to the CPMO or to the VP of Product. Both configurations exist in the wild. The cleaner version, in B2B Enterprise, is for growth to report to the CPMO directly when the role spans both product surfaces and marketing surfaces. When growth is purely a product-surface function, it can sit under the VP of Product. When it is split, the split itself is usually a sign that the role has not been thought through clearly.
The third is whether revenue operations sits in the CPMO org or the CRO org. The cleaner answer is that revenue ops sits with the CRO, and marketing ops and product ops sit with the CPMO. A unified ops function that spans both organizations sounds appealing on the org chart but produces a function whose loyalty is to neither executive and whose work is shaped by whichever leader is more demanding in any given week.

8.3 Cadence: The Operating Rhythm Emerges
The operating rhythm at Engine matures from the weekly cadence of Wedge into a structured executive operating system that is the same in shape, if not in detail, as the system the company will run for the rest of its life.
The weekly cadence is anchored by a CPMO leadership team meeting - ninety minutes, attended by the five direct reports, with a consistent agenda that covers the state of the business, the state of the loop, and the decisions that need to be made this week. The agenda is not negotiable, but the contents are. The state of the business covers pipeline, customer health, and any active crises. The state of the loop covers what was learned in Sense, what is being tested in Frame, what is being committed in Shape, what is shipping in Ship, and what is compounding in Scale. The decisions section is the one most CPMOs underinvest in. It is the place where the small number of cross-functional calls that need executive attention get made, with named decision rights and named timelines. A weekly leadership meeting that produces no decisions is a status meeting wearing a leadership label.
A second weekly cadence is the CPMO-CRO standing meeting - sixty minutes, just the two executives, focused on the shared surface described in Chapter 2. ICP refinement, win/loss synthesis, sales enablement, pipeline coverage, pricing discipline. This meeting is the operational expression of the partnership the role depends on. Engine-stage CPMOs who skip this cadence - usually because they believe their relationship with the CRO is good enough that it does not need a standing meeting - produce the most expensive cross-functional dysfunction in the company.
The monthly cadence is the monthly business review, three hours, attended by the CPMO leadership team, the CRO and key revenue leaders, and the CEO when the agenda warrants. The review is structured around the loop rather than around functional reports. Sense covers what changed in the market in the past month. Frame covers any positioning tests or narrative shifts. Shape covers what was committed and what was de-prioritized. Ship covers the launches that landed, the launches that missed, and the readiness for the next month's launches. Scale covers the loop metrics - activation, retention, expansion, NRR by segment, and the leading indicators of pipeline quality. The monthly review is the document that the CEO and the board can rely on to understand the state of product and marketing in the company. It is also the document that becomes the substrate of the quarterly business review.
The quarterly cadence is the quarterly planning and review cycle, with two distinct events at each end of the quarter. The quarterly review at the end of the quarter assesses what was committed, what was delivered, what was learned, and what the implications are for the next quarter. The quarterly planning at the start of the next quarter commits to the small number of cross-functional priorities the CPMO function will pursue. The discipline of quarterly planning at Engine is to commit to fewer things than the leadership team thinks possible. A quarter with three CPMO-level priorities will produce more than a quarter with eight.
The annual cadence is the annual strategy reset and the budget cycle, typically conducted in the final quarter of the year for the following year. The strategy reset is a deeper version of Sense, Frame, and Shape, run with longer horizons and more deliberate input from the CEO, the CFO, and the board. The budget cycle is where the CPMO defends investment levels for the function against the CFO's pressure for efficiency and the CRO's pressure for revenue. CPMOs who arrive at the annual budget cycle without a year of strong operating data lose this argument, and the resulting under-investment compounds for the following twelve months.
8.4 Metrics: Pipeline, Win Rate, CAC Payback
The metrics that matter at Engine are the metrics that are noise at Wedge and signal at Scale. The transition is not subtle. A CPMO who is still operating with Wedge-stage qualitative metrics at Engine is missing the operating signal the company needs. A CPMO who is reaching for Scale-stage portfolio metrics before they are statistically meaningful is operating on fiction.
The metric set at Engine is built around the loop and segmented by the dimensions that matter - segment, motion, and product line where applicable.
Pipeline metrics become real at Engine for the first time. Pipeline created (in dollars and in deal count), pipeline coverage against next quarter's revenue target, pipeline by source (marketing-sourced, sales-sourced, partner-sourced, customer-sourced), and pipeline quality (measured by stage progression rates, conversion rates, and average deal velocity). The CPMO is accountable for the volume and quality of pipeline created. The CRO is accountable for its conversion. Both report to a shared coverage target. The metric set is the operational expression of that shared accountability.
Win rate metrics become reliable at Engine. Win rate against the full deal set, win rate against the qualified deal set, win rate by segment, win rate by competitor, and win rate by deal size. The most useful version of this metric is win rate by segment by competitor - a small grid that exposes exactly where the company is winning and losing, against whom, and in which segments. This grid is the input to almost every Frame stage decision. Companies that are losing consistently to a specific competitor in a specific segment have a positioning problem, a product gap, or a pricing problem in that intersection - and the grid is what makes the diagnosis possible.
CAC and payback period metrics become defensible at Engine, with the caveat that they have to be computed correctly. CAC computed as marketing spend divided by new customers is wrong. CAC computed as fully-loaded sales and marketing spend divided by new logo annualized contract value is approximately right and is the version that the CFO and the board will compare against industry benchmarks. Payback period - the months of revenue required to recover CAC - is the more meaningful metric for capital efficiency, and the one that determines how aggressively the company can invest in growth. CPMOs at Engine who do not have a defensible CAC and payback computation are CPMOs who will lose every meaningful capital allocation argument.
Net revenue retention becomes the central health metric of the company at Engine, even if the conventional benchmarks suggest it is more important at Scale. NRR captures the compounding behavior of the customer base - the rate at which existing customers are growing, churning, or shrinking - and is the leading indicator of whether the loop is genuinely compounding. NRR above 110% in B2B Enterprise indicates a healthy expansion motion. NRR below 100% indicates that churn is exceeding expansion, which is a structural problem that no amount of new pipeline can compensate for indefinitely.
Activation and time-to-value metrics, which became real at Wedge, become more refined at Engine. The activation milestone, defined empirically at Wedge, gets segmented by ICP and motion. Time-to-value gets measured both in days and in correlation with retention, with the empirical relationship between faster time-to-value and higher one-year retention becoming the basis for product investment decisions.
Three categories of metrics are dangerous at Engine because they look like signal but are mostly noise. Vanity brand metrics - impressions, reach, social engagement - should not be reported to the executive team because they do not connect to any decision the executive team will make. Lead volume metrics, divorced from quality, produce sales teams that complain about lead quality and marketing teams that complain about sales execution; the metric that matters is qualified pipeline created, not leads generated. Single-month variance metrics produce reports that fluctuate dramatically based on deal timing, vacation schedules, and accounting treatments; the rolling three-month or trailing twelve-month version is almost always the correct measurement.
**
8.5 Traps: Hiring a VP Marketing Who Wants a Brand Refresh**
Five traps catch Engine-stage companies more often than any others.
The first is the title-of-this-section trap: hiring a senior marketing leader whose first instinct is to spend the first six months on a brand refresh, a website redesign, and a positioning exercise that produces beautiful artifacts and no measurable change in pipeline. The hire is well-credentialed. The work is genuinely good. The timing is wrong. At Engine, the company needs a marketing leader who can build a demand creation system, instrument it, and produce predictable pipeline. Brand refresh work is real and necessary, but it is a Scale or Platform stage discipline. A CPMO who lets a new VP of Marketing spend two quarters on a rebrand at Engine has lost two quarters of pipeline construction.
The second is the over-elaboration of the org structure. Engine-stage CPMOs, often hired from larger companies, import the org structures they knew at Scale or Platform. They build matrix structures, dotted-line reporting, regional segments, and product-line specializations before the company has the volume to support them. The result is an org that looks impressive on paper and produces less actual work than a leaner structure would. The discipline at Engine is to build the smallest org that can do the work, not the largest org that the budget supports.
The third is the segmentation that becomes a script. The company's ICP, defined at Wedge with care, becomes a segmentation model that is increasingly precise and increasingly disconnected from reality. New customer segments emerge from the market that do not fit the model. Existing segments begin to behave differently. The model, treated as authoritative, prevents the company from seeing the changes. The CPMO's job is to maintain the segmentation as a living instrument - updated quarterly, tested against win/loss data, and refined when the evidence demands it. Most Engine-stage companies treat segmentation as a one-time project rather than a continuous discipline.
The fourth is the launch as theater. As the launch system matures, there is a temptation to use launches as marketing performance - large announcements, polished events, executive keynotes - for products and features that do not warrant the investment. The launches consume disproportionate executive attention, produce content that is not rooted in real customer need, and train the company to value the launch event over the product impact. The CPMO function's job is to enforce launch tier discipline - most launches are tier-three or tier-four, run by the team without executive involvement; only the small number of genuinely strategic launches earn the full launch system.
The fifth is the hardest one, and the one most Engine-stage CPMOs do not see until it has done its damage: optimizing the funnel while the category shifts. The company's loop is now operating well. Pipeline is predictable. Win rates are stable. NRR is healthy. The metrics all look good. Meanwhile, the underlying market is changing - buyers are evaluating differently, a new competitor is reframing the category, the technology underpinning the product is being disrupted by an AI-native alternative. The CPMO, head down in operational excellence, optimizes the existing engine while the market that engine was built to serve is being redefined. By the time the change becomes visible in the metrics, the lead time required to respond is longer than the time available. This trap is so consequential that Chapter 9, on the Scale stage, returns to it as one of the central failures of that stage. It begins at Engine.
The Engine stage ends when the company has built a system that produces predictable pipeline at predictable cost, delivers product reliably across multiple segments, and retains and expands customers without heroic individual effort. When that condition is met - typically somewhere between $20M and $30M ARR, though the operating reality matters more than the revenue figure - the company is ready to enter the Scale stage, where the question shifts from "can we build the engine" to "can we compound it." That is the subject of the next chapter, and the stage at which the CPMO role is hardest, where most CPMOs fail, and where the structural decisions made at Engine determine whether the company breaks through or stalls.

Read the full book: Zenodo · Amazon · Google Play · LeanPub · Gumroad

Chapter 7. Stage 2 - Wedge

Ali Sadhik Shaik — Sat, 04 Jul 2026 01:14:28 +0000

7.0 What Wedge Means
The Wedge stage begins when a company has found something real - a specific customer segment, a specific problem, and design partners who use the product because it works rather than because they like the founder - and ends when that something has been made repeatable. Most B2B Enterprise companies enter this stage with somewhere between three and seven design partners and exit it somewhere between $1M and $3M in annual recurring revenue. The exit is not defined by the revenue number. It is defined by whether the company can win deals predictably in a defined segment without the founder personally driving every step.
Two things are true at Wedge that were not true at Founding. The first is that the product works for someone - a specific someone, in a specific context, doing a specific job. The second is that the company has not yet proved this can be repeated. A wedge that produced three customers might produce three hundred. It might also produce no more than three. The Wedge stage is the period during which that question is answered.
This is the stage at which the CPMO function is most often hired into the company for the first time, or the stage at which a founder begins to hand off pieces of the loop to specialists. The decisions made in this transition shape the company more than the founder usually realizes. A premature handoff produces a company whose loop is run by people who do not yet know the wedge well enough. A delayed handoff produces a founder who becomes a bottleneck and a company that cannot move past the wedge it has found.
The ambition of this chapter is to describe the work clearly enough that founders can see what they are actually doing, and aspirants can see why the seat at this stage is so different from the one at Engine or Scale.

7.1 The CPMO's Job at the Wedge Stage
The job at Wedge is to make the wedge repeatable.
Repeatability is a precise concept and worth being explicit about. A wedge is repeatable when the company can describe, in writing, who buys the product, why they buy it, what triggers the buying decision, what they are replacing or comparing it against, what objections appear in every deal, and what the buying process looks like - and when that description holds up across at least eight to twelve customers who were not personally sold by the founder. Anything less than that is a pattern in formation. Anything more is the beginning of an engine.
The CPMO function at Wedge is doing four things in parallel, with most of the founder's time still consumed by the first two and progressively more delegated to others as the stage matures.
The first is converting the design partner relationships into paying customers and reference accounts. Design partners are not customers in the conventional sense. They have favorable pricing, often-substantial influence over the roadmap, and a relationship that is closer to co-development than to vendor-buyer. The work at Wedge is to convert this relationship into something more conventional - actual contracts at actual prices, actual usage at scale within the customer's organization, and actual willingness to serve as a reference for new prospects. This conversion is delicate. Push too hard and the relationship sours. Don't push at all and the company never learns whether the wedge can support a real economic transaction.
The second is finding the next ten to twenty customers who are similar enough to the design partners to validate the pattern but different enough to test its boundaries. The discipline here is precise. The CPMO function at Wedge is not trying to find any customer. It is trying to find customers who match the emerging ICP closely enough that their experience will sharpen the pattern, while occasionally testing customers slightly outside the pattern to discover where the boundaries actually lie. Companies that take any customer who will buy at this stage produce muddy data and an ICP that they cannot articulate at the end of the year. Companies that are too narrow produce a pattern that is real but too small to scale.
The third is beginning to externalize the founder's tacit knowledge into systems that other people can run. The way the founder described the product in a sales conversation has to become a sales narrative. The objections the founder learned to handle have to become a competitive battle card. The patterns the founder identified in customer conversations have to become a written ICP description. The reasoning behind product priorities has to become a strategy document that engineers can refer to when the founder is not in the room. None of this externalization is glamorous, and most founders avoid it because it slows them down. The deferral is a mistake. A company that cannot scale beyond the founder's head is a company that cannot scale.
The fourth is the first deliberate construction of the loop's other stages. At Founding, Sense was the dominant stage; everything else was reactive. At Wedge, Frame begins to matter - positioning has to be tested in language, not just embodied in product decisions. Shape begins to matter - the roadmap has to commit to a defensible set of priorities, not just respond to whatever the latest design partner asked for. Ship begins to matter - releases have to be coordinated with messaging, even when the messaging is just a single email to ten customers. Scale does not yet matter, because there is nothing to scale. But the other four stages are now operating, and the CPMO function is the discipline of making sure none of them are neglected while the founder's attention naturally pulls toward whichever one is currently on fire.

7.2 Team Shape: First PMM, First Growth Hire
The team at Wedge grows from the Founding-stage cluster of three to six people into a more recognizable B2B Enterprise org of ten to fifteen people. The shape of that growth matters more than the size.
The first hire that earns its place at Wedge, almost without exception, is a senior product marketer. Not a marketing leader, not a brand executive, not a demand generation manager. A specific kind of operator: someone who can sit with the founder, absorb the wedge through repeated customer conversations, and translate it into language the rest of the company and the early market can use. This person is part-writer, part-strategist, part-research synthesizer. They do not run a team. They do not manage campaigns. They produce the artifacts the company needs to scale beyond the founder's voice - the positioning document, the sales narrative, the website that finally reflects what the company actually does, the first real launch announcement, the customer interview synthesis that feeds the next product decision.
The second hire, often within six months of the first, is a growth-flavored operator. The right shape depends on the dominant motion. If the company has any meaningful self-serve or product-led component, this person is a growth product manager who owns activation, in-product conversion, and the early lifecycle surfaces. If the company is purely sales-led, this person is a demand generation manager who owns the early pipeline-building experiments - paid acquisition, content distribution, event presence in the segments that matter. In either case, the hire is operational rather than strategic. They execute against the patterns the founder and the product marketer have identified, and they begin to instrument the loop for measurement.
The first product manager hire - distinct from the founder - typically happens late in Wedge, often only as the company approaches Engine. This is later than most founders expect and earlier than most CPMO playbooks recommend. The reason is that product strategy at Wedge is still founder work. A product manager hired before the wedge is repeatable will either follow the founder's direction without adding value or override the founder's direction without enough context. The right time to hire the first PM is when the founder has externalized enough of their tacit knowledge that the PM has something concrete to operate against.
A few hires that are tempting and almost always premature: a head of marketing, a sales leader (as opposed to the first salespeople), a customer success manager (as opposed to the founder doing customer success directly), a designer leader (as opposed to a strong individual designer), and any kind of operations or analytics leader. Each of these may earn their place at Engine. None of them earn their place at Wedge.
The reporting structure remains close to flat. The product marketer and the growth operator both report to the founder, as do the engineers, the designer, and the first salespeople. The founder is still the integration point of the loop. A company at Wedge that has built a layer of management between the founder and the people doing the work has either grown faster than the wedge supports or has hired senior people whose seniority is not matched to the work. The flatness is not an accident. It is the structural condition under which the founder can still run the loop personally.

7.3 Cadence: Weekly Learning Loops
The operating rhythm at Wedge shifts from the daily cadence of Founding to a weekly cadence that introduces, for the first time, the early elements of an executive operating system.
The center of the Wedge cadence is the weekly leadership review. Two to three hours, typically on a Monday or Friday, attended by the founder and the small leadership team. The agenda is consistent across weeks, which is how it earns its place in the calendar. The review covers the week's customer signal - wins, losses, churn, design partner feedback, support themes. It covers the week's product progress - what shipped, what is shipping next, what is blocked. It covers the week's pipeline - every active prospect, every late-stage deal, every relationship at risk. And it covers the week's experiments - what was tested, what was learned, what the next experiment is.
The Sense memo, which existed informally at Founding, becomes a deliberate artifact at Wedge. It is updated weekly, typically by the founder or the product marketer with the founder's review. It captures the company's current view of the wedge - who the customer is, what the pattern looks like, where the boundaries are, what is still uncertain. The memo is the spine of the weekly review. Decisions that are not consistent with the memo either change the decision or change the memo. Memos that have not been updated for a month are a signal that the company has stopped learning, which is a worse signal at Wedge than at any other stage.
A monthly cadence begins to appear, mostly in the form of a board update or investor letter. This is not yet a monthly business review in the conventional sense - the data is too thin for that - but it is a discipline of writing down what changed in the month, what was learned, and what the next month's bets are. The act of writing the monthly note forces a synthesis that the weekly cadence does not. Founders who treat the monthly note as a chore rather than a thinking instrument are missing the point.
Quarterly planning is now real but lightweight. A typical Wedge-stage quarterly plan is a three-to-five-page document that names the two or three things the company is committing to in the quarter and ignores everything else. The document is ruthless about what is not being done. The temptation at Wedge is to commit to every promising thing the founder has noticed in the past three months. The discipline is to commit to the small number of things that will most directly test or extend the wedge.
There is no annual plan worth the name at Wedge. The company is still moving too fast and learning too much. There is, however, a single annual artifact: a written description, at the end of each year, of what the company learned about its wedge that it did not know at the start of the year. This document, written for the founder more than for any external audience, is the most important artifact a Wedge-stage company produces, and the one most often skipped.

7.4 Metrics: Time-to-Value and Activation
The metrics that matter at Wedge are different from Founding, sharper than Founding's qualitative signals, but still narrower than the conventional B2B SaaS metric set that takes over at Engine.
The first metric that begins to carry real signal is time-to-value. How long does it take, from the moment a new customer signs a contract or starts a trial, until they experience meaningful value from the product? The measurement is concrete: typically the time from sign-up to first material use, where "material use" is defined specifically for the product's job. For a security product, it might be the first scan completed. For a developer tool, the first deployment. For a workflow product, the first task completed end-to-end. Time-to-value at Wedge is usually long, often weeks, and the reduction of that time is one of the most consequential things the CPMO function can do, because it directly determines whether the customer becomes a reference, an expansion, or a churn risk.
The second is activation rate. What percentage of new accounts reach a defined activation milestone - a state of the customer's usage that strongly correlates with eventual retention and expansion? The activation milestone has to be defined empirically rather than aspirationally. Most Wedge-stage companies define it wrong on the first attempt and refine it over the following two quarters. The right activation milestone is the smallest set of customer behaviors that, observed in the first thirty to sixty days, predicts retention and expansion at the one-year mark. Until that empirical definition exists, activation is a placeholder rather than a metric.
The third is qualitative retention signal. Conventional retention metrics - gross dollar retention, net dollar retention, logo retention - exist at Wedge but are not yet reliable, because the customer base is too small and the time horizon is too short. The signal that matters is more textured: are the customers who signed twelve months ago still actively using the product, expanding their usage, recommending it to peers, and renewing without negotiation drama? A Wedge-stage company with eight customers, six of whom are deeply engaged and two of whom have churned, is healthier than one with twenty customers, fifteen of whom are barely using the product. The aggregate metric does not capture the difference. The qualitative signal does.
The fourth is the first leading indicator of pipeline quality, which is the rate at which sales conversations result in second meetings. This is a more honest metric at Wedge than win rate, which is too volatile when deal volume is low. A Wedge-stage company whose sales conversations advance to a second meeting more than half the time has positioning that resonates. A company whose conversations rarely produce second meetings has a positioning problem that no amount of sales training will fix.
The fifth, and the most important Wedge-stage metric, is the cycle time of the loop itself. How long does it take from a customer signal - a churn, a request, a competitive loss - to a meaningful response? At Founding, this was instant; the founder heard the signal and acted on it. At Wedge, with more people in the org and more customers in the base, the cycle time can quietly stretch from days to weeks to months. A Wedge-stage company whose loop cycle time has stretched beyond two weeks has begun to lose the velocity that made it competitive in the first place. The CPMO function's job is to keep the cycle time short, even as the company grows past the size where short cycle time is automatic.
Conventional B2B SaaS metrics - CAC, payback, magic number, sales efficiency - exist at Wedge but should be treated with skepticism. They are computed on a small enough base that they fluctuate dramatically quarter to quarter, and a CPMO who reports them to a board with confidence at this stage is producing fiction. They become real at Engine. At Wedge, they are noise wearing the clothes of signal.

7.5 Traps: Confusing Revenue with PMF
Five traps catch Wedge-stage companies more often than any others.
The first is the most famous one, and the one most B2B Enterprise founders fall into despite knowing it: confusing revenue with product-market fit. A Wedge-stage company can produce real revenue from customers who are not actually fit for the product - customers who bought because of the founder's relationship, because the price was discounted aggressively, because the buyer was budget-flush at the end of a fiscal year, or because the customer's actual job was so urgent that they bought the closest available solution without caring whether it was right. Revenue from these customers is real money. It is also a false signal of fit. The diagnostic is whether the customer is using the product, expanding within it, and willing to renew at full price. If any of those is missing, the revenue is not telling the truth about fit.
The second is segment drift. Founders, under pressure to show traction, take customers who are not in the target segment because the customers are willing to buy. Each individual exception is defensible. The cumulative effect is destructive. A company that started targeting mid-market financial services and now has customers in healthcare, retail, government, and small business has not expanded its addressable market. It has muddied its wedge. The CPMO function's job is to maintain segment discipline against the natural pull of available revenue, and to say no to customers who are not in the segment even when the revenue is welcome.
The third is the premature scale of go-to-market. A company that has eight reference customers in a wedge does not yet need a sales team of fifteen, a marketing budget of three million dollars, or a partnership program. The temptation appears as soon as the first round of growth-stage capital is raised, and the temptation is reinforced by the board, the new VP of Sales, and the consultant who wrote the GTM plan. The trap is real: a Wedge-stage company that scales its GTM before the wedge is repeatable will burn the capital, blame the people, and find itself eighteen months later with a much larger team, a much smaller bank account, and a wedge that is no clearer than it was before.
The fourth is the founder who hires too many senior people too fast in an attempt to compensate for their own exhaustion. The hires are expensive, often impressive, and individually competent. They are also wrong for the stage. A Wedge-stage company that has hired a CMO, a CRO, a Head of Customer Success, and a VP of Engineering before $5M ARR has built an executive layer that is bigger than the operating reality of the company. The executives will spend their first year fighting each other for unclear scope, building plans against an undefined ICP, and producing the appearance of organization while the underlying work - finding the wedge's repeatability - slows down.
The fifth is the most quietly damaging: the founder who refuses to externalize their tacit knowledge. The work of writing down the ICP, the positioning, the sales narrative, the product strategy, and the operating principles is tedious. Founders avoid it by saying they will get to it later, by delegating it to a junior hire who cannot do it without their input, or by claiming the tacit knowledge cannot be externalized. The claim is wrong. The tacit knowledge can be externalized; it just requires sustained effort the founder does not want to give. The company that does not externalize cannot scale, because the loop continues to run inside one person's head, and that person becomes the bottleneck on every decision, every hire, every customer conversation, every product call.
The Wedge stage ends when the company can describe its ICP in writing, sell to that ICP repeatedly without the founder in every conversation, and produce a predictable pipeline within a defined segment. When that condition is met - typically somewhere between $3M and $5M ARR, though the revenue number is a marker rather than a definition - the company is ready to enter the Engine stage, where the question shifts from "can we make this repeatable" to "can we build a real engine around it." That is the subject of the next chapter, and the stage at which most aspirants will first encounter the company they hope to lead.

Read the full book: Zenodo · Amazon · Google Play · LeanPub · Gumroad

Chapter 6. Stage 1 - Founding

Ali Sadhik Shaik — Tue, 23 Jun 2026 13:47:26 +0000

6.0 What Founding Means
The Founding stage is the period from the company's first line of code to its first signed design partners - the small group of customers willing to commit time, attention, and ideally money to a product that does not yet fully exist. It is the stage before product-market fit is even a meaningful question, because the product is still a hypothesis. Most companies are in this stage for somewhere between six and twenty-four months. A few burn through it in three. A few stay in it for four years and call themselves something else.
There is no CPMO seat at Founding. The role exists, but the title does not. The function - the integration of insight, framing, product, launch, and growth into a single accountable loop - sits inside the founder's head, alongside everything else they are accountable for. Almost without exception in B2B Enterprise, the founder is the first CPMO. They are also the first CTO, often the first CRO, and frequently the first CFO. The hat is invisible because every hat is invisible. But the loop is real, and the loop is being run, and how it is run at this stage shapes everything the company becomes.
This chapter is written for two audiences. First, founders who are running a CPMO function without recognizing it, and who will benefit from a clearer mental model of what they are doing. Second, aspirants - the PMs and PMMs reading this playbook because they want a CPMO seat eventually - who will benefit from understanding why the role looks the way it does at later stages. The Founding stage is where the patterns are set, and many of the dysfunctions visible at Engine and Scale are inheritances from Founding-stage choices that were never revisited.

6.1 The CPMO's Job at the Founding Stage
The job at Founding is to find the wedge.
A wedge is a specific, narrow, defensible point of entry into a market - a particular customer with a particular problem who is willing to pay for a particular solution, where the solution is small enough to be built by a small team and important enough to be worth the customer's switching cost. Every successful B2B Enterprise company started with a wedge. Stripe started with developers who needed a simpler payment API. Atlassian started with software teams who needed a lightweight bug tracker. Figma started with designers who needed real-time collaboration in the browser. The wedge is not the eventual market. It is the entry point that lets a company earn the right to expand later.
The CPMO function at Founding is the work of finding that wedge - and, equally important, refusing to act as if it has been found before it has been. Most founders, especially technical ones, have a strong opinion about the market they are entering before they have the right to that opinion. The opinion is a hypothesis. The Founding stage is the period during which the hypothesis is tested against reality, in tight cycles, until the wedge is found or the company is killed.
Concretely, the CPMO function at Founding is doing five things in parallel, every week, with overlapping outputs.
The first is sustained customer discovery - typically thirty to fifty hours of customer conversations per quarter, conducted personally by the founder, with detailed notes and a discipline of looking for disconfirming evidence rather than validation. The discipline that distinguishes a useful Founding-stage discovery practice from a useless one is whether the founder is genuinely trying to find out they are wrong. Most founders are trying to find out they are right, and accumulate confirming evidence while filtering out the disconfirming kind. The wedge does not appear until the disconfirming evidence is taken seriously.
The second is design partner cultivation. A design partner is not a customer in the traditional sense. They are a co-conspirator - a buyer at a target company who has committed to using the product in its early form, providing feedback, and tolerating the bugs and gaps in exchange for influence over the roadmap and, often, favorable pricing. The CPMO function is responsible for identifying the right design partners (not the easiest, not the most enthusiastic, but the most representative of the eventual ICP) and structuring the relationship. Three to seven design partners is the typical right number. Fewer than three and the signal is too narrow. More than seven and the founder cannot maintain the personal relationships the stage requires.
The third is narrative drafting. The company's story is not yet ready for the market, but it is ready to be written, tested in conversations, and revised. Most founders avoid this work or delegate it to a future marketing hire. This is the wrong move. The narrative drafted at Founding becomes the foundation of every later positioning iteration. A founder who cannot articulate, in three sentences, what their company exists to do and why anyone should care, will produce a company whose Frame stage is permanently weak. The drafting is the work. The output is just a side effect.
The fourth is rapid product iteration tied to design partner usage. The product is being built, and at this stage every meaningful feature decision is also a positioning decision. What goes into the product expresses who the company is for, what it values, and what it is not. The CPMO function is the discipline of refusing to let the product drift toward whatever the engineering team finds most interesting and instead anchoring it to the design partner signal, even when that signal is uncomfortable.
The fifth is founder-led selling. Until the wedge is found, no salesperson can be hired. The reason is simple: there is nothing to sell yet, only something to learn. The founder sells, not because they are the best closer, but because the act of selling is the act of testing the wedge against the market in the highest-fidelity way possible. The objections heard in a sales conversation are signal that no other research method produces. The CPMO function at Founding is in the meeting, taking the objections seriously, and feeding them back into the product, the positioning, and the next conversation.

6.2 Team Shape: Founder as CPMO
The team at Founding is small enough to fit around a single table - typically two to six people in product and adjacent functions, with the founder personally running the CPMO loop and the rest of the team executing slices of it.
The standard composition in a well-run B2B Enterprise Founding-stage team includes the founder, one or two engineers (or a co-founder CTO with a small team), one designer (often part-time or contract), and possibly a product-marketing-flavored hire who functions as a writer, content producer, and customer interview synthesizer. There is no dedicated marketing hire. There is no growth hire. There is no product manager other than the founder. There is no analyst, no ops person, no salesperson, no customer success manager. Every additional hire at this stage is a luxury that should be deferred until the wedge is more clearly defined.
The most consequential team-shape question at Founding is whether to bring in a head of marketing or a senior product marketer. The temptation is real. The founder is exhausted. The narrative work is hard. The website looks bad. The content engine is non-existent. A senior marketing hire would, in theory, take all of this off the founder's plate.
This is the wrong move at Founding, and one of the most common Founding-stage mistakes in B2B Enterprise. The wedge has not been found. A senior marketer hired into a company without a wedge will spend their first six months attempting to manufacture demand for a product that does not yet have a market, will produce campaigns that miss because the positioning is still wrong, and will either burn out or be fired. The hiring decision will look like it failed. In fact, the underlying decision - to hire a senior executor before the strategic foundation existed - was the failure.
The right hire at Founding, if any senior marketing-flavored hire is made, is a writer. A person who can produce founder-quality narrative content, capture customer interview synthesis in publishable form, and serve as a sparring partner for the founder's own thinking. This is not a marketing leader. It is a craft hire. It is the right shape for the stage.
The reporting structure is flat. Everyone reports to the founder, including the design contractor who works two days a week. The founder is the integration point. There is no layer of management between the founder and the people doing the work, and there should not be. A Founding-stage company that has built management layers has either grown faster than its wedge can support or has hired senior people for status reasons rather than work reasons.

6.3 Cadence: Daily Discovery
The operating rhythm at Founding is daily, and the unit of cadence is the customer conversation rather than the planning cycle.
There is no quarterly planning at Founding because the company does not yet know enough to plan a quarter. There is no monthly business review because the metrics that would populate it do not yet exist. There is a weekly all-hands, but it is a stand-up, not a review - fifteen to thirty minutes, focused on what was learned in the past week and what will be tested in the next.
The CPMO function at Founding operates on a daily cadence with a weekly synthesis. The daily cadence is the discipline of customer conversations, design partner check-ins, and product iteration decisions. The weekly synthesis is the working document - usually called the Sense memo, in the language of Chapter 4, though most founders do not give it a name - that captures what was learned in the week and what it implies for the wedge. The Sense memo is the founder's instrument. It is not shared publicly. It is shared with co-founders and the small leadership team. It is the basis on which every other decision gets made.
The most common cadence failure at Founding is the absence of synthesis. Founders run from conversation to conversation, accumulating signal in their head without ever writing it down. The signal degrades. Patterns that would be visible in writing remain invisible in memory. Decisions get made on the most recent conversation rather than on the accumulated body of evidence. The discipline of the weekly synthesis is the difference between Founding-stage companies that find their wedge in a year and those that take three.
The annual cadence at Founding is barely real. There is no annual plan worth writing, because the company will pivot at least twice in the year. There is, however, a single annual question worth holding: at the end of this year, what will we have learned that would let us either commit to scaling or kill the company. That question is the Founding stage's only annual artifact.

6.4 Metrics: Conviction Over Numbers
The metrics that matter at Founding are not the metrics that will matter at any later stage, and the most common metrics failure at Founding is the premature import of later-stage metrics.
A Founding-stage company that is reporting MRR, CAC, payback period, and pipeline coverage is reporting fiction. The numbers exist. They are not yet meaningful. The customer base is too small, the time horizon is too short, and the variance is too high for any of these metrics to carry signal. A founder who is optimizing for them is optimizing for noise.
The metrics that genuinely matter at Founding are different in kind, not just in quantity. They are qualitative or near-qualitative, and they measure conviction rather than performance.
The first is the strength of design partner engagement. Are the design partners using the product weekly without prompting? Are they introducing the product to colleagues without being asked? Are they paying for it, even at a discount, even when they could have negotiated for free access? These are signals of genuine engagement, and they cannot be faked or accidentally produced.
The second is the quality of the customer interview synthesis. After thirty to fifty conversations, what patterns are visible? Are the patterns sharp or fuzzy? Are different customers describing the same problem in similar language, or in different language? When the language converges, the wedge is approaching. When it remains divergent after dozens of conversations, the wedge has not been found.
The third is the founder's own conviction trajectory. This is a strange metric to write down, but it is real. The founder's conviction in the company's wedge should be growing over time as the evidence accumulates. If conviction is decreasing, that is a signal - either of something wrong with the wedge or of something wrong with the founder's relationship to the work. If conviction is high but not connected to evidence, that is a different signal, and a more dangerous one.
The fourth is the rate of disconfirmation. How often is the founder updating their hypothesis based on customer evidence? A founder who has not changed their mind about anything significant in the past month is either right about everything (rare) or not actually testing their hypotheses (common). The discipline of measuring disconfirmation rate is the Founding-stage discipline.
Numerical metrics start to matter at the end of the Founding stage, not the beginning. The triggers that signal the company is ready to leave Founding and enter Wedge - covered in the next chapter - include the first signed paid contracts, the first repeat reference within a target segment, and the first time a sales conversation closes without the founder personally driving every step. Until those triggers are hit, conviction and learning rate are the metrics that matter, and dashboards are a distraction.

6.5 Traps: Hiring Marketing Too Early
Five traps catch Founding-stage companies frequently enough that they are worth naming directly.
The first is the trap already discussed: hiring a senior marketing leader before the wedge is found. The hire is well-intentioned, the resume is impressive, the references are strong, and within nine months the company has spent meaningful capital on campaigns that did not work, on a brand exercise that did not land, and on a leader who is now blamed for failing to produce demand for a product that did not yet have a market. The trap is not the hire. The trap is the timing.
The second is premature scaling of the engineering team. A Founding-stage company that has fifteen engineers but only three design partners is structurally over-built. The engineers will produce features, the features will get shipped, and the design partners will not use them. The CPMO function - the discipline of anchoring engineering output to design partner signal - fails when the engineering team is too large for the design partner base to absorb.
The third is the founder who delegates the customer conversations. The conversations are not delegable. The signal that comes from a conversation conducted by someone other than the founder is degraded by an order of magnitude, because the founder is the only person who can hear an objection and make a real-time decision about whether it implies a product change, a positioning change, or a customer-fit change. Founders who delegate this work - usually to a junior product manager or a research contractor - produce companies whose Sense stage is permanently impaired.
The fourth is the design partner who becomes a customization customer. The design partner relationship is a co-conspiracy structured around a generalizable product. When a design partner starts requesting features that are specific to their workflow, their environment, or their organizational structure, and the company starts shipping those features, the company has stopped building a product and started doing consulting at a discount. The signal is not whether the design partner is happy - they are usually thrilled - but whether the features being shipped will benefit anyone other than them. The CPMO function at Founding is the discipline of saying no to the design partner often enough that the product remains generalizable.
The fifth is the founder who confuses personal credibility with company traction. A well-known founder can sell a wedge that does not exist, because the buyer is buying the founder rather than the product. Early revenue can flow on the strength of the founder's reputation, the founder's previous company, or the founder's personal network - and that revenue can mask the absence of a wedge for months or years. The diagnostic is brutal but necessary: would this customer buy from a stranger with the same product? If the answer is no, the wedge has not been found, regardless of what the revenue looks like.
The Founding stage ends when the wedge is real - when the company has identified a specific customer segment, a specific problem, and a specific willingness to pay that holds up across multiple buyers who do not personally know the founder, who use the product because it solves their problem, and who refer it to others because it works. When that condition is met, the company is ready to enter the Wedge stage, where the question shifts from "can we find a wedge" to "can we build a repeatable motion around it." That is the subject of the next chapter.

Chapter 5. The Four Cross-Cutting Layers

Ali Sadhik Shaik — Sat, 20 Jun 2026 14:11:53 +0000

5.0 Why Cross-Cutting Layers Exist
The CPMO Loop describes the what of the role: the five stages a CPMO is accountable for running as a single integrated system. It does not, on its own, describe the how. Two CPMOs running the same loop, in companies at the same stage, can produce radically different outcomes - not because one understands the loop better, but because the underlying disciplines through which the loop is operated are different.
There are four such disciplines. They are not stages of the loop. They are layers that run through every stage, shaping how that stage gets operated in practice. They are the operating system on which the loop runs.
The four layers are organizational design, metrics and economics, the AI stack, and governance and trust. They are introduced briefly here and developed in dedicated chapters in Part IV (Chapters 12 through 17). The purpose of this chapter is to make the layers visible to the reader before the stage-by-stage playbook begins, so that when a stage chapter says "the cadence at this stage requires this org shape with these metrics," the reader has the conceptual scaffolding to know what each of those layers is and why it matters.
The four layers share a single property worth naming. None of them can be delegated by the CPMO to someone else without breaking the role. The CPMO can have an org design partner, a finance partner, an AI lead, and a trust officer working alongside them. The CPMO cannot delegate the integration of the four layers to anyone else, because the integration is the seat. Just as the loop cannot be coordinated by a project manager standing between functional leaders, the layers cannot be administered by a chief of staff standing between functional disciplines. The CPMO holds them in their own head, or they don't get held.

5.1 Organizational Design
The first cross-cutting layer is the question of what people exist underneath the CPMO, how they are organized, what they are accountable for, and how they coordinate.
Organizational design is the layer most CPMOs think about most often and operate worst. The reason is that org design is usually treated as an HR question - a matter of titles, reporting lines, and headcount approval - rather than as a strategic instrument. In a CPMO context, org design is strategic. The shape of the team determines which parts of the loop get attention and which atrophy. A team heavy on product management and light on product marketing will produce a company whose Frame stage is permanently underweight. A team heavy on demand generation and light on positioning will produce a company that runs out of pipeline quality even while pipeline volume looks healthy. The org chart is the loop made flesh.
The cross-cutting question for the CPMO is not "what is the right org chart" - there is no single right answer - but "is the current org chart matched to the stage of the company and the cadence the loop requires." A founding-stage org should be flat and integrated. A scale-stage org should have specialized leaders for each major stage of the loop. A platform-stage org should have portfolio structure. A reinvention-stage org has to run two operating models at once. Each stage has different correct answers, and each transition between stages requires deliberate redesign.
A few specific patterns are worth flagging now and developed in Chapter 12.
The reporting line of product marketing is the single most consequential org design choice the CPMO makes. Product marketing reporting into product produces tighter strategic alignment but weaker market translation. Product marketing reporting into marketing produces stronger campaign integration but weaker product strategy. Product marketing reporting directly to the CPMO - the configuration most modern B2B Enterprise CPMOs converge on - produces the cleanest loop integration but requires the CPMO to give it real time. There is no costless option.
The placement of growth - meaning the function responsible for activation, expansion, and product-led acquisition surfaces - is the second most consequential choice. Growth as a separate function reporting to the CPMO is the cleanest design when product-led motion is meaningful. Growth embedded within product management is cleaner organizationally but tends to under-invest in marketing surfaces. Growth as a unit reporting to the CRO, which some companies still attempt, almost always fails because it puts the loop between two executives who do not have shared accountability.
The placement of operations - revenue ops, marketing ops, product ops, and the analytics functions - is the third. Centralized ops produces consistency and slower execution. Embedded ops produces faster execution and inconsistent reporting. The right answer depends on stage. Most CPMOs rebuild the ops structure at least once during their tenure, usually around the Engine-to-Scale transition.

5.2 Metrics and Economics
The second cross-cutting layer is the question of what the CPMO measures, what the CPMO reports, and what economic logic the CPMO is responsible for.
Metrics is the layer most often confused with the layer it should serve. Companies generate metrics easily. Dashboards are cheap. The hard work is not producing metrics but producing the right small set of metrics that genuinely express the health of the loop, can be tracked over time, and connect to the economic logic the CFO cares about.
The cross-cutting question for the CPMO is whether the metrics being reported actually drive decisions. Most B2B Enterprise companies have a metrics problem that goes in one of two directions. Either they have too many metrics - board decks with thirty KPIs that no one can hold in their head, weekly reviews where no metric ever moves enough to matter, dashboards that everyone consults and no one uses - or they have too few of the right metrics, with revenue and headcount on display while the leading indicators of customer health, positioning effectiveness, and loop velocity are invisible.
The CPMO's discipline is to maintain three layers of metrics simultaneously. The first layer is the small set of company-level outcome metrics that the executive team and board agree on - typically five to seven numbers that capture the state of the business. The second is the operating metric set that the CPMO uses internally to manage the function - typically fifteen to twenty-five metrics across the loop, segmented by stage. The third is the experimental metric set that captures what is being tested in any given quarter - typically five to ten metrics that exist for a defined window and then either graduate to the operating set or get retired.
The economics layer is the part most CPMOs from product backgrounds underinvest in. Pricing economics, packaging economics, CAC and payback, gross margin per segment, contribution margin per product line, the unit economics of every growth loop - these are not finance concerns the CPMO consults on. They are CPMO concerns the CFO partners on. A CPMO who cannot defend the unit economics of the loops they are running is a CPMO who will lose every meaningful budget conversation, regardless of how well the qualitative narrative is developed.
The AI-era shift in metrics is the rise of leading indicators that did not exist five years ago: signal from LLM-mediated buyer research, content surface visibility in model-generated summaries, in-product activation patterns at AI-native cadence, and the velocity of the loop itself measured in days rather than quarters. Most companies are still measuring 2020 metrics in a 2026 market. The CPMO who modernizes the metric set is operating with a clearer view of the business than peers who have not.

5.3 The AI Stack
The third cross-cutting layer is the question of what AI capability the CPMO builds into the operation of the loop itself, and what the company's own use of AI looks like across the function.
AI as a cross-cutting layer is a 2026 reality that did not exist as an organizational question in any meaningful sense before 2023. It is now unavoidable. Every stage of the loop has been or is being rebuilt with AI as a primary input rather than a marginal tool. Sense is being rebuilt by tools that synthesize customer interviews and surface telemetry patterns. Frame is being rebuilt by tools that test positioning against simulated buyer responses and that generate content variations at a cadence no human team can match. Shape is being rebuilt by tools that compress prototyping and pricing simulation. Ship is being rebuilt by tools that produce launch assets, sales enablement, and documentation in parallel rather than sequence. Scale is being rebuilt by tools that personalize lifecycle communication and surface expansion signals in real time.
The cross-cutting question for the CPMO is not "are we using AI" - every company is using AI - but "is our AI use coherent enough to compound, or is it a scattered set of tools each function adopted independently." The default state in most B2B Enterprise companies is the scattered state. Product is using one set of tools. Marketing is using a different set. Growth is using a third. None of them share data, none of them share prompts, none of them share evaluation criteria, and none of them produce institutional learning that transfers from one team to another.
The CPMO's discipline in this layer is to treat the AI stack as a capability map rather than a tool list. The capability map asks, for each stage of the loop, what the function needs to be able to do, whether to build that capability internally or buy it, and how to govern it. The output is not a procurement decision. It is a capability strategy that compounds. Companies that build a coherent AI stack across the loop will operate at a cadence that competitors with scattered tooling cannot match. Companies that treat AI procurement as a line-item decision will accumulate cost without compounding capability.
The build-buy-govern decision, which Chapter 15 develops in detail, is the central CPMO call in this layer. Build means investing in a capability the company will use as a strategic differentiator, where the value of customization or proprietary data justifies the cost. Buy means using a vendor capability where the function is undifferentiated and vendor velocity exceeds internal velocity. Govern means establishing the policies, evaluation standards, and risk controls under which any AI capability - built or bought - is deployed in the loop. Most CPMOs are over-invested in buy, under-invested in build, and under-invested in govern. The right balance varies by stage and by the strategic role AI plays in the company's product itself.

5.4 Governance and Trust
The fourth cross-cutting layer is the question of how the CPMO maintains the conditions of trust under which the company can operate, sell, and grow.
Governance and trust as a CPMO concern is a recent development and one that many CPMOs from operating backgrounds resist, because it sounds adjacent to legal, security, or compliance functions that they correctly believe they should not own. The resistance is misplaced. Governance and trust as a CPMO layer is not about owning legal or security. It is about recognizing that in a B2B Enterprise market where 80% of buyers now apply stricter AI evaluation requirements through their security and legal teams, where data handling and AI usage are first-order purchase criteria, and where a single trust failure can collapse a year of category-building work, trust is no longer a downstream concern. It is a primary input to whether the loop functions at all.
The cross-cutting question for the CPMO is whether the company's positioning, product, and growth surfaces are operating on a foundation of trust that the buyer, the regulator, and the public can verify. This is not a marketing claim. It is a structural condition. A company that says it is trustworthy without behaving trustworthy in its product, its data handling, its AI use, and its public communication is a company whose narrative will collapse the moment a single failure exposes the gap. In B2B Enterprise, the gap between claim and reality is now exposed faster than ever before, because every customer, every regulator, and every analyst has access to the same LLM-mediated synthesis tools that compress investigation from weeks to minutes.
The CPMO's discipline in this layer is to treat trust as a commercial asset rather than a compliance burden. This means investing in the surfaces that make the company's trustworthiness verifiable: transparent documentation, public security postures, clear AI usage policies, honest pricing, customer references that hold up under scrutiny, and analyst relationships built on substance rather than briefings. Companies that build these assets deliberately produce a competitive moat. Companies that treat trust as something for the legal team to defend produce a fragile narrative that can be unwound by any motivated competitor or journalist with an LLM and an afternoon.
The governance layer - the policies, standards, and review mechanisms that ensure the company's actions match its claims - is the operational expression of trust. The CPMO does not draft these policies alone; the CFO, General Counsel, Chief Information Security Officer, and Chief Trust Officer (where the role exists) are primary partners. But the CPMO is the executive whose loop the policies most directly shape, and the executive whose narrative most directly depends on whether the policies hold. The integration cannot sit anywhere else.

5.5 How the Layers Compound
The four layers are introduced separately, but they do not operate separately. A weakness in any one layer cascades into the others, and a strength in any one layer amplifies the others.
A company with strong organizational design but weak metrics will produce a loop that runs in the wrong direction efficiently. A company with strong metrics but weak organizational design will produce a loop that everyone can see but no one can move. A company with strong AI stack but weak governance will produce a loop that scales rapidly into a trust failure. A company with strong governance but weak AI stack will produce a loop that is trustworthy and slow, while AI-native competitors run faster and erode the market.
The CPMO's job is not to optimize each layer independently. It is to maintain coherent investment across all four, with the balance shifting as the company stage shifts. At Founding, organizational design barely matters because the team is so small; metrics barely matter because the signal is qualitative; the AI stack matters as a velocity multiplier; governance matters as a foundation that will be expensive to retrofit. At Scale, all four layers are operating at full intensity simultaneously, and the CPMO who has not built deliberate practice across all four will be exposed in whichever layer they neglected. At Reinvention, the layers have to be partially rebuilt while the existing business continues to run.
The stage chapters that follow - Chapters 6 through 11 - describe how the loop and the layers interact at each stage. The cross-cutting chapters in Part IV - Chapters 12 through 17 - develop each layer in operational depth. This chapter is the bridge between the framework and the practice.
The next chapter begins the stage-by-stage playbook, starting with the Founding stage, where the CPMO function is usually held by the founder and the loop is being run for the first time.

Chapter 4. The CPMO Loop

Ali Sadhik Shaik — Sat, 20 Jun 2026 13:47:59 +0000

4.0 Why a Loop, and Why These Five Stages
Every operating playbook needs a spine. A spine is the framework the rest of the document references - the shared mental model that lets a reader connect a chapter on cadence to a chapter on metrics to a chapter on org design without losing the thread. The spine of this playbook is the CPMO Loop: a five-stage operating cycle that the CPMO is accountable for running, end to end, at the cadence the market demands.
The choice of a loop rather than a funnel matters and is worth being explicit about.
The funnel is the dominant inherited framework in B2B marketing. Most operators trained in the last twenty years have it embedded in their thinking: awareness at the top, leads in the middle, deals at the bottom, with each stage owned by a different function and graded on its own conversion rate. The funnel is useful as a diagnostic instrument for a single transaction. It is not useful as a description of how a modern B2B Enterprise business actually grows.
The case against funnels as a strategic spine has been made well by others - most influentially by Brian Balfour and the Reforge team in their 2018 essay "Growth Loops are the New Funnels," which has become the canonical reference for product-led companies. The argument is structural: funnels operate in one direction, with inputs at the top and outputs at the bottom, and no inherent mechanism for the output to feed back into the input. They produce linear growth, they create functional silos because each layer is owned by a different team, and they break down when product, marketing, and revenue are interlinked rather than sequential. Growth loops, by contrast, are closed systems where every output reinvests as an input, producing compounding growth and forcing the operator to think about product, channels, and monetization as a single integrated system.
The CPMO Loop adopts this logic and extends it. Where most growth-loop frameworks describe how a single product grows once it exists, the CPMO Loop describes the full insight-to-revenue cycle the CPMO is accountable for - including the strategic stages that precede the growth surfaces and the learning systems that close the cycle back to the start. It is a strategy loop, not a growth loop. The growth loops live inside it, in the Scale stage, where they belong.
The five stages are Sense, Frame, Shape, Ship, and Scale. They are not a process diagram. They are a continuous operating discipline that runs at multiple cadences simultaneously - some at the speed of a quarterly planning cycle, some at the speed of a single product release, some at the speed of a daily customer conversation. The CPMO is the only executive in the company whose remit covers all five stages, and that is precisely why the role exists.

4.1 Sense - Reading the Market and the Product
The first stage is the discipline of seeing reality clearly, before anyone else in the executive team does.
The Sense stage is the work of consolidating signal from every surface where it appears: customer conversations, win/loss data, product telemetry, competitive moves, analyst commentary, community discussion, sales pipeline patterns, support tickets, churn interviews, partner feedback, public discourse on LinkedIn and developer forums, and increasingly the synthesized summaries that LLMs produce when buyers research the category. In a conventional org, each of these signals lives in a different function. Product research has the customer interviews. Sales ops has the win/loss data. Marketing analytics has the campaign performance. Engineering has the telemetry. Customer Success has the churn signal. The CPMO's job is to consolidate all of this into a single coherent view of what is actually happening, and to do it on a cadence faster than the underlying market is changing.
This is harder than it sounds, and most CPMOs underinvest in it for the first six to twelve months in the seat. The temptation is to delegate Sense to a research function or an analytics team and consume their summaries. This is structurally wrong. Sense cannot be delegated, because the integration of signals - the recognition that a pattern in churn data lines up with a shift in win/loss commentary that lines up with what a competitor said at a conference last week - is the work itself. A research team can produce reports. Only the executive holding the full loop can produce the synthesis.
The output of the Sense stage is not a dashboard. It is a written, regularly updated document - typically a living memo of three to ten pages - that captures the CPMO's current view of the market, the customer, and the product. The best CPMOs I have observed update this document weekly. It feeds every other stage of the loop. When positioning gets tested in Frame, the test is against the Sense memo. When strategy is set in Shape, the strategy is downstream of the Sense memo. When launches are debated in Ship, the launch logic is grounded in the Sense memo. The discipline of writing it forces the synthesis. The discipline of updating it forces the cadence.
The AI-era shift in this stage is not subtle. Tools that synthesize customer interviews, surface patterns in product telemetry, monitor competitor releases, and track LLM-mediated discourse about the category have collapsed the cost of signal gathering by an order of magnitude. The constraint is no longer access to data. The constraint is interpretation, and interpretation is where the human CPMO earns the seat.

4.2 Frame - Positioning and Narrative
The second stage is the discipline of converting the Sense view into language that the rest of the company, the market, and the buyer can hold in their heads.
Frame is positioning and narrative work, but the right way to think about it is not as marketing output. It is the upstream decision that determines what the company is selling, who it is selling to, and why the buyer should care. Positioning is the short version: the answer to "what is this and why does it matter, in this quarter, to this segment." Narrative is the long version: the category point of view, the executive worldview, the manifesto that anchors a year or more of company communication.
The reason Frame is a CPMO accountability rather than a marketing accountability is that positioning is upstream of every other decision in the business. The product roadmap should reflect the positioning. The pricing should reflect the positioning. The hiring should reflect the positioning. The partnerships should reflect the positioning. When positioning lives downstream of product strategy - as it does in companies where the CPO ships the product and then hands it to a CMO to figure out how to sell it - the company is structurally incoherent. The CPMO's job is to set positioning early enough that everything else aligns to it, not late enough that it becomes a translation exercise.
The most useful test of Frame is the one most companies fail. If a sample of ten employees from across the company - a senior engineer, a customer success manager, a salesperson, a finance analyst, a designer - are asked to describe what the company sells and why it matters, do their answers converge or diverge? In a company where Frame is working, the answers converge. The vocabulary may differ but the substance is the same. In a company where Frame is broken, the answers diverge in ways the executive team is usually unaware of, because the executive team has never tested it.
The narrative layer of Frame is where the long-term positioning of the company is built. This includes the executive points of view that go on LinkedIn, the keynote content delivered at industry conferences, the analyst briefings that shape Magic Quadrant placement, the open-source releases that signal technical credibility, and the public writing that establishes category leadership. In an LLM-mediated buying environment, the narrative layer is no longer optional - it is the primary input to how models will describe the company when buyers ask. A company without a coherent narrative is a company that LLMs will describe in the language of its competitors.

4.3 Shape - Strategy, Roadmap, Packaging
The third stage is where Sense and Frame become committed strategic decisions about what the company will build, ship, and charge for.
Shape is the territory most often described in conventional product strategy literature, and it is also the stage most CPMOs are most comfortable in, because most CPMOs come from product backgrounds. The risk is that the comfort produces over-investment. A CPMO who spends seventy percent of their time in Shape and thirty percent across the other four stages is running a CPO function, not a CPMO function. The discipline is to do Shape well enough and then move on.
Shape includes the product roadmap, the platform strategy, the portfolio decisions, the pricing architecture, the packaging strategy, and the partnership map. It is the stage where the company says yes to some things and no to others, and where those decisions become legible to the rest of the organization in the form of plans that can be executed.
The most important Shape decision in a B2B Enterprise company is almost always pricing, and pricing is also the decision most often made badly. The reason is structural: in companies without a CPMO, pricing tends to live in either product (where it is treated as a feature decision) or in sales (where it is treated as a deal decision). It is neither. Pricing is a strategy decision that expresses positioning and shapes which customers the company will and will not be able to win. The CPMO owns it because no other executive has the full vantage point.
The packaging decision - how the product is divided into editions, tiers, modules, or add-ons - is downstream of pricing and equally consequential. It is the structure the buyer sees, the structure the salesperson sells, and the structure the customer experiences over time. Packaging changes are quietly some of the most expensive decisions a B2B Enterprise company makes, because they propagate through every customer contract, every billing system, every onboarding flow, and every renewal conversation. The CPMO's discipline is to make packaging decisions rarely, deliberately, and with the full loop in view.

4.4 Ship - Launch as a System
The fourth stage is where strategy meets execution, and where most B2B Enterprise companies leak the most value.
Ship is the discipline of moving a product change, a positioning shift, or a packaging update into the market in a coordinated way. In the conventional org, Ship is what companies call "launch," and it is treated as a marketing event - the moment when the product, which has been built, is announced. This framing is wrong in two ways. It treats the launch as a discrete event rather than a continuous system, and it treats marketing as the owner rather than the executor.
A modern launch in B2B Enterprise is a system that simultaneously updates the product itself, the documentation, the website, the pricing page, the LLM-legible content surfaces, the analyst briefings, the customer communications, the sales enablement materials, the partner channel, the community, and the public point of view. None of these can be sequential. All of them have to land within a narrow window - typically days, not weeks - because the buyer is consuming all of them in parallel and any delay between them creates dissonance that competitors will exploit.
The CPMO's job in Ship is to own the launch system, not to run any individual launch. The system includes the launch tier definitions (what counts as a tier-one launch versus a tier-three launch, with corresponding investment), the launch playbook (the standard operating procedure that any team can run), the launch readiness criteria (what has to be true before a launch is approved), and the post-launch review discipline (the structured retrospective that feeds back into Sense). When the system is working, individual launches are handled by product marketing and product management leaders below the CPMO, with the CPMO involved only in tier-one launches and in periodic reviews of the system itself.
The AI-era shift in Ship is the compression of timelines. A launch that took six weeks of preparation in 2020 can be executed in days in 2026 with the right tooling, but only if the system is designed for that compression. Companies that try to run modern launches at conventional cadence are not just slow - they are structurally outpaced by competitors who have rebuilt their launch system for the new physics.

4.5 Scale - Compounding Loops
The fifth stage is where the conventional growth-loop literature is most useful and where the CPMO's accountability is sharpest.
Scale is the discipline of building the systems through which the existing customer base and the existing product produce more customers and more revenue without proportional new spend. In the funnel framing, this is the bottom of the funnel - retention, expansion, referral. In the loop framing, this is where the output of every other stage compounds back into the input of acquisition.
The growth loops that matter most in B2B Enterprise are different from the consumer loops most often cited. Viral referral loops, while real, are usually a smaller contributor than four other loop types. Content loops - where the company's writing, research, and points of view attract buyers who become customers who produce case studies and references that produce more buyers - are the dominant acquisition loop in B2B Enterprise. Sales loops - where deals fund more sellers who close more deals - are the operational loop that scales the revenue engine. Expansion loops - where customers grow inside the product through usage, seat expansion, or product attachment - are the most efficient revenue source in any mature B2B SaaS company. Network loops - where customers bring their counterparties, partners, or vendors into the product - are the most defensible long-term moat.
The CPMO's job in Scale is to identify which loops the company is actually running, instrument them, and decide which to invest in. This is rarely obvious. Many B2B Enterprise companies believe they are running a content loop when they are in fact running a paid acquisition loop with a content veneer. Many believe they have a viral loop when they have a referral incentive that does not actually compound. The discipline of Scale is the discipline of being honest about which loops are real and which are theater.
The output of Scale feeds back into Sense. The customers acquired through the loops are signal for the next iteration of the Sense memo. The expansion patterns are signal for the next Shape decision. The content that worked is signal for the next Frame iteration. The launches that landed best are signal for the next Ship system update. The loop closes, and the cycle starts again at a higher level.

4.6 Why It Is a Loop, Not a Funnel
The structural argument for the loop framing is best made by contrast.
A funnel-based CPMO would think of the role as a coordination function across stages owned by different people. Marketing runs the top, product runs the middle, sales runs the bottom, customer success runs the post-sale. The CPMO's job, in this framing, is to make sure the handoffs work. This is the addition fallacy from Chapter 3 in operating form - and it is why companies that adopt the title without rethinking the operating model produce CPMOs who behave like glorified project managers across functions they do not actually own.
A loop-based CPMO thinks of the role as the single accountability for an integrated system. The five stages are not handoffs. They are the same continuous discipline operating at different cadences, all of them in the CPMO's head at the same time. Sense is happening every day, in real time, as customer conversations and product telemetry and competitive signal arrive. Frame is happening every quarter, as positioning is tested and refined. Shape is happening every planning cycle, as roadmap and packaging are committed. Ship is happening every launch, with a system that compresses the cadence to match the build cycle. Scale is happening continuously, as the loops compound.
The CPMO is not coordinating across these stages. The CPMO is running them as one system. The org chart underneath supports the system - product management leaders run pieces of Shape and Ship, product marketing leaders run pieces of Frame and Ship, growth leaders run pieces of Scale, research leaders run pieces of Sense - but the integration is not delegated. It cannot be. The integration is the role.
The five stages are not chronological. They run in parallel, at different cadences, with the CPMO holding all of them in mind at the same time. A new customer conversation in the morning updates Sense. A board meeting in the afternoon tests Frame. A pricing decision the next day commits Shape. A product release the next week executes Ship. The loops compounding underneath, every day, are Scale. There is no top of the funnel and no bottom. There is one integrated system with one accountable executive.
This is why the loop is the spine of the playbook. Every stage chapter that follows - every chapter about how the CPMO operates at Founding, Wedge, Engine, Scale, Platform, and Reinvention - references the same five stages, with the emphasis shifting as the company stage shifts. Every cross-cutting chapter - on org design, metrics, executive operating system, AI stack, crisis, governance - addresses how that discipline shows up across the loop. The loop is not a deliverable. It is the operating model.
The next chapter introduces the four cross-cutting layers - organizational design, metrics, AI stack, and governance - that run through every stage of the loop and shape how it is operated in practice.

Chapter 3. Why CPO + CMO CPMO

Ali Sadhik Shaik — Sat, 20 Jun 2026 13:44:44 +0000

3.1 The Addition Fallacy
The most expensive mistake B2B Enterprise companies make when they decide they need a CPMO is to look at their existing CPO and CMO job descriptions, staple them together, and post the combined document as a single role. The thinking goes something like this: we have a product leader, we have a marketing leader, the work between them is poorly coordinated, so we will hire one person to do both jobs and the coordination problem will go away. The math seems intuitive. The math is wrong.
Adding two senior roles together does not produce a senior role of double the size. It produces a role that is structurally impossible - a job that requires the time, attention, and operational depth of two full-time executives in the body of one. The companies that try this discover the failure mode quickly. Either the executive defaults to the function they came from and the other half atrophies, or they try to do both and burn out within eighteen months. In either case the company has paid CPMO compensation for half a CPO or half a CMO, and the underlying coordination problem is still there.
The deeper error in the addition framing is that it misunderstands what a CPMO actually does. A CPMO is not a person who does product work in the morning and marketing work in the afternoon. A CPMO is a person who runs a single integrated function - the insight-to-revenue loop - that requires fewer total people and fewer total decisions than the sum of a separate product organization and a separate marketing organization. Done well, the role is not larger than a CPO plus a CMO. It is smaller, because the integration eliminates a meaningful percentage of the coordination overhead that a divided structure produces.
The right way to think about it is not addition but substitution. The CPMO replaces a coordination interface with a unified accountability. The work that used to be done in the friction between two functions - the launch briefs that took six weeks because product and marketing disagreed on positioning, the pricing debates that escalated to the CEO because the CPO and CMO had different views on packaging, the analyst briefings that were rewritten three times because the product narrative and the corporate narrative did not align - that work mostly disappears. Not because it is no longer needed, but because the disagreements that produced it are now resolved inside one head.
This is why the addition fallacy is not just an HR error. It is a strategic error. A company that posts a job description titled "Chief Product and Marketing Officer" and lists every responsibility from a CPO job description followed by every responsibility from a CMO job description has signaled to every credible candidate that the company has not understood the role it is hiring for. The best CPMO candidates will not apply. The role will be filled by someone who interpreted the job description literally, which is precisely the wrong person for the seat.

3.2 Three Signs You Need a CPMO, Not Two Leaders
Not every B2B Enterprise company needs a CPMO. The role makes sense in some contexts and is actively destructive in others. Three signals, when they appear together, indicate that a company has crossed the threshold where a CPMO is the right answer rather than two strong functional leaders working in close partnership.
The first signal is product-led discovery. If a meaningful portion of your customer base - not all of it, but a portion large enough to influence company strategy - is discovering, evaluating, and adopting your product without significant sales involvement, the conventional product/marketing division is already broken in your company. The product itself is doing marketing's job. The pricing page is doing the demo's job. The empty state of the dashboard is doing the salesperson's job. In this context, having a CPO who optimizes the product and a CMO who runs campaigns is structurally inefficient - both executives are working on the same surface from different angles, and neither has authority over the whole. The CPMO is not a luxury here. It is the structural fix.
This pattern is not limited to obvious PLG companies. Many B2B Enterprise companies that consider themselves sales-led have, on closer examination, twenty or thirty percent of their pipeline arriving through self-serve channels, free tiers, developer adoption, or product-influenced expansion. The signal is not the dominant motion; it is whether a meaningful portion of revenue is being shaped by product surfaces rather than sales motions. When that portion crosses some threshold - usually around twenty percent of new logo or expansion revenue - the CPMO question becomes live.
The second signal is AI-native cadence. If your engineering team is now shipping meaningful product changes in days or weeks rather than quarters, and your competitors are doing the same, the marketing function cannot keep up at conventional cadence. The launch system has to operate at the same speed as the product system, which means the two systems have to be designed together and run by the same person. Companies where the CPO is shipping every two weeks and the CMO is planning campaigns six weeks out have a structural mismatch that no amount of cross-functional ritual will fix. The CPMO exists to compress the cadence to a single rhythm.
This signal is the one most companies under-detect. They notice that launches are slow, that messaging lags the product, that the website is always six features behind reality, but they treat these as execution problems rather than structural problems. They hire more product marketers, add more launch reviews, build more shared documents. The dysfunction reduces but does not disappear, because the underlying cadence mismatch is not a process problem. It is an org chart problem.
The third signal is buyer behavior that has moved upstream of sales. If your buyers are arriving at sales conversations already convinced - having evaluated your product through documentation, peer reviews, LLM-mediated research, and community signal before any seller engagement - the marketing function is no longer running a top-of-funnel awareness motion. It is running the entire pre-sales evaluation. And the content that drives that evaluation is not really marketing content. It is documentation, technical writing, security postures, integration guides, pricing logic, and product narrative - all of which are product surfaces as much as marketing surfaces. The CPMO exists to own this hybrid territory as a single domain rather than a contested one.
When all three signals are present, the CPMO is the right call. When only one is present, the company can usually make a strong CPO and a strong CMO partnership work, with the CEO acting as the integration point. When none of them are present - which is rare in modern B2B Enterprise but does occur in long-cycle, deeply consultative enterprise sales - the CPMO is a solution looking for a problem.

3.3 Three Signs You Do Not
The inverse case is just as important. Three patterns suggest a company is reaching for a CPMO when it should be reaching for something else.
The first is the coordination panic. A CEO has a CPO and a CMO who do not get along. Launches are messy. Strategy slides do not match. The CEO is exhausted from refereeing. The temptation is to merge the two seats and let one person sort it out. This is almost always the wrong move. The dysfunction is usually a symptom of unclear strategy at the CEO level, weak operating cadence, or one of the two executives being the wrong person for the role. Hiring a CPMO does not solve any of these. It often makes them worse, because now the failure of strategy or cadence is concentrated in a single replaceable person rather than diffused across a leadership team. If you are considering a CPMO because your CPO and CMO are fighting, the right question is not "should we merge the roles" but "do we have the right people in the roles, and is the strategy clear enough that two senior leaders should be able to align."
The second is the budget compression motivation. A company under cost pressure looks at two senior salaries and considers whether one CPMO at 1.5x the cost would replace two executives at 2x the cost. This logic is mathematically appealing and operationally disastrous. The CPMO role works when it is filled by an unusual operator with a rare skill profile. It does not work as a cost-saving exercise. A CPMO hired for budget reasons rather than strategic reasons will be set up to fail by the same finance pressure that produced the role - they will not get the team, the runway, or the authority they need to make the integration actually work. The result is a more expensive failure than running with two leaders would have been.
The third is the title aspiration trap. Some companies create a CPMO role because a senior internal executive has earned a promotion and "Chief Product Officer" or "Chief Marketing Officer" alone feels insufficient. The combined title becomes a retention tool rather than a strategic decision. This is the most quietly damaging version of the mistake, because it can persist for years before the dysfunction becomes visible. The role exists on paper. The executive has the title. But the company has not actually integrated the functions, the operating model has not changed, and the CPMO is in practice running whichever side of the role they are most comfortable with while the other side runs on autopilot. The seat is occupied but not operating.
The honest test is to ask whether the company would create the role if the candidate did not exist. If the answer is no - if the CPMO title is being created to retain a specific person rather than to solve a specific structural problem - the role will not function as designed regardless of who occupies it.

3.4 The Quiet Variant: When the Title Does Not Match the Job
There is a fourth pattern worth naming, because it is the most common version of the CPMO role in the wild and it complicates the picture. Many companies have a CPMO in operating reality without having one in title. The CPO has quietly absorbed product marketing, growth, and sometimes brand. Or the CMO has quietly absorbed product strategy, packaging, and pricing. Or a Chief Growth Officer or Chief Commercial Officer has been given authority over both product and marketing without anyone calling it a CPMO seat.
These are real CPMO roles, even when the title is something else. The substance - single accountability for the insight-to-revenue loop - is what matters. The title is a marker, not the thing itself.
For aspirants reading this playbook, this matters in a specific way. The path to a CPMO seat in 2026 often does not run through a job posting that says "CPMO." It runs through a CPO role that is offered with marketing in the scope, or a CMO role that is offered with product strategy attached, or a Chief Growth Officer role at a company that has decided to call the seat something else. Recognizing these as CPMO roles, even when the title is different, is part of the pattern recognition that gets a person to the seat in the first place.
For sitting executives reading this playbook, the implication is different. If you are a CPO whose remit has expanded to include marketing, or a CMO whose remit has expanded to include product strategy, you are already a CPMO in operating substance. The question is whether your operating model has caught up to your remit, or whether you are running the new role with the habits of the old one. Most quiet CPMOs are still running the function they came from with the other function bolted on. The playbook from here forward is largely about the gap between those two states.

3.5 The Test That Matters
A simpler version of all of the above. There is a single diagnostic question that distinguishes companies that need a CPMO from companies that do not, and a single diagnostic question that distinguishes a real CPMO role from a labeled one.
The first question, for the company: can the build-and-sell loop in this business operate at the cadence the market demands, with two separate executives running it through coordination? If the answer is yes, two leaders is the right structure. If the answer is no, the integration has to be structural, and the CPMO is the structural answer.
The second question, for the role: does this executive have single accountability for the conditions under which the company creates demand, ships product, and converts both into revenue - or are they sharing that accountability with another peer through a coordination mechanism? If single accountability is real, the role is real. If accountability is shared through coordination, the role is a label.
The two questions together filter most of the noise out of the CPMO conversation. They distinguish the companies that need the role from the ones that are reaching for it for the wrong reasons. They distinguish the executives who are actually doing the job from the ones who carry the title. And they give aspirants a way to evaluate any opportunity that uses the CPMO label - by asking, before accepting the role, whether the structural conditions for the seat to function are actually present in the company that is offering it.

Chapter 2. What a CPMO Actually Owns

Ali Sadhik Shaik — Tue, 16 Jun 2026 13:19:03 +0000

The CPMO role attracts a particular kind of confusion. Half the people defining it stretch it too wide, assuming the title means everything that touches product or marketing. The other half draw it too narrow, treating it as a renamed CPO with a marketing team underneath. Both errors produce the same result: a role that fails within eighteen months, not because the person was wrong, but because the seat was never defined.
This chapter draws the boundary. It names what the CPMO actually owns, what stays with the CEO, what stays with the CRO, what the two share, and how the cross-executive decision rights resolve in writing. The reader who internalizes the framing in this chapter will be able to walk into any CPMO conversation - interview, board review, peer disagreement, executive offsite - with a clear answer to the question of where the role begins and ends.
2.1 The Five Accountabilities
The most common mistake in defining the CPMO role is to draw the territory by adding the CPO's responsibilities to the CMO's responsibilities and calling the sum CPMO. That is not the job. The job is narrower in some places, broader in others, and entirely different in a few critical ones.
A CPMO in a B2B Enterprise company owns five accountabilities. Each is non-negotiable. None of them can be delegated to a peer without breaking the loop. Together, they define the seat.
The first is market and customer insight. The CPMO is the company's primary instrument for understanding what is actually happening in the market - not the dashboard view, but the textured, contradictory, signal-from-noise view. This includes ICP definition, segmentation, win/loss analysis, competitive intelligence, and the discipline of staying close enough to real customers that the executive team is never the last to know when something has changed. In most companies this work is fragmented across product research, marketing analytics, and sales operations. The CPMO consolidates it and is accountable for the synthesis.
The second is product strategy. Not roadmap execution - that stays with engineering and product management leaders below the CPMO. Strategy: what the company will build, what it will not build, what the next product will be, what the platform thesis is, how the portfolio fits together, and how packaging and pricing express the strategy. The CPMO does not write every PRD. The CPMO sets the conditions under which PRDs get written and approved.
The third is positioning and narrative. This is the highest-leverage accountability and the one most likely to be misallocated. Positioning is the answer to the question of why this company exists and why this buyer should care, in this language, this quarter. Narrative is the longer arc - the category point of view, the manifesto, the executive POVs, the analyst story, the conference keynote, the investor framing. In conventional orgs, positioning lives in product marketing and narrative lives in corporate communications. The CPMO owns both, because they are the same thing operating at different timescales.
The fourth is go-to-market execution. Demand generation, product marketing, launch operations, brand, content, community, partnerships, developer relations where applicable, and the pricing-and-packaging discipline that converts product strategy into revenue. The CPMO does not own quota. The CPMO owns everything that arrives at the salesperson's door before a deal is in the pipeline, and everything that surrounds the product after it is in the customer's hands.
The fifth is growth and lifecycle revenue. This is where the boundary with the CRO matters most, and where most CPMO definitions get sloppy. The CPMO owns the systems that drive acquisition, activation, retention, and expansion as product-and-marketing functions. Onboarding flows, in-product growth surfaces, lifecycle communications, expansion triggers, churn prevention by product means. The CPMO does not own the salesperson, the sales quota, or the renewal conversation. The CPMO owns the conditions under which those things succeed.
These five accountabilities are not aspirational. They are the minimum scope below which the role is not a CPMO. If the company is hiring an executive whose remit covers only four of the five - or who holds the title but reports through an executive who actually owns one of the five - the seat is structurally compromised before the executive arrives. The aspirant evaluating a CPMO opportunity should test the role against this list before accepting.
2.2 What Stays with the CEO
The CPMO is not a shadow CEO. Several things sit one level above the CPMO and stay there permanently. Naming them explicitly is part of the discipline, because the role attracts ambitious operators, and ambitious operators tend to overreach.
Capital allocation is a CEO and board responsibility. The CPMO proposes investment levels for product and marketing; the CEO and CFO decide. A CPMO who tries to set the company's overall capital allocation is overreaching, and it ends badly.
The company-level strategic narrative - as distinct from the product or category narrative - belongs to the CEO. The CPMO shapes it, drafts it, often writes it. But the CEO owns it in the sense of ultimate authorial voice and accountability. When the company has to explain itself to the board, the press, or its employees in a moment of strategic redefinition, that is the CEO speaking.
M&A strategy and execution sits with the CEO and CFO. The CPMO is consulted heavily on any acquisition that touches the product portfolio or the brand, and often runs the post-merger product and marketing integration. But the deal itself is not a CPMO function.
Public-company investor relations is a CEO and CFO function. The CPMO is a critical input - most growth narratives presented to investors are CPMO-shaped - but the relationship with the investor base belongs to the CEO and CFO.
Senior executive hiring at the VP level and above is a CEO decision with the executive team consulted. The CPMO recommends, the CPMO interviews, the CPMO sometimes pushes hard for or against a candidate. The final call belongs to the CEO.
These boundaries matter because the role is large enough on its own. Trying to make it larger is how CPMOs get fired. The CPMOs who succeed in the seat are the ones who treat these CEO-level decisions as inputs they shape rather than territory they claim.
2.3 What Stays with the CRO
The boundary with the Chief Revenue Officer is the single most important and most contested boundary in modern B2B Enterprise org design. Get it wrong and the executive team will spend more energy fighting itself than fighting the market.
The CRO role, as it has stabilized in B2B SaaS over the past decade, owns end-to-end accountability for revenue performance. McKinsey, in its analysis of the role across SaaS unicorns and Fortune 100 companies, frames the CRO as the executive responsible for creating a single revenue engine - from lead generation through closing the sale - with authority over sales, customer success, and revenue operations as the standard scope. In many companies, marketing also reports into the CRO, which is precisely where the CPMO question gets contested.
The clean way to draw the boundary, in a company that has both a CPMO and a CRO, is by accountability time horizon and primary instrument.
The CRO is accountable for this quarter's revenue and next quarter's pipeline. The CRO owns sales execution, sales hiring, territory design, quota setting, sales enablement delivery, deal desk, customer success, renewals, and revenue operations. The CRO's primary instruments are people - salespeople, customer success managers, and the systems that make them productive.
The CPMO is accountable for the conditions under which the CRO can succeed, and for the next several years of revenue durability. The CPMO owns the product, the positioning, the demand creation system, the brand, and the growth surfaces that make pipeline arrive and customers expand. The CPMO's primary instruments are the product itself and the systems of content, community, and category that surround it.
Two specific friction points deserve named treatment, because they show up in every CPMO and CRO relationship and they cause more dysfunction than any other issue.
The first is the pipeline question. Who owns the pipeline number? In a healthy CPMO and CRO partnership, the CPMO owns the generation of pipeline through demand creation, content, brand, partnerships, and the product itself. The CRO owns the conversion of that pipeline into revenue. Both are accountable to a shared coverage target, but the metrics they report on are different. The CPMO reports on pipeline created and pipeline quality. The CRO reports on win rate, deal velocity, and revenue closed. When this is muddled - when the CPMO is graded on revenue or the CRO is graded on top-of-funnel volume - the incentives break.
The second is the pricing decision. Pricing is one of the highest-leverage decisions a B2B Enterprise company makes, and it sits genuinely on the boundary. The CPMO owns pricing strategy - the structure, the packaging, the model, the way price expresses positioning. The CRO owns deal pricing - the discounting authority in live negotiations, the contract terms, the procurement defense. When a customer asks for a thirty percent discount, the CRO answers. When the company asks whether the enterprise tier should exist and at what price point, the CPMO answers. Confusing these two leads to either a CPMO who undermines deals in the field or a CRO who slowly degrades the price architecture into chaos.
2.4 The Genuinely Shared Surface
There is a third territory, larger than most companies acknowledge, where the CPMO and the CRO genuinely share accountability. Pretending it is owned by one or the other produces theater. The mature approach is to name the shared surface explicitly and design a joint operating mechanism for it.
The ICP. The ideal customer profile is a product strategy decision and a sales strategy decision at the same time. Drift in either direction breaks the company. The CPMO and the CRO must agree on it, in writing, every quarter.
Win/loss synthesis. The CRO's team has the data - every deal that closed and every deal that did not. The CPMO needs it to feed positioning, product strategy, and content. The synthesis is shared work, and the action items go to both organizations.
Sales enablement. The CPMO produces the strategic content - positioning, competitive battle cards, value narratives. The CRO consumes it and delivers it to the field. Both are accountable for whether it actually changes win rates. A CPMO who writes enablement the field does not use has failed. A CRO whose team will not use enablement they helped scope has also failed.
Customer Advisory Boards and reference customers. These are revenue assets and product assets simultaneously. The CRO uses them to close deals and inform expansion. The CPMO uses them to test positioning, validate roadmap, and shape narrative. Joint ownership, joint cadence.
The handoff between marketing-qualified and sales-qualified pipeline. This is where most B2B revenue engines leak. The fix is not better technology. It is a CPMO and a CRO who meet weekly, look at the same data, and agree on the rules. When the rules drift - when marketing changes the definition of a qualified lead, or when sales changes the criteria for accepting one - the leak widens and neither executive notices until quarterly numbers expose it.
The shared surface is not a sign of weak organizational design. It is a sign of mature organizational design. Two senior executives, holding joint accountability for a small number of explicit decisions, produce better outcomes than one executive holding sole accountability for a domain where two perspectives are genuinely required. The discipline is to keep the shared surface small - typically three to five decisions - and to design the operating mechanism that resolves them deliberately.
2.5 The CPMO RACI
A clean RACI is the difference between a CPMO who functions and a CPMO who is in turf war for their first eighteen months. The matrix below is the one I would lock in writing on day one of the role, in a B2B Enterprise company with a CRO peer.
The matrix is organized by decision category rather than as a single flat list, so that the structure of the role becomes visible at a glance. Six executive roles appear: the CPMO, the CRO, the CEO, the CFO, the CTO or VP of Engineering, and the General Counsel where the decision touches trust, contracts, or regulatory exposure.
The standard RACI conventions apply. A means Accountable - the single owner of the decision. R means Responsible - the executor of the work. C means Consulted - input required before the decision is made. I means Informed - told after the decision is made. Every decision row has exactly one A.
A separate section at the end of the matrix names the genuinely shared surfaces - decisions that cannot be cleanly assigned to a single accountable executive and that require a joint operating mechanism instead. These are the exception, not the rule, and naming them explicitly is part of the discipline.

Category 1: Strategy and Direction
| Decision | CPMO | CRO | CEO | CFO | CTO | GC |
|---|:---:|:---:|:---:|:---:|:---:|:---:|
| Product strategy and portfolio direction | A | C | C | I | C | I |
| Positioning and category narrative | A | C | C | I | I | I |
| Pricing strategy and packaging architecture | A | C | C | C | I | C |
| ICP definition and segmentation | A | C | C | I | I | I |
| Brand strategy and long-term investment | A | I | C | C | I | I |
| Company-level strategic narrative | C | C | A | C | I | I |
| Public and investor strategic narrative | C | I | A | C | I | C |

Category 2: Execution and Operations
| Decision | CPMO | CRO | CEO | CFO | CTO | GC |
|---|:---:|:---:|:---:|:---:|:---:|:---:|
| Demand generation and pipeline creation | A | C | I | C | I | I |
| Product roadmap execution and delivery | C | I | I | I | A | I |
| Sales execution and pipeline conversion | I | A | I | I | I | I |
| Sales enablement content and tools | A | C | I | I | I | I |
| Customer onboarding and activation | A | C | I | I | C | I |
| Customer success and renewals | C | A | I | I | I | I |
| Product-led growth and expansion surfaces | A | C | I | I | C | I |
| Analyst relations and category influence | A | C | C | I | I | I |
| Launch operations and tier discipline | A | C | I | I | C | I |

Category 3: Commercial and Financial
| Decision | CPMO | CRO | CEO | CFO | CTO | GC |
|---|:---:|:---:|:---:|:---:|:---:|:---:|
| Discount authority on live deals | C | A | I | C | I | I |
| Pricing realization and discount discipline | A | C | I | C | I | I |
| CPMO function budget allocation | A | I | C | C | I | I |
| Go-to-market budget allocation | C | A | C | C | I | I |
| Engineering investment levels | C | I | C | A | C | I |
| Total enterprise capital allocation | C | C | A | C | I | I |

Category 4: Org Design and Headcount
| Decision | CPMO | CRO | CEO | CFO | CTO | GC |
|---|:---:|:---:|:---:|:---:|:---:|:---:|
| Product and marketing org structure | A | I | C | I | I | I |
| Product and marketing headcount | A | I | C | C | I | I |
| Go-to-market org structure | I | A | C | I | I | I |
| Go-to-market headcount | I | A | C | C | I | I |
| Engineering org structure | I | I | C | I | A | I |
| Senior executive hires at VP level and above | C | C | A | C | C | I |

Category 5: Trust, Governance, and Risk
| Decision | CPMO | CRO | CEO | CFO | CTO | GC |
|---|:---:|:---:|:---:|:---:|:---:|:---:|
| Public AI usage policy | A | I | C | I | C | C |
| Customer data handling policy | C | I | C | I | C | A |
| Security posture and certifications | I | I | C | C | C | A |
| Crisis communication authority | A | C | C | I | I | C |
| Regulatory and compliance decisions | I | I | C | C | I | A |
| Contract terms and customer commitments | C | A | I | C | I | C |

The Genuinely Shared Surfaces
Three decision areas cannot be cleanly assigned to a single Accountable executive. They are genuinely shared between two senior executives, and the operating mechanism is a standing weekly or biweekly review at which the two arrive at a single answer together. If they cannot, the CEO breaks the tie. This pattern should remain rare; in most decisions, single accountability is the correct design.

The Genuinely Shared Surfaces
| Shared Decision | Joint Owners | Operating Mechanism | Tiebreaker |
|---|---|---|---:|
| ICP refinement and segment evolution | CPMO and CRO | Weekly CPMO and CRO standing meeting | CEO |
| Win/loss synthesis and competitive response | CPMO and CRO | Monthly business review with joint write-up | CEO |
| Pipeline coverage target setting | CPMO and CRO | Quarterly planning cycle | CEO |

A few notes on the matrix worth holding in mind.
The CPMO is Consulted on discount authority but not Accountable. This is the most common place where well-meaning CPMOs get into trouble. The price architecture is yours; the live deal is not. The discipline is to set the architecture clearly enough that the CRO's team rarely needs to call you, and to refuse to be the discount authority in the moment.
Engineering capacity and roadmap execution belong to the CTO or VP of Engineering, not to the CPMO. The CPMO sets the strategy and the priorities. Engineering decides how to staff against them and how to deliver them. A CPMO who tries to allocate engineers directly is doing the engineering leader's job and breaking the partnership that the role depends on. Engineering investment levels - how much the company spends on engineering in aggregate - are a CFO call with the CTO and CPMO consulted, not a CTO call alone.
The CFO sits in a Consulted role on most CPMO decisions, but three are different: pricing strategy, the CPMO function budget, and engineering investment levels. On those, the CFO is a primary partner, not a stakeholder. A CPMO who treats the CFO as a downstream approver rather than an upstream collaborator on these surfaces will lose the budget argument every annual planning cycle.
The General Counsel column is the most important addition in the matrix. In a market where buyers evaluate AI usage policies, data handling, and security posture as primary purchase criteria, the GC is no longer a downstream function. Customer data handling, regulatory decisions, and security posture sit with the GC as Accountable. The CPMO is the executive whose narrative most directly depends on these decisions, which is why the CPMO is Consulted on all of them and why the partnership between CPMO and GC is one of the most consequential cross-functional relationships in the role. CPMOs from earlier-generation training who treat the GC as a compliance support function are CPMOs whose trust posture will eventually be exposed.
The CEO appears as Accountable on four rows: the company-level strategic narrative, the public and investor narrative, total enterprise capital allocation, and senior executive hires. This is correct. These four decisions are where the CPMO and CRO converge, where the financial and product strategy interact, and where the executive team is being assembled. The CEO is the only person above them with the authority to set the frame.
The matrix is not a substitute for trust between the CPMO and the CRO. Trust is the operating system. The matrix is the documentation that makes the operating system legible when trust is being built or tested. In every CPMO transition I have seen go well, the first artifact produced - sometimes within the first thirty days - is some version of this matrix, signed by the CPMO, the CRO, the CEO, and where appropriate the GC. In every transition I have seen go badly, the matrix was either never written or written too late.
The seat is large. The territory adjacent to it is even larger. Drawing the boundary on the first day is how the CPMO buys themselves the eighteen months they will need to actually do the job.

Chapter 1. Why the CPMO Role Now

Ali Sadhik Shaik — Tue, 16 Jun 2026 13:04:44 +0000

1.1 Three Forces Collapsing the Wall
For three decades, B2B Enterprise software was built on a clean division of labor. Product was built first. Marketing dressed it up. Sales sold it. Customer Success kept it alive. Each function had its own leader, its own budget, its own quarterly rhythm, and its own definition of success. The architecture worked because the underlying physics worked: build cycles were measured in years, sales cycles in quarters, and buyers learned about software the way they learned about everything else - from analysts, from peers, from the trade press, from the vendor's own salespeople.
That architecture is now actively breaking. Three forces are collapsing the wall between product and marketing, and each one is independently sufficient to force a structural rethink. Together, they make the old org chart untenable.
The first force is product-led growth dissolving the handoff model. When the product itself is the primary acquisition surface - when a free trial converts into a paying account without a salesperson, when a developer adopts a tool on a Tuesday and brings it into a procurement conversation on a Friday - the question of where product ends and marketing begins becomes structurally meaningless. The onboarding flow is the demand-generation funnel. The empty-state of a dashboard is the value proposition. The pricing page is the product strategy. Companies that grew up under product-led growth never built the wall in the first place. The companies that did build it are now spending enormous energy trying to dismantle it without dropping anything.
The second force is AI compressing the build-to-market cycle from quarters to days. A feature that would have taken a 12-person engineering team six months to design, build, test, and launch can now be prototyped in an afternoon by a single PM with a code-generation tool. The time between "we should try this" and "customers are using it" has collapsed by an order of magnitude. The implication for org design is brutal: the old cadence of annual roadmaps reviewed quarterly, with marketing campaigns planned six weeks ahead of launch, is now slower than the underlying technology cycle. The cadence has to compress. And when cadence compresses, sequential handoffs between product and marketing leaders break - there isn't time for the relay race anymore.
The third force is the most underappreciated and the most consequential: buyers have moved their evaluation inside large language models. The data here is not subtle. According to 6sense's 2025 Buyer Experience Report, based on a survey of nearly 4,000 global B2B buyers, 94% of B2B buyers now use LLMs at some point during a software purchase. G2's March 2026 Buyer Behavior Report, surveying 1,076 B2B software decision-makers, found that 51% of buyers now begin their software research with an AI chatbot more often than with Google - up from 29% just eleven months earlier. In the same study, 69% of buyers reported choosing a different software vendor than initially planned based on AI chatbot guidance, and one in three purchased from a vendor they were not previously familiar with. The 6sense data also shows that B2B buyers complete their vendor shortlist before any seller contact in 95% of cases - and the pre-contact favorite wins the deal in 80% of cases.
Read those numbers slowly. A B2B Enterprise vendor's shortlist position, in eighty percent of cases, is decided before a single human conversation. The salesperson is not influencing the shortlist; they are inheriting it. The marketer is not generating awareness through a funnel they control; they are generating training data for models they don't. The product manager is not building a feature for a buyer who will read a datasheet; they are building a feature for a buyer whose primary research instrument is a model that has never seen the datasheet.
When all three forces hit a single company at the same time - which they do, in every modern B2B Enterprise business - the conventional CPO and CMO seats become structurally inadequate. Not because the people in them are bad. Because the seats themselves are designed for a market that no longer exists.
1.2 The End of Sequential Build-and-Sell
The single deepest assumption baked into the conventional B2B org chart is that build comes first and sell comes second. The CPO owns build. The CMO owns sell. They coordinate through quarterly business reviews and launch readouts. This works when the build cycle is long enough that marketing has time to plan against it, and when the buyer is patient enough to wait for the marketing to reach them.
Both of those conditions are gone.
In an AI-native B2B Enterprise company, the build cycle is now shorter than the marketing cycle. A team can ship a meaningful product change in two weeks. The corresponding marketing campaign - positioning, messaging, sales enablement, analyst briefing, customer comms, launch event - takes six. By the time marketing catches up, the product has shipped two more iterations and the original positioning is stale. The handoff model produces a permanent lag. And the lag is not cosmetic - it is the gap through which competitors take the narrative.
The dysfunction shows up in a specific, recognizable pattern. Engineering ships a feature. Product Marketing writes a launch brief two weeks later. Marketing executes the campaign three weeks after that. Sales is enabled a week after the campaign. Customer Success learns about it from a customer who saw the LinkedIn post. Meanwhile, the buyer has been asking ChatGPT about the feature space for the past month, and the model is citing a competitor's six-month-old blog post because that competitor wrote with LLM ingestion in mind and you didn't.
This is not a coordination problem. It is a structural problem. No amount of cross-functional standup will fix it, because the org chart itself encodes the sequence. The CPO is graded on shipping velocity; the CMO is graded on pipeline; their incentives are not actually aligned, and at the senior leadership review they are competing for budget, headcount, and CEO attention. The CEO, who is theoretically the integration point, is not operating at the cadence required to integrate them in real time. So integration falls through the cracks.
The companies that have figured this out have made a single structural move: they have collapsed the two seats into one. Sometimes the title is CPMO. Sometimes it is "Chief Growth Officer" with full P&L over product, marketing, and growth. Sometimes it is a CPO whose remit has quietly absorbed everything that used to belong to the CMO. The title varies. The substance is the same. One executive is now accountable for the full insight-to-revenue loop, with the authority to compress the cadence to match the underlying physics.
1.3 What Buyers Now Expect
The buyer-side change is worth dwelling on, because most operators are still under-reacting to it.
The conventional B2B Enterprise marketing playbook was built around what the industry research firm 6sense, tracking buyer behavior across multi-year longitudinal studies, used to call the "70/30 journey": buyers completed roughly 70% of their evaluation independently, then engaged a vendor for the final 30%. The implication was that marketing's job was to be present and persuasive during the 70%, so that the buyer arrived at the sales conversation already convinced. That model held for most of the last decade.
It no longer holds. 6sense's 2025 data shows the journey has shifted to what the firm now calls the "60/40 journey" - point of first vendor contact has moved from 69% to 61% of the buyer's journey. Buyers are contacting vendors earlier. But not because they trust them more - because they need them to validate what an LLM has already told them. The same research finds that buyers are not primarily using LLMs at the start of the journey to ask "who are the top vendors?" Instead, they use them in the middle of the journey, after they have already identified a shortlist, to compare offerings side-by-side, synthesize vendor documentation, model costs, draft RFP language, and build implementation plans.
In other words: the LLM is not replacing the salesperson. The LLM is doing something more dangerous. It is synthesizing the vendor's own documentation, comparing it against competitors, modeling its pricing, and presenting the buyer with a structured verdict - before the salesperson ever gets a chance to frame the conversation. G2's research adds another layer: roughly 8 out of 10 buyers now report stricter requirements for AI software evaluations from their internal IT security, legal, and compliance teams. The buyer is arriving at the sales conversation with a more rigorous evaluation framework than the seller often has.
For a CPMO, this rewires the job description in three concrete ways.
The product itself has to be legible to LLMs. Documentation, API references, integration guides, security postures, pricing logic - every piece of content that historically lived in a marketing collateral pipeline now also serves as training and retrieval material for the models that buyers consult. A product feature that ships without LLM-legible documentation is, in a meaningful sense, invisible. This is not a marketing concern. It is a product concern. And the person who decides where that documentation lives, what it says, and how it is structured cannot be a coordination committee. It has to be one executive who owns both surfaces.
The category narrative has to be built before the buyer asks. When the model returns a shortlist, it is drawing on whatever discourse has accumulated about the category in its training data and retrieval sources. Companies that have invested in category creation - whitepapers, conference talks, open-source releases, executive points of view, analyst relationships - show up in those answers. Companies that have not, do not. The category narrative is now a product input, not a marketing output.
The launch is no longer an event. It is a system. A modern launch in B2B Enterprise has to simultaneously update the product, the documentation, the LLM-legible content surfaces, the analyst briefings, the customer communications, the sales enablement, the partner channel, and the public point of view - all within a window short enough that competitors do not define the narrative first. No CPO and no CMO can run that system alone. The integration has to be structural.
1.4 The Seat That Did Not Exist Five Years Ago
The CPMO role, as a named seat with a stable definition, did not meaningfully exist before 2022. It is being invented in real time, in companies that are responding to the three forces above. The pattern is messy and the title is inconsistent, but the substance is converging.
The clearest documented signal of this convergence is at the operational level rather than the title level. Stripe's investment in Stripe Press - the company's publishing imprint, founded in 2017, which produces hardcover books, funds the documentation function, and treats the Stripe.com homepage as a craft object rather than a lead-generation page - is a publicly reported example of a company that has structurally refused the conventional product-marketing division. The decision to publish books, to fund developer documentation at the level of a flagship product surface, and to treat brand as a function of product taste rather than campaign output, is a CPMO-level decision made before the title existed in the market.
A second documented pattern is the rise of the "Chief Growth Officer" title with combined product and marketing authority. Public job postings and executive search reports from firms including Korn Ferry and Heidrick & Struggles have tracked an accelerating split in conventional CMO postings, with companies increasingly separating the role into a "Chief Commercial Officer" or "Chief Growth Officer" with full revenue authority on one side, and a brand or communications leader on the other - or, in the convergent variant, combining product and growth under a single executive. This is not yet a settled market. It is a transitional pattern, visible in postings rather than in textbooks.
A third signal is the elevation of Product Marketing into product rather than into marketing in modern B2B SaaS organizations. This shift, documented across multiple industry surveys including the Product Marketing Alliance's annual State of Product Marketing reports, has been gradual but consistent: the function that historically translated product into marketing language is increasingly reporting into the product organization, with pricing, packaging, and positioning decisions made jointly at the executive level rather than handed off through a launch brief.
What these patterns share is not a title. It is a recognition that the build-and-sell loop has to be run as a single system, with one executive accountable for the whole loop, and that the conventional CPO and CMO division either does not exist or is being quietly worked around.
For aspirants - the product managers and product marketing managers reading this playbook because they want the seat - the implication is direct. The CPMO role is not earned by being the best CPO and then "adding marketing." It is not earned by being the best CMO and then "adding product." It is earned by being one of the small number of operators who can think and operate across the whole loop, who can hold product strategy and category narrative in their head at the same time, and who can compress the cadence between them to match what AI-native buyers now expect.
The seat is being created in real time. The people who get it first will be the ones who see the structural shift before their companies' org charts catch up. The rest of this playbook is about how to be that person.

Read the full book: Zenodo · Amazon · Google Play · LeanPub · Gumroad

Chapter 1. Why the CPMO Role Now

Ali Sadhik Shaik — Sun, 07 Jun 2026 03:02:34 +0000

1.2 The End of Sequential Build-and-Sell
The single deepest assumption baked into the conventional B2B org chart is that build comes first and sell comes second. The CPO owns build. The CMO owns sell. They coordinate through quarterly business reviews and launch readouts. This works when the build cycle is long enough that marketing has time to plan against it, and when the buyer is patient enough to wait for the marketing to reach them.
Both of those conditions are gone.
In an AI-native B2B Enterprise company, the build cycle is now shorter than the marketing cycle. A team can ship a meaningful product change in two weeks. The corresponding marketing campaign - positioning, messaging, sales enablement, analyst briefing, customer comms, launch event - takes six. By the time marketing catches up, the product has shipped two more iterations and the original positioning is stale. The handoff model produces a permanent lag. And the lag is not cosmetic - it is the gap through which competitors take the narrative.
The dysfunction shows up in a specific, recognizable pattern. Engineering ships a feature. Product Marketing writes a launch brief two weeks later. Marketing executes the campaign three weeks after that. Sales is enabled a week after the campaign. Customer Success learns about it from a customer who saw the LinkedIn post. Meanwhile, the buyer has been asking ChatGPT about the feature space for the past month, and the model is citing a competitor's six-month-old blog post because that competitor wrote with LLM ingestion in mind and you didn't.
This is not a coordination problem. It is a structural problem. No amount of cross-functional standup will fix it, because the org chart itself encodes the sequence. The CPO is graded on shipping velocity; the CMO is graded on pipeline; their incentives are not actually aligned, and at the senior leadership review they are competing for budget, headcount, and CEO attention. The CEO, who is theoretically the integration point, is not operating at the cadence required to integrate them in real time. So integration falls through the cracks.
The companies that have figured this out have made a single structural move: they have collapsed the two seats into one. Sometimes the title is CPMO. Sometimes it is "Chief Growth Officer" with full P&L over product, marketing, and growth. Sometimes it is a CPO whose remit has quietly absorbed everything that used to belong to the CMO. The title varies. The substance is the same. One executive is now accountable for the full insight-to-revenue loop, with the authority to compress the cadence to match the underlying physics.

1.3 What Buyers Now Expect
The buyer-side change is worth dwelling on, because most operators are still under-reacting to it.
The conventional B2B Enterprise marketing playbook was built around what the industry research firm 6sense, tracking buyer behavior across multi-year longitudinal studies, used to call the "70/30 journey": buyers completed roughly 70% of their evaluation independently, then engaged a vendor for the final 30%. The implication was that marketing's job was to be present and persuasive during the 70%, so that the buyer arrived at the sales conversation already convinced. That model held for most of the last decade.
It no longer holds. 6sense's 2025 data shows the journey has shifted to what the firm now calls the "60/40 journey" - point of first vendor contact has moved from 69% to 61% of the buyer's journey. Buyers are contacting vendors earlier. But not because they trust them more - because they need them to validate what an LLM has already told them. The same research finds that buyers are not primarily using LLMs at the start of the journey to ask "who are the top vendors?" Instead, they use them in the middle of the journey, after they have already identified a shortlist, to compare offerings side-by-side, synthesize vendor documentation, model costs, draft RFP language, and build implementation plans.
In other words: the LLM is not replacing the salesperson. The LLM is doing something more dangerous. It is synthesizing the vendor's own documentation, comparing it against competitors, modeling its pricing, and presenting the buyer with a structured verdict - before the salesperson ever gets a chance to frame the conversation. G2's research adds another layer: roughly 8 out of 10 buyers now report stricter requirements for AI software evaluations from their internal IT security, legal, and compliance teams. The buyer is arriving at the sales conversation with a more rigorous evaluation framework than the seller often has.
For a CPMO, this rewires the job description in three concrete ways.
The product itself has to be legible to LLMs. Documentation, API references, integration guides, security postures, pricing logic - every piece of content that historically lived in a marketing collateral pipeline now also serves as training and retrieval material for the models that buyers consult. A product feature that ships without LLM-legible documentation is, in a meaningful sense, invisible. This is not a marketing concern. It is a product concern. And the person who decides where that documentation lives, what it says, and how it is structured cannot be a coordination committee. It has to be one executive who owns both surfaces.
The category narrative has to be built before the buyer asks. When the model returns a shortlist, it is drawing on whatever discourse has accumulated about the category in its training data and retrieval sources. Companies that have invested in category creation - whitepapers, conference talks, open-source releases, executive points of view, analyst relationships - show up in those answers. Companies that have not, do not. The category narrative is now a product input, not a marketing output.
The launch is no longer an event. It is a system. A modern launch in B2B Enterprise has to simultaneously update the product, the documentation, the LLM-legible content surfaces, the analyst briefings, the customer communications, the sales enablement, the partner channel, and the public point of view - all within a window short enough that competitors do not define the narrative first. No CPO and no CMO can run that system alone. The integration has to be structural.

1.4 The Seat That Did Not Exist Five Years Ago
The CPMO role, as a named seat with a stable definition, did not meaningfully exist before 2022. It is being invented in real time, in companies that are responding to the three forces above. The pattern is messy and the title is inconsistent, but the substance is converging.
The clearest documented signal of this convergence is at the operational level rather than the title level. Stripe's investment in Stripe Press - the company's publishing imprint, founded in 2017, which produces hardcover books, funds the documentation function, and treats the Stripe.com homepage as a craft object rather than a lead-generation page - is a publicly reported example of a company that has structurally refused the conventional product-marketing division. The decision to publish books, to fund developer documentation at the level of a flagship product surface, and to treat brand as a function of product taste rather than campaign output, is a CPMO-level decision made before the title existed in the market.
A second documented pattern is the rise of the "Chief Growth Officer" title with combined product and marketing authority. Public job postings and executive search reports from firms including Korn Ferry and Heidrick & Struggles have tracked an accelerating split in conventional CMO postings, with companies increasingly separating the role into a "Chief Commercial Officer" or "Chief Growth Officer" with full revenue authority on one side, and a brand or communications leader on the other - or, in the convergent variant, combining product and growth under a single executive. This is not yet a settled market. It is a transitional pattern, visible in postings rather than in textbooks.
A third signal is the elevation of Product Marketing into product rather than into marketing in modern B2B SaaS organizations. This shift, documented across multiple industry surveys including the Product Marketing Alliance's annual State of Product Marketing reports, has been gradual but consistent: the function that historically translated product into marketing language is increasingly reporting into the product organization, with pricing, packaging, and positioning decisions made jointly at the executive level rather than handed off through a launch brief.
What these patterns share is not a title. It is a recognition that the build-and-sell loop has to be run as a single system, with one executive accountable for the whole loop, and that the conventional CPO and CMO division either does not exist or is being quietly worked around.
For aspirants - the product managers and product marketing managers reading this playbook because they want the seat - the implication is direct. The CPMO role is not earned by being the best CPO and then "adding marketing." It is not earned by being the best CMO and then "adding product." It is earned by being one of the small number of operators who can think and operate across the whole loop, who can hold product strategy and category narrative in their head at the same time, and who can compress the cadence between them to match what AI-native buyers now expect.
The seat is being created in real time. The people who get it first will be the ones who see the structural shift before their companies' org charts catch up. The rest of this playbook is about how to be that person.

Read the full book: Zenodo · Amazon · Google Play · LeanPub · Gumroad