DEV Community: Ali Sadhik Shaik

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.

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 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