Here's the 30-day plan in four steps. Week one: have 10 to 15 conversations with people who have the problem. Week two: build a simple one-page website and see how many people sign up by email. Week three: offer early-bird pricing and see how many will actually pay. Week four: decide to build it or move on. The only signal that matters is someone paying money — or committing to pay — before the product exists. Everything else is just polite encouragement.
Micro SaaS — a small subscription software business — is a focused product built and run by one person or a very small team. It targets a narrow group of customers, runs on very little, and is designed to make money without investor funding. The market for these small businesses is growing roughly 30% a year. The fastest path to actual income is testing whether people want it before you write any code.
The average founder who skips this step spends eight months or more building before finding out nobody wants it. This 30-day plan tells you the same thing in 30 days, for free.
Most people running these businesses alone skip this step entirely. They have an idea, they start building, and eight months later they have a polished product nobody buys. That mistake is brutal — you spend hundreds of hours before learning the demand was never there.
This isn't about proving your idea is good. It's about finding out, as fast and as cheaply as possible, whether enough people have the problem and will actually pay to fix it.
The founders who reach $1,000 in monthly subscription income fastest all share one habit: they test the idea before they build. Not because they read a startup book, but because they got burned once and never wanted to repeat it. Here's how it works.
"Finding out an idea is bad in week two costs you nothing. Finding out in month nine costs you everything."
Why Most Ideas Don't Survive the Test (And What to Expect)
The point of these 30 days isn't to confirm your idea is good. It's to find out whether real people have the problem strongly enough to pay for a fix. Most ideas that feel exciting to founders turn out to target problems that are either not painful enough, or already handled well enough by existing tools.
Expect this: about 70% of ideas that feel promising in your head won't survive contact with 10 potential customers. An IndieLaunches study (a tracker that monitors software product launches and outcomes) of 326 projects posted on Hacker News (a popular tech discussion forum where founders share products) found that founders who got real payment commitments before building were three times more likely to reach $1,000 in monthly subscription income than those who launched cold. That isn't failure — that's the plan doing its job. Finding out the idea is bad in week two costs you nothing. Finding out in month nine costs you everything.
The only signal that counts is someone paying money — or agreeing to pay money — before the product exists. Sign-ups, compliments, and "I'd use that" don't count. A credit card charge counts.
Week 1: Problem Conversations (Days 1–7)
You are not selling them anything. You are asking questions about the problem. The best conversations feel like a chat, not a survey.
You want at least 8 out of 15 people to confirm the problem is real, happens often, and costs them time or money. Fewer than 8 means the problem is either too narrow or not painful enough to build a business on.
Meet on Zoom or call — not text. Take notes but don't record. Spend 80% of the time on how they handle the problem today, not on your solution. You want them describing the pain in their own words, not reacting to your sales pitch.
Your goal in week one is 10 to 15 conversations with people who match your idea of the perfect customer. You are not selling them anything. You are asking questions about the problem. The best conversations feel like a chat, not a survey.
The five questions that matter:
Where to find people to talk to: LinkedIn (search for the job title you're targeting and send a note saying you're doing research, not selling anything), Reddit (post asking for people who experience a specific problem), your own network, and replies under Twitter/X posts about the problem area.
Week 2: Landing Page Test (Days 8–14)
If 5% or more of visitors from online communities give you their email, that's the minimum signal worth continuing. Under 5% means the headline needs a rewrite — either the problem isn't clear or you're reaching the wrong people.
Send 100+ visitors from two or three community posts. 5% or more giving their email — keep going. Under 5% — rewrite the headline. The problem is unclear or you're reaching the wrong people.
Build the page in one day. It doesn't need to look beautiful. It needs to answer three things: what's the problem, what does your fix do, and how do I get early access.
After 10 to 15 conversations, you should know whether the problem is real and happens often. If it does, build a one-page website describing the fix — in a single afternoon. You don't need design skills. Carrd (a tool for building simple one-page websites in minutes), Notion, or even a Google Doc shared as a public link works.
The page should have: one clear headline naming the problem and the fix, three bullet points describing what the tool does, a pricing section (even if it's a guess), and an email sign-up box with the line "Join the waitlist — founding-member pricing." That last part matters: you're not collecting emails for a newsletter — you're measuring whether anyone wants to buy.
Post the link in three places: the most relevant subreddit for your perfect customer, one Slack or Discord community where they hang out, and your own Twitter/X or LinkedIn. Don't frame it as "I built this." Frame it as "Is this something you'd use? Trying to figure out if it's worth building."
What to measure: the share of visitors who become sign-ups. Anything above 5% is a strong positive signal. Below 2% means either the traffic was wrong (wrong community) or the wording needs work. The number of sign-ups matters less than that share at this stage.
Week 3: Early Payments (Days 15–21)
One real payment is worth more than 100 email sign-ups. Offer 50% off lifetime access or 3 months free. Ask for a card. People actually paying is the signal — everything else is just polite noise.
This is the most important week. Email everyone who signed up on your one-page site with an offer: founding-member access at a discount, paid today, product delivered in 30 days. Something like: "We're building [Product]. As an early sign-up you can lock in founding-member pricing at $X (regular price will be $Y) — paid today, full access when we launch in four weeks. Interested?"
The goal is five paying customers from that email. Not 50, not 100. Five. Five paying customers means five people who believe in the problem enough to hand you money before they've seen the product. That's a real signal.
If you get fewer than five, don't build yet. Go back to the people you talked to in week one and to the people who signed up but didn't pay — ask why they passed. The answers are almost always one of four things: "not painful enough," "price too high," "wrong timing," or "I already found another tool." Each answer points to a fix.
Week 4: Decision (Days 22–30)
If you cleared the checkpoints: start building. If you didn't: have more conversations, change the message, or move to the next idea. The whole 30 days are designed to make this decision cheap.
By week four you have real data: notes from your conversations, the share of visitors who signed up, and the number of people who actually paid. Make the decision cleanly on those numbers — not on how attached you are to the idea.
If you got five or more paying customers: start building immediately. Your only constraint now is delivering the product on the timeline you promised. Weekly updates to those early customers build trust and surface feature questions that save you weeks of building the wrong thing.
If you didn't hit five paid commitments, take stock. Was the problem real (the conversations said yes) but nobody paid? That's usually a pricing or wording problem — try a lower price or a different description. Was the problem not real (the conversations were lukewarm)? Drop the idea and start the plan over with something new.
The 30 days taught you something valuable either way. Founders who build successful products aren't the ones with the best first ideas — they're the ones who cycle through bad ideas fastest until they find one that gets a real response.
The Signals to Trust (And the Ones to Ignore)
Compliments, upvotes, and "I'd definitely use that" don't count. A credit card charge counts. Here's the full breakdown.
Trust: someone who pays before the product exists. Someone who uses a clunky workaround for hours every week. Someone who has already tried to solve the problem with other tools and failed. These are the customers who will stick around and give you honest feedback.
Ignore: someone who says "I'd definitely use that." Someone who joins the waitlist but doesn't reply to the early-payment email. Someone who gives you long, detailed feedback but won't pay. Enthusiasm without money isn't proof — it's encouragement, which is worth less than you think when you're deciding whether to spend four months of your life on this.
This 30-day plan isn't designed to feel comfortable. It's designed to be fast and definitive. Thirty days of focused testing is worth more than eight months of building in the dark.
Frequently Asked Questions
Once you've cleared this 30-day test, these guides cover what comes next: how long it takes to reach $1,000 in monthly subscription income, and which channels bring in first customers.
Further reading: Indie Hackers · Product Hunt