A launch is a distribution event, not a publish event
Shipping the code is the easy part. The work is getting the right capability in front of the right developers, through every channel where they already pay attention, on a coordinated timeline, with the assets ready for each one. A changelog post and a single tweet is not a launch. It is a release that quietly happened.
I treat a launch as a planned sequence where the narrative, the demo, the docs, the social, and the founder's posts all point at the same thing and reinforce each other. I ran this for OpenMeter's launch weeks and for Mutagent's Helix launch. The pattern holds every time: the announcement is the smallest part, and the distribution around it is what decides whether anyone shows up.
What counts as a release worth launching
Not every release deserves a launch, and pretending otherwise trains your audience to ignore you. A release earns a launch when it changes what a buyer can do, not when it changes a version number. New capability, new workflow, a limit that no longer blocks them.
A refactor, a dependency bump, a minor flag, and most point releases belong in the changelog where the people who care will find them. Part of my job is telling you which releases are the big ones and saving your firepower for those. I walk through the full framework in the [devtools launch playbook](/blog/devtools-launch-playbook).
The narrative, and the content that carries it
A launch rests on a clear story: what changed, who it is for, and why it matters to an engineer who is evaluating it skeptically. I build that narrative first, then turn it into the assets that carry it, the announcement post, the social series, the founder's posts, and the framing for the demo.
This is the same content discipline I run everywhere, pointed at a single moment. The announcement is written to be understood and shared by a technical reader, the social is written natively for each channel instead of the same link pasted five times, and the whole sequence is built so it can be quoted, which matters now that buyers ask an AI before they ask you.
The channels, including the risky ones
Developers gather in specific places on launch day: Hacker News, the right subreddits, X, your own newsletter and social, and sometimes Product Hunt. Each has its own culture and its own way of punishing anything that smells like marketing. I prep the launch for the ones that actually fit, with content worth posting and a plan for showing up as a participant rather than a drive-by.
Hacker News and Product Hunt in particular are amplifiers, not origin stories, so they land far better when you already have real usage and a real story behind the release. I will tell you honestly when a channel is worth the effort and when it is a party that pays nothing.
Measured against pipeline, not upvotes
A spike on a launch aggregator feels great and pays nothing. I measure launches against whether they created conversations with people who could actually buy, and whether signups turned into real usage, not how many people clapped on launch day.
If a launch did not put your product in front of the right developers and move some of them toward trying it, it was a party, not a launch, and we use that to make the next one better.
How an engagement runs
Launches run either as a focused engagement around a specific release or as part of an ongoing content retainer, from 5,000 dollars a month. I am one person with GTM experience inside more than 30 devtools companies, so you are working with me, not an agency pod or a junior drafting your announcement.
The work is launch strategy and content: the narrative, the assets, the channel plan, and the measurement around a specific moment. I am American, based in Spain, and I cover EMEA and North America without you doing timezone math.
What this covers
A launch narrative built on what actually changed and why an engineer should care
The announcement post and blog content, written to be understood and shared by a technical reader
A social series across the channels your buyers read, written natively for each one
Founder and exec posts timed to the launch, ghostwritten in their real voice
Hacker News and Product Hunt prep for the launches where they genuinely fit
A launch-week sequence that coordinates the narrative, demo, docs, and social
A plan to measure the launch against pipeline and real usage, not upvotes
“She played a key role in shaping our marketing efforts, from content and social to our launch weeks. She brought creativity, structure, and energy that helped us punch above our weight and tell our story effectively.”
PETER MARTON · CO-FOUNDER, OPENMETERQuestions on this service
How do you launch a developer tool?
You treat it as a distribution event, not a publish event. Shipping the code is the easy part, so the real work is the narrative, the content, and the coordinated sequence that gets the right developers to actually try it on launch day. I build the story first, then the assets and the channel plan around it, and I build pre-launch attention before the date, because most of the evaluation happens before anyone talks to you.
What makes a release worth launching?
A release is worth a launch when it changes what a buyer can do, not when it changes a version number. If a developer can now solve a problem they could not solve yesterday, that earns a launch. A refactor, a dependency bump, or a minor flag belongs in the changelog, and launching everything just trains your audience to ignore your signal.
When should we start planning the launch?
Earlier than most teams think, usually three to four weeks before the date. Most of the evaluation happens before anyone talks to you, so the narrative, the pre-launch attention, and the assets all need to be in motion while engineering is still finishing. Coming to me the week before means we ship the announcement on time and skip everything that makes a launch actually land.
How do you measure a launch beyond upvotes?
Against pipeline and real usage, not applause. A spike on a launch aggregator feels good and tells you almost nothing about whether the right developers showed up. I track signups that turn into actual usage and the conversations the launch created with people who could buy, then use that to make the next launch better.
Related quests
Need this handled?
Tell me where this is stuck at your company and I'll tell you honestly whether I can move it.