A launch playbook for solo founders: the four-week arc

Most launches underperform because they're treated as a single day rather than a four-week process. A launch is not the reveal at the end. It's a campaign that starts a month before and continues for two weeks after. This is the working playbook we use and recommend.

One important shift in 2026: a launch is no longer a single one-shot event. On Shippin, a product can launch many times. You can ship a closed-beta launch this quarter, an open-launch a few months later, and a major-feature launch after that. Each one gets its own page, its own weekly leaderboard slot on /launches, and its own chance to earn a top-3 weekly or monthly award. The four-week arc below applies to each launch event.

The four-week arc

The strong launches we've seen, the ones that drive real signups and compounding traffic rather than just a traffic spike, all follow a similar shape:

• Weeks −4 to −3: Finalize the product, write the announcement post, line up the launch channels.
• Weeks −2 to −1: Seed the narrative. Tease features, collect testimonials, warm up your audience.
• Launch day (Tuesday, Wednesday, or Thursday): The coordinated push.
• Weeks +1 to +2: Follow through with retros, metrics, and lessons. This is where most of the compounding happens, and where any awards from the weekly leaderboard land on your profile.

Four weeks out: the foundation

Decide what "launch" means for your product

A launch has to be concrete. "We're launching our platform" is vague and nobody will remember it. "We're opening the waitlist. First 500 get free access for a year" is specific, memorable, and gives people a reason to act on launch day.

Strong launch framings include:

• Going from closed beta to public beta
• Opening signups with a specific incentive for early users
• Shipping a major feature with a clear before/after
• Reaching a milestone worth celebrating (1,000 users, first $1K in revenue)
• Public API release, SDK release, mobile app release

Pick your launch day

Tuesday, Wednesday, or Thursday. Mondays are inbox-triage days for most people. Fridays sink because reach dies into the weekend. If you're launching on Product Hunt, aim for a Tuesday or Wednesday, when fewer big players launch.

Avoid the week of a major industry event (WWDC, Google I/O, major Apple or Google keynotes), major holidays, and the week between Christmas and New Year.

On Shippin, schedule the launch event in advance so it appears under Upcoming on /launches. The countdown chip on your product profile turns the wait into part of the story, and people who follow the product get a heads-up when the launch goes live.

Write the announcement post first

Write the post you'll send to your list and pin on your profile before you do anything else. This forces you to clarify the story. If you can't write a crisp 200-word announcement, you don't know what you're launching yet.

Two weeks out: seeding the story

Tease specifics, not hype

"Big news coming soon!" is worthless. Specifics create anticipation. Share screenshots, preview features, show a demo to 20 people and post what they said. The goal is to make launch day feel inevitable, not surprising.

Line up your channels

On a shared doc, list every channel you'll use on launch day. For a typical solo launch:

• Your main social platform (X, LinkedIn, or Threads)
• Shippin build log with the launch announcement, and the matching /launches event
• Product Hunt launch (if applicable)
• Relevant subreddits, pre-check rules, never post twice
• Hacker News Show HN (if product has technical substance)
• Indie Hackers milestone post (if there's revenue to report)
• Your email list
• Slack/Discord communities you're actively part of, the real ones, not spam
• Direct DMs to 20 people who asked to be notified

Collect testimonials and quotes

If you have beta users, now is when you ask for quotes. Reach out to 10 people, ask for two sentences, and use them on launch day. Specific quotes beat generic ones; a testimonial that mentions a concrete use case is worth five that say "great product."

One week out: the dress rehearsal

1. Check every link. Pricing, signup, docs, demo video. Assume at least one will be broken on launch day if you don't verify now.
2. Write all launch-day posts in advance. You'll be too frazzled on the day to write well. Draft every post, every tweet, every email, and schedule or pre-load them.
3. Set up monitoring. Real-time analytics, error reporting, server capacity. If you get a surge, you need to see it.
4. Prepare the post-launch retro doc. You'll want to capture numbers while they're still live. A simple doc listing signups, conversion, sources, top tweets, errors caught, ready to fill in.
5. Sleep. Actually. The launch lasts days; tired judgment is worse than no launch.

Launch day

The first hour

Post on your main social platform first. This is the post you'll link everywhere else. Then Product Hunt if you're launching there. Then email your list. Then the communities. The sequence matters because each channel will reference the others. On Shippin, your scheduled launch flips from Upcoming to This Week automatically, so the leaderboard starts working for you the moment the clock strikes.

The first four hours

• Reply to every comment and DM. Not later, now.
• Share progress metrics in public if they're good ("We just hit 500 signups in 90 minutes")
• Don't chase rankings obsessively. Refresh Product Hunt once an hour, not once a minute.
• Have someone (a friend, cofounder, or partner) watching your DMs for anything urgent.
• On /launches, ranking is by trust-weighted upvotes. A vote counts toward the leaderboard if the voter has an aged account (≥7 days), an existing post older than 24 hours, or a follow-graph relationship. So invite real builders, not anonymous throwaways.

The rest of the day

Keep replying. Post two or three update posts throughout the day with real numbers and highlights. Thank specific people publicly. The people who comment on launch day become your most durable supporters, so acknowledge them.

Week +1 and +2: where compounding happens

The launch itself drives a spike. The follow-through is what converts that spike into a durable asset. Most founders skip this part.

Write the retrospective

Within 72 hours, write an honest retro. Real numbers. What worked. What didn't. A well-written retro is the single most durable piece of content you can produce; it ranks in Google, it gets shared by other founders, and it builds the credibility that compounds for years.

Include:

• Signups by source (X vs Product Hunt vs HN vs email vs Reddit)
• Conversion rate from visit to signup, and signup to activation
• Top content that drove traffic
• What you'd do differently
• Genuine surprises, positive and negative

Convert launch-day momentum into recurring habits

A good launch buys you two weeks of unusual attention. Use it to establish the habits you want to sustain, like publishing a weekly build log on Shippin, posting Friday retrospectives on X, answering Reddit comments in the communities that brought you users. If you return to silence after launch, everything you gained decays.

Close the loop with new users

Email everyone who signed up in the first 72 hours. Ask them one specific question: "What were you hoping Shippin would do when you signed up?" The answers are worth a quarter of user research. Act on them in the following week.

Common failure modes

• Launching before you're ready. A launch with a broken signup flow or an unclear value proposition is worse than no launch. The week you spent rallying attention is gone, and the leaderboard slot is gone with it.
• Going too quiet for two weeks before. "Saving up" for the launch usually means your audience has moved on by the time you post.
• Obsessing over one metric. Product Hunt rank is a proxy, not the goal. The goal is durable signups and feedback.
• Skipping the retrospective. You've just generated 2–4 weeks of data about what works. Not writing it up wastes that.
• Treating the launch as the finish line. It's the starting gun.

How Shippin fits a launch

Shippin is designed to carry the launch arc as a single narrative. The product profile exists from day one. The waitlist sits on the product profile. Build logs accumulate in the lead-up. On launch day, the product profile becomes the landing page for new users, already populated with weeks of development history. An interactive iframe demo lets visitors click and type the running product right there on the profile, so they can try it before they sign up rather than watch a video.

Around launch day, four things on Shippin do real work:

• /launches with three tabs. This Week ranks live launches by trust-weighted upvotes. Upcoming gives you a countdown. Past Winners is the persistent archive. Schedule your launch in advance to take a slot in Upcoming, then ride the weekly leaderboard once it goes live.
• Multi-launch model. A product can launch many times. Closed-beta, public-launch, major-feature relaunches all get their own event row, their own leaderboard week, and their own shot at a top-3 award. Awards stack on the profile rather than overwriting each other.
• Persistent badges. Top-3 weekly and monthly winners earn awards that stay on the product profile and the maker's profile. Past Winners is searchable, so earned credibility compounds rather than disappearing once the spike passes.
• Embed badge. Once you have an award or a leaderboard slot, paste the live SVG badge into your own landing page. It's three variants and two themes, served fresh from Shippin every time it loads.

You still want Product Hunt for the launch-day spike and Reddit for long-tail SEO. But the continuous build-in-public thread, the thing that makes launch day feel earned rather than sudden, lives naturally on Shippin. Start a product profile on Shippin as soon as you start building. By the time you're four weeks out from launch, you'll have a foundation to launch from.