How Do You Plan a Launch for a Product Nobody Is Waiting For?

What does a launch mean when nobody is waiting for your product?

It means a deliberate week of concentrated effort to create the first evidence that anyone cares. Not an announcement, because announcements assume an audience. A first launch is an experiment with a date attached, and the output you should expect is information about who responds, not a spike in revenue.

Almost every founder I talk to plans their first launch as though the second kind exists. They write the announcement, pick the day, and are then surprised when a quiet day follows. The plan was built for a company that already had attention.

So the useful question is what a launch is for when you are starting from nothing, and what you should actually put in the plan.

Why do most first launches produce nothing?

Because they are scheduled as an event rather than designed as a distribution problem. The product goes live, a post goes out, and the plan ends there. Nothing in it answers the only question that matters, which is how a specific group of people who do not know you will encounter this.

The second failure is treating one day as the unit. A launch day concentrates whatever attention you can generate into twenty-four hours, which is useful if you have a list and a network to mobilise. With no audience, that same effort spread across a fortnight of direct conversations will almost always produce more.

The third is measuring the wrong thing. Traffic on launch day tells you how many people you could reach once. It tells you nothing about whether the product is worth reaching them about, and founders routinely read a good traffic day as validation and then wonder why the following month is empty.

What should you decide before you pick a date?

Three things. Who specifically you want to reach, what you want them to do, and what result would make you continue versus stop. Write those down before you choose a day, because the date is the last decision in a launch plan and most people make it first.

Being specific about the audience is where this usually falls apart. Marketers is not an audience. Heads of marketing at ten to fifty person B2B software companies who currently manage their site in Webflow is an audience, because you can list them. If you cannot write a list of actual names or communities, you do not yet have a launch plan, you have a hope.

The stop condition matters just as much. Decide in advance what a disappointing outcome looks like and what you will do about it, because in the aftermath you will be strongly motivated to reinterpret whatever happened as encouraging. This is closely tied to how you choose whether to sell to one vertical first, since a narrow launch produces a much clearer signal than a broad one.

Should you launch on Product Hunt?

Only if your product fits what the platform features, and only as one part of a wider plan. Product Hunt is a real distribution channel with real rules, and the single most common mistake is treating it as a guaranteed audience rather than as a place that decides, every day, what it will show.

The mechanics are documented. Product Hunt's launch guide says 12:01 am Pacific Time is the best time to launch for makers that are planning ahead, while also saying the best day to launch is the day on which you are most prepared. It states the only real rule is that you cannot ask people directly to upvote your product, and that you should instead ask them to visit and comment.

Two more points from the same guide are worth knowing before you plan around a hunter or a company profile. Company accounts are prohibited. And Product Hunt says it encourages makers to hunt their own products, with no discernible advantage to using a third-party hunter. A good deal of launch folklore is built on the opposite assumption.

What does Product Hunt actually feature, and what does it reject?

Its featuring guidelines are specific, and many businesses are excluded outright. Product Hunt says it focuses on digital products and services that are currently available, looking for launches that are useful, novel, high craft or creative, and notes that featured launches do not need to score high in every category.

The exclusion list is the part to read before you build a plan around it. The guidelines exclude waitlisted products unless immediate access is provided, directories or lists, templates, boilerplates, podcasts, courses, reports, events, books, services, commerce sites and stores, deal sites, most Kickstarter projects, and hardware unless it has a prominent digital component.

If you sell services, that list includes you, and no amount of launch-day preparation changes it. The guidelines also say products may be rejected as vaporware when they are not ready for use, and that the moderation team considers reaching out rarely necessary, with additional context not guaranteeing featured status. Plan for the possibility that the channel simply does not apply to your business.

What is a better first channel than a launch site?

Direct conversations with the specific people you listed. Fifty individual messages to people who plausibly have the problem will teach you more in a week than any aggregator, and they produce the thing a launch cannot, which is a small number of people who will answer your follow-up questions.

This is slower and much less pleasant, which is precisely why most founders skip it in favour of a post. But it is the only channel available to you that does not depend on somebody else's audience, and it is where the first ten customers almost always come from. I have written at length about where those first ten customers actually come from, and it is rarely a launch site.

If a few of those conversations go well enough that people will pay before the product is finished, you are no longer planning a launch, you are running a design partner program, and that is a better use of the same weeks. I set out how to structure one in how to run a design partner program before launch.

Communities are the middle ground, provided you were there beforehand. A Slack group, a subreddit, Indie Hackers, Hacker News or a LinkedIn circle all work on the same terms. Turning up to a forum on launch day to announce yourself works about as well as it sounds. Turning up in a community you have participated in for months and saying you have built the thing people kept complaining about works, because you are a member rather than an advertisement.

How long should a launch actually run?

Plan a fortnight, not a day. Use the first week for direct outreach to your list, the second for whatever public surfaces you have earned the right to use, and treat any single platform date as one event inside that window rather than as the window itself.

A longer window also solves a practical problem, which is that you will be wrong about your message in week one. The first twenty conversations will teach you which sentence lands, and you want to still have audience left to use it on. Spending your whole reach on your worst version of the pitch is the most avoidable launch mistake there is.

Keep one thing fixed across the whole window. The product should not change mid-launch, or you will not be able to tell whether a better response came from a better message or a different product. Change the words freely, and leave the thing itself alone until the window closes.

How do you know whether the launch worked?

Count conversations, not clicks. The honest measures are how many people replied, how many took a real action such as booking a call or starting a trial, and how many came back a week later without being prompted. Traffic is an input to those numbers, not a result.

Reply rate to direct outreach is the single most informative number you will get, because it is unfiltered by any platform. A low reply rate on a well-targeted list is not a distribution problem. It is usually a message problem or a product problem, and knowing which is worth more than a busy launch day.

Track the second week separately from the first in GA4, or whatever analytics you run. Whatever survives after the initial push is your actual baseline, and that baseline is what you are building on when you go looking for your second acquisition channel. Launch spikes are borrowed attention and they always get returned.

What should you do next?

Before anything else, write the list. Actual names, actual companies, actual communities. If you cannot get to fifty, your positioning is too broad and that is the problem to fix first, ahead of any launch plan or any date on a calendar.

Then check whether the platforms you were counting on will even accept you. Reading Product Hunt's featuring guidelines takes ten minutes and will save some readers of this article an entire month of preparation for a launch that was never going to be featured. Better to find that out now than on the morning.

Finally, give yourself a fortnight and a stop condition, and be willing to honour it. A launch that teaches you the market does not want this is a successful launch, just not the kind anyone enjoys. If you are planning a first launch and want someone to pressure-test the plan before you commit to a date, reach out.