Topic 5 — Go-to-market and launches

Goal: Plan how a product reaches its market and lands a successful launch.

Lesson 5.1 — The plan that ties everything together

Imogen's first three weeks at Verdana were spent on pieces. A persona built from Brigid Salas, the owner of Iron Fern Studio. A positioning statement. A value proposition for the homepage. Good work, all of it, sitting in separate documents. Then Hollis Bram, her manager, dropped a one-line message: "Verdana's launching automated billing reminders in five weeks. You own the go-to-market. Where do we start?" Imogen stared at it and realized she had ingredients but no recipe.

That recipe is a go-to-market (GTM) strategy — the plan for how a product reaches and wins its customers. Building the feature is Devesh Patil's job. Getting it into the hands of studio owners who'll pay for it is hers. A GTM strategy pulls the earlier topics into one plan and answers five questions:

• Who is the target audience? (the personas from Topic 3 — small gym and studio owners like Brigid)
• What is the value proposition and positioning? (Topic 4)
• Where will you reach them — which channels?
• How much does it cost, and what's the pricing?
• When — the timing and the sequence of activities.

A GTM strategy is everything you've learned so far, finally pointed at one launch date.

Hollis put it to her plainly over coffee: a good product with no GTM plan is a message in a bottle. You did the hard part and then trusted the ocean. The whole reason product marketing exists is to refuse that bet.

Lesson 5.2 — Channels: the paths to your people

Imogen's instinct, fresh from radio, was to make noise everywhere. Hollis stopped her with a question: "Where does Brigid Salas actually spend her attention?"

A channel is a path to your audience. Verdana doesn't need every channel — it needs the few where studio owners already are. The common ones:

• Organic search (SEO) — being found on Google when someone searches "yoga studio booking software." Slow to build, but it compounds.
• Content marketing — blog posts, guides, and videos that pull people in and build trust ("How to cut no-shows at your studio").
• Paid advertising — ads on search and social. Fast, but you pay for every result.
• Social media — presence and community where your audience scrolls.
• Email — direct messages to prospects and existing customers.
• Sales-led outreach — a salesperson like Wren Okafor reaching out directly (common in B2B, selling to businesses, where deals are bigger).
• Referrals / word of mouth — happy owners bringing in other owners. Cheap and powerful.
• Partnerships — teaming up with, say, a yoga-teacher certification body to reach their members.

The product shapes the mix. A low-cost B2C app (selling to consumers) often leans on social and referrals, because the buyer decides fast and alone. A complex B2B product usually needs content plus a sales team, because several people weigh in and the sale takes weeks.

Verdana sells to studio owners — small businesses, one or two decision-makers, a few hundred dollars a month. So Imogen lands on a blend: SEO and content to get found, email to nurture, and Wren's outreach for the bigger multi-location studios. Instagram, where Verdana's gym customers do post, but where no owner shops for billing software, gets cut. Picking channels is mostly the discipline of saying no.

Lesson 5.3 — Not every release deserves a parade

A week in, Imogen made a quiet mistake: she started planning the billing-reminders feature like a Super Bowl ad. Press outreach, a webinar, a redesigned homepage. Hollis pulled up Verdana's release calendar — eleven things shipping this quarter — and asked if she planned to do all that, eleven times. She did not.

Mature PMM teams solve this with launch tiers: you scale the effort to the importance of the release.

Tier	What it is	Effort
Tier 1	A major launch — new product or flagship feature	Full campaign: press, content, email, social, sales enablement, maybe a webinar
Tier 2	A medium launch — a meaningful improvement	A blog post, an email, social, a heads-up to sales
Tier 3	A lightweight release — small change or fix	A changelog note and maybe one email

Verdana's automated billing reminders directly reduce the late-payment headaches Brigid complains about — that's a Tier 1. A new export button next month is a Tier 3 changelog line and nothing more.

Tiers aren't bureaucracy. They stop the team arguing about effort and start it aligning on impact.

The relief on Imogen's face was real. She didn't have to throw a parade for every release. She had to throw the right-sized one for each.

Lesson 5.4 — The three phases of a launch

So billing reminders is Tier 1. What does Imogen actually do with five weeks? A launch runs in three phases, and the work splits cleanly across them.

Before. This is most of the job, and it's invisible from the outside. Imogen finalizes the positioning and messaging, then prepares every asset: the landing page, the announcement emails, supporting content, the sales deck Wren will use, and an FAQ for support. Then she briefs and trains the people on the front line — she walks Wren and the support team through what shipped, why it matters to a studio owner, and how to answer the obvious questions (Topic 6 covers this enablement work). Nothing is announced yet. The wave is being built.

During. Launch day, the message lands everywhere at once. The email goes out, the blog post publishes, the social posts fire, the in-app banner appears, and Wren starts working his list. Coordination is the entire point: every channel telling one clear story on the same day, so a studio owner who sees the email, then the post, then hears from Wren gets the same message three times instead of three different ones.

After. The part beginners skip. Imogen watches the results against the numbers she set in advance, gathers feedback (including a quick note to Brigid asking what she thought), flags issues for Devesh to fix, and keeps the momentum alive with follow-up content. A launch is a start, not a one-day event. The day the announcement goes out is the day the real measuring begins.

To hold it all together, Imogen writes a one-page launch plan. It captures the target audience, the key message, the success metrics, the assets required, the timeline, and — the part that makes it real — a named owner for every task. "Email — Imogen. Sales deck — Imogen, reviewed by Wren. In-app banner — Devesh." No orphan tasks, no launch day with someone realizing nobody built the landing page.

Lesson 5.5 — Coordination, the right audience, and proof

Three principles separate a launch that works from one that just happens.

Coordinate tightly. Everyone aligned on the same message and the same timing. A strong product undermined by a sloppy, contradictory launch is a genuine tragedy — the work was good and the rollout wasted it. When Wren is pitching one benefit while the email touts another, prospects feel the seam.

Target the right audience. Imogen could blast all forty thousand Verdana contacts. She won't. Billing reminders matter most to owners who've complained about late payments, so the launch email leads with them. Blasting everyone trains people to ignore you.

Define success in advance. Before launch day, Imogen and Hollis agree on the numbers that will prove it worked: feature adoption among existing studios, landing-page traffic, trial sign-ups, and conversions. Success metrics are set before the launch, not invented after to make it look good.

That last point is the one Imogen, coming from broadcast, had to unlearn. In radio, a great show felt great. Here, "it felt like a big launch" means nothing. A launch is judged by predefined numbers — sign-ups, traffic, activation, conversions — not by vibes. If you didn't name the target before launch day, you can't honestly say whether you hit it.

Coordinating a launch — many people, many moving parts, one clear story — is a signature PMM skill. It's also a showcase tailor-made for an organized, communicative career-changer. The person who can keep a story straight across a sales team, a blog, an inbox, and an app is doing the exact job Imogen used to do live on air, just with a funnel underneath it.

Worked example — Imogen launches automated billing reminders

Five weeks out, Hollis confirms the tier: billing reminders directly attack late payments, a top pain for owners like Brigid. Tier 1.

Who and what. Audience: existing Verdana studios with a history of overdue invoices, plus new prospects shopping for studio software. Key message: "Stop chasing late payments. Verdana now reminds members automatically, so you can teach instead of invoice."

Channels. Email to the targeted list of existing owners, a blog post optimized for "reduce late payments studio" (SEO), a sales deck so Wren can pitch the multi-location prospects, and an in-app banner. No paid ads — the budget goes to content that keeps working after launch week.

Before (weeks 1–4). Imogen finalizes messaging with Devesh, builds the landing page, drafts the emails and FAQ, and trains Wren and support in a 30-minute session. She calls Brigid for an early look; Brigid's reaction — "finally" — becomes a line in the launch email.

Success metrics, set now: 30% of eligible studios turn on reminders within two weeks; landing-page traffic up; 50 trial sign-ups from new prospects.

During (launch day). Email, blog, in-app banner, and Wren's outreach all go live the same morning. One story, four places.

After (weeks 5–7). Adoption hits 34% — past target. Sign-ups land at 41, short of 50, so Imogen digs into the funnel (Topic 7) and finds the landing page converting weakly. She and Devesh tighten the headline. Brigid sends a thank-you note that becomes a testimonial. The launch worked, and Imogen can prove it with numbers instead of adjectives.