The Indie Hacker's Guide to Launching One Idea Per Month

In 2014, Pieter Levels announced he'd launch 12 startups in 12 months. He didn't finish all 12, but two of the products he built during that year -- Nomad List and Remote OK -- became profitable businesses that generated millions of dollars in revenue.

The method wasn't recklessness. It was a deliberately compressed validation loop: not building twelve products, but testing twelve problem hypotheses in rapid succession. Most failed to show signal. Two did. Two was enough.

The one-idea-per-month approach isn't right for every founder or every idea. But it's one of the most effective frameworks for the specific subset of indie hackers who need to find their idea before they can commit to it deeply.

Here is how to do it correctly.

What "Launching" Means at This Cadence

A one-per-month launch is not a product launch. Let's be exact about what it is.

In 30 days, you cannot build, polish, and ship a production-ready product. What you can do -- entirely, from zero -- is:

• Research whether the problem is real (5-10 conversations or community checks)
• Build a landing page with an email capture form
• Drive enough traffic to get 50-200 strangers to the page
• Collect their signups and email them one question
• Measure the reply rate and the quality of replies
• Make a keep-or-kill decision based on real signal

That's a "launch" at this cadence. Not a product. A signal experiment. The product, if any, comes later -- after one of your experiments shows the kind of signal that justifies deeper investment.

This matters because founders who try to build a product in a month produce twelve unfinished products. Founders who run twelve signal experiments produce one or two finds worth building.

The Weekly Structure

Four weeks, four activities. Each week has a clear output. If the output isn't produced by the end of the week, the idea doesn't progress.

Week 1: Problem Research

The output: A written, one-paragraph problem statement that you can confirm from real evidence -- not from your own experience or assumption.

Spend Week 1 on community research and five quick conversations. Not formal interviews -- brief exchanges. A Reddit post asking whether people experience the problem you're thinking about. Five direct messages to people who match the target audience asking "does this problem sound familiar?" A look through existing discussions to see how frequently it comes up and with what emotional weight.

By end of Week 1, you should be able to write: "People who [identity descriptor] consistently experience [problem] when [trigger moment]. The specific thing they find most frustrating about this is [specific language from your research]."

If you can't write this paragraph with actual evidence by the end of Week 1, kill the idea. Move to the next one.

Time required: 8-12 hours across the week, not full-time.

Week 2: The Minimum Page

The output: A live landing page with an email capture form, accessible at a real URL.

This is not a polished landing page. This is the minimum credible page required to capture an email address from someone who has the problem.

Elements:

• One headline (specific outcome or specific problem naming)
• One supporting sentence
• One email capture form with a submit button
• No navigation, no about page, no link to social profiles

Tools: Carrd ($19/year) or a free Webflow/Framer template. Custom domain optional but recommended -- a .carrd.co URL is functional but conveys less credibility than a [productname].com registered for $12.

The page should be live by end of Day 3 in Week 2. Days 4-7 of Week 2 are for the email setup: a welcome email with one question, an email tool (Beehiiv free tier), and the form connected to the list.

Time required: 8-10 hours across the week.

Week 3: Traffic and Signal Collection

The output: 50-200 visitors from outside your personal network, 5-30% conversion to email signups, at least 5-10 email replies to your welcome question.

Drive traffic through two channels maximum. Any two of:

• One Reddit problem post (the most consistent channel for stranger traffic)
• One Indie Hackers post or Product Hunt coming-soon listing
• One Hacker News Show HN if the idea is technical enough for that audience
• Five targeted DMs to people who match the target profile on Twitter or LinkedIn
• One Slack or Discord community post (after the 3-day contribution minimum)

Do not spend money on ads during this phase. If the idea needs paid traffic to get its first 100 visitors, it's not the right idea to spend money on yet.

By end of Week 3, you should have seen at minimum 50 strangers visit the page. If you can't drive 50 strangers to a page in two weeks with the free channels available, the problem niche is either too small or you haven't found the community where it lives.

Time required: 10-15 hours across the week.

Week 4: Measure and Decide

The output: A written keep-or-kill decision with the data that drove it.

This is the hardest week because the decision requires intellectual honesty. Two common forms of failure here:

Premature killing: "Only 18 people signed up, that's not enough signal." The number isn't the signal. The quality of the replies is. If 18 people signed up and 9 of them replied to your welcome email with specific, emotional descriptions of the problem, you have more validation signal than a founder with 200 signups and no replies.

Unjustified keeping: "Signups are low but I still believe in the idea." The month is a forcing function precisely because belief is cheap. Signal is expensive to manufacture. If the signal isn't there after a real traffic test, keep isn't the right call.

The data to evaluate:

Metric	Threshold for keeping
Conversion rate (strangers to signups)	Above 8% from at least one traffic source
Welcome email reply rate	Above 15%
Quality of replies	At least 3 replies with specific, emotional problem descriptions
Any unsolicited sharing	At least 1 person forwarded or shared without being asked

If three of these four are met, keep. If two or fewer, kill and move to next month.

Note "kill" doesn't mean destroy the page. It means don't invest more time in active promotion or product development. Leave the page live. Occasionally you'll see a trickle of signups from organic discovery weeks later. That trickle is data. But your primary attention moves to the next idea.

What This Approach Actually Develops

The benefit of this framework isn't just finding good ideas. It's developing three specific capabilities that almost every first-time founder lacks.

Pattern recognition for real signal vs. polite interest: After running this process for three or four months, you develop an instinct for the difference between somebody being kind and somebody being genuinely excited. The quality of the reply to your welcome question becomes something you can read accurately rather than interpret optimistically.

Speed and efficiency in page creation: By Month 3, you can have a landing page live in under two hours. You've built the same core structure multiple times. The wheel is invented. What remains is content.

Channel familiarity: You've posted in several communities, seen how different audiences respond, and identified which channels consistently produce the right profile of visitor for your ideas. This channel knowledge compounds across ideas.

The Honest Trade-Offs

This approach has real costs that founders choosing it should understand.

You don't build deep customer relationships in a month. The richest validation comes from ongoing conversations with the same customers over weeks. The one-per-month framework produces shallower relationships but covers more problem space.

Ideas that need longer to find their audience will be killed too early. Some products operate in niches where the audience is small, spread across many communities, and slow to coalesce. A month of traffic testing won't reach them efficiently.

You risk confusing validation with product-market fit. Getting email signups and getting a product people love are different thresholds. Signal from this process means "the problem is real and people are interested in a solution." It does not mean you've found the exact solution.

Who This Is and Isn't For

It's for: Founders with a technical or design background who can execute pages quickly, and who have more ideas than certainty about which to pursue. Indie hackers who have previously built a full product only to find low demand and want a better method for idea selection. People who have six to twelve months and want to spend the first three finding the right idea.

It's not for: Founders who've already done significant customer research and are confident in their problem. Founders building in regulated industries where the trust-building required for validation takes longer than one month. Founders for whom the validation conversation is the hardest part -- those founders need to practice that skill in depth, not at speed.

The Exit from the Loop

One final note on when to stop running monthly experiments and start building.

The monthly loop is a search process. It ends when you've found what you're searching for. When one of your signal experiments produces clear, strong signal -- when the welcome email reply rate is 25%+, when people unsolicited share your page, when someone emails asking "can I pay for this now?" -- that idea exits the loop and enters the build phase.

At that point, the architecture shifts. Keep the waitlist active. Start the 3-email nurture sequence. Begin building. The monthly experiment continues with other ideas only if you have capacity, which at that point you probably don't.

The goal was never to launch twelve ideas. The goal was to find the one worth building.

Find it first. Build it once.