How to get your first 100 paid users without ads is one of the most persistent questions in SaaS—and a recent founder update offers a more grounded answer than the usual growth-hack checklist. The short version: build around a problem you understand, publish useful proof consistently, and treat a completed payment as a much stronger signal than a signup.

In a post shared with the r/SaaS community, two brothers described building two products around problems they had repeatedly encountered: deciding what to build and figuring out how to market it. One product, FoundersDB, packages founder stories and startup data; the other, Slidefy, helps users turn product information into social content. The founders reported that FoundersDB had passed 100 paid customers with no paid advertising, while Slidefy had reached more than 250 users and landed its first customer through the product itself. Those are self-reported figures, not independently verified financial disclosures, but the operating lessons are useful precisely because they are modest and specific: payments over vanity metrics, consistency over novelty, and firsthand stories over generic feature lists. (reddit.com)

The important takeaway is not that every SaaS should avoid advertising. It is that ads are a distribution amplifier, not a substitute for clear positioning, credible proof, functional onboarding, or a reason to pay. Before spending to accelerate traffic, founders need to know whether the offer earns attention from the right people and whether that attention survives contact with a checkout page.

The real lesson behind 100 paid users with zero ads

The phrase “zero ads” can sound like a promise of effortless organic growth. It is not. Organic acquisition still requires work: research, publishing, customer conversations, product iteration, positioning, support, and repeated distribution. In many cases, it is harder than purchasing clicks because the feedback loop is slower and the founder cannot outsource the core insight.

What the brothers’ update shows is a more practical form of bootstrapped go-to-market. They did not begin with an abstract category such as “AI for founders” or “social media automation.” They began with two pains they had felt themselves:

Founders struggle to identify ideas with commercial evidence behind them.
Early-stage builders struggle to translate a product into ongoing marketing content.

Those are not identical audiences or buying moments. The first is an information and decision-making problem. The second is a production and distribution problem. But both benefit from a similar strategy: make the value concrete enough that a prospect can understand it quickly, then keep publishing evidence that the product understands the job.

That distinction matters because early SaaS marketing often fails at the level of abstraction. “Find validated ideas faster” is a promise. A collection of founder stories that explains what someone built, how it got customers, and how it made money is evidence. “Create better social content” is a promise. Generating post-ready assets from a product description is a visible output. Buyers are far more likely to act when they can picture the before-and-after state without having to interpret a vague feature set.

The broader startup advice is consistent with this approach. Y Combinator’s guidance emphasizes talking to users, building what they want, and iterating quickly rather than getting distracted by activities that do not improve the product’s fit with customer needs. (ycombinator.com)

Why a payment matters more than a signup

The sharpest point in the original post is also the easiest metric lesson to forget: signups indicate interest, while payments indicate a willingness to exchange money for value.

A signup can mean many things. Someone may be curious about the category, attracted by a free tool, saving a link for later, comparing competitors, testing a workflow, or simply avoiding missing out. None of those explanations is useless. Top-of-funnel activity is worth measuring. But treating every signup as product-market fit turns a weak signal into an emotional milestone.

A payment is not perfect validation either. A buyer can churn after one month, request a refund, or represent a narrow segment that does not scale. Still, a payment has friction: the buyer must understand the offer, see enough expected value, trust the business, accept the price, and finish checkout. That makes it a consequential behavioral signal rather than a stated preference.

Stripe’s own conversion documentation defines a completed Checkout Session as the conversion point for most payments and recommends tracking movement through the funnel rather than stopping at page views or button clicks. (docs.stripe.com) For a young SaaS business, this reinforces an essential principle: optimize for the deepest event you can measure reliably.

A practical hierarchy of early SaaS evidence

Not all signals deserve equal weight. A simple hierarchy can stop teams from celebrating the wrong thing:

Impressions and views: Someone encountered the message.
Clicks: The message created enough curiosity to earn a visit.
Email captures or signups: The visitor sees possible relevance.
Activation: The user reaches a meaningful first outcome.
Payment: The customer believes the outcome is worth money.
Repeat payment or renewal: The product continues to create value.
Referral or unprompted recommendation: The customer sees enough value to attach their reputation to it.

For FoundersDB, a paid subscription or one-time purchase is far more revealing than an email waitlist. For Slidefy, the first inbound paying customer is especially meaningful because it suggests the product and its surrounding messaging did enough work to move someone from discovery to purchase without a sales call.

The next move after the first 100 payments is not to stop measuring. It is to ask what those payments have in common. Which acquisition source produced the buyers? Which use case was cited during onboarding? What did customers expect to happen in the first session? Which accounts retained after the first billing cycle? A founder should be able to distinguish “we got 100 customers” from “we found a repeatable path to customers who stay.”

Start with a problem you can describe without jargon

“Build for yourself” is often misread as advice to create a product only for your personal preferences. A stronger interpretation is this: choose a problem whose context you understand deeply enough to describe its expensive, repetitive, frustrating parts in the customer’s own language.

That appears to be what happened here. The founders did not need to invent a persona’s anxieties from a spreadsheet. They were founders trying to find viable ideas and market products. That proximity gives a builder several advantages:

They know the moments when the problem becomes urgent.
They understand the current workaround and why it is unsatisfying.
They can spot jargon or generic claims that would not persuade them.
They have a natural supply of content topics, examples, and objections.
They can test the product in their own workflow before asking strangers to use it.

This is a major reason customer-led products are easier to market. Good marketing is not a pile of promotional copy. It is an accurate explanation of a real problem, a credible mechanism for solving it, and proof that the result occurs. When the founder has direct experience with the problem, they are less likely to hide behind vague category language.

Turn personal experience into a market hypothesis

Personal pain is a useful starting point, not final proof. The leap from “I have this problem” to “enough people will pay for this solution” requires evidence.

A disciplined way to test the hypothesis is to write down five statements before building too much:

Audience: Who experiences this problem frequently enough to care?
Trigger: What event makes them seek a solution now?
Current alternative: How do they solve it today, if at all?
Cost of inaction: What time, money, risk, or lost opportunity does the problem create?
Paid outcome: What specific improvement would justify the price?

For an idea-research product, the trigger may be a founder deciding what to build next. The current alternative might be scattered Reddit threads, Product Hunt launches, App Store rankings, newsletters, and hours of manual research. The paid outcome is not “more data”; it is greater confidence that a problem has buyers and that there is a visible business model worth studying.

For a social-content tool, the trigger may be launching a product or needing to maintain weekly visibility. The current alternative could be staring at a blank page, hiring a freelancer, adapting generic templates, or posting inconsistently. The paid outcome is not “AI-generated words”; it is a usable set of on-brand content assets created quickly enough to sustain a publishing habit.

Founder stories are a product asset, not just a content format

The FoundersDB premise reveals another important insight: people often pay for contextualized examples because examples reduce uncertainty.

Features tell a buyer what software can do. Stories demonstrate what someone did, the decisions they made, the obstacles they encountered, and the result. For a founder deciding whether to pursue a niche, that context can be more valuable than an undifferentiated directory of startups. A list of companies says a market exists. A good case study begins to explain why the market exists, how a product was positioned, and how the business reached customers.

The founders’ V2 reportedly added startup and app data, including estimated revenue and download information. That is a sensible expansion because it joins qualitative explanation with quantitative signals. The story gives a prospective builder hypotheses; the data helps them investigate whether those hypotheses are commercially plausible. (reddit.com)

But data products have an important trust requirement: labels must be explicit. Estimated revenue is not reported revenue. Download estimates are not retention, conversion rate, profit, or customer satisfaction. The best products in this category explain their methodology, show the date range, state what a metric can and cannot prove, and give readers a path to form their own judgment.

How to turn customer stories into a distribution engine

Founders do not need a large media operation to use stories effectively. They need a repeatable editorial system that produces insights for a specific audience.

A useful case-study template includes:

The customer or company context: Who are they serving and what was happening when the problem appeared?
The constraint: What made the problem hard to solve with existing tools or habits?
The decision: What did they choose to build, buy, change, or stop doing?
The mechanism: What exactly produced the outcome?
The evidence: Revenue, time saved, conversion movement, customer quotes, or other appropriately qualified results.
The lesson: What can a reader borrow, and what is unique to that situation?

This format works for blog posts, LinkedIn carousels, short videos, email newsletters, launch pages, and onboarding messages. It also creates a virtuous loop: publishing a story attracts readers with the same problem, some become customers, and their experiences become the next source of proof.

Google’s guidance on helpful content makes the same strategic point from an organic-search perspective. It says content should be created primarily to help people, with clear attention to who created it, how it was produced, and why it exists—not simply to capture rankings. (developers.google.com) Real case studies, transparent methodology, and useful interpretation are much more durable than thin pages designed around a keyword.

Consistency beats the hunt for a viral moment

The brothers said there was no single viral moment behind their early progress. Instead, they pointed to showing up week after week. That is less glamorous than a viral launch, but it is a more controllable operating model.

Viral reach can accelerate a product that already has a clear message and strong activation. It can also create a distracting flood of poorly matched users, support requests, and superficial praise. Consistent publishing is slower, but it helps founders learn which messages resonate, which customer segments reply, and which formats generate intent rather than applause.

Consistency should not mean posting the same promotion every day. It means repeatedly helping a defined audience solve adjacent problems while making the product’s point of view visible. A founder who documents research methods, shares product decisions, publishes anonymized customer patterns, and explains tradeoffs is building familiarity and credibility before asking for the sale.

Build a sustainable weekly distribution cadence

A good cadence is one the founder can maintain during busy product weeks. For a small SaaS team, that may look like this:

One deep weekly asset: A case study, teardown, benchmark, customer interview, or tactical guide.
Three to five short derivatives: A lesson, chart, opinion, workflow, or before-and-after example drawn from the main asset.
One product-linked call to action: An invitation to try a relevant workflow, browse a data set, or join a focused list.
A weekly customer-feedback block: Review support conversations, lost deals, cancellation reasons, and questions from prospective users.
A weekly metrics review: Compare traffic, activation, checkout starts, payments, and retention by source.

The output may be smaller than what a dedicated content team produces, but it compounds. Each quality asset can serve search, social discovery, sales enablement, onboarding, and product research. More importantly, it creates a visible archive of expertise that prospective buyers can evaluate on their own schedule.

The marketing lesson is not “post every day at all costs.” It is “maintain a feedback loop.” Publish something useful, observe who responds and what they ask, use those patterns to improve the product and the next piece of content, then repeat.

Zero ads does not mean zero customer acquisition cost

It is worth being precise about the economics. Organic acquisition can have a lower cash cost than paid acquisition, especially in the earliest stage. It does not have zero cost.

The founders’ time has value. Writing, researching, building, supporting users, maintaining datasets, and sharing updates all consume resources. If a company is spending 20 hours a week on content and community participation, it is making an investment—even if no advertising invoice arrives.

This is not a criticism of organic growth. It is a reason to measure it honestly. A founder should compare channels using the same basic questions:

How many qualified prospects did this activity reach?
How many activated?
How many paid?
How much did the activity cost in cash and labor?
Did those customers retain or expand?
Can the process be repeated without burning out the team?

Paid ads may eventually be useful after a business has a clear offer, a converting landing page, a low-friction checkout, and enough retention data to estimate payback. Until then, buying traffic often magnifies ambiguity. It can produce more signups while making it even harder to understand whether the product is genuinely valuable.

Stripe recommends examining the checkout funnel to identify whether users abandon before completion or encounter payment failures. That illustrates why growth work should go beyond getting visitors to a page: a prospective customer can agree with the marketing message and still fail to complete a purchase because the payment flow, pricing logic, mobile experience, or trust signals introduce friction. (docs.stripe.com)

Design the product so it can make the first sale itself

One detail from Slidefy is particularly interesting: the founders said the first paying customer came through the app itself, without a direct message or sales call. That is a milestone worth examining because it means the product and its funnel did enough selling on their own.

For self-serve SaaS, a first sale usually depends on several systems working together:

The prospect encounters a message that accurately describes their problem.
They reach a landing page or product experience that makes the outcome understandable.
They can test or preview value before committing.
Pricing feels proportional to the expected gain.
Checkout is clear and technically reliable.
The buyer knows what to do immediately after paying.

A product-led first sale does not mean founders should never talk to customers. Quite the opposite: conversations are how founders discover the words, objections, and outcomes that make a self-serve journey persuasive. But the long-term advantage is leverage. If every customer requires a custom call, the business has learned how to sell manually, not necessarily how to acquire customers repeatably.

Reduce uncertainty before asking for payment

For tools that generate marketing content, the product should demonstrate output early. Let a prospect see examples, choose a platform, enter a product description, or preview an editable result. For research products, show the structure and quality of the analysis, reveal a sample data point, and explain how frequently information is updated.

The aim is not to give everything away for free. It is to answer the buyer’s most important question before the paywall: “Will this work for my situation?”

A strong activation moment should be concrete. Instead of measuring whether a user opened the dashboard, measure whether they generated a post they might actually publish, saved an idea worth investigating, created a campaign draft, or completed another meaningful job. Once the team knows the activation event, it can improve onboarding around that event rather than adding random tutorials and tooltips.

A first-100-paid-users playbook for founders

The original post offers principles. Here is how to convert them into an operating plan over the next 30 to 60 days.

1. Narrow the customer and the painful job

Do not target “founders,” “creators,” or “marketers” as if they were uniform groups. Pick a segment with a shared moment of urgency. Examples include solo founders validating a second product idea, agencies needing a repeatable content-production workflow, or B2B SaaS teams launching a new feature without a dedicated social manager.

Write a one-sentence positioning statement in this format: “For [specific person] who needs to [job], [product] helps them [outcome] without [painful alternative].” If the sentence requires several clauses or buzzwords, the offer is not yet sharp enough.

2. Interview people about behavior, not hypothetical desire

Ask potential customers what they did the last time the problem occurred. Ask what they tried, how much time it took, what it cost, what went wrong, and why the workaround was insufficient. Avoid questions such as “Would you use an AI tool for this?” because people are generous with hypothetical enthusiasm and inconsistent with actual behavior.

Keep a simple evidence log. Record the exact phrases people use, their existing tools, their budget signals, and the trigger event. Repeated language from real conversations should guide the landing page much more than brainstorming sessions do.

3. Build the smallest version that produces a paid outcome

The smallest viable product is not necessarily the fewest features. It is the smallest experience that helps a customer complete the important job. A manual or semi-manual process is acceptable if it teaches the team what the automated product should do.

For example, a content tool might initially create a small number of high-quality platform-specific posts from a guided form. A startup-research product might begin with deeply researched case studies in a narrow industry rather than trying to become a universal business database on day one.

4. Publish proof, not just promotional updates

Create content from the work the product is already doing. Share a mini teardown, a lesson from customer interviews, a framework for assessing a niche, a screenshot with methodology, or a before-and-after content example. Always separate observed facts from interpretation.

This builds trust and gives prospects a reason to follow before they are ready to purchase. It also creates sales assets that reduce repetitive explanations later.

5. Instrument the funnel from source to renewal

Track at least these events: visitor source, landing-page view, signup, key activation event, pricing-page view, checkout start, completed payment, refund or cancellation, and renewal. Use plain definitions that everyone on the team understands.

Do not stop at a blended conversion rate. Compare pathways. A small niche newsletter may generate fewer signups than a viral social post but more buyers. A directory listing might produce customers who churn quickly. These differences tell you where to invest scarce time.

6. Personally follow up with early customers

Early customers are not merely revenue; they are access to the truth. Send a short, human note after purchase. Ask what prompted the decision, what they hoped to achieve, whether they reached that outcome, and what nearly stopped them from buying.

Do not frame every conversation as a request for feature ideas. Look for pattern-level insight. If several customers describe the same desired outcome but use different workarounds, there may be an opportunity to improve onboarding, reposition the product, or simplify the workflow.

7. Treat retention as the next validation threshold

A hundred purchases are promising. A meaningful percentage of those customers remaining active, renewing, referring peers, or expanding usage is much stronger evidence. Set a retention review date before you celebrate the acquisition milestone.

If people buy but quickly leave, examine whether the offer overpromised, the activation moment arrived too late, the product solved a one-time task rather than an ongoing need, or the wrong customer segment was targeted. Churn is not always a product failure, but it is always useful information.

What founders should avoid copying blindly

There is a risk in turning one founder’s update into a rigid formula. The right lesson is not “sell founder stories” or “launch a social-content generator.” It is to understand the underlying mechanisms.

Do not copy the surface-level product category if you do not have access to differentiated data, real expertise, or a clear audience. A database with thin entries is not the same as a trusted research product. An AI content generator without a specific workflow advantage is likely to blend into a crowded market.

Do not mistake public building for a strategy by itself. Posting progress can create accountability and trust, but it does not automatically create demand. The content must remain useful to the audience, not merely interesting to the founder.

Do not use “no ads” as an identity. There is nothing morally superior about avoiding paid acquisition. If a company has sound unit economics, clear conversion data, and a retained customer base, paid channels can be a rational way to scale. The mistake is paying to acquire more ambiguity.

Finally, do not turn every early payment into a broad market claim. One hundred customers can validate a problem, a segment, a channel, or an offer. It does not prove that every adjacent segment wants the product or that growth will remain linear. Founders should celebrate the milestone while continuing to test the boundaries of what is actually working.

The second-order advantage: a company that learns in public

The strongest long-term idea in this story may be the decision to keep adding case studies and share numbers over time. Transparently documenting progress can become more than a marketing tactic. It can become a research system.

When founders consistently share what they are learning, several things happen. Prospective customers see the team’s judgment in action. Existing customers can respond with corrections and requests. Potential partners identify complementary opportunities. The founders accumulate a public body of work that differentiates them from tools making interchangeable claims.

This is especially valuable in AI and marketing software, where feature parity changes quickly. A competitor can replicate a workflow or add a similar model integration. It is much harder to replicate a library of trusted research, a distinctive point of view, accumulated customer language, and a community that returns because it learns something useful.

That is why the advice to focus on stories instead of features should not be understood as anti-product. Product quality still matters. Rather, stories help prospects interpret product quality in a real-world setting. They make the value legible.

Conclusion: aim for paid learning, not vanity growth

The path to the first 100 paid users is rarely a single launch tactic. It is a sequence of small acts of validation: noticing a repeated problem, understanding how people handle it today, building a focused solution, expressing the value in plain language, publishing credible proof, making checkout easy, and learning from every payment and cancellation.

The r/SaaS post from the two brothers is useful because it rejects a familiar early-stage trap. Signups feel exciting, but they can conceal uncertainty. Consistent work feels mundane, but it compounds. Features can be copied, but customer stories and firsthand understanding create trust.

For founders trying to get their first 100 paid users, the practical goal is not to generate the biggest audience possible. It is to create a repeatable path from a sharply defined problem to a customer who can recognize the outcome, complete a purchase, get value quickly, and decide to stay.

FAQ

Can a SaaS get its first 100 paid users without paid ads?

Yes, but “without paid ads” does not mean without marketing effort. Founders can earn early customers through useful content, direct customer conversations, communities, partnerships, SEO, product-led discovery, and referrals. The key is having a clear problem, credible proof, and a purchase path that does not create unnecessary friction.

Are signups a useful SaaS metric?

Yes, but signups are an early signal rather than proof of value. Measure signups alongside activation, checkout starts, completed payments, retention, and referrals. A signup becomes more meaningful when it reliably leads to a customer reaching a valuable outcome.

What should founders publish to attract early customers?

Publish material that helps the exact audience you want to serve: case studies, workflow teardowns, customer lessons, benchmarks, templates, research methods, and clear explanations of tradeoffs. The best content demonstrates genuine experience and gives the reader something useful even if they do not buy immediately.

When should a startup start running ads?

Consider paid acquisition after you can explain who converts, why they convert, what activation looks like, and whether customers retain long enough for the economics to work. Ads are most useful when they amplify a proven offer; they are least useful when the team is still unsure what problem it solves or which audience will pay.

What is the most important milestone after the first 100 paid users?

Retention. Review whether customers renew, use the core feature repeatedly, achieve the promised outcome, and recommend the product. The first 100 payments validate willingness to try; sustained retention is stronger evidence that the business is creating ongoing value.

How to Get Your First 100 Paid Users Without Ads