7.0 What Wedge Means
The Wedge stage begins when a company has found something real - a specific customer segment, a specific problem, and design partners who use the product because it works rather than because they like the founder - and ends when that something has been made repeatable. Most B2B Enterprise companies enter this stage with somewhere between three and seven design partners and exit it somewhere between $1M and $3M in annual recurring revenue. The exit is not defined by the revenue number. It is defined by whether the company can win deals predictably in a defined segment without the founder personally driving every step.
Two things are true at Wedge that were not true at Founding. The first is that the product works for someone - a specific someone, in a specific context, doing a specific job. The second is that the company has not yet proved this can be repeated. A wedge that produced three customers might produce three hundred. It might also produce no more than three. The Wedge stage is the period during which that question is answered.
This is the stage at which the CPMO function is most often hired into the company for the first time, or the stage at which a founder begins to hand off pieces of the loop to specialists. The decisions made in this transition shape the company more than the founder usually realizes. A premature handoff produces a company whose loop is run by people who do not yet know the wedge well enough. A delayed handoff produces a founder who becomes a bottleneck and a company that cannot move past the wedge it has found.
The ambition of this chapter is to describe the work clearly enough that founders can see what they are actually doing, and aspirants can see why the seat at this stage is so different from the one at Engine or Scale.
7.1 The CPMO's Job at the Wedge Stage
The job at Wedge is to make the wedge repeatable.
Repeatability is a precise concept and worth being explicit about. A wedge is repeatable when the company can describe, in writing, who buys the product, why they buy it, what triggers the buying decision, what they are replacing or comparing it against, what objections appear in every deal, and what the buying process looks like - and when that description holds up across at least eight to twelve customers who were not personally sold by the founder. Anything less than that is a pattern in formation. Anything more is the beginning of an engine.
The CPMO function at Wedge is doing four things in parallel, with most of the founder's time still consumed by the first two and progressively more delegated to others as the stage matures.
The first is converting the design partner relationships into paying customers and reference accounts. Design partners are not customers in the conventional sense. They have favorable pricing, often-substantial influence over the roadmap, and a relationship that is closer to co-development than to vendor-buyer. The work at Wedge is to convert this relationship into something more conventional - actual contracts at actual prices, actual usage at scale within the customer's organization, and actual willingness to serve as a reference for new prospects. This conversion is delicate. Push too hard and the relationship sours. Don't push at all and the company never learns whether the wedge can support a real economic transaction.
The second is finding the next ten to twenty customers who are similar enough to the design partners to validate the pattern but different enough to test its boundaries. The discipline here is precise. The CPMO function at Wedge is not trying to find any customer. It is trying to find customers who match the emerging ICP closely enough that their experience will sharpen the pattern, while occasionally testing customers slightly outside the pattern to discover where the boundaries actually lie. Companies that take any customer who will buy at this stage produce muddy data and an ICP that they cannot articulate at the end of the year. Companies that are too narrow produce a pattern that is real but too small to scale.
The third is beginning to externalize the founder's tacit knowledge into systems that other people can run. The way the founder described the product in a sales conversation has to become a sales narrative. The objections the founder learned to handle have to become a competitive battle card. The patterns the founder identified in customer conversations have to become a written ICP description. The reasoning behind product priorities has to become a strategy document that engineers can refer to when the founder is not in the room. None of this externalization is glamorous, and most founders avoid it because it slows them down. The deferral is a mistake. A company that cannot scale beyond the founder's head is a company that cannot scale.
The fourth is the first deliberate construction of the loop's other stages. At Founding, Sense was the dominant stage; everything else was reactive. At Wedge, Frame begins to matter - positioning has to be tested in language, not just embodied in product decisions. Shape begins to matter - the roadmap has to commit to a defensible set of priorities, not just respond to whatever the latest design partner asked for. Ship begins to matter - releases have to be coordinated with messaging, even when the messaging is just a single email to ten customers. Scale does not yet matter, because there is nothing to scale. But the other four stages are now operating, and the CPMO function is the discipline of making sure none of them are neglected while the founder's attention naturally pulls toward whichever one is currently on fire.
7.2 Team Shape: First PMM, First Growth Hire
The team at Wedge grows from the Founding-stage cluster of three to six people into a more recognizable B2B Enterprise org of ten to fifteen people. The shape of that growth matters more than the size.
The first hire that earns its place at Wedge, almost without exception, is a senior product marketer. Not a marketing leader, not a brand executive, not a demand generation manager. A specific kind of operator: someone who can sit with the founder, absorb the wedge through repeated customer conversations, and translate it into language the rest of the company and the early market can use. This person is part-writer, part-strategist, part-research synthesizer. They do not run a team. They do not manage campaigns. They produce the artifacts the company needs to scale beyond the founder's voice - the positioning document, the sales narrative, the website that finally reflects what the company actually does, the first real launch announcement, the customer interview synthesis that feeds the next product decision.
The second hire, often within six months of the first, is a growth-flavored operator. The right shape depends on the dominant motion. If the company has any meaningful self-serve or product-led component, this person is a growth product manager who owns activation, in-product conversion, and the early lifecycle surfaces. If the company is purely sales-led, this person is a demand generation manager who owns the early pipeline-building experiments - paid acquisition, content distribution, event presence in the segments that matter. In either case, the hire is operational rather than strategic. They execute against the patterns the founder and the product marketer have identified, and they begin to instrument the loop for measurement.
The first product manager hire - distinct from the founder - typically happens late in Wedge, often only as the company approaches Engine. This is later than most founders expect and earlier than most CPMO playbooks recommend. The reason is that product strategy at Wedge is still founder work. A product manager hired before the wedge is repeatable will either follow the founder's direction without adding value or override the founder's direction without enough context. The right time to hire the first PM is when the founder has externalized enough of their tacit knowledge that the PM has something concrete to operate against.
A few hires that are tempting and almost always premature: a head of marketing, a sales leader (as opposed to the first salespeople), a customer success manager (as opposed to the founder doing customer success directly), a designer leader (as opposed to a strong individual designer), and any kind of operations or analytics leader. Each of these may earn their place at Engine. None of them earn their place at Wedge.
The reporting structure remains close to flat. The product marketer and the growth operator both report to the founder, as do the engineers, the designer, and the first salespeople. The founder is still the integration point of the loop. A company at Wedge that has built a layer of management between the founder and the people doing the work has either grown faster than the wedge supports or has hired senior people whose seniority is not matched to the work. The flatness is not an accident. It is the structural condition under which the founder can still run the loop personally.
7.3 Cadence: Weekly Learning Loops
The operating rhythm at Wedge shifts from the daily cadence of Founding to a weekly cadence that introduces, for the first time, the early elements of an executive operating system.
The center of the Wedge cadence is the weekly leadership review. Two to three hours, typically on a Monday or Friday, attended by the founder and the small leadership team. The agenda is consistent across weeks, which is how it earns its place in the calendar. The review covers the week's customer signal - wins, losses, churn, design partner feedback, support themes. It covers the week's product progress - what shipped, what is shipping next, what is blocked. It covers the week's pipeline - every active prospect, every late-stage deal, every relationship at risk. And it covers the week's experiments - what was tested, what was learned, what the next experiment is.
The Sense memo, which existed informally at Founding, becomes a deliberate artifact at Wedge. It is updated weekly, typically by the founder or the product marketer with the founder's review. It captures the company's current view of the wedge - who the customer is, what the pattern looks like, where the boundaries are, what is still uncertain. The memo is the spine of the weekly review. Decisions that are not consistent with the memo either change the decision or change the memo. Memos that have not been updated for a month are a signal that the company has stopped learning, which is a worse signal at Wedge than at any other stage.
A monthly cadence begins to appear, mostly in the form of a board update or investor letter. This is not yet a monthly business review in the conventional sense - the data is too thin for that - but it is a discipline of writing down what changed in the month, what was learned, and what the next month's bets are. The act of writing the monthly note forces a synthesis that the weekly cadence does not. Founders who treat the monthly note as a chore rather than a thinking instrument are missing the point.
Quarterly planning is now real but lightweight. A typical Wedge-stage quarterly plan is a three-to-five-page document that names the two or three things the company is committing to in the quarter and ignores everything else. The document is ruthless about what is not being done. The temptation at Wedge is to commit to every promising thing the founder has noticed in the past three months. The discipline is to commit to the small number of things that will most directly test or extend the wedge.
There is no annual plan worth the name at Wedge. The company is still moving too fast and learning too much. There is, however, a single annual artifact: a written description, at the end of each year, of what the company learned about its wedge that it did not know at the start of the year. This document, written for the founder more than for any external audience, is the most important artifact a Wedge-stage company produces, and the one most often skipped.
7.4 Metrics: Time-to-Value and Activation
The metrics that matter at Wedge are different from Founding, sharper than Founding's qualitative signals, but still narrower than the conventional B2B SaaS metric set that takes over at Engine.
The first metric that begins to carry real signal is time-to-value. How long does it take, from the moment a new customer signs a contract or starts a trial, until they experience meaningful value from the product? The measurement is concrete: typically the time from sign-up to first material use, where "material use" is defined specifically for the product's job. For a security product, it might be the first scan completed. For a developer tool, the first deployment. For a workflow product, the first task completed end-to-end. Time-to-value at Wedge is usually long, often weeks, and the reduction of that time is one of the most consequential things the CPMO function can do, because it directly determines whether the customer becomes a reference, an expansion, or a churn risk.
The second is activation rate. What percentage of new accounts reach a defined activation milestone - a state of the customer's usage that strongly correlates with eventual retention and expansion? The activation milestone has to be defined empirically rather than aspirationally. Most Wedge-stage companies define it wrong on the first attempt and refine it over the following two quarters. The right activation milestone is the smallest set of customer behaviors that, observed in the first thirty to sixty days, predicts retention and expansion at the one-year mark. Until that empirical definition exists, activation is a placeholder rather than a metric.
The third is qualitative retention signal. Conventional retention metrics - gross dollar retention, net dollar retention, logo retention - exist at Wedge but are not yet reliable, because the customer base is too small and the time horizon is too short. The signal that matters is more textured: are the customers who signed twelve months ago still actively using the product, expanding their usage, recommending it to peers, and renewing without negotiation drama? A Wedge-stage company with eight customers, six of whom are deeply engaged and two of whom have churned, is healthier than one with twenty customers, fifteen of whom are barely using the product. The aggregate metric does not capture the difference. The qualitative signal does.
The fourth is the first leading indicator of pipeline quality, which is the rate at which sales conversations result in second meetings. This is a more honest metric at Wedge than win rate, which is too volatile when deal volume is low. A Wedge-stage company whose sales conversations advance to a second meeting more than half the time has positioning that resonates. A company whose conversations rarely produce second meetings has a positioning problem that no amount of sales training will fix.
The fifth, and the most important Wedge-stage metric, is the cycle time of the loop itself. How long does it take from a customer signal - a churn, a request, a competitive loss - to a meaningful response? At Founding, this was instant; the founder heard the signal and acted on it. At Wedge, with more people in the org and more customers in the base, the cycle time can quietly stretch from days to weeks to months. A Wedge-stage company whose loop cycle time has stretched beyond two weeks has begun to lose the velocity that made it competitive in the first place. The CPMO function's job is to keep the cycle time short, even as the company grows past the size where short cycle time is automatic.
Conventional B2B SaaS metrics - CAC, payback, magic number, sales efficiency - exist at Wedge but should be treated with skepticism. They are computed on a small enough base that they fluctuate dramatically quarter to quarter, and a CPMO who reports them to a board with confidence at this stage is producing fiction. They become real at Engine. At Wedge, they are noise wearing the clothes of signal.
7.5 Traps: Confusing Revenue with PMF
Five traps catch Wedge-stage companies more often than any others.
The first is the most famous one, and the one most B2B Enterprise founders fall into despite knowing it: confusing revenue with product-market fit. A Wedge-stage company can produce real revenue from customers who are not actually fit for the product - customers who bought because of the founder's relationship, because the price was discounted aggressively, because the buyer was budget-flush at the end of a fiscal year, or because the customer's actual job was so urgent that they bought the closest available solution without caring whether it was right. Revenue from these customers is real money. It is also a false signal of fit. The diagnostic is whether the customer is using the product, expanding within it, and willing to renew at full price. If any of those is missing, the revenue is not telling the truth about fit.
The second is segment drift. Founders, under pressure to show traction, take customers who are not in the target segment because the customers are willing to buy. Each individual exception is defensible. The cumulative effect is destructive. A company that started targeting mid-market financial services and now has customers in healthcare, retail, government, and small business has not expanded its addressable market. It has muddied its wedge. The CPMO function's job is to maintain segment discipline against the natural pull of available revenue, and to say no to customers who are not in the segment even when the revenue is welcome.
The third is the premature scale of go-to-market. A company that has eight reference customers in a wedge does not yet need a sales team of fifteen, a marketing budget of three million dollars, or a partnership program. The temptation appears as soon as the first round of growth-stage capital is raised, and the temptation is reinforced by the board, the new VP of Sales, and the consultant who wrote the GTM plan. The trap is real: a Wedge-stage company that scales its GTM before the wedge is repeatable will burn the capital, blame the people, and find itself eighteen months later with a much larger team, a much smaller bank account, and a wedge that is no clearer than it was before.
The fourth is the founder who hires too many senior people too fast in an attempt to compensate for their own exhaustion. The hires are expensive, often impressive, and individually competent. They are also wrong for the stage. A Wedge-stage company that has hired a CMO, a CRO, a Head of Customer Success, and a VP of Engineering before $5M ARR has built an executive layer that is bigger than the operating reality of the company. The executives will spend their first year fighting each other for unclear scope, building plans against an undefined ICP, and producing the appearance of organization while the underlying work - finding the wedge's repeatability - slows down.
The fifth is the most quietly damaging: the founder who refuses to externalize their tacit knowledge. The work of writing down the ICP, the positioning, the sales narrative, the product strategy, and the operating principles is tedious. Founders avoid it by saying they will get to it later, by delegating it to a junior hire who cannot do it without their input, or by claiming the tacit knowledge cannot be externalized. The claim is wrong. The tacit knowledge can be externalized; it just requires sustained effort the founder does not want to give. The company that does not externalize cannot scale, because the loop continues to run inside one person's head, and that person becomes the bottleneck on every decision, every hire, every customer conversation, every product call.
The Wedge stage ends when the company can describe its ICP in writing, sell to that ICP repeatedly without the founder in every conversation, and produce a predictable pipeline within a defined segment. When that condition is met - typically somewhere between $3M and $5M ARR, though the revenue number is a marker rather than a definition - the company is ready to enter the Engine stage, where the question shifts from "can we make this repeatable" to "can we build a real engine around it." That is the subject of the next chapter, and the stage at which most aspirants will first encounter the company they hope to lead.
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)