How to Validate a Micro SaaS Idea Before Writing a Single Line of Code

The most expensive mistake in micro SaaS isn't a bad architecture decision or an ugly UI. It's spending eight weekends building a tool nobody asked for, then discovering that out at launch when the silence is deafening. Validation exists to move that discovery earlier, back to week one, when the only thing you've lost is a few evenings instead of a quarter of your life.

Most advice on this topic stops at "talk to your customers," which is true and also useless as a process. Talking to customers can mean anything from a rigorous structured interview to a friend saying "yeah, sounds cool" over coffee. What follows is the actual sequence I use: a landing page with a waitlist, cold outreach to a narrow list of real prospects, and a pricing conversation before any code exists. Each step is designed to produce a signal you can act on, not a vague feeling of encouragement.

Step 1: Build the landing page before the product

The landing page is not marketing collateral. It's a test instrument. Its only job is to state the problem and the promised outcome clearly enough that a stranger who has that problem stops scrolling and gives you their email.

Keep it to one page: a headline that names the specific pain (not the feature), three or four bullet points on what the tool does, and a single call-to-action to join a waitlist or book a five-minute call. Skip the fake testimonials, skip the "as seen in" logo bar you don't have a right to use, and skip the pricing table at this stage — you don't know your price yet. Tools like Carrd, a single static HTML page, or a simple Laravel Blade view all work equally well; the platform doesn't matter, the clarity of the offer does.

What you're measuring is conversion from visitor to signup, but more importantly you're measuring whether you can even get visitors who match your target user in front of the page at all. If you can't find 100 relevant people to send to it, that's information too — it usually means the audience is either too small or you don't yet know where they hang out, both of which are cheaper problems to discover now than after you've built something.

A realistic benchmark, not a magic number

There's no universal "good" conversion rate here — a cold audience from a Reddit post behaves very differently from a warm list of people who already emailed you asking for something like this. Instead of chasing a percentage, look at whether real, identifiable people who match your target user came back a second time, replied to a follow-up email, or asked a clarifying question about how the tool would work. That kind of engagement is worth more than a big number of anonymous signups from a broad audience that doesn't actually have the problem.

Step 2: Cold outreach to twenty target users

A waitlist page tells you if the pitch is compelling in writing. It doesn't tell you if the problem is real, urgent, or already being solved with a workaround people are content with. For that you need conversations, and the fastest way to get them is direct outreach to a small, specific list — not a mass blast.

Pick twenty people who plausibly have the exact problem you're solving, ideally people whose job title or public activity makes the fit obvious. Freelancers in a specific niche, small agency owners, community moderators, whoever your beachhead is. Message them individually, referencing something specific about their situation, and ask for fifteen minutes — not to pitch, but to understand how they currently handle the problem.

A message structure that consistently gets replies:

• Open with a specific, non-generic observation about them (their content, their business, a post they made) — proves you're not spamming a list.
• State the problem you're exploring in one sentence, framed as a question rather than a pitch.
• Ask for a short call or even just a text reply about how they currently solve it, not whether they'd buy your unbuilt product.
• Make the ask low-friction: "no deck, no demo, just fifteen minutes" removes the fear of a sales pitch.

The goal of these calls isn't to hear "yes I'd pay for that" — people are polite and will say that to be nice. The goal is to hear them describe their current workaround in detail: the spreadsheet they've hacked together, the three tools they stitch together with copy-paste, the manual process they complain about but haven't fixed. Detailed, specific complaints about a real workaround are a far stronger signal than enthusiasm about your idea.

Illustrative example: a receipt-reconciliation tool

To make this concrete, here's a composite scenario based on the kind of pattern that shows up repeatedly in early-stage validation — not a verified case study, but representative of how this plays out. A founder wanted to build a tool that auto-matched bank transactions to invoices for small agencies. The landing page pitch ("stop manually matching payments to invoices") got a modest trickle of signups from a niche bookkeeping subreddit, nothing dramatic. But the cold outreach calls told a different story: twelve of the twenty people described the exact same workaround — a shared spreadsheet with manual VLOOKUPs redone every Friday — and several volunteered that they'd tried two existing tools and abandoned both because the bank sync kept breaking. That combination (real workaround, real dissatisfaction with the closest existing alternatives) is what actually justified building. The landing page conversion rate alone would have looked unremarkable and might have caused the founder to walk away.

Step 3: Have the pricing conversation before you build

This is the step almost everyone skips, and it's the one that actually de-risks the build. If someone on a call describes their pain in detail and seems genuinely engaged, ask directly: "If I built exactly what we just discussed, what would you expect to pay per month for it?" Then stop talking and let the silence sit.

You're not trying to lock in a sale. You're trying to see whether a number comes out quickly and confidently, or whether it's hedged, low, or followed by "well, it depends." A confident number — even a modest one — from someone who isn't your friend and has no reason to flatter you is a much stronger validation signal than a hundred waitlist emails. If you get several people independently landing in a similar range, you now have a starting price and a demand signal in the same conversation, which is more useful than either alone. For more on turning that starting number into an actual pricing structure, see how I've approached pricing a micro SaaS product across three real launches.

If you can, go one step further and ask for a small deposit or a "pay when it ships" pre-order, even a token amount. Money changing hands, even a small refundable amount, filters out politeness far more effectively than any survey question. Not every idea needs this level of commitment testing, but for anything that will take more than a couple of weekends to build, it's worth the awkwardness of asking.

What a "no build" signal actually looks like

It's worth being explicit about what should stop you, because founders are extremely good at rationalizing forward. Red flags worth taking seriously:

• Nobody can describe a specific current workaround — they say "that would be nice" but aren't currently doing anything to solve the problem, which usually means it isn't painful enough yet.
• Every price suggestion comes back near zero, or people redirect to "I'd only use it if it were free."
• You can't find the twenty people to talk to in the first place — the audience is smaller or harder to reach than you assumed.
• The people who are most enthusiastic are hobbyists or fellow builders, not people who'd actually be paying with their own business's money.

None of these individually kill an idea, but two or three together are a strong signal to either narrow the target user, change the angle, or move on to the next idea. That's not failure — that's the entire point of doing this before the code exists rather than after.

Where to actually find your twenty people

The outreach step stalls for a lot of founders not because the message is bad but because they can't find twenty people who plausibly fit. A few sources that consistently work better than a cold LinkedIn search:

• Niche subreddits or forums where people describe the problem in their own words — search the community for phrases close to your problem statement and message people who posted about it, not just anyone active there.
• Public directories tied to a profession — agency listing sites, freelancer marketplaces, membership directories for a trade association — which give you a name, a business, and often contact details in one place.
• Reviews and complaints about the closest existing competitor or workaround tool, left on review sites or in app store comments — someone complaining publicly about a competitor's missing feature is about as qualified a lead as you'll find.
• Your own network, one layer out — not your friends, but people your friends work with who match the target profile. A warm introduction, even a thin one, gets a noticeably higher reply rate than pure cold outreach.

If you genuinely cannot find twenty plausible people through any of these in a couple of hours of searching, treat that difficulty itself as validation data. A market that's hard to locate is usually either smaller than you assumed or requires a different kind of expertise to reach than you currently have.

How long this should actually take

Validation has no fixed timeline, but as a rough anchor: the landing page can be built and live in a day, the twenty outreach messages can go out over the following week (a handful per day, not a mass send), and the calls themselves usually stretch over one to two weeks depending on how quickly people respond. Total elapsed time from "I have an idea" to "I have enough signal to decide" is typically two to three weeks, not two to three days and not two to three months.

Founders who skip validation almost always cite speed as the reason — "I just wanted to start building." But three weeks of validation against six to eight weeks of building the wrong thing is not a close call, and the three weeks aren't wasted even if the idea doesn't pan out: the conversations, the list of contacts, and the pattern-matching skill all carry forward to the next idea.

Turning validation into a build decision

Once you have landing page signups from people who match your target user, a handful of detailed workaround stories, and at least a rough pricing number that several people independently arrived at, you have enough to justify a build — not certainty, but a reasonable bet. Set yourself a small, deliberately narrow first version: the single workflow you heard about repeatedly, nothing else. Resist the pull to add the features people mentioned as "nice to have" during calls; those are almost never why they'd pay.

If you're building anything that touches invoicing or billing as part of this first version, it's worth looking at what's already available rather than building it from scratch — a tool like an invoice generator can save you the first few weeks of plumbing work so you can spend that time on the part of the product that's actually differentiated.

Validation isn't a gate you pass once and never revisit. The same landing page, outreach, and pricing conversation loop is worth running again every time you're considering a new feature tier or a pivot in target audience — it's just cheaper and faster the second time because you already know how to run it.