Module 2 — Brand, Product and Price · Lesson 2.2
Product Marketing and Launches
Who owns the story of the product, and how to launch something people can verify
What you'll learn
- Describe what product marketing owns that neither product nor sales does
- Tier launches by how much they change the buyer's job, and size the effort to the tier
- Run a launch through readiness gates: proof, enablement, channels, measurement
- Plan the post-launch period, where most of the learning happens
Launches attract a disproportionate share of attention and a disproportionate share of disappointment. The announcement goes out, there is a spike of interest, and three weeks later usage looks as it did before. Usually the product was fine. What failed was the translation: nobody had made clear which job the new thing does better, for whom, with what proof — and nobody had prepared the people and channels that buyers actually consult.
What product marketing owns
In a small company product marketing is rarely a person; it is a set of responsibilities that fall between product and sales and get dropped. They are: the positioning of each product or feature against the job (Lesson 1.3), the message hierarchy for it (Lesson 1.4), the proof that backs each claim, the enablement that lets sales, support and partners explain it, and the feedback loop that carries what buyers say back to the product team.
The Jobs to Be Done lens gives the role its question: what progress does this make possible, in which circumstance, that was not possible before? A feature list answers 'what did we build'; product marketing answers 'what can you now get done'. The second is the only one buyers care about.
Proof before the announcement
Joan Schneider and Julie Hall, who run a firm specializing in launches, wrote in Harvard Business Review in 2011 that they regularly hear from founders and brand managers with 'revolutionary' products who, asked about the research behind their claims, reply that they have not done it yet but know anecdotally that the product works — and that they can often tell from that one conversation whether the launch will succeed.
There is a commercial and a legal reason to fix this before launch. Commercially, buyers who are 60% or more of the way through their decision before contacting anyone (6sense's 2025 survey, Lesson 1.4) will check your claims against what they can find, and an unsupported superlative costs credibility you cannot easily get back. Legally, the FTC's guidance for businesses is that advertisers need evidence for both express and implied claims before the ad runs, not after a customer complains. 'The fastest way to build client reports' needs a basis; 'set up in one afternoon, median across our last twenty customers' has one.
So the first readiness gate for any launch is proof: at least one real customer outcome, measured, that you are allowed to cite.
Tiers and readiness gates
Not every release is a launch. A practical tiering, which is our recommendation rather than an industry standard: Tier 1 changes the job you can do for a segment and gets the full treatment — positioning, proof, enablement, a campaign, measurement. Tier 2 meaningfully improves an existing job and gets a message, an announcement to customers and enablement. Tier 3 is a fix or a small improvement and goes in the changelog.
A Tier 1 launch then moves through gates, each with an owner and a definition of done. Proof: the cited outcome and the evidence on file. Positioning and message: the one-sentence claim, pillars and proof, reviewed against the brand standard. Enablement: a short brief for sales and support, a demo path, the three objections you expect and their answers. Channels: which owned, earned and paid channels carry it, in what order — existing customers first is usually right, since they are the cheapest audience to reach and the most likely to give fast feedback. Measurement: the one or two numbers that will tell you in thirty days whether it worked, written down before launch so the result cannot be rationalized afterwards.
A launch date is set when the gates are on track, not the other way round.
After the spike
Most of the value of a launch is learned in the four weeks after it. Watch which segment responded, which pillar prospects repeat back, which objection kept coming up, and whether the people who tried the new capability kept using it. Then make the follow-on decisions explicitly: double down on the segment that responded, rewrite the pillar nobody repeated, add the missing proof.
Write a short launch retrospective while it is fresh. It is the cheapest research you will ever do, and it is what makes the next launch better rather than merely different.
Run a launch as gated work
- 1
Create a launch project with one task per gate
On /projects/tasks, create Proof, Message, Enablement, Channels and Measurement tasks, each with an owner, due date and a definition of done in the description. Add a dependency so the announcement task visibly waits on Proof.
- 2
Check the date against capacity
On /planning, look at whether the people who own the gates have room in the sprint before launch. A launch date that ignores capacity is a date that slips quietly.
- 3
Collect beta or early-access requests with a public form
On /requests, publish a request page with the fields you need. Submissions arrive in the requests inbox and can be converted to tasks; they do not create Deal Room contacts automatically, so assign someone to triage them.
- 4
On /knowledge, record the launch retro: what responded, what did not, what you will change.
Launch outcomes
- Gate completion at launch
- Share of readiness-gate tasks complete on the announcement date.
- Healthy signal: All of them for Tier 1. Launching with Proof incomplete is the failure this lesson is about.
- Thirty-day adoption
- Share of eligible customers who used the new capability at least twice in the first thirty days. Measured in your product analytics, not in Kavanah.
- Healthy signal: Whatever you wrote down before launch; the point is to compare against the pre-committed number.
- Launch-sourced conversations
- New qualified conversations in the thirty days after launch that cite the launch. Recorded on the deal.
- Healthy signal: Above your normal monthly baseline.
Key takeaways
- ·Product marketing owns the translation from what was built to the job it does — positioning, proof, enablement and feedback.
- ·Proof is the first launch gate, for commercial and legal reasons.
- ·Tier releases, and give only Tier 1 the full treatment.
- ·Pre-commit the success measure, and learn deliberately in the four weeks after launch.
A launch tells buyers what a product does. The price tells them what it is worth — and moves profit faster than almost anything else. Pricing and packaging is next.
Sources
- 1.Why Most Product Launches Fail
Joan Schneider and Julie Hall · Harvard Business Review, April 2011 · 2011
Launch specialists report that 'revolutionary' products often arrive with no research behind their claims, and that this predicts launch outcomes.
- 2.Advertising FAQ's: A Guide for Small Business
US Federal Trade Commission · ftc.gov (edited January 2025) · 2001
Claims must be truthful and substantiated before they are made, including implied claims.
- 3.2025 B2B Buyer Experience Report
6sense (vendor research) · 6sense.com · 2025
Buyers first contact sellers around 61% of the way through the journey, so launch claims are checked before you are in the room.
- 4.Jobs to Be Done Theory
Christensen Institute · christenseninstitute.org · 2024
Frames a feature by the progress it enables in a circumstance — the core question product marketing answers.