Launch in Seven Days: A Day-by-Day Plan for a Product That Already Works
A seven-day launch is for a product that already works for a stranger. Spend days one and two making the page understandable, days three and four warming up ten named people, publish once on day five, add one community on day six and read the numbers on day seven. The week succeeds if you finish it knowing what to change, whatever the traffic.
Is this week for you?
It is for a product that already works for a stranger and has a small amount of evidence behind it: a few people who tried it. It is not for building; if the main task is not finished, the weekend plan is the better first step. It is also not a thirty-day plan squeezed into a week. Seven days leave room for one public launch and one follow-up, nothing more.
Before day one, block thirty to sixty minutes a day on the calendar, and one longer slot for day five. A week works because every day has one job. A day with two jobs is a day where neither gets done.
Days one and two: make the page understandable to a stranger
Day one is for the sentence. Write who it is for and what it does, then read it to someone who knows nothing about it and ask them to say it back. Rewrite until they can. The launch copy generator drafts options, and what makes a good product tagline lists the common failures.
Day two is for the page and the plumbing. The top of the page shows the sentence, one screenshot and one button. Make a separate tagged link for every place you will share, and check that your visit counter records them. Open the page on a phone and in a private window and fix the first thing that looks wrong. Write the contact address on the page, since interest has nowhere to go without one.
Days three and four: warm up ten named people
A public post with no one expecting it is a cold start. Make a list of ten real people, each with a name, a reason and a channel: someone who has the problem, someone who writes about the field, someone who will tell you the truth. Ask them for a small thing that does not involve a vote, such as trying the main task and replying with one sentence on where it felt unclear.
Hi [name], I made [product], which [one sentence]. I am putting it live on [day]. Would you try [the main task] and tell me the first thing that confused you? It takes about [two] minutes. No need to share it or vote on it. Here is the link: [tagged link]. Thank you either way.
On day four, read the replies and fix only what at least two people tripped on. Resist new features. If nobody on the list replies, that is early information: the sentence may be wrong, or the list may be the wrong people. Better to learn it now than on a public page.
Day five: publish once, and stay
Pick the place that costs the fewest steps, because day five belongs to replies, not forms. The free launch board has no queue and no account; fill in the form, open the emailed link and press Publish. An unconfirmed launch is deleted after 24 hours, so confirm it the same day. Then open your own listing as a visitor would and check the tagline, category and link.
- Reply to every comment the same day, in your own words, with an answer and not a link.
- Message your list with the live link and thank the ones who tried it.
- Do not post anywhere else today. One thread you can finish beats three you cannot.
Days six and seven: add one community, then read the numbers
On day six, post in one community where the problem is discussed, after reading its rules. Lead with what you learned from the first visitors, not with the product name. If you are unsure which place fits, subreddits for sharing your project and indie maker communities list options with what to check before you post.
On day seven, put the numbers in one table: visits per tagged link, tasks finished, replies, and anyone who came back. The directory traffic calculator makes the comparison quick. Write three lines: what worked, what confused people and what you will change. Then decide what the next seven days are.
What should this week skip?
- A launch video: it costs two days and rarely changes whether a visitor tries the product.
- A paid queue skip, which sells position for a product that has not yet shown it converts.
- A press email. A week-old product with a handful of users does not yet have a story.
- More than two public posts. Replies decide the week.
To see how concrete a one-line description can get, read the productivity ideas people have posted on the board. For a longer arc with gates, see the thirty-day launch plan.
Frequently asked questions
Is seven days enough to launch a product?
Yes, for a product that already works for a stranger. One day for the sentence, one for the page, two for warming up ten named people, one public launch, one community post and a review is a full week. It does not leave room for building, so use the weekend plan for that.
Which day should I publish?
Day five, once the page is understandable and a few people have tried it. That leaves days one to four for preparation and days six and seven for a follow-up and a review. Pick the weekday on which you can be online for hours, since replies decide the week.
Who should be on my list of ten people?
Real people with a reason: someone who has the problem, someone who writes about the field, and someone who will be honest. Ask each for one small, specific thing, such as trying the main task and naming what confused them. Do not ask for votes or shares.
What if nobody replies during the warm-up?
Treat it as information. The sentence may be unclear, or the list may be the wrong people. Rewrite the sentence, replace half the list with people who have the problem and try again before you publish. Learning this before a public post is cheaper than after one.
Written by Post your build ideas with AI assistance and edited for this site. Where a page names another product, the facts came from that product’s own pages on the date shown above; terms change, so check them before you rely on them. About the publisher.