Framework · 5 min read
Product Development Stage Framework
PMM activities aligned with the product's development stage.
Robert G. Cooper · View sources ↓At a glance
- Use this when
- You need to know what PMM should contribute at each stage of product development.
- What you will work towards
- PMM activities aligned with the product's development stage.
- Bring to the reading
- A specific decision from your work and the customer evidence you have so far.
What it is
A process-oriented framework that guides product marketers through key activities during different phases of product development: ideation, prototype, beta, launch, and maturity. It defines PMM's role at each stage (research, validation, messaging, enablement) and ensures market insights inform product decisions before launch, rather than after the product has already been built around untested assumptions. The framework's core insight is timing: the value of product marketing input is highest early, when direction can still change cheaply, and lowest at launch, when most of the expensive decisions have already been locked in.
When to use it
Use this as a playbook when launching new products, major features, or entering new markets. It answers: "What should product marketing be doing right now?" Apply it from day one of a new initiative; too many companies start PMM work after product launch, when it's too late to influence the most important decisions. It is equally useful as a diagnostic: if you cannot say which phase a current initiative is in, or what PMM's output for that phase should be, that is itself a sign the initiative is under-resourced on the marketing side.
Ownership
At a scaled company with a specialised PMM team, the VP Product owns the overall phase gates and the go or no-go call at each stage, while the Head of Product Marketing owns the PMM-side outputs, positioning, messaging, and enablement, and jointly agrees the launch date and scope with VP Product. At a solo or founding-PMM stage, the founding PMM owns every PMM output outright and works directly with the founder or Head of Product, who makes the final call on timing and scope without a formal phase-gate process.
How to apply it
Phase 1: Ideation & Research (Weeks 1–4)
- Conduct customer discovery: What problem does this solve? Who has it? How urgent is it, on a scale from "mild annoyance" to "actively costing them money or time every week"?
- Analyse the competitive landscape: Who else solves this, directly or with a workaround? How will we differ, and is that difference something customers will actually pay for?
- Estimate TAM and pricing sensitivity using comparable products and early customer conversations, not just internal assumptions.
- Output: Customer research doc, problem validation, rough positioning hypothesis.
Phase 2: Prototype & Validation (Weeks 5–12)
- Share a prototype with 15–20 target customers; validate problem-solution fit rather than just gathering polite feedback on the interface.
- Refine positioning based on what customers say unprompted, particularly the language they use to describe the problem.
- Identify go-to-market risks early (e.g., "No one will pay for this" or "Sales can't explain it in under two minutes").
- Output: Validated positioning, refined ideal customer profile (ICP), early case study customer identified and willing to go on record.
Phase 3: Beta & Messaging (Weeks 13–20)
- Recruit 5–10 beta customers for deep feedback, chosen deliberately to represent the primary target segment rather than whoever was easiest to reach.
- Draft a complete positioning statement, value proposition, and three to five key messages.
- Create three to five early case study scenarios, each grounded in a specific beta customer's measurable result.
- Build initial sales enablement: demo script, objection handling document, and a one-pager that a rep can send within a minute of a call ending.
- Output: Final positioning, messaging playbook, draft collateral.
Phase 4: Launch (Week 21+)
- Coordinate go-to-market activity: simultaneous messaging across website, sales, PR, and events so no channel is telling a different story.
- Build the full collateral suite: landing page, case studies, webinar, and email campaign, each tested against the Phase 3 messaging playbook for consistency.
- Run sales enablement training and a formal kickoff, with a short quiz or role-play to confirm reps can actually deliver the pitch, not just that they attended the session.
- Output: Go-to-market execution, customer wins, initial demand.
Phase 5: Maturity & Optimisation (Months 4+)
- Monitor win rates, sales feedback, and recurring customer questions for signals that messaging needs to adjust.
- Iterate messaging based on structured win/loss analysis rather than anecdote.
- Expand positioning to adjacent segments once the primary segment shows a repeatable, predictable sales motion.
- Output: Refined positioning, segment-specific messaging, upsell strategy.
Example
A fictional data infrastructure startup called Streamline Data followed this framework for a new "real-time analytics" product. Phase 1 interviews with 22 prospective customers revealed that operations teams spent 40% of their day waiting for reports to refresh. Phase 2 prototype testing with 18 target customers confirmed genuine willingness to pay, with an average stated budget of £2,400 per month. Phase 3 beta ran with eight customers over eight weeks; two of them, a mid-market logistics company (fictionally named RouteFlow) and a payments processor (fictionally named LedgerPay), agreed to be named case studies describing how the product cut their reporting lag from four hours to under ten seconds. Phase 4 launch message: "See your data in seconds, not hours." The first month produced 120 trials and 8 paid customers, against a target of 5. By month 6, the product had 200 paying customers and £150,000 ARR, and the team tracked trial-to-paid conversion (6.7%), monthly logo churn (1.8%), and average time-to-first-value (11 minutes) as the explicit success metrics that told them the launch had actually worked, not just that it had happened.
Pitfalls
- Skipping phases to move faster. Launching without Phase 2 validation (problem-solution fit) often means building for a market that doesn't exist or at a price no one will pay.
- PMM joining too late (Phase 4). If marketing joins only at launch, the product may already be un-positionable. Involvement from Phase 1 prevents costly misalignment.
- Treating case study customers as an afterthought. Waiting until Phase 4 to look for reference customers usually means scrambling for names under deadline pressure, which produces thin, generic case studies. Recovery: identify at least one likely reference customer in Phase 2, and formally confirm their willingness to be named by the end of Phase 3, so the launch collateral has real detail rather than a vague, anonymised "a logistics company saw improved efficiency" placeholder.
How the ideas connect
Choose where to go next
Make it useful
Bring it back to your work.
Name one decision this guide could help you make. Write down the evidence you need, the output you would produce, and how you would know it was useful.
Check your understanding
Practise applying Product Development Stage Framework in five short scenarios.
5 practical scenarios. Choose an answer, explore the reasoning, and revisit the guide whenever you need.
Sources
- No single originator; this entry adapts the general phased new-product-development model to PMM's specific inputs and outputs at each stage. The most documented version of that underlying phased model is Robert G. Cooper's Stage-Gate system, developed from the mid-1980s: Stage-Gate International, "Our Story".
← All entries in Market & Customer Understanding · Try the category quiz