The cold email after a product launch.
Product-launch signals reward counter-cyclical patience. Most senders fire during launch week — exactly when the company's own marketing is shouting loudest. The window that actually converts opens after the hype dies, before the rep settles back into status quo. The attention curve, three worked examples, and the discipline that turns the second-most-overused signal into a real opening.
What counts as a launch signal.
Launches come in distinct shapes, and the outbound playbook differs by shape. A net-new-product GA opens a 6-week category-spend window. A version bump rarely opens anything. The mistake most outbound teams make is treating every "we just shipped X" announcement as the same trigger.
The four sub-types worth chasing
- Net-new product launches into a new category. Highest yield. The company is establishing a new line of business and needs to evaluate adjacent tooling (CRM for a new GTM motion, observability for a new platform, etc.).
- Public beta → paid GA transitions. Strong yield. The company has committed to monetizing the product, which means it now has revenue lines, pricing tiers, and budget authority for adjacent tools.
- Major version releases (v2 → v3 type shifts). Medium yield. Signals architectural maturity; only useful if your product is downstream of the new version's architecture.
- Acquisition + product re-launches. Strong yield. The acquiring company is rebuilding the launched product's stack for the combined entity — every vendor in the launched product's existing stack is up for review.
The attention curve.
The thesis of this playbook in one chart. Two overlapping curves — the company's own launch marketing (loud, brief) and the recipient's openness to vendor outreach (quiet, delayed). The window that converts is where the second curve is rising while the first has died down.
The single counterintuitive lesson: the noisier the launch (Product Hunt #1, TechCrunch coverage, founder thread), the further to the right the optimal send-window shifts. Big launches have longer hype tails; the counter-cyclical window opens later.
Most outbound teams send during launch week to "ride the moment." The moment isn't yours to ride. The counter-cyclical send is what separates the launch outbound that converts from the launch outbound that gets archived.
Why most launch emails fail.
Four patterns we see across roughly 80% of launch outbound corpora.
- "Congrats on the launch!" as the entire opener. Same dynamic as the leadership-change "congrats" — the company received dozens of these from people they actually know. Yours is indistinguishable.
- Launch-day sends with no operational angle. "Saw you launched X — we help X companies scale!" Reads as not actually having looked at the launch, just the headline.
- Pitching a competitor of the launched product. Tone-deaf at any timing. The team just shipped something; positioning a competitor 7 days later reads as adversarial.
- Ignoring the actual launch type. Sending the same "scale-up" message for a beta-to-GA transition as for a major version bump. The launch type determines the buyer's mental state — generic templates miss the difference.
The 4-line frame, post-hype.
Same skeleton as the other playbooks, but the gating variable is timing. The frame only works in weeks 2–4 — not launch day, not launch week.
are you planning to build this in or partner as the framing.
Three rules:
- Wait two weeks. Always. The launch-day send is the universally wrong move, even when it feels like the right one.
- Reference what you've actually seen post-launch. Real usage observations beat press-release rephrasing. If you haven't used the product, say so honestly.
- Frame as collaboration, not competition. Build-vs-buy framing positions you as adjacent. Anti-competitor framing positions you as a threat to the work they just shipped.
Three worked examples by launch type.
Example 1 · Net-new product GA (Series B SaaS)
Spent some time in Trellix Routes last week — the webhook architecture is a really clean separation between event-source-of-truth and downstream notification, and the rate-limit headers exposed in the response are a level of polish most v1 launches skip.
The pattern most teams who ship this shape hit around month 2: customers want to retry webhooks per-endpoint after their downstream goes down, and "build a retry queue" turns into a 4-week project. We built that exact layer.
Curious if Trellix is planning to build the retry semantics in-house or evaluating partners — usually a Q3 question for products that shipped in Q2.
If useful, I'll send the open-source spec we built it against — it's compatible with Routes' header format. No demo, just the doc.
Jay
Example 2 · Beta-to-paid GA (early-stage startup)
The pricing-page launch caught me — Lumend's choice to ship usage-based as the only tier (no annual fixed-fee option) is the harder right call but a very specific bet on customer acquisition cost.
The pattern at the next 3 founders who shipped usage-only pricing: month-3 churn is fine, month-9 expansion is harder than projected because there's no commitment moment in the year. The fix is usually a "soft commitment" tier added between month 6 and 12.
Are you planning to layer that in eventually, or staying purely usage as a deliberate strategy?
If you want the doc I wrote on the soft-commitment patterns from the other 3, it's 1 page — happy to send.
Samira
Example 3 · Major version release (Series C platform)
Read the v3 release notes — the new event-typed APIs are a real upgrade over the string-based ones from v2, and the migration guide acknowledging "v2 will be supported through Q4 2027" is the kind of honesty most platform teams under-do at major versions.
The pattern from teams who shipped major-version migrations: customer-facing teams ship to v3 in month 1, internal tooling lags by 6+ months because nobody owns the migration. By Q3 most teams have a parallel-version technical debt problem.
Are you handling the internal migration in-house, or has the platform team flagged a partner for the legacy-instance translation layer?
Happy to send the migration-pattern doc from the 5 other v2→v3 transitions we've worked on. 1 page.
Nate
The receipts test.
Every launch email should pass: is there a specific implementation, design, or doc detail in line 1? If no, rewrite. If you can't because you haven't used the product, skip the signal.
When not to use this signal.
- The "launch" is a Product Hunt post or marketing event, not a shipping milestone. Use a different signal on the account; PH launches don't typically open category-spend windows.
- You're outside the weeks 2–4 window. Launch-day sends underperform pure-cold baseline. Late sends (week 9+) revert to baseline. Wait for the next signal.
- You haven't used or read docs for the launched product. The receipts test will fail, and the team will know. Skip rather than fake it.
- You sell a direct competitor to what was just shipped. Anti-competitor framing 2 weeks post-launch reads as tone-deaf at any quality level. Wait 6+ months or pick a different account.