Chapter 4. The CPMO Loop

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.