One announcement is not a launch

When a launch lands flat, the first explanation to arrive is that people did not want the thing. Resist that one for a week. There is a duller explanation that turns out to be true far more often: most of the people you were talking to never found out you had said anything at all.

Do the arithmetic on paper. Invent the numbers — yours will be different, and the shape is the part worth looking at. Say you have eight hundred people on your list and twelve hundred followers on whichever social platform you actually use. You write one email and one post. Forty percent of the list opens the email, which is a good rate, so three hundred and twenty people see it. The post gets shown to perhaps eight percent of your followers, so call it a hundred more, and some of those are the same people who got the email. So the whole launch reached something like a third of your audience, once, on a Tuesday when they were busy with their own work.

And "reached" is generous. Seen once is not the same as registered. The email was opened in a lift between two meetings and closed again. The post went past at speed on the way to something else. Nobody was sitting still, waiting to find out what you shipped. This is not apathy and it is not a failure of your copy — it is what one exposure is worth, for everybody, including the companies whose marketing you admire.

A launch is a campaign, not a day

The fix is unglamorous: decide the repeats before you decide the date. Four or five touches spread over two or three weeks, planned at the same time as the thing itself, treated as one piece of work rather than as five separate decisions you will have to find the will to make later.

What those touches must not be is the same message pasted five times. Each one takes a different angle on the same news, and each one has to stand on its own for somebody who missed everything before it. The announcement. Then the problem it solves, told as a situation rather than a feature. Then a worked example with real detail in it. Then the question people kept asking, answered in public. Then, if it is the kind of thing that ends, a plain last call. Five touches, one subject, five different reasons for someone to stop.

saying it twice is not spam, it is arithmetic

The thing that stops most founders here is the fear of being repetitive, and that fear is a trick of perspective. By the time you publish, you have lived with this message for weeks. You wrote it, cut it, rewrote the subject line, read it aloud. You have seen it forty times. Your reader has seen it once, at best, in the middle of a Thursday. The gap between those two experiences is enormous, and it is why the person closest to the work is always the worst judge of how much it has been said. The same asymmetry is behind most of the sending people never do — it is the argument in you are probably under-emailing your list, arriving from a different direction.

There is also an economic argument, and it is the one that usually lands. You already paid for this. The thinking, the building, the writing of the first draft — that cost is sunk. A second and third angle on the same subject cost you an hour each and reach people the first one missed entirely. Compare that to the price of acquiring an equivalent number of new people through ads, and repetition stops looking like laziness and starts looking like the cheapest distribution you have. It is the same instinct as mining the archive rather than always starting blank, which we made the case for in the best post to write next is one you already wrote.

None of this rescues something nobody wants, and you should be careful not to use reach as a permanent excuse. So make the distinction deliberately. Look at the people who definitely saw it — the ones who clicked, replied, opened the page and stayed. If that group is engaging and the totals are still small, you have a reach problem and repetition is the answer. If the people who saw it clearly and did nothing are the bulk of your audience, you have a demand problem, and the fifth email will not fix it. Be honest about how few people that judgement rests on, too: with a hundred openers you are reading a hint, not a verdict.

The practical failure mode for a solo founder is not disagreeing with any of this. It is week two. The launch day energy is gone, something broke, a customer needs you, and the follow-up touches quietly never happen. The only defence that has ever worked is writing them all in one sitting, while the context is hot and you can still remember every objection you heard during the build. Draft the whole sequence at once, then let each piece sit and wait for the day it goes out. This is exactly the shape of work worth handing to an AI draft — five angles on a subject you have already explained once, each one waiting in front of you to approve or throw away, none of them going anywhere until you say so.

So: plan the repeats before you plan the day. A launch you announce once is a launch that most of your audience never attended — and the difference between a thing nobody wanted and a thing nobody heard about is the most expensive mistake to get backwards, because one of them tells you to stop building and the other one just tells you to say it again.