How to Validate a SaaS Idea Before You Spend on Ads

How to validate a SaaS idea is one of the hardest questions for solo founders because building feels like progress while customer indifference is often quiet. A recent r/SaaS founder story makes the gap painfully clear: one product absorbed nine months and roughly £4,000 in promotion without gaining a single paying customer; the next began earning with almost no ad spend.

The post is valuable not because it offers a universal six-point formula for startups, but because it exposes a mistake that AI-assisted builders, marketers, and indie hackers can make faster than ever: treating traffic acquisition as validation. It is not. Traffic can reveal demand, but it cannot manufacture it.

The founder described building Ancestorii, a private family-memory product for saving photographs, stories, and history. After months of development, they spent across Meta, Google, YouTube, Reddit, creator-made UGC, sponsorships, SEO, and outreach. One Meta test reportedly generated about 15,000 visits from £210 in seven days—and zero paying customers. Removing the paywall produced signups, but still no paid conversion. By contrast, their subsequent product, Prep66, targets students preparing for Part-66 aircraft maintenance licensing exams. The founder says the first full-price customer arrived nine days after a relevant Reddit post, followed by early recurring revenue from organic demand. (reddit.com)

The lesson is not simply “build painkillers, not vitamins.” The more practical lesson is that validation should be designed as a sequence of increasingly expensive tests. First establish that a narrowly defined buyer has a high-stakes problem. Then prove they will take a meaningful action. Only after that should you buy scalable attention.

The founder story: two products, radically different signals

The original r/SaaS post compares two projects built by the same person. That matters because it reduces some of the usual explanations for startup outcomes: this was not a comparison between a talented operator and an inexperienced one, nor between a well-funded company and a bootstrapper. It was one builder learning through two markets.

Ancestorii appears to have been emotionally resonant. Few people would argue that preserving family memories is unimportant. But importance in the abstract is different from an active buying trigger. A visitor can agree that they should organize family photos someday, feel warm about the product, and still close the tab without losing sleep.

Prep66, according to the founder, serves people working toward Part-66 examinations. That category is connected to an identifiable professional pathway: the UK Civil Aviation Authority states that aircraft maintenance licence applicants must use its exam process, while Part-66 licence routes involve demonstrating required knowledge and experience. (caa.co.uk) A study product in that environment has a much clearer moment of need than a general-purpose family archive.

The contrast is revealing:

• Ancestorii received attention but did not produce payment. The founder saw visits and signups, yet no durable evidence that users valued the product enough to fund it.
• Prep66 found a pre-existing gathering place. A Reddit post put the offer in front of people who already cared about the problem.
• Prep66 addressed a job-linked outcome. Passing an exam can affect time, career progression, credentialing, and future earnings.
• The buyer had a reason to act now. Exam dates create a natural deadline; preserving stories often has no immediate deadline until an external event creates one.

None of that means a family-memory business cannot work. It means its initial market, packaging, trigger, and business model may need to be very different. A product can be meaningful and still be difficult to sell as self-serve SaaS.

Why paid traffic is not product validation

Advertising is a distribution tool. It can expose a product to more people, test messages at speed, and generate useful conversion data. But it does not answer the core question of whether the product is sufficiently valuable to a specific audience.

That distinction is easy to forget because dashboards look active. Impressions rise. Clicks arrive. Signups appear. A founder sees motion and assumes the business is moving forward. Yet every stage of a funnel answers a different question.

What each funnel metric actually tells you

A simple funnel can be read as a chain of hypotheses:

1. Impressions and clicks: Does the message attract attention from the chosen audience?
2. Landing-page engagement: Do visitors understand and care about the promise?
3. Signup or lead capture: Will they exchange some effort or contact information for possible value?
4. Activation: Do they complete the action that lets them experience the promised outcome?
5. Payment: Is the outcome valuable enough, urgent enough, and credible enough to justify a purchase?
6. Retention and referral: Did the product deliver ongoing or repeatable value?

A visitor who clicks is not necessarily a prospect. A signup is not necessarily an activated user. And payment is not the sole success metric, but it is a much stronger signal than vanity metrics when the product is meant to become a business.

This is why the £210-to-15,000-visits figure in the Reddit post drew attention from commenters. One reader noted that the founder should look beyond the absence of payments and inspect the steps after signup: did users upload a memory, invite a family member, or return a week later? That is exactly right. Payment is the final commercial outcome, but failure to activate can reveal whether the product, audience, onboarding, or original premise is broken first. (reddit.com)

Ads buy faster feedback, not better demand

There is a useful reformulation of the post’s “ads buy the bad news faster” line: ads amplify whatever is already true about your offer.

If a landing page addresses a painful, familiar, urgent problem for the right people, paid acquisition may accelerate growth. If the offer is vague, optional, poorly timed, or aimed at people with no immediate motivation, paid acquisition may accelerate loss instead.

That does not make the ad campaign worthless. It may have supplied the evidence needed to stop. The expensive mistake was not running a small test; it was continuing to fund acquisition after the product had repeatedly failed to turn interest into value-creating behavior.

How to validate a SaaS idea: test demand before building deeply

A better way to think about validation is not “Can I get anyone to sign up?” It is: “Can I gather credible evidence that a defined buyer will change behavior and pay to solve this problem?”

That requires reducing uncertainty in the right order. You should not spend six months creating a full product merely to discover whether the problem matters. Nor should you assume that a few supportive comments prove a viable market.

Start with a painfully specific customer and moment

Describe the customer using more than a demographic label. “Families” is broad. “Adult children coordinating a parent’s 80th-birthday memory book within six weeks” is a buying situation. “Students” is broad. “Part-66 candidates sitting Module 11 within the next month” is a buying situation.

A good early market definition has four components:

• Who: A recognizable group with shared context.
• Situation: The event or workflow that creates demand.
• Current workaround: What they do today without your product.
• Consequence: What gets worse if they delay or fail.

That framework helps avoid building for an imagined average user. The average user has no deadline, no particular trigger, and no reason to pay today. Real customers buy within a context.

Interview for behavior, not compliments

Founders often ask prospective users, “Would you use this?” The answer is low-quality evidence because people are polite, optimistic, and answering a hypothetical question. Ask about the past instead.

Useful questions include:

• “Tell me about the last time this problem happened.”
• “What did you do instead?”
• “What did that cost in time, money, stress, or lost opportunity?”
• “What have you already tried?”
• “Who approves spending on this?”
• “When would you need a solution by?”
• “Could I show you a manual or early version this week?”

Notice what is absent: no request for general opinions on your concept. You are looking for existing pain, existing spending, and existing workarounds. A buyer who has tried spreadsheets, tutors, contractors, or multiple competing tools is often more promising than someone who says your concept sounds “really cool.”

Seek commitments that have a cost

The most reliable early signals ask users to give up something meaningful. That cost can be money, time, data, access, reputation, or scheduling effort.

An evidence ladder might look like this:

1. A person says the problem is real.
2. They agree to an interview.
3. They share detailed workflow information.
4. They use a manual prototype.
5. They introduce you to another potential customer.
6. They book time for onboarding.
7. They pay a deposit, pre-order, or subscription.
8. They continue paying or expand use.

Each step is stronger than the previous one. Do not ignore qualitative enthusiasm, but do not confuse it with a commercial commitment.

Mandatory problems beat merely admirable problems

The Reddit author’s most persuasive observation was that Prep66 supports a mandatory outcome while Ancestorii addressed something people could postpone indefinitely. This is a powerful heuristic, but it needs nuance.

“Mandatory” does not always mean imposed by a regulator or employer. It can mean the buyer has a non-negotiable business process, compliance date, revenue target, client expectation, or operational failure they must address. The key is that inaction has a concrete downside.

A practical urgency scorecard

Before building, rate the idea from one to five on these dimensions:

A weak score does not automatically kill an idea. Consumer products, creative tools, and community products can work without regulatory urgency. But weak urgency changes the go-to-market strategy. You may need stronger emotional positioning, seasonal moments, gift-based pricing, partnerships, a service layer, or a different revenue model.

For example, a family-memory product may become more urgent when positioned around a reunion, milestone birthday, terminal illness, bereavement, estate planning, or a professional memoir service. Those segments have a triggering event. The broad promise of “preserve your memories” may still be true, but it is less likely to produce immediate action from cold traffic.

Activation is the metric the original post leaves open

The strongest community response did not reject the vitamin-versus-painkiller framing. It sharpened it: what happened after users joined?

That question deserves more attention because a product can fail to convert for multiple reasons:

• The audience is curious but not the target buyer.
• The promise is appealing, but onboarding is too much work.
• Users do not reach the first valuable outcome quickly enough.
• Pricing arrives before users see value.
• The product solves a real problem but in a weak or incomplete way.
• The product is valuable to one person but needs other participants to work.

Ancestorii may have encountered several of these at once. Family-memory software can have a collaboration problem: the person who starts the account may need photos, stories, consent, and contributions from relatives. That creates coordination friction before the user gets a satisfying result. A study product, by comparison, can deliver value to one person immediately through practice questions, explanations, and mock tests.

Define the “first value” event before you write code

Every SaaS product needs an activation event: a behavior that correlates with a person experiencing the product’s core value. The exact event differs by category.

For an email delivery platform, it might be sending a first production email. For a design tool, it might be exporting an asset. For accounting software, it might be reconciling the first transaction. For exam prep, it could be completing a diagnostic quiz and receiving a tailored study path.

For a collaborative memory app, activation might not be “account created.” It might be:

• Creating the first family space;
• Uploading at least 10 photos;
• Adding a story or caption;
• Inviting one relative; and
• Receiving one contribution from that relative.

That is a much higher bar than a signup, but it is closer to genuine value. Instrument it early. If people do not cross it, do not rush to buy more traffic.

Cohort analysis is useful here because aggregate totals can hide a deteriorating experience. Stripe’s guidance on SaaS cohort analysis recommends grouping users by meaningful shared traits or start periods to see adoption, return behavior, expansion, and drift rather than treating the customer base as one averaged number. (stripe.com)

The six rules are useful heuristics, not laws

The founder distilled the experience into six attributes they believe a product needs before strangers will pay. In the supplied post, the first three are clear: a mandatory problem, a deadline, and a real cost of failure. The broader idea is sensible, but one commenter made an important counterpoint: those rules may describe this particular app and market more than they describe every successful company. (reddit.com)

That criticism is fair. Some of the biggest software categories are not mandatory in the strict sense. People buy creative tools, entertainment products, habit trackers, games, communities, and lifestyle apps because they want delight, identity, status, convenience, or belonging. The absence of immediate pain does not equal the absence of a business.

The difference is economic and strategic:

• A high-urgency product can often convert through direct response because the buyer is already searching for relief.
• A low-urgency product may require brand, community, habit formation, virality, partnerships, or a compelling emotional moment.
• A workflow tool may need less “pain” if it saves enough time for a business buyer with a budget.
• A consumer product may monetize better through one-off purchases, bundles, gifting, or services than a recurring subscription.

Use the six rules as a risk filter. If your idea lacks urgency, clear consequences, and known buyers, do not necessarily abandon it. Be honest that it will require a more sophisticated route to market than simply launching a landing page and buying Meta traffic.

Why the second SaaS had a friendlier acquisition channel

The traction story around Prep66 is also a channel lesson. The founder did not begin with broad targeting. They posted where potential students already gathered, and the offer was legible to that community.

This is one reason niche SaaS can outperform broader ideas in the earliest stages. The total market may be smaller, but the founder can identify where buyers talk, what language they use, what deadlines they face, and which outcomes they want. Distribution is not an afterthought; it is part of the product opportunity.

Find demand where it already concentrates

For a new SaaS, make a list of places where prospective users already reveal intent:

• Search queries framed around a task, failure, or deadline;
• Professional forums and subreddits;
• Industry associations and training groups;
• Job communities;
• Newsletters and specialist podcasts;
• Existing software marketplaces;
• Consultants, agencies, and educators who serve the buyer;
• Templates, spreadsheets, and online communities built around the workaround.

The goal is not to spam every community with a launch post. It is to learn the language of the problem and earn the right to offer help. A founder who understands the exact question people ask before an exam, an audit, or a reporting deadline can write a much more credible landing page than one targeting a vague interest category.

The UK CAA’s current Part-66 guidance illustrates why this niche is legible: it defines a formal licensing context, directs applicants to examination processes, and distinguishes categories and licence privileges. That gives a product builder recognizable concepts around which to create practice tools, content, onboarding, and search-focused messaging. (caa.co.uk)

How AI changes the validation problem

The founder said ChatGPT wrote much of the code for the first product. That detail is increasingly common, and it changes the startup risk profile.

AI coding tools reduce the cost of turning an idea into software. That is good news for builders. But they also reduce the natural friction that once forced founders to think harder before building. When it takes days rather than months to create a polished prototype, it becomes easier to overinvest in an unvalidated premise.

The bottleneck moves from implementation to judgment:

• Which customer segment matters first?
• What problem is urgent enough to pay for now?
• What is the smallest experience that proves value?
• What metric means a user actually succeeded?
• Which acquisition channel can reach that buyer efficiently?

AI can help with research synthesis, copy variants, prototype interfaces, support content, analytics queries, and repetitive engineering tasks. It cannot substitute for the customer memory that comes from tracking what you tried, who responded, what they did, and whether they paid. One commenter in the discussion made a related point: general AI advice becomes generic when the tool lacks persistent context about experiments, outcomes, and prior decisions. (reddit.com)

Keep a decision log. For every experiment, write the hypothesis, audience, channel, budget, expected signal, actual result, and next decision. That gives your AI tools better context—and gives you an auditable record when optimism tries to reinterpret weak results.

A lean validation plan for the first 30 days

Founders need a plan that is concrete enough to follow before they disappear into product work. Here is a practical 30-day sequence for testing a SaaS idea.

Days 1-7: Map the problem and buyer

Choose one narrow segment. Conduct 10 to 15 conversations with people who have recently faced the problem. Ask for examples, workflows, failed attempts, deadlines, and money already spent.

Write a one-sentence positioning statement: “For [specific buyer] who needs to [job] before [trigger], this helps them [measurable outcome] without [current pain].” If that statement sounds generic, the market definition is probably generic too.

Days 8-14: Build an offer, not a full application

Create a landing page, clickable prototype, sample report, manual service, or concierge workflow. Show the core output rather than a long feature list.

Ask for a commitment. Depending on the category, that could be a paid pilot, a refundable deposit, an onboarding call, a pre-order, or access to a limited beta with a stated price after the trial. Free waitlist emails are useful, but they should not be the finish line.

Days 15-21: Deliver the promised outcome manually

Do work behind the scenes if necessary. If the customer needs an exam study plan, create it manually. If they need a report, compile it manually. If they need a workflow, onboard them personally.

This phase tells you whether the problem is worth solving before you automate it. It also shows which parts of the outcome customers value enough to pay for—and which features they never mention.

Days 22-30: Measure activation, payment, and return behavior

Review the results with discipline:

• How many qualified people saw the offer?
• How many took the next meaningful action?
• How many reached first value?
• How many paid or made a credible commitment?
• Why did non-buyers decline?
• Did users return without being chased?
• What did paid users ask for next?

If you choose to test paid acquisition, cap the budget in advance. A small budget should answer a single question, such as whether a message attracts the right audience or whether a keyword produces qualified demos. Do not let a campaign become an open-ended emotional referendum on the product.

When to stop, pivot, or keep investing

One of the most painful lines in the original story is that the founder noticed the lack of conversion early and continued spending because hope made it hard to say stop. This is common. Builders have invested time, identity, and money, so changing course can feel like admitting failure.

A pre-committed decision rule makes that easier. Before launching a test, decide what result would cause you to stop, revise, or continue.

For example:

• Continue: At least three target users pay or schedule implementation after seeing the offer.
• Revise positioning: Prospects understand the problem but do not recognize the proposed solution as the answer.
• Fix activation: Signups occur but users do not reach first value within a defined period.
• Change segment: Some users activate strongly, but they differ from the intended audience.
• Stop or shelve: Repeated qualified conversations show no existing pain, no spending, no urgency, and no willingness to commit.

The point is not to create fake statistical certainty from tiny samples. A Reddit commenter correctly warned against letting very small numbers dictate a channel strategy too confidently. Two signups or a handful of clicks are directionally interesting, not proof. (reddit.com)

Still, early-stage decisions do not require perfect significance. They require intellectual honesty. You are not trying to publish a clinical trial; you are trying to avoid spending another six months and thousands of pounds on a signal that has already said no.

What marketers can learn from this case

For marketers, the story is a reminder to separate acquisition performance from business performance. A campaign can succeed at generating low-cost traffic and fail at generating a viable business. Cost per click, cost per lead, and even cost per signup are secondary if activated users do not convert and retain.

Subscription businesses especially need to connect acquisition data to post-purchase behavior. Stripe notes that retention and churn are core subscription metrics because they reveal whether customers are continuing to get enough value to stay. (stripe.com)

A more useful reporting stack for an early SaaS is:

1. Qualified visitor rate: What proportion of visitors match the intended buyer and use case?
2. Activation rate: What proportion reaches first value?
3. Paid conversion rate: What proportion pays after experiencing value?
4. Early retention: Do they return, renew, or complete the next critical workflow?
5. Payback potential: Could the likely customer value eventually support the acquisition cost?

This does not mean early founders need elaborate analytics infrastructure. A spreadsheet and a few product events can be enough. What matters is that the dashboard follows the customer’s path to value, rather than stopping at the easiest metric to improve.

The real takeaway: build evidence before scale

The r/SaaS post is not really a story about a bad first product and a good second product. It is a story about the difference between building from personal belief and building from market evidence.

Ancestorii may have been a thoughtful product for a real human need. But the initial go-to-market did not find enough people with a strong reason to act, complete the necessary setup work, and pay. Prep66 appears to have begun with a narrower customer, a clearer deadline, a defined professional outcome, and an accessible community. Those conditions made even small signs of revenue more meaningful.

If you are deciding how to validate a SaaS idea, do not begin by asking which ad platform to use. Start with the buyer’s moment of urgency. Learn what failure costs them. Identify the behavior that proves they reached value. Ask for a commitment before building extensively. Then use ads as an instrument for learning and scaling—not as a rescue plan for a product the market has not chosen.

FAQ

What is the fastest way to validate a SaaS idea?

Talk to a narrow group of people who recently experienced the problem, offer a manual or lightweight version of the outcome, and ask for a commitment such as a paid pilot, deposit, or scheduled onboarding. Payment is the strongest signal, but behavior that requires real effort is also valuable evidence.

Are signups enough to validate a SaaS product?

No. Signups only show that people were willing to register. Track whether users reach the first valuable outcome, pay, return, and recommend the product. If they sign up but do not activate, investigate onboarding, audience quality, and the underlying need before buying more traffic.

Should a startup only build painkillers and avoid vitamins?

No. Products that create delight, identity, convenience, or connection can become successful businesses. But optional products generally need stronger positioning, better timing, more emotional resonance, or a different distribution and monetization model than products tied to a deadline or costly failure.

How much should I spend on ads before product-market fit?

Spend only enough to answer a specific, pre-defined question—for example, whether a message attracts qualified prospects or whether a search term produces booked demos. Set a cap and stop rule before launching. Do not use open-ended ad spending to compensate for weak activation or no willingness to pay.

What should I measure before scaling SaaS marketing?

Measure qualified traffic, activation, paid conversion, retention, and customer feedback by cohort. A low cost per click or signup is not enough if those users do not reach value and remain customers.