A Product Launch Plan That Lands Press Without an Agency
Summary
A product launch plan that includes press needs about six weeks of prep, a 25-name journalist list, a one-page kit and a short pitch with a real number in it. Decide what the news is first, pick an embargo or an exclusive, script launch week, and track opens and replies. Skip press when the release has no story, and use your own channels instead.
Most founders write a product launch plan that is 90% Product Hunt and 10% hope. Then launch day comes, nobody writes about them, and an agency pitches them a $12K/month retainer to fix it. Here is the plan I use instead: six weeks, one spreadsheet, about 25 journalists, and zero retainer.
I'm Nico. I run a bootstrapped B2B data tool out of Sydney, and I've documented every press experiment on my Substack, including the three launch pitches that got exactly zero replies. This plan is what survived. The press part is where most plans fall apart, so that is where we start.
Why most launch plans have no press line item
A typical launch plan has a feature list, a landing page, a Product Hunt date and a tweet thread. Press shows up as one bullet: "reach out to media". That bullet is where launches die.
Journalists do not cover launches. They cover news. Y Combinator's guide to pitching launch stories boils it down to three things a story needs: timeliness, credibility and uniqueness. A new button in your dashboard has none of the three. A new product with a clear customer, a real number and a reason to exist this week might have all of them.
So the first job of your product launch plan is not scheduling. It is deciding what the news actually is. If you cannot finish the sentence "This is news because ___" in one line, push the launch back or drop press for this one and save it for the next release.
Skip the press release distribution services at this stage. A wire post to nobody is the cheapest way to feel busy. A pitch to one reporter who covers your exact beat beats it every time.
Week -6 to -4: Build the list before you have a story to tell
Start with the people, not the pitch. You want 25 names, split in three tiers:
Tier 1 (3 names): reporters at the outlets you would screenshot for your homepage.
Tier 2 (10 names): trade newsletters, niche publications and podcast hosts in your category.
Tier 3 (12 names): bloggers, Substack writers and independent analysts who actually reply.
Build it by reading, not by buying a database. Search the last 90 days of coverage in your category, note who wrote each piece and what angle they took. Write one line per person: what they covered, and what they have not covered yet. That gap is your pitch.
If you want a database anyway, the honest comparison is expensive. Muck Rack and Cision are priced for teams with a comms budget, and Prowly sits lower but still costs real money every month. For a first launch with 25 names, a spreadsheet and a free afternoon do the same job.
Skip any tool that promises "10,000 verified journalist contacts" before you know what you are pitching. Contacts without an angle just produce 10,000 ignored emails.
Week -4 to -2: Write the news, not the announcement
This is the part agencies charge for, and the part you can do in an evening.
Your press kit is one page of 500 to 800 words with the hard news in the first paragraph or two. YC recommends exactly that range for a media kit. Put these in it:
One sentence on what the product does and who it is for.
One number that is yours: users on the waitlist, hours saved in beta, revenue, pilots signed.
One founder quote that sounds like a human said it.
Two screenshots and a logo, linked, not attached.
Your availability for calls in the launch week.
Then write the pitch itself. Muck Rack's guidance for pitching tech reporters is to keep the subject line under 50 characters and to avoid hype, because tech journalists value accuracy over marketing buzz. I go shorter than their 200 to 400 word ceiling. Mine run about 90 words.
Here is the structure I copy and paste every time:
Subject: Embargo Tue 9am ET: [one-line news]
Hi [first name], I read your piece on [specific article]. You wrote that [specific point].
We're launching [product] on [date]. [One sentence on what it does]. In beta, [one real number].
Happy to share the full kit under embargo until [exact date, time, timezone]. Want it?
[Name], [role], [phone number]
No flattery paragraph. No "I hope this finds you well". The first line proves you read their work, and the second states the news.
Week -2: Embargo, exclusive or neither?
People mix these up, and it costs them coverage.
An embargo means many reporters get the story early and agree not to publish until a set time. An exclusive means one outlet gets it first, alone. YC is blunt about the difference: an embargo is not an exclusive, because many outlets can hold the same story at once.
Which one you pick depends on your tier 1 situation:
You have one dream outlet: offer them an exclusive for a fixed window. YC suggests giving one or two top-choice journalists one day to claim it, then moving on to the rest of the list under embargo if they pass.
You want a wave of coverage on launch day: go embargo, and send the pitch about seven days before the embargo lifts, with one follow-up two to three days later.
Your news is small: skip both. Pitch the day of, to the few people whose beat it fits, and expect fewer results.
Two rules I never break. First, get the reporter to confirm the embargo and the lift time before you send the full kit. Muck Rack says the same: agree the terms before sharing details, and put the exact date, time and timezone in writing. Second, keep it off your blog and social accounts until the lift. One early tweet burns the whole list.
Launch week: A script, not improvisation
Launch day is not the time to decide who does what. Write the script a week before.
T-1 day: send the full media kit to everyone who confirmed the embargo. Re-check every link and every number in the kit. One wrong figure in a journalist's draft is hard to undo.
Launch morning: the embargo lifts. Publish your own post, send the email to your list, then post on social. In that order, so reporters see your version has the same facts as theirs.
Launch day, all day: answer every journalist within the hour. YC's line on this is worth pinning above your monitor: they probably won't spend more than an hour on your story.
T+1 to T+3: reply to every piece of coverage with a thank-you and one useful follow-up fact. Send the pieces to the tier 2 and 3 people who did not bite the first time, with a short "this ran in X, thought you might want the angle". Do this once. Journalists tell you to follow up once or twice per story at most, and three is the ceiling in YC's guide.
If you want a place to publish your own launch post and keep an email list for the follow-up, a newsletter tool does the job without a CMS project.
What to measure so the next launch costs less
Most founders stop at "we got three articles". That tells you nothing you can repeat. Track these in the same spreadsheet as the list:
Pitches sent, by tier.
Opens and replies. YC treats anything above a 35% open rate as a success, and reports 45 to 50% on its own pitches. If you are far below that, your subject line is the problem, not your product.
Replies by angle. If the "first customer" angle gets replies and the "AI-powered" angle gets none, you have your headline for next time.
Placements, with the date and the referral traffic each one sent.
Hours spent, so you can compare against the agency quote. The honest number for my last launch was about 22 hours over six weeks.
I do not have a clean dataset on average reply rates for founders across all categories, and I will not invent one. The sources I found give open-rate guidance, not reply-rate benchmarks. Build your own over two launches and you will beat any average.
When the plan should say "skip press"
Not every release deserves outreach. Some guides argue that embargoes are only worth it for launches with real news, and that feature updates usually do not warrant proactive media outreach. I agree.
Skip press and put the effort into your own channels if:
The release is an incremental feature with no new customer story.
You have no number you can share.
You cannot be reachable for the whole launch week.
The only angle you have is "we launched".
In those cases your plan is a changelog post, an email to your list and a note to the three newsletter writers who already like you. That is a perfectly good launch. It just is not a press launch.
The six-week plan on one screen
If you only copy one section, copy this one:
Week -6: pick the news, write the "This is news because" line, start the 25-name list.
Week -5 and -4: finish the list with one gap line per name. Draft the one-page kit.
Week -3: write and test the pitch on two friendly reporters or founders who have been covered.
Week -2: send tier 1 pitches. Offer the exclusive if you have one.
Week -1: send embargo pitches to tiers 2 and 3. Follow up once. Lock the kit.
Launch week: script, answer fast, thank everyone.
Week +1: measure, log, decide what the next launch skips.
Total cost: a spreadsheet, a few evenings and a coffee habit. That is the whole product launch plan. The agency version is the same steps with a $12K/month invoice attached. Fire the agency.