Spend week one on people, not features. Answer every comment fast, post in one community you skipped, list the app in 5 to 10 places, ask your first users four questions, and fix the one thing that blocked the most of them. Below is a seven day plan to paste into a note, a description template and a survey you can send tonight.
Week one is for distribution and your first users, not new features
Most launch advice piles the effort into the first 72 hours and plans nothing after that. Create.xyz lists this as a common launch mistake: too much energy on the product, too little on distribution.
Shipping is easy now. Getting users is the hard part, and week one is where it starts. Put days 1 to 7 on the calendar before you launch, the same way you booked the launch itself.
Paste this seven day plan into a note
Each day gets one job and a time box. If you have a day job, each fits in an evening.
- Day 1 (60 min): Answer every comment, email and message. Write down each question people ask.
- Day 2 (30 min): Answer what came in overnight. Turn the three most repeated questions into a short FAQ list.
- Day 3 (60 min): Post in one community you skipped on launch day, as a lesson, not a repeat of the launch post.
- Day 4 (90 min): Submit to 5 to 10 directories and newsletters with one prepared description. Log each one.
- Day 5 (60 min): Message the people who showed interest before launch, one each, with one question. Send the four question survey to everyone who tried the app.
- Day 6 (90 min): Fix the one thing that blocked the most people.
- Day 7 (60 min): Publish a short "one week later" recap and check visits and signups per channel.
Then ship one visible update by about day 14. The DEV Community launch checklist puts the feedback-based update at that mark, so early users see you listening.
When you run out of time, drop things in this order
- Keep the replies (days 1 and 2) and the fix (day 6). Everything else depends on them.
- Cut the recap (day 7) next. It is the cheapest thing to do in week two.
- Cut the directories (day 4) last. Five good listings beat ten rushed ones.
Reply inside 30 minutes while the thread is alive (days 1 and 2)
Answer comments the same day. Inside 30 minutes is better. Create.xyz's playbook puts it as 50 engaged comments beating 200 silent upvotes, and a thread that sits for hours can lose the early audience you worked for.
Set a phone alert on your launch thread and answer on breaks.
Keep one plain list of every question people ask. Those questions are your FAQ and your next post. If three people ask how to export their data, that is a page, not a coincidence.
Post again in a community you skipped, with a lesson (day 3)
Pick one community you did not post in on launch day. Come in with a different angle: "what I learned shipping X" or a short how-to. Do not paste your launch text again. The same text in five places can read as spam and get you removed.
Read that community's self promotion rules first. The Reddit guide on this site has the full rule set, and the core holds on most forums: help first, say you built the app, link only where the rules allow it.
List the app in 5 to 10 places, not 100 (day 4)
Free launch lists run to the hundreds. One on Indie Hackers has 261. Skip the long list. Ten to twenty relevant listings beat a hundred spam submissions, so cap week one at 5 to 10.
Pick by who reads the place, not by the visitor numbers it advertises. A curated indie feed that reviews submissions beats a giant list with no review. Skip any place that asks you to pay in week one: you can finish this whole plan for free.
Write one description and paste it everywhere
Keep it to 50 to 100 words that say what makes the app different. Copy this template and fill the brackets:
[App name] helps [who] do [one task] without [the usual hassle]. It is free to try. [One line on how it is different]. Feedback welcome: [link].
Write it once. If you rewrite it for each site, your message drifts and you cannot tell which version worked.
Track what each listing sends
Make a table with one row per listing. A week later, fill in visits and signups, then divide signups by visits.
Example: say you submitted to three places. These numbers are illustrative.
| Listing | Visits | Signups | Signups / visits |
|---|---|---|---|
| Small curated indie feed | 45 | 6 | 13.3% |
| Newsletter submission | 120 | 9 | 7.5% |
| Big general directory | 400 | 8 | 2.0% |
The big directory sent the most traffic and the worst rate. The small feed sent the least traffic and the best rate. In week two, look for more places like the small feed, not the biggest one.
Message the people who knew you before launch, one at a time (day 5)
Waitlist signups, friends who said they would try it, people who replied to your early posts: write to each one. One message each, not a blast.
Ask one specific question about the app and do not pitch. For example: "You said the invoice step looked confusing in the demo. Did it make more sense once you used the real thing?" It costs you one evening and these are the people most likely to answer.
Send four questions and read the answers as reasons (day 5)
Put a short form behind a link in your reply, a welcome email or the app. Send it to people who signed up or tried the app, not to people who only saw the post.
- How would you feel if you could no longer use [app]? (Very disappointed / Somewhat disappointed / Not disappointed / I no longer use it)
- What is the main benefit you get from [app]?
- What would you use if [app] were not available?
- What is the one thing we could change to make it better for you?
Question 1 is the Sean Ellis question. Over 40 percent "Very disappointed" is the usual sign of a good chance of product market fit. That line is a rule of thumb, not a guarantee.
With fewer than 40 answers, read the words and ignore the percentage
At least 40 respondents are needed before the number means much, and in week one you will probably have fewer. Sort the written answers into themes and fix the theme named most often.
Example: say 10 people answer and 3 say "Very disappointed." That is 30 percent, which tells you almost nothing from 10 answers. What matters is that 6 of the 10 wrote that the signup step confused them. That is your day 6 fix.
When someone says "Very disappointed," ask what they would use instead. Their words belong in your headline and your directory description. When someone says "Not disappointed" or "I no longer use it," ask what stopped them.
Fix the one thing that blocked the most people (day 6)
Pick one fix: an unclear first screen, a long signup, a missing explanation. Do not build the feature one person asked for.
The rule: when two or more people ask for the same thing, it goes to the top of the list. When one person asks, log it and wait. One fix beats a feature list because you can finish it in an evening, and your next visitors see the difference.
Publish a one week recap and send week two to the best channel (day 7)
Write a short post: what you shipped, what people asked, what you changed, what you will change next. Share it in the community from day 3. It gives you a new reason to talk there.
Then check visits and signups per channel. Week two goes to the channel with the best signups per visit, not the most traffic.
Your next ten minutes
Open a note and write your 50 to 100 word description from the template. Do that one thing, then stop.
Want a manual task off your plate this week?
If a repetitive job is eating your launch week, tell me what it is. You get a reply from one person, not a handoff chain. Email Me.
