Guide
30-day app launch plan for solo developers (week by week)
Published April 30, 2026 by ChannelScout
Most solo dev launch advice falls into two categories. Vague motivation ("just ship it") or overwhelming tactics lists with no sequence. Neither helps you when you're one person with 10 hours a week and an app that's ready to go.
This is the actual sequence. 30 days. Four weeks. Each week has a specific job. Do them in order.
Before you start: two things to get straight
One: define "launch success" in advance.
Not "go viral." Something specific. 50 signups. 10 paying customers. 200 upvotes on Product Hunt. Pick a number before Day 1 so you know what you're actually working toward. Vague goals produce vague effort.
Two: pick your primary channel.
You have 10 hours a week. You cannot do everything. Reddit, Product Hunt, X, YouTube, Instagram, newsletters, Discord. That's 7 channels. Running all 7 at 10 hours a week means each one gets 85 minutes. That's not a strategy. That's noise.
Pick the one channel with the best fit for your product and your target user. Do that one well. Maintain the others with whatever time is left.
Week 1: Foundations
Week 1 is not about posting. It's about building the infrastructure that makes everything else work.
Day 1: Verify your site in Google Search Console and Bing Webmaster Tools
Go to search.google.com/search-console. Add your property. Verify via DNS TXT record at your registrar. Submit your sitemap.xml. Then go to bing.com/webmasters and do the same thing. 30 minutes total. Bing feeds ChatGPT Search and a chunk of Perplexity queries, so this is AEO work too, not just SEO. Do it once, benefit for months.
You'll come back to Search Console in Weeks 2-4 to verify indexing and pull search queries that feed your content roadmap. Setup is a one-time task. Reading the data is a weekly habit.
Day 2: Submit to indie launch directories
BetaList, Uneed, Tiny Launch, Hunted Space, and a post in the Indie Hackers forum are the standard starting points. These are mostly copy-paste form submissions. Budget 45 minutes. Long-tail discoverability that keeps paying out for weeks after you've moved on to other things.
Day 3: Research your communities
Before you post anywhere, you need a short list of communities where your target user already exists. Not communities where your app category exists. Communities where the specific person who has the specific problem your app solves is already active and already talking about it.
Search for the frustration your app solves, not the solution it provides. If you can find 3 or more threads in the past 6 months where someone asked a question your app answers, that community is warm. If you can't find any, it's cold. Move on.
For the full methodology on finding the right communities for any kind of app, see how to find communities for your app launch.
Build a list of 4-5 communities before you post anything. This step saves you weeks of posting into the wrong places.
Day 4: Set up your accounts in those communities
Whatever platforms your target communities live on, get your profiles set up today. Real name or founder name. One-line bio that explains what you build and who it's for. Don't post yet. Just exist there with a complete profile.
Day 5: Start warming up your communities
Cold posting almost never works. Most platforms have minimum activity requirements. All of them have unwritten norms about self-promotion from new accounts.
Start commenting. Answer questions. Add something genuinely useful to existing threads. You're not promoting anything yet. You're showing up like a member, not a marketer. Do this for at least a week before you post about your product.
Day 6: Research newsletters in your space
Find 5 newsletters that cover your niche. For each one, check: when did they last publish, do they feature tools, and is there a submission form or sponsor slot? This list becomes your outreach targets in Week 2.
Day 7: Log what you found
Which communities felt active? Which ones had people talking about your exact problem? Write 3 sentences. This is your baseline.
By the end of Week 1: search tools verified, directory submissions done, a short list of 4-5 target communities, accounts set up, warmup started, newsletter targets identified.
Week 2: First real posts and outreach
Week 1 was setup. Week 2 is where you start putting things in front of people.
Post in your top community
Lead with the problem, not the product. The posts that convert tell a real story. They make the reader feel seen before they make them curious about the solution.
The angle that works: "I built this because I kept running into this specific problem and couldn't find a good solution." Not "I built this because I thought there was a market opportunity."
Be specific. Name the exact frustration. Keep it under 300 words. The first 2 sentences do most of the work. Reply to every comment in the first 2 hours.
Newsletter outreach: send 3 pitches
Take your Week 1 list and pick the 3 best fits. Write a 4-5 sentence pitch for each one. Offer a guest piece or a short write-up they can feature. Keep it specific to their audience. Send all 3 on the same day. One reply is a win. If you get no reply by Day 5, send one follow-up to your top pick only. Then move on.
Post a thread on X or LinkedIn
Pick whichever platform your target user actually uses. Write about the real reason most launches in your category fail. Lead with a number or a specific fact. Keep each post short. Stay online for 30 minutes after posting to reply to anyone who engages.
Join 2-3 Discord servers or Slack groups in your niche
Find the ones with active #showcase or #tools channels. Join them. Read for a few days before posting. You're learning the norms.
Set up your Product Hunt "coming soon" page
Product name, tagline, short description, thumbnail. Submit for review. This gets you on the upcoming feed and lets people subscribe before launch day. Do this at least 10 days before your planned launch date.
Find 5 early supporters
Message 5 people you've genuinely engaged with this week. Tell them you're launching on Product Hunt soon and you'd appreciate their support. Short message, no template feel. Save their names. These are your launch crew.
Verify your pages are getting indexed
Open Search Console. Go to the Pages report under Indexing. Compare the "Indexed" count to the number of pages you actually expect (homepage, /start, /pricing, every guide, /about, etc.). If anything you care about is missing or shows as "Discovered, currently not indexed," paste the URL into the URL Inspection tool at the top and click "Request indexing." Google usually picks it up within a few days.
5-10 minutes. Catches the most common SEO mistake of week 1: the page is live but Google never crawled it.
By the end of Week 2: first community post live with real engagement, newsletter pitches sent, a social thread posted, Discord or Slack servers joined, Product Hunt coming soon page up, 5 launch supporters confirmed, all pages indexed in Search Console.
Week 3: Double down and prepare for launch
Week 3 has one job: figure out what's working and put more weight on it. And get everything ready for launch day.
Check your numbers across every channel
Which post drove the most clicks? Which community produced the most genuine replies? Write 3 bullets. One channel outperformed the others. That's where your remaining time goes this week.
Post in the community that felt most active
Find a thread where someone is asking about the problem your app solves. Leave a genuinely useful reply. If mentioning your app fits naturally and the community rules allow it, you can do it in one sentence. Don't force it.
Send newsletter follow-ups
Check replies from Week 2. If anyone replied, send the draft immediately. If no replies, send one follow-up to the top 2 on your list. Two follow-ups max, then move on.
Post a launch teaser
7 days out from your Product Hunt date. Tell people something is coming. What it does. Who it's for. Why you built it. One hashtag max. Reply to everyone who comments.
Find a Product Hunt hunter
Search producthunt.com/leaderboard, filter by this month, find hunters with 500+ followers who hunt products in your category. Send a short DM. 3 sentences: who you are, what your app does in one line, ask if they'd hunt it. Send to 3 people.
Finalize your Product Hunt assets
Thumbnail (240x240), 3-5 product screenshots, tagline under 60 characters. Write your maker comment in advance. Answer: what problem it solves, who it's for, what's included, why you built it. Under 150 words. Save it where you can paste it instantly on launch day.
Pull search queries from Search Console
Open Search Console. Go to the Performance report. Set the date range to the last 28 days. Look at the Queries tab.
Some of these queries will be ones you intentionally targeted. Most won't be. The unintentional ones are gold. Google is telling you what real people are searching for that brought them to your site, even before you wrote anything specifically for it.
Take any query showing impressions in the past month and feed it into your topic research. Run it through Topic Finder if you're using ChannelScout, or just write down the question the searcher was probably asking. Each one is a candidate for a dedicated guide.
This is how SEO and AEO compound. Every published guide ranks for queries you didn't intend. Each unintended query is the seed for the next guide. The cycle keeps paying out for months.
By the end of Week 3: best channel identified, community outreach done, newsletter follow-ups sent, hunter lined up, all PH assets ready, teaser post live, 3-5 search query candidates captured for future content.
Week 4: Launch and learn
2 days before launch: notify your list
Message everyone who said "let me know when you launch." Check your DMs, Discord replies, newsletter signups, any waitlist. Short message: what's launching, when, what they get for showing up early. 2 days notice, not 2 hours.
Launch day
Submit your Product Hunt listing at 12:01am PST. That's when the daily ranking resets. You want the full 24 hours. Paste your maker comment immediately. Post your launch announcement wherever you've been active. No cold posting into new communities today. Only go where you've already shown up.
Reply to every Product Hunt comment within 20 minutes for the first 6 hours. That's the whole job today.
Day after launch: post your results
Exact numbers. Upvotes, sales, where traffic actually came from. What worked, what didn't, what surprised you. This post almost always outperforms the launch post itself. People trust honest post-mortems more than launch announcements.
Pull Search Console queries again
Same drill as Week 3. Open Search Console, look at the Queries tab, capture anything new. Launch traffic and any press coverage tend to surface queries that didn't show up the week before. Each one is another guide candidate.
From here on, this is your weekly cadence. Every Monday or Friday, 5 minutes in Search Console, capture rising queries, add the strongest ones to your content backlog. Compounds over months without much ongoing effort.
Final days: review and plan Month 2
Answer 3 questions. Which channel drove the most clicks or sales? Which task took the least time for the most return? Which channel are you dropping because it produced nothing?
Write your Month 2 plan in 5 bullets. One channel gets 60% of your time. You now have 30 days of real data. Use it.
The full sequence at a glance
- Week 1: Search Console and Bing setup, directory submissions, community research, account setup, warmup started, newsletter targets identified.
- Week 2: First community post, newsletter pitches, social thread, Discord or Slack joins, Product Hunt coming soon page, launch crew outreach, indexing check in Search Console.
- Week 3: Analytics review, community posting, newsletter follow-ups, X teaser, hunter outreach, PH assets finalized, Search Console queries pulled into content backlog.
- Week 4: Pre-launch notifications, launch day execution, results post, Search Console queries pulled again, Month 2 plan.
30 days. One person. No team required.
The sequence matters as much as the tactics. Week 1 without Week 2 warmup means cold posts. Week 4 without Week 3 prep means a weak launch day. Do them in order.
Skip the hardest step in Week 1
The step most people underestimate is Day 3: finding the right communities before you launch. That's the difference between traction and silence. ChannelScout gives you a ranked list of the rooms where apps like yours already got real users. Communities, newsletters, video platforms, wherever your people actually are. $19 one-time, includes a Launch Blueprint plus 30 days of Scout to keep iterating. It won't replace the warmup work, but it tells you exactly where to show up.
Start your Blueprint