How I stepped in a week after a PMM resigned and kept every launch on track
The company: a Series A, European B2B SaaS company in the middle of changing its ICP.
The situation
Their product marketing manager had just resigned and was leaving in two weeks. The team had spent months building new products, and several were ready to launch.
Three teams were stuck:
- Product had built great products and had nobody to take them to market.
- Marketing had a strong demand gen team that couldn't start until the positioning, the messaging and the timelines were final.
- Sales couldn't sell the new products without understanding them and getting the right assets, like a sales deck and a one-pager.
Why they brought me in
Hiring a full-time PMM would take months, and the launches couldn't wait that long. The VP Marketing couldn't take on the launches himself on top of his other priorities. They reached out to me and I joined straight away. They started the search for a permanent PMM at the same time, and hired one in four to five months.
What I did
Built a launch system first.
I tiered every upcoming release as T1, T2 or T3, so the team knew where to spend its time and budget. I used that system for two major launches and three smaller ones.
| Tier | What it is | Launch investment |
|---|---|---|
| T1 | Market-defining. Drives new or expansion revenue, and no competitor has it. | Full channel stack, all resources. |
| T2 | Drives new or expansion revenue. Competitors may have something similar. | Focused launch on a targeted set of channels. |
| T3 | Improves adoption. No direct revenue impact. | Lightweight, often bundled with other T3 releases. |
Ran every major launch with my launch process.
I took each launch through seven steps, from studying the product and the market to measuring the results, and walked the sales team through the story before anything went public.
See my full product launch process →
The launch brief I fill in before I build anything for a launch
- Why we're launching: the commercial goal (new revenue, upsell or adoption) and why now.
- What we're launching, and for who: the feature in one line, and the segment it's for.
- Who needs to know internally: sales, CS, marketing and support, enabled before anything goes public.
- Who we're reaching externally: existing customers, new-business prospects, or both.
- When we go live: the four dates (product release, internal enablement, customer comms, public launch).
- Where we announce it: the channels, pulled from the tier.
- Success metrics: leading and lagging, one set per goal.
Built 30-second interactive demos in Storylane.
Sales had nothing to show a prospect who asked "how does this work?", and the landing pages didn't show the product at all. I scripted the demos and built them in Storylane, so anyone can see the product end to end in about 30 seconds. Marketing used them on landing pages and sales used them with leads, and both teams found them really helpful for converting.
Built a customer story engine for the new ICP.
The company had plenty of case studies, but all of them were from the old ICP. The new ICP needed new stories, and the CSMs had no time and no system to work out who to ask. I worked out which customers to approach, built the list with the CSMs, and gave them an AI skill that turns a call transcript into a case study draft.
Ramped up the new PMM before I left.
When they hired a permanent PMM, I handed everything over, from the launch system and the documents to the story engine, and stayed on for a few weeks until she was fully ramped up. I do this with every client.
What changed
- I ran two major launches and three smaller ones while the PMM role was empty.
- Sales had a talk track, a deck and an enablement session for each major launch from day one.
- When the new PMM started, she took over a working launch tier system, all the launch documents and the customer story engine.
Talk to Gokul →