8.0 What Engine Means
The Engine stage begins when a B2B Enterprise company has a repeatable wedge - a defined ICP, a sales motion that closes deals without the founder in every conversation, and a product that delivers value reliably to customers who match the pattern - and ends when the company has built a system that can compound that repeatability across multiple segments, multiple channels, and multiple product lines without the system itself becoming the constraint. Most companies enter this stage somewhere between $3M and $5M in annual recurring revenue. Most exit it somewhere between $20M and $30M. The exit is not defined by the revenue number. It is defined by whether the company has built an actual engine - a set of interlocking systems for product, marketing, sales, and customer success that produce predictable output without heroic individual effort - or has accumulated a large team running on the same founder-driven energy that worked at Wedge.
This is the stage where the CPMO seat genuinely exists for the first time, where the title appears on org charts, and where the structural challenges of the role become visible. It is also the stage where most CPMOs are first hired from outside. The founder-CPMO of the Founding and Wedge stages has either grown into the role and remains accountable for it, or has handed it to a hired executive and stepped back to focus on company-building, capital, and the other CEO functions that now demand full attention. Either path is viable. The path that does not work - the founder who claims to have hired a CPMO but continues to operate as one - produces the failure mode this chapter spends most of its energy describing.
The Engine stage is also the stage at which the loop, in the language of Chapter 4, is operating in all five stages simultaneously for the first time. Sense was the dominant stage at Founding. Frame and Shape were added at Wedge. At Engine, all five stages are active, all five have specialized leaders below the CPMO, and the integration across them is the work the CPMO is paid to do. The org chart that supports this integration is more elaborate than at any previous stage and requires deliberate design, which is the subject of Section 8.2.
8.1 The CPMO's Job at the Engine Stage
The job at Engine is to convert a repeatable wedge into a compounding system.
This phrasing is deliberate. A repeatable wedge produces predictable output as long as the conditions of the wedge hold. A compounding system produces output that grows faster than the inputs grow, because the loops described in Chapter 4 are now real and reinforcing. Repeatability is linear. Compounding is exponential. The Engine stage is the stage at which the company makes the transition from one to the other, and the CPMO is the executive accountable for whether the transition succeeds.
Concretely, the CPMO function at Engine is doing six things in parallel, with each one requiring more deliberate management than at Wedge because each one now involves a specialist leader and a team beneath them.
The first is segment expansion. The company found a wedge in one segment. The Engine stage is when the company tests whether that wedge can be extended to adjacent segments. The discipline is not to spray new segments hoping something works, but to identify the two or three segments most likely to share the same buying triggers, run controlled experiments in those segments, and either commit or retreat based on the evidence. A company that is winning consistently in mid-market financial services has natural adjacencies: mid-market insurance, financial services in larger enterprise, financial services internationally. Each adjacency is a hypothesis. Each hypothesis needs testing with the rigor of the original wedge work. The CPMO function is the discipline of running these tests with the same care the original wedge received.
The second is the construction of a real demand creation system. At Wedge, demand came from the founder's network, from a small content effort, and from the early sales team's outbound work. At Engine, demand has to come from a system - a set of interlocking content, brand, partnership, event, and product-led surfaces that produce pipeline at predictable rates without the founder. The construction of this system is the largest investment the CPMO makes at Engine, and the one most often executed badly. Most Engine-stage companies build the demand system by hiring a senior demand generation leader and asking them to produce pipeline. The CPMO function's job is to ensure the demand system is consistent with the positioning, integrated with the product surfaces, and instrumented well enough that what works can be scaled and what doesn't can be killed.
The third is pricing and packaging maturation. At Wedge, pricing was approximate, packaging was simple, and most deals were negotiated personally. At Engine, the pricing architecture has to support a sales team that can close deals without executive escalation, the packaging has to support multiple buyer profiles within the ICP, and the discount discipline has to be tight enough that the company is not slowly destroying its own price realization. This is the stage at which most B2B Enterprise companies make their first significant pricing error - usually by discounting too aggressively to win deals, which trains the sales team and the market that the list price is fictional. The CPMO function's job is to set the architecture clearly enough that discount discipline is enforceable, and to refuse to be the discount authority in live deals.
The fourth is the institutionalization of competitive intelligence. At Wedge, competitive intelligence was the founder's mental model of a small set of alternatives. At Engine, the competitive set has expanded, the competitors are responding to the company's success, and new entrants are emerging because the category is now visible. The CPMO function builds a competitive intelligence system that produces real-time signal - win/loss patterns by competitor, feature parity tracking, narrative monitoring, analyst commentary, customer perception research - and that integrates this signal into both product and positioning decisions. Most Engine-stage companies do this work badly. They produce competitive battle cards that are out of date within a quarter, win/loss reports that no one reads, and analyst briefings that are reactive rather than strategic.
The fifth is the deliberate construction of the launch system. At Wedge, every launch was a one-off run by the founder and the product marketer. At Engine, launches happen monthly or more often, span multiple product lines and segments, and require coordination across product, marketing, sales, customer success, and partner functions. The launch system - the standardized playbook for tier-one through tier-three launches, the readiness criteria, the post-launch review discipline - has to be built once and then continuously refined. A CPMO who is personally running individual launches at Engine is doing the work of someone two layers below them and producing chaos in everything they are not personally running. The work is to build the system, staff it, and let it run.
The sixth is the establishment of the executive operating cadence - the weekly, monthly, and quarterly rhythm under which the CPMO's team and the CPMO's peer relationships are managed. This is the work that separates Engine-stage CPMOs who succeed from those who survive for eighteen months and burn out. The cadence is not optional. The cadence is what makes the rest of the work tractable. Section 8.3 develops it in detail.
8.2 Team Shape: Building the First Real Org
The team at Engine grows from the lean Wedge-stage cluster of ten to fifteen people into a structured org of thirty-five to seventy. The shape of that growth is more consequential than the absolute size, and most Engine-stage CPMOs design the org wrong on the first attempt and rebuild it within eighteen months.
The standard composition of an Engine-stage CPMO org, in a B2B Enterprise company between $5M and $25M ARR, includes specialized leaders in five functions reporting to the CPMO.
A VP of Product, accountable for product management, design, and product strategy execution. This person manages the PM team that runs individual product lines or major surfaces, and is the CPMO's primary partner on roadmap, packaging, and the Shape stage of the loop. The relationship between the CPMO and the VP of Product is the most consequential reporting relationship in the org. When it works, the CPMO can think about strategy and integration while the VP of Product runs execution. When it does not, the CPMO ends up doing both jobs, the VP of Product becomes a coordinator, and the company under-invests in either strategy or execution.
A VP of Product Marketing, accountable for positioning, launch execution, sales enablement, competitive intelligence, and the translation of product into market. This is the role most often hired wrong at Engine. The temptation is to hire a brand marketer or a content leader for this seat. The right hire is an operator who has personally run product marketing at a B2B Enterprise company through a similar stage transition, who understands the discipline of positioning as a strategic instrument, and who can manage relationships with both the product team and the sales team without becoming captured by either.
A VP of Demand Generation or VP of Growth, accountable for the systems that produce pipeline. The title and the scope vary by the dominant motion. In a sales-led company, this person owns demand gen - paid acquisition, content distribution, events, partnerships, and the early funnel. In a product-led company, this person is more often called Head of Growth and owns activation, in-product conversion, and lifecycle expansion. In hybrid companies, both functions exist with different leaders. The CPMO's job is to ensure the function is matched to the dominant motion and that its leader has authority over the surfaces that actually produce pipeline.
A Head of Brand, Content, or Communications, accountable for the long-term narrative work, the public point of view, the analyst relationships, and the content surfaces that compound over time. This is the function most often under-resourced at Engine, because its outputs do not show up in this quarter's pipeline number. The under-investment is a strategic error that the company will pay for at Scale, when the absence of accumulated brand and category equity will leave the company indistinguishable from cheaper or faster competitors.
A Head of Operations, accountable for the data, systems, and analytics that support the rest of the function. This person owns the marketing automation stack, the product analytics infrastructure, the reporting cadence, and the experimentation discipline. In smaller Engine-stage companies, this role is held by a strong individual contributor rather than a leader with a team. In larger ones, the role splits into separate marketing ops, product ops, and analytics functions.
Below these five leaders sit the teams that do the actual work. Product managers, designers, product marketing managers, content writers, demand gen managers, growth product managers, and operations specialists. The total team size at the end of Engine is typically sixty to ninety people, depending on the company's size and motion.
Three structural choices in this org shape are worth flagging because they are the most contested.
The first is whether product marketing reports to the CPMO directly or through the VP of Product Marketing. At Engine scale, the VP of Product Marketing should manage the team and the CPMO should focus on strategic positioning calls. The CPMO who manages individual PMMs directly is a CPMO who is doing the VP's job and not their own.
The second is whether growth reports to the CPMO or to the VP of Product. Both configurations exist in the wild. The cleaner version, in B2B Enterprise, is for growth to report to the CPMO directly when the role spans both product surfaces and marketing surfaces. When growth is purely a product-surface function, it can sit under the VP of Product. When it is split, the split itself is usually a sign that the role has not been thought through clearly.
The third is whether revenue operations sits in the CPMO org or the CRO org. The cleaner answer is that revenue ops sits with the CRO, and marketing ops and product ops sit with the CPMO. A unified ops function that spans both organizations sounds appealing on the org chart but produces a function whose loyalty is to neither executive and whose work is shaped by whichever leader is more demanding in any given week.
8.3 Cadence: The Operating Rhythm Emerges
The operating rhythm at Engine matures from the weekly cadence of Wedge into a structured executive operating system that is the same in shape, if not in detail, as the system the company will run for the rest of its life.
The weekly cadence is anchored by a CPMO leadership team meeting - ninety minutes, attended by the five direct reports, with a consistent agenda that covers the state of the business, the state of the loop, and the decisions that need to be made this week. The agenda is not negotiable, but the contents are. The state of the business covers pipeline, customer health, and any active crises. The state of the loop covers what was learned in Sense, what is being tested in Frame, what is being committed in Shape, what is shipping in Ship, and what is compounding in Scale. The decisions section is the one most CPMOs underinvest in. It is the place where the small number of cross-functional calls that need executive attention get made, with named decision rights and named timelines. A weekly leadership meeting that produces no decisions is a status meeting wearing a leadership label.
A second weekly cadence is the CPMO-CRO standing meeting - sixty minutes, just the two executives, focused on the shared surface described in Chapter 2. ICP refinement, win/loss synthesis, sales enablement, pipeline coverage, pricing discipline. This meeting is the operational expression of the partnership the role depends on. Engine-stage CPMOs who skip this cadence - usually because they believe their relationship with the CRO is good enough that it does not need a standing meeting - produce the most expensive cross-functional dysfunction in the company.
The monthly cadence is the monthly business review, three hours, attended by the CPMO leadership team, the CRO and key revenue leaders, and the CEO when the agenda warrants. The review is structured around the loop rather than around functional reports. Sense covers what changed in the market in the past month. Frame covers any positioning tests or narrative shifts. Shape covers what was committed and what was de-prioritized. Ship covers the launches that landed, the launches that missed, and the readiness for the next month's launches. Scale covers the loop metrics - activation, retention, expansion, NRR by segment, and the leading indicators of pipeline quality. The monthly review is the document that the CEO and the board can rely on to understand the state of product and marketing in the company. It is also the document that becomes the substrate of the quarterly business review.
The quarterly cadence is the quarterly planning and review cycle, with two distinct events at each end of the quarter. The quarterly review at the end of the quarter assesses what was committed, what was delivered, what was learned, and what the implications are for the next quarter. The quarterly planning at the start of the next quarter commits to the small number of cross-functional priorities the CPMO function will pursue. The discipline of quarterly planning at Engine is to commit to fewer things than the leadership team thinks possible. A quarter with three CPMO-level priorities will produce more than a quarter with eight.
The annual cadence is the annual strategy reset and the budget cycle, typically conducted in the final quarter of the year for the following year. The strategy reset is a deeper version of Sense, Frame, and Shape, run with longer horizons and more deliberate input from the CEO, the CFO, and the board. The budget cycle is where the CPMO defends investment levels for the function against the CFO's pressure for efficiency and the CRO's pressure for revenue. CPMOs who arrive at the annual budget cycle without a year of strong operating data lose this argument, and the resulting under-investment compounds for the following twelve months.
8.4 Metrics: Pipeline, Win Rate, CAC Payback
The metrics that matter at Engine are the metrics that are noise at Wedge and signal at Scale. The transition is not subtle. A CPMO who is still operating with Wedge-stage qualitative metrics at Engine is missing the operating signal the company needs. A CPMO who is reaching for Scale-stage portfolio metrics before they are statistically meaningful is operating on fiction.
The metric set at Engine is built around the loop and segmented by the dimensions that matter - segment, motion, and product line where applicable.
Pipeline metrics become real at Engine for the first time. Pipeline created (in dollars and in deal count), pipeline coverage against next quarter's revenue target, pipeline by source (marketing-sourced, sales-sourced, partner-sourced, customer-sourced), and pipeline quality (measured by stage progression rates, conversion rates, and average deal velocity). The CPMO is accountable for the volume and quality of pipeline created. The CRO is accountable for its conversion. Both report to a shared coverage target. The metric set is the operational expression of that shared accountability.
Win rate metrics become reliable at Engine. Win rate against the full deal set, win rate against the qualified deal set, win rate by segment, win rate by competitor, and win rate by deal size. The most useful version of this metric is win rate by segment by competitor - a small grid that exposes exactly where the company is winning and losing, against whom, and in which segments. This grid is the input to almost every Frame stage decision. Companies that are losing consistently to a specific competitor in a specific segment have a positioning problem, a product gap, or a pricing problem in that intersection - and the grid is what makes the diagnosis possible.
CAC and payback period metrics become defensible at Engine, with the caveat that they have to be computed correctly. CAC computed as marketing spend divided by new customers is wrong. CAC computed as fully-loaded sales and marketing spend divided by new logo annualized contract value is approximately right and is the version that the CFO and the board will compare against industry benchmarks. Payback period - the months of revenue required to recover CAC - is the more meaningful metric for capital efficiency, and the one that determines how aggressively the company can invest in growth. CPMOs at Engine who do not have a defensible CAC and payback computation are CPMOs who will lose every meaningful capital allocation argument.
Net revenue retention becomes the central health metric of the company at Engine, even if the conventional benchmarks suggest it is more important at Scale. NRR captures the compounding behavior of the customer base - the rate at which existing customers are growing, churning, or shrinking - and is the leading indicator of whether the loop is genuinely compounding. NRR above 110% in B2B Enterprise indicates a healthy expansion motion. NRR below 100% indicates that churn is exceeding expansion, which is a structural problem that no amount of new pipeline can compensate for indefinitely.
Activation and time-to-value metrics, which became real at Wedge, become more refined at Engine. The activation milestone, defined empirically at Wedge, gets segmented by ICP and motion. Time-to-value gets measured both in days and in correlation with retention, with the empirical relationship between faster time-to-value and higher one-year retention becoming the basis for product investment decisions.
Three categories of metrics are dangerous at Engine because they look like signal but are mostly noise. Vanity brand metrics - impressions, reach, social engagement - should not be reported to the executive team because they do not connect to any decision the executive team will make. Lead volume metrics, divorced from quality, produce sales teams that complain about lead quality and marketing teams that complain about sales execution; the metric that matters is qualified pipeline created, not leads generated. Single-month variance metrics produce reports that fluctuate dramatically based on deal timing, vacation schedules, and accounting treatments; the rolling three-month or trailing twelve-month version is almost always the correct measurement.
**
8.5 Traps: Hiring a VP Marketing Who Wants a Brand Refresh**
Five traps catch Engine-stage companies more often than any others.
The first is the title-of-this-section trap: hiring a senior marketing leader whose first instinct is to spend the first six months on a brand refresh, a website redesign, and a positioning exercise that produces beautiful artifacts and no measurable change in pipeline. The hire is well-credentialed. The work is genuinely good. The timing is wrong. At Engine, the company needs a marketing leader who can build a demand creation system, instrument it, and produce predictable pipeline. Brand refresh work is real and necessary, but it is a Scale or Platform stage discipline. A CPMO who lets a new VP of Marketing spend two quarters on a rebrand at Engine has lost two quarters of pipeline construction.
The second is the over-elaboration of the org structure. Engine-stage CPMOs, often hired from larger companies, import the org structures they knew at Scale or Platform. They build matrix structures, dotted-line reporting, regional segments, and product-line specializations before the company has the volume to support them. The result is an org that looks impressive on paper and produces less actual work than a leaner structure would. The discipline at Engine is to build the smallest org that can do the work, not the largest org that the budget supports.
The third is the segmentation that becomes a script. The company's ICP, defined at Wedge with care, becomes a segmentation model that is increasingly precise and increasingly disconnected from reality. New customer segments emerge from the market that do not fit the model. Existing segments begin to behave differently. The model, treated as authoritative, prevents the company from seeing the changes. The CPMO's job is to maintain the segmentation as a living instrument - updated quarterly, tested against win/loss data, and refined when the evidence demands it. Most Engine-stage companies treat segmentation as a one-time project rather than a continuous discipline.
The fourth is the launch as theater. As the launch system matures, there is a temptation to use launches as marketing performance - large announcements, polished events, executive keynotes - for products and features that do not warrant the investment. The launches consume disproportionate executive attention, produce content that is not rooted in real customer need, and train the company to value the launch event over the product impact. The CPMO function's job is to enforce launch tier discipline - most launches are tier-three or tier-four, run by the team without executive involvement; only the small number of genuinely strategic launches earn the full launch system.
The fifth is the hardest one, and the one most Engine-stage CPMOs do not see until it has done its damage: optimizing the funnel while the category shifts. The company's loop is now operating well. Pipeline is predictable. Win rates are stable. NRR is healthy. The metrics all look good. Meanwhile, the underlying market is changing - buyers are evaluating differently, a new competitor is reframing the category, the technology underpinning the product is being disrupted by an AI-native alternative. The CPMO, head down in operational excellence, optimizes the existing engine while the market that engine was built to serve is being redefined. By the time the change becomes visible in the metrics, the lead time required to respond is longer than the time available. This trap is so consequential that Chapter 9, on the Scale stage, returns to it as one of the central failures of that stage. It begins at Engine.
The Engine stage ends when the company has built a system that produces predictable pipeline at predictable cost, delivers product reliably across multiple segments, and retains and expands customers without heroic individual effort. When that condition is met - typically somewhere between $20M and $30M ARR, though the operating reality matters more than the revenue figure - the company is ready to enter the Scale stage, where the question shifts from "can we build the engine" to "can we compound it." That is the subject of the next chapter, and the stage at which the CPMO role is hardest, where most CPMOs fail, and where the structural decisions made at Engine determine whether the company breaks through or stalls.
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.
Top comments (0)