How to Validate a SaaS Idea Without an Audience or Self-Promotion

The Real Problem: You Have an Idea But No Audience to Test It On

The validation advice that gets shared most is written by people who already had an audience when they launched. “Post on Twitter, build in public, share your landing page” — great advice if you have 10K followers who trust your judgment. Useless if you’re starting from zero and your last tweet got three likes from bots.

The failure mode I see constantly: someone spends 12 weeks building a SaaS, launches to their personal network, gets 15 signups, and interprets that as product-market fit. Then they spend another 6 months building features while the number stays at 15. Those initial signups were social charity — friends and former colleagues who signed up because saying no felt awkward. This isn’t validation. It’s politeness dressed up as data.

There’s a sharp line between what feels like validation and what actually is. Feels like validation: a friend says “I’d totally pay for that,” someone emails to say they love the idea, a Reddit comment gets upvoted. Actually is validation: a stranger who discovered your product through search or a community gives you their credit card, or spends 20 minutes onboarding without you holding their hand, or emails you unprompted asking when a feature ships. The common thread is that the person has no social incentive to be kind to you. They’re reacting to the product, not to you.

The specific thing you’re trying to manufacture here is signal from people who don’t know you exist. That means getting in front of communities where you’re a nobody, writing copy that has to stand on its own without your reputation propping it up, and treating a stranger’s indifference as real data. One person who finds your landing page through a Google search and converts is worth more than ten friends who signed up to support you. The mechanics of how to actually get those strangers — without a following, without paid ads, without self-promotion — is what the rest of this covers.

Step 1 — Mine Reddit Before You Write a Single Line of Code

The most useful thing I found when validating my last SaaS idea wasn’t a competitor analysis or a market sizing spreadsheet — it was a two-year-old Reddit thread with 200 comments where people were describing the exact pain I was trying to solve, word for word. Someone had already done the customer discovery interview for me. I just had to find it.

Start with Google, not Reddit’s built-in search. Reddit’s own search is notoriously bad at surfacing old threads. Instead, use the site: operator to let Google index it properly:

# Search for frustration signals
site:reddit.com "anyone else frustrated with" invoice software

# Search for active workaround threads (gold mine)
site:reddit.com "how do you handle" client onboarding

# Search for people literally describing your product
site:reddit.com "is there a tool that" automatically syncs

# The "we just use spreadsheets" pattern — signals a gap
site:reddit.com "we just use a spreadsheet" contract tracking

That last query type — “is there a tool that does X” — is the most valuable signal you can find. Someone is describing your product for you, unprompted, in public, with other people either agreeing or recommending the one tool they found. If that tool they’re recommending is clunky, expensive, or enterprise-only, that gap is where you live.

Thread quality matters more than thread recency. Skip posts with 3 replies. The threads worth reading have 50+ comments, people describing workarounds they’ve duct-taped together, and at least one person asking “did anyone ever find a solution to this?” Those unanswered threads are particularly telling — they mean the problem is persistent and no one has solved it cleanly enough to satisfy the crowd. I look specifically for threads where people list multiple tools they’ve tried and explain why each one failed. That’s your competitive space in plain English.

The subreddits worth your time depend heavily on your niche, but a few consistently produce high-signal threads:

• r/smallbusiness and r/Entrepreneur — ops pain, bookkeeping nightmares, hiring chaos. Good if you’re building workflow tools.
• r/freelance — invoicing, scope creep, client communication. The complaints here are remarkably consistent and specific.
• r/sysadmin and r/devops — tooling gaps, automation frustration, on-call misery. Technical audience, very direct about what’s broken.
• r/consulting — proposal management, client reporting, time tracking. Under-served compared to how much money these people spend on tools.

Copy the exact phrases people use into a running doc. Don’t paraphrase them. When someone writes “I spend half my Monday just chasing down status updates from three different Slack channels,” that’s not a note to yourself — that’s a headline for your landing page. The language that converts isn’t language you write, it’s language you collect. I’ve had landing pages where nearly every bullet point came verbatim from Reddit threads, and those pages convert at double the rate of anything I wrote from scratch. The vocabulary your customers use to describe their own pain is the vocabulary that makes them feel like you’re reading their mind.

Step 2 — Build a Landing Page in a Day (Not a Week)

The thing that kills most validation attempts is the builder spending two weeks on a Next.js app with a custom design system before a single stranger has seen the idea. I’ve done this. You ship a beautiful product page for an idea nobody wants. The landing page is not your product — it’s a hypothesis test, and it needs to be live today, not after you’ve picked the perfect font.

Use Carrd ($19/year for a custom domain) or Typedream (free tier gets you far enough). Both let you go from blank to published in under two hours without touching code. The reason I push back on “but I could just do this in Next.js” is that it’s a trap — you start optimizing the build pipeline instead of talking to users. If your idea fails validation, you wasted a day on Carrd. If you’d done it in Next.js, you wasted a week.

Your page needs exactly three things and nothing else:

• One sentence explaining what it does. Not a tagline. A functional description. “Automatically turns your Notion database into a weekly email digest for your team” beats “Work smarter, together.”
• Who it’s for. Explicit and narrow. “For indie SaaS founders who manage support without a team” not “for businesses of all sizes.”
• An email capture. That’s the entire conversion goal of this page. Nothing else.

Go back to the Reddit threads you found in Step 1 and literally steal the phrasing people used to describe their problem. If someone wrote “I’m so sick of manually copying Slack messages into Jira every morning” — that’s your headline. Not a cleaned-up version of it. The actual words. Real users convert when they read their own frustration reflected back at them. Marketing speak written by someone who doesn’t have the problem converts nobody.

Don’t hook up a bare email field. Use Tally (free) or Typeform and ask one qualifying question after they submit their email. Something like: “What tool do you currently use for this?” or “How are you solving this today?” This does two things — it filters out casual clickers from people with the actual problem, and it gives you customer discovery data on autopilot. A signup with “I use a combination of Zapier, a Google Sheet, and prayer” in the answer field is worth ten bare email signups.

# Tally embed in Carrd — paste as custom embed block
# Your Tally form URL looks like:
https://tally.so/r/yourformid

# In the form builder, set it up as:
# Page 1: Email field (required)
# Page 2: "What are you currently using to solve this?" (short text, required)
# Redirect after submit: a simple thank-you message, no social share hooks yet

Spend $0 on design right now. No logo, no custom illustrations, no Figma mockups. A black Carrd template with your three pieces of content will convert just as well as a polished page if the idea resonates — and it will not convert if the idea doesn’t, regardless of how good it looks. The only design decision that matters at this stage is: can someone read this on mobile in under 30 seconds and understand exactly what you’re offering? That’s it. Anything beyond that is procrastination dressed up as productivity.

Step 3 — Post Where People Already Have the Problem

The thing that surprised me most about early validation is that the demand already exists — written down, timestamped, publicly searchable. Someone posted “does anyone know a tool that automatically reconciles Stripe payouts with bank statements?” six months ago. That thread is still sitting there. That’s not a place to self-promote. That’s a place to answer a direct question from someone who has the exact problem you’re solving.

Search Reddit, Indie Hackers, and niche forums with queries like "does anyone know a tool that [X]" or "is there a way to automate [X]" or "we do this manually but it's killing us". When you find a thread that matches your idea, read the whole thing first. If it’s six months old and unanswered, you can reply with a genuine answer — describe the manual workaround, mention why it’s painful, and then say something like: “I’m actually building something that handles exactly this — it’s early but if you want to be in the loop, here’s the waitlist.” That’s not spam. That’s someone asking for directions and you saying “I’m building that road.”

Reddit will ban you fast if you get this wrong. The mistake is opening with the product. Your first sentence should engage with the actual question — share something real about the problem, even if it’s just “yeah, I ran into this same thing at my last job.” Mods and users can smell the formula: generic empathy sentence → pivot to product link. Don’t do it. I’ve seen posts with genuine 3-paragraph answers that organically mention a waitlist get 40 upvotes and zero mod action. I’ve seen one-liners with a link get removed in 20 minutes. The ratio of value to pitch has to be heavily weighted toward value. Some subreddits like r/SaaS or r/Entrepreneur are more tolerant; r/smallbusiness and niche industry subs are much less so — read the rules before posting anything.

Hacker News “Ask HN” posts are a different animal. The ones that work don’t pitch — they frame a problem and ask a pointed question. Compare these two approaches:

BAD: "Ask HN: Would you use a tool to automate expense reporting?"
(Yes/no question — you'll get 3 comments and a lot of silence)

GOOD: "Ask HN: How are you handling reconciliation between Stripe, expense tools,
and your accountant? We're doing it all in spreadsheets and it takes 6 hours/month."
(Specific, admits a real pain, invites comparison — you'll get stories)

The second framing works because it lets people either commiserate or show off their better solution. Both responses tell you something valuable. If five people describe the same 6-hour-spreadsheet process you described, that’s signal. If three people say “we just use [competitor],” that’s also signal — and you should go look at that competitor. Mention at the bottom, briefly, that you’re exploring building something here and link a Typeform or waitlist — but only after you’ve had the actual conversation. Don’t lead with it.

Slack communities and Discord servers are where I’ve gotten the highest-quality early feedback, partly because conversations are smaller and more targeted. Most active communities have a #tools, #resources, or #shameless-plugs channel where dropping a “hey I’m building X for people who deal with Y — would love 15 minutes with anyone who’s hit this” is explicitly welcome. The trick is you need to have participated in the community before this, even a little. Two or three real replies to other people’s questions over the preceding week gives you enough social capital that your post doesn’t read as drive-by spam. Find these communities by searching “[your industry] Slack” or “[your niche] Discord” — most have public invite links. A bootstrapped ops-tools community with 800 members will give you better feedback than posting in a 50,000-person general startup Discord where your message disappears in 4 minutes.

Step 4 — Do Fake-Door Testing Before You Build the Feature

The thing that surprised me most the first time I ran a fake-door test: people clicked the “Export to CSV” button — which literally did nothing — three times more than the main “Generate Report” button I’d spent two weeks building. That’s not a UX failure. That’s market research you can’t buy. Fake-door testing means you wire up a button or link for a feature that doesn’t exist, track who clicks it, and use that data to decide what to build next. No surveys, no guessing, no “I think users want X.”

PostHog is the right tool for this if you’re pre-revenue or early-stage. The free tier gives you 1 million events per month, which is more than enough before you hit meaningful traffic. Setup takes about 10 minutes. Drop the snippet into your HTML, then capture a custom event on the button click:

<!-- Button for a feature that doesn't exist yet -->
<button id="bulk-import-btn">Bulk Import (Coming Soon)</button>

<script>
  document.getElementById('bulk-import-btn').addEventListener('click', () => {
    // Log the intent, then show a "we're building this" message
    posthog.capture('fake_door_clicked', {
      feature: 'bulk_import',
      page: 'dashboard',
      user_plan: 'free' // segment by plan if you have auth
    });
    alert('This feature is coming soon! We\'ll notify you when it\'s ready.');
  });
</script>

The user_plan property is the part most people skip. You want to know which users are clicking — free-tier tire-kickers or people who’ve already paid. PostHog lets you filter your event counts by any property you capture. If your bulk import button is getting hammered exclusively by free users, that’s a different signal than if it’s your paying users clicking it every session. You can also use PostHog’s feature flags to show the fake door only to a percentage of visitors if you want to A/B test the messaging around it.

If you’re not far enough along to have a live product and you’re still running Tally forms to talk to potential users, add a “features you’d want” checkbox section at the bottom. Keep it to 5-6 options max — more than that and people just check everything. The specific combination of boxes someone checks tells you more than any single answer. If you’re consistently seeing “offline mode” and “team sharing” checked together, that’s a workflow pattern worth understanding before you write a single line of code.

# Example Tally form field config (via Tally's embed API or direct form builder)
# Add this as a multi-select checkbox block

Question: "Which of these would make you switch from your current tool?"
Options:
  - [ ] Bulk import from spreadsheet
  - [ ] Offline / local-first mode
  - [ ] Team sharing with permissions
  - [ ] API access
  - [ ] White-label / custom branding

# Track the raw form responses in Airtable or Notion
# Filter by respondents who said they'd pay $X+/month first

The most underrated fake-door signal is pricing page visits from people who came to your landing page before your product is functional. If you’ve set up a “Pricing” nav link that goes to a page — even a simple one saying “pricing coming soon, join the list” — and PostHog shows you someone visited that page twice in one session, that’s a warm lead. Not a “maybe interested” lead. Someone who voluntarily navigates to a pricing page twice is running mental math on whether they’d pay. Follow up with them manually. Find them via the email they submitted or look at your Tally responses sorted by date. A short “hey, I noticed you checked out our pricing — what were you hoping to see?” message will get responses. That’s a sales conversation that costs you nothing except 5 minutes of your time, and it’ll tell you more than 50 click events.

Step 5 — Run Five Customer Interviews Before You Trust Any of This

The waitlist number is lying to you. A hundred signups feels validating, but email addresses are cheap — people click things they’d never pay for. The thing that cuts through is a 20-minute phone call where someone has no social pressure to be nice to you. Getting five of those calls done, with strangers who owe you nothing, will tell you more than 500 signups ever could. The offer should be exactly this: “I’m building something and want your input to shape it — no pitch, no product demo, just your perspective.”

Rob Fitzpatrick’s The Mom Test framework changed how I run these permanently. The core rule: never ask forward-looking opinion questions. “Would you use this?” is useless because people answer based on how they want to see themselves, not how they actually behave. Instead, drag them into the past:

• “Walk me through the last time you dealt with this problem.” — past behavior, not hypothetical.
• “What did you try first? What did you try after that didn’t work?” — reveals how hard they’ve actually searched for a solution.
• “How much time does this typically eat up for you?” — anchors the problem in real cost, not perceived importance.
• “What does your current workaround look like?” — if they have a workaround, the problem is real enough to have caused action.

The filtering question — the one most founders chicken out of asking — is some version of: “If I launched this tomorrow at $49/month, would you sign up today?” You’re not asking for money. You’re watching their face (or listening to the pause). Real demand sounds like “yeah, actually” or “I’d need to check with my manager but yes.” Polite interest sounds like “oh definitely, that would be really useful” with zero specificity. Hedging, subject changes, and hypothetical conditionals (“if it had X feature I might…”) are all soft no’s. Log them as such.

Finding five strangers to talk to without a following is annoying but solvable. The $10 Amazon gift card offer posted in a relevant subreddit works surprisingly well — something like r/freelance, r/smallbusiness, or whatever community matches your ICP. Keep the post honest: “I’m doing 5 customer interviews, 20 minutes, $10 gift card, no pitch.” Moderators tend to allow these if you’re not promoting anything. If you have $200–$400 to spend, Respondent.io lets you recruit screened participants by job title, industry, and company size — much cleaner signal, less scrappy hustle. For B2B ideas specifically, this is often worth it because finding actual procurement decision-makers on Reddit is hit or miss.

Here’s what you’re actually listening for during these calls — not general enthusiasm, but three specific signal types:

• Time loss with specificity: “I spend probably four hours every Friday doing this manually” beats “it takes forever.”
• Money loss they’ve already accepted: If they’re currently paying $200/month for a bad solution, your $49/month offer is a no-brainer — but only if you hear about that existing spend unprompted.
• Workarounds they’re embarrassed by: “We basically have a Google Sheet with 12 tabs that three people maintain” is gold. Embarrassment about a workaround means they know it’s broken and have been tolerating it — that’s a paying customer waiting to exist.

Record every call with permission (Otter.ai at the free tier handles this fine for five calls). After you finish all five, don’t read your notes — read the transcripts and highlight every place someone mentioned a specific tool, a specific dollar amount, or a specific amount of time. If those highlights are sparse across all five calls, you don’t have a problem worth solving at the price point you’re targeting. If two or three people independently mention the same broken tool or the same manual step, you have something real. Five calls isn’t statistically significant, but it’s enough to know whether you’re in the right zip code.

The Actual Signal Thresholds Worth Trusting

Most people building SaaS validation lists are collecting vanity metrics and calling it signal. An email signup from cold traffic — a Reddit post, a landing page from a Google ad, someone’s newsletter mention — tells you almost nothing. People sign up for things reflexively. They see a headline that resonates, they drop their email, and they never think about it again. I’ve seen landing pages with 400 signups where literally zero people responded to the follow-up email. That’s not a list. That’s a graveyard.

The threshold I actually trust looks like this: the person signed up, and they replied to a follow-up email, and in that reply or in a short form they answered a qualifying question. All three. The qualifying question should be something that separates real pain from curiosity — not “are you interested in X?” but something like “how are you currently handling this problem?” or “how much are you spending on your current solution per month?” Someone who answers that question in specifics has a real problem. Someone who writes “sounds cool!” does not. The gap between those two groups is the gap between a business and a hobby project.

Pre-sales are the only way to eliminate polite interest entirely. Even charging $1 changes the conversation because it forces a micro-decision that email signups don’t. You’re not asking someone to spend mental energy imagining future value — you’re asking them to make a real trade now. The cleanest way to run this without a product is through Stripe’s payment link feature. Create a one-time payment link, set the price to whatever your early access fee is (I’d suggest $29–$99 for most SaaS, not $1 — you want commitment, not a novelty purchase), and add a description that’s unambiguous:

# Stripe Payment Link description example
Product name: [YourTool] Early Access
Description: You're reserving early access. We'll charge this card 
when we launch (estimated Q3 2025). You can cancel before then 
for a full refund. No product exists yet — this is a pre-sale.

# Then track in your notes:
- Date they paid
- Which channel they came from
- Whether they answered the qualifying question before paying

That last line in the note matters more than the money itself. If someone found you from cold outreach — not a warm audience, not a community you built over years — and they still paid, that’s the strongest signal you can get at zero-scale. The refund policy isn’t weakness, it’s honesty, and honest pre-sales convert better because people trust them more. I’ve watched founders hide the “no product yet” detail and then deal with chargebacks two months later. Put it front and center.

The number I track obsessively during validation isn’t total signups, and it isn’t even total pre-sales. It’s the percentage of people I actually spoke to who asked when they could pay. Not “this is interesting” — specifically asking about payment or pricing. If I do 20 cold outreach conversations and 8 of those people ask about pricing or next steps, that’s 40%, and I’m building. If I do 20 conversations and nobody asks, I don’t care that I have 200 email signups. The signups didn’t ask. The humans I talked to — who had nothing to gain from being polite to a stranger — didn’t show buying intent. That asymmetry is the whole signal.

• Minimum bar: signup + reply + qualifying answer — all three before you count someone as a real lead
• Pre-sale setup: Stripe payment link, honest description, refund policy stated upfront, no product required
• The ratio that matters: (people who asked about pricing) ÷ (total conversations) — aim for above 25% before committing to a build
• Ignore: total pageviews, social likes, newsletter open rates, and signups from people who never replied to anything

Tools That Actually Help at Each Stage

The thing that caught me off guard early on was how much time people waste picking tools instead of validating. Pick the boring option that ships fast. Here’s what actually works at each stage, with the real trade-offs.

Landing Page

Carrd at $19/year is the one I keep recommending. Custom domain, clean output, and it takes under two hours to get something that doesn’t look embarrassing. The Pro Lite tier at $19 is enough — you don’t need Pro Standard unless you want form submissions routed through Carrd itself (skip that, use Tally instead). Typedream’s free tier is genuinely usable early on if you don’t need a custom domain yet. I’ve seen people run the first two weeks of validation on a Typedream subdomain without any problem. The moment someone asks “wait, is this a real company?” is the moment you drop $19 on Carrd.

Email Capture and Waitlist

Tally is free, has no submission limits that’ll bite you during early validation, and embeds cleanly into both Carrd and Typedream. Build a form in five minutes, grab the embed code, done. If you already know you want automated email sequences — a welcome message, a follow-up three days later asking for a quick call — start with ConvertKit from day one instead of migrating later. ConvertKit’s free tier caps you at 1,000 subscribers, which is more than enough runway. The migration tax of moving contacts and rebuilding sequences mid-validation is real and annoying.

Analytics

Don’t pay for Mixpanel while you’re still figuring out if anyone cares. PostHog’s cloud free tier gives you 1 million events per month free, which is absurd value at this stage. You get funnels, session recordings, and custom event tracking. The self-hosted option exists if you’re paranoid about data, but the Docker setup takes a couple hours and you’re on the hook for maintenance — not worth it until you’re post-validation. The one thing to set up immediately is an explicit waitlist_signup event separate from a generic page view, so you can filter your funnel properly:

posthog.capture('waitlist_signup', {
  source: 'homepage_hero',   // track which CTA converts
  plan_interest: 'pro'       // if you're testing tiered pricing copy
})

Customer Interviews

Use Cal.com (free tier, self-hostable) for scheduling. Skip Calendly’s paid plan at this stage — Cal does everything you need. For the actual interview, record it and run it through Otter.ai. Here’s the important part: read the full transcript, not just the AI-generated summary. Otter’s summaries collapse nuance in a way that’ll make every interview sound like the person loved your idea. The gold is usually in a throwaway sentence buried in the middle — “oh yeah we actually already built a spreadsheet for that” — which the summary will completely omit.

Pre-Sales

Stripe payment links require no app, no code, and no Stripe account beyond basic setup. You go to dashboard.stripe.com, create a payment link, set the price, copy the URL. Ten minutes start to finish. I use these to sell founding member spots ($49–$299 one-time) before a line of product code exists. Someone clicking that link and entering their card is real signal in a way that “I’d definitely pay for this” in an interview absolutely is not. If you need a refund policy, add it to the product description field — Stripe shows it on the checkout page.

Prototype Tooling

If you’re a developer who needs to spin up something clickable fast — not production-ready, just good enough to put in front of five users — the Best AI Coding Tools in 2026 covers the current space of AI-assisted coding options worth considering. The gap between “static landing page” and “throwaway interactive prototype” has shrunk dramatically. A throwaway prototype can move an interview from “I think I’d use it” to “yeah, I’d pay for that” — which is the whole point.

What to Do When You Get No Signal

The most common mistake I see is founders treating zero signups as evidence the idea is bad. After 200 unique visitors with no conversions, the first thing I’d change is the headline — not the product, not the pricing, not the landing page layout. The headline is almost always the culprit. If someone lands on your page and your value prop isn’t clear in under five seconds, they’re gone, and you’ll never know why. Rewrite it to be brutally literal: “Automates your Shopify refund emails” beats “simplify your post-purchase experience” every single time. Run that change first before you touch anything else.

No replies to a Reddit post stings differently. But what it usually tells you is that you’ve found a latent problem — one people have quietly adapted around rather than one that’s actively making them angry. There’s a specific phrase pattern I look for when reading replies: people who are frustrated will say things like “I’ve tried three tools and they all suck” or “I just gave up and do it manually in a spreadsheet.” If nobody says anything like that, the problem probably doesn’t have enough pain behind it to drive purchasing behavior. Silence isn’t neutral — it’s signal.

The mental model that actually helps here is the difference between “nice to have” and “I need this now or something breaks.” You can hear the gap clearly in interviews. When someone describes their current workaround without any irritation — “Oh yeah, I just export to CSV and clean it up, takes maybe 20 minutes” — that’s a nice-to-have. When they describe it and their tone shifts — “It’s embarrassing, honestly, we’re a $2M company and we’re literally copying rows into a Google Sheet” — that’s a real problem. If you’re five interviews in and nobody has described their workaround with any visible frustration, you’re probably not digging into the right layer of the problem yet.

My personal rule for when to kill versus when to pivot: if five consecutive interviews produce zero budget questions — nobody asks about pricing, nobody asks “how much would this cost”, nobody mentions what they’re currently paying for an adjacent tool — kill it. Budget questions are the single most honest buying signal you’ll get in a validation conversation. People ask about price when they’re mentally spending money. On the other hand, if the problem clearly exists and people are frustrated but they keep misreading your framing (“oh so it’s like a CRM?”), that’s a pivot signal, not a kill signal. The product is fine; the positioning is wrong.

For a second round of testing, change exactly one variable. I’ve watched founders change the subreddit, the headline, the qualifying question, and the call-to-action all at once and then have no idea which change moved the needle. Pick one:

• Change the headline if you got traffic but no signups — your targeting was fine, your message wasn’t landing.
• Change the subreddit if you got no upvotes and no comments — you were talking to the wrong audience entirely.
• Change the qualifying question if people engaged but dropped off before giving you contact info — the ask was too big or the framing felt like a sales call.

Run each variation for the same time period against a similar audience. A week in a mid-sized subreddit (50k–200k members) is usually enough to get a directional read. If your second round with a rewritten headline still gets under a 1% conversion rate on a landing page, that’s when I’d seriously consider whether the audience you can reach organically is the right one, or whether this idea needs a fundamentally different distribution channel to validate properly.

Common Mistakes That Kill Validation Before It Starts

The most expensive mistake I see first-time founders make is asking “what do you think of my idea?” That question is socially engineered to produce encouragement. Nobody wants to crush your excitement to your face. They’ll say “oh that’s really interesting” or “I could see myself using that” — and you’ll walk away feeling validated when you’ve learned exactly nothing. The only signal worth anything is behavior: did they lean forward and start asking how they can get access? Did they volunteer a problem story unprompted? Did they offer to pay? Enthusiasm is cheap. Specificity is the tell.

Building an MVP before you have ten people who’ve said they’d pay is not validation — it’s a very expensive form of hoping. I’ve watched founders spend four months building something because three friends said “yeah I’d use that.” Paying is a fundamentally different cognitive act than using. “I’d use a free tool” means nothing. “Here’s my card number, ship it when it’s ready” means everything. The bar isn’t ten signed contracts. It’s ten people who gave you money, a LOI, or booked time on their calendar specifically to see a demo — not because they like you, but because they have the problem badly enough to move.

Reddit upvotes and Twitter likes are engagement metrics, not purchase intent. A post about your idea getting 400 upvotes on r/entrepreneur tells you it’s a relatable concept. That’s it. The people upvoting are rarely the people who’d pay for a solution — they’re scrolling, pattern-matching to something familiar, and hitting the arrow key. The actual signal would be: you posted in r/smallbusiness describing a problem (not a product), and fifteen people DMed asking how they solve it. That’s a different thing entirely. Engagement means your framing was interesting. Purchase intent means someone experienced a problem severely enough to take action.

Only running your idea past people in your professional network is a subtle form of data poisoning. They know you. They want you to succeed. They also know that if they tell you it’s a bad idea, they’ll see you at the next meetup and it’ll be awkward. Your colleague, your former manager, your LinkedIn connections — these are the worst validation sources. Strangers in a niche forum who have no social obligation to you will tell you the truth fast, usually in the first reply. “I tried to solve this exact problem two years ago and gave up because X” is a gift. Your network will give you “this sounds promising!”

Waiting until the product feels “ready enough” to start talking to potential customers is exactly backwards. The entire point of pre-build validation is that you haven’t built anything yet, so the feedback is free. Every week you wait costs you development time, opportunity cost, and psychological anchoring — once you’ve written the code, you’re emotionally committed to the idea in a way that makes negative feedback harder to hear and act on. A landing page with a waitlist form takes a day to ship. A Typeform with five questions about the problem costs nothing. The conversations you have before you write a line of code are the cheapest data you will ever collect.

---

---