skip to content
← blog

a launch is a spike, not a channel

5 min read

i launched mypage.cc on product hunt. i launched screenfine on daniellaunches and it won daily winner.

screenfine is pre-revenue. i say that in public because the alternative, saying nothing, lets people assume a daily winner badge means something arrived in a bank account.

what a launch actually gives you

a day of attention and a permanent link.

the attention ends. it ends faster than you expect, and the graph afterwards looks like a failure even when nothing went wrong, because you are comparing every normal day to the one abnormal day.

what stays is more useful than the spike, and nobody talks about it:

a page that ranks. the launch listing itself sits in search results for your product name basically forever. that is free credibility to anyone who looks you up later.

comments from people with no reason to be nice. this is the real prize. the top comment on my screenfine launch asked for scheduled lock windows, a doom block. that one comment reordered my roadmap. i had spent weeks on features nobody asked about and the first strangers to touch it pointed at the same missing thing.

proof you finished something. underrated. most side projects die at 80%. a launch is a forcing function that drags the last 20% out of you: the privacy policy, the screenshots, the pricing page you kept postponing.

what it does not give you

users, past week two.

the mistake i made, and i think most people building alone make, is treating launch day as the start of distribution. it is the end of building. distribution starts the next morning and looks completely different: search, content, comparison pages, being the answer when somebody asks a question somewhere.

that work is slow and boring and produces no dopamine, which is exactly why the launch feels like the important part. it is not. it is the cheapest and most fun part, so it gets all the attention.

the mistake underneath the mistake

i launched twice in one summer, and both times i did the same thing: shipped, launched, then went and built the next feature.

what i should have done after the spike was distribution work on the thing that was already live. instead the graph went flat, flat felt bad, and building felt good, so i built.

that is not a strategy. that is choosing the activity with the better feeling attached to it and calling it work.

what i would tell someone about to launch

do not save it up. i see people delay a launch by months for polish nobody outside their head is measuring. launch earlier, with less, and use the comments to decide what the polish should have been.

write down what you expect. a number, before the day. otherwise whatever happens will feel simultaneously like a triumph and a disaster depending on your mood at 11pm.

plan the week after. not the day. the week after, in advance, on the calendar, before you launch, because you will not be in the mood to plan it once the spike is over.

expect one useful comment. not fifty. one. mine was worth the entire day.

where this leaves me

two things live. one badge. one product with no revenue yet and a roadmap now set by a stranger’s comment.

that is not a success story or a failure story. it is the normal middle, which is the part that never gets written up because there is no screenshot to attach to it.