How you get your first 100 SaaS users shapes far more than an early vanity metric. It determines whether you learn from real buyers, build a product people return to, and find a repeatable growth motion before paid marketing consumes a limited budget.

A recent question in r/SaaS asked founders what they would prioritize if they were starting from zero with almost no marketing spend: how they got their first users, how they priced, which channels produced the best return, and what they would tell their earlier selves. It is the right bundle of questions, but the order matters. Before a founder optimizes a channel, they need evidence that the product solves an urgent problem for a clearly defined group.

The Reddit post did not include top-comment responses in the material available for this article, so it would be misleading to present a community consensus that was not there. Instead, the question offers a useful framework for a practical early-stage playbook: validate manually, sell directly, make onboarding observable, retain users, then turn what works into a channel.

Why the first 100 SaaS users are different

The first 100 users are not simply a smaller version of the next 10,000. At the beginning, scale is often the enemy of learning. A founder who brings in hundreds of poorly matched free users may see more sign-ups but learn less than one who works closely with 15 people experiencing the same costly workflow problem.

Early traction has three jobs:

Prove pain: prospective customers can describe a problem in concrete terms, including what it costs them in time, revenue, risk, or frustration.
Prove behavior change: users complete the key action and return often enough to suggest the product fits into their workflow.
Prove willingness to pay: at least some customers will exchange money, budget approval, or a serious purchase commitment for the outcome.

These are separate proofs. A product can get attention without retention. It can get free users without buyers. It can even close a few deals through the founder’s network without proving that a broader market exists.

That distinction is consistent with the retention-first argument made by Andreessen Horowitz: acquiring customers before they stay creates a leaky bucket. For a bootstrapped SaaS company, this is more than a strategy aphorism. If a $20-per-month customer leaves after one month, spending time or money to replace them is a poor foundation for compounding growth.

Measure active users, not just registrations

Define an activation event before seeking more traffic. The event should represent the moment a user receives the product’s promised value, not a shallow action such as creating an account.

For example:

An AI meeting-notes app might define activation as importing a meeting, generating notes, and sharing them with a teammate.
An ecommerce analytics tool might define it as connecting a store and viewing a profitable insight from the first dashboard.
A creator SEO platform might define it as publishing or optimizing a page that reaches a measurable ranking or content-quality milestone.
A vertical operations tool might define it as completing a real client workflow, such as sending an estimate or scheduling a job.

Track the path to that event: visitor, sign-up, connected data source, first value, second session, and paid conversion. With only a few dozen users, manual notes can be more useful than a polished analytics stack.

Start with a narrow ideal customer profile

The highest-leverage decision for a low-budget SaaS is usually who not to serve. “Small businesses,” “marketers,” and “creators” are markets, not useful early customer profiles. They contain different jobs, budgets, language, software stacks, and purchase processes.

A strong early ideal customer profile, or ICP, is specific enough that a founder can make a list of 50 plausible people without buying a database. It might be “independent Shopify brands doing $1 million to $5 million in annual sales that run weekly email campaigns but lack a dedicated analyst,” rather than “ecommerce companies.”

Specificity makes product development and distribution less expensive. It tells you where people already gather, which integrations matter, what words they use to describe pain, and who can introduce you to them.

Use the problem, frequency, and access test

Score potential niches using three simple questions.

Problem: Is the problem painful enough that people already spend money, time, or workarounds on it? A spreadsheet, virtual assistant, agency, or complicated sequence of tools can be a positive signal.

Frequency: Does the problem happen weekly or daily? Products used only once a year need an exceptionally high value per use or a different commercial model. Habitual workflows create more natural retention.

Access: Can you reach 30 to 50 likely users directly? A huge market is not helpful if every buyer is hidden behind enterprise procurement. An accessible niche with visible communities, directories, events, or social profiles is often a better start.

Vertical software is particularly attractive when a founder has domain access. Bessemer Venture Partners’ work on vertical software emphasizes that industry-specific products can build defensibility through workflow depth, data, distribution, and domain knowledge. For an early founder, the immediate lesson is simpler: choose a sector where you can understand the work well enough to earn trust.

Do customer discovery before polishing the product

A common early mistake is to ask people whether they like an idea. Most people are polite, hypothetical answers are cheap, and feature requests can send a product in ten directions. Better discovery examines what a person already does.

Ask for a recent, specific story:

“Walk me through the last time this happened.”
“What did you do before you found a workaround?”
“Which tools, files, or people were involved?”
“How long did it take?”
“What happens if this is done badly or late?”
“Have you paid to solve it? What made that solution insufficient?”

Do not lead with your product. If the interviewee describes a different problem than the one you plan to solve, that is useful evidence, not a failed call.

Turn interviews into a problem ledger

After each conversation, record the same fields: role, company or audience type, triggering event, current workaround, cost of the problem, urgency, tools used, exact language, and whether the person agreed to try or pay for a solution. After 15 to 20 interviews within one narrow segment, patterns should become visible.

Look for repetition, not enthusiasm. If multiple people independently use the same phrase—“I have to reconcile this every Friday,” for example—that phrase may belong in the landing page, outreach message, and product navigation. If every interview yields a different workflow, the ICP may be too broad.

Discovery also protects founders from confusing a feature request with a purchase decision. Someone may request an integration because it sounds convenient, yet refuse to switch behavior. The stronger test is a commitment: a pilot, a data export, an introduction to the budget owner, a prepayment, or scheduled implementation time.

Sell the outcome manually before automating it

For many SaaS products, the first version should be a productized service with software around it. This is not a retreat from building a SaaS business. It is a way to observe the messy steps that software eventually needs to handle.

Suppose a founder is building an AI tool that turns customer-support tickets into weekly product insights. Rather than building a full self-serve platform immediately, they can ask five support leaders for exports, generate and review the reports manually, deliver them every week, and learn what customers actually act on. The founder will discover whether clustering, prioritization, Slack delivery, CRM links, or executive summaries matter most.

Manual work has limits, but it creates three advantages early:

It gets a real outcome to customers quickly.
It exposes edge cases that no product specification anticipated.
It creates a credible paid offer before a large engineering investment.

The key is to be transparent where needed. Do not claim an automated capability that is actually done by hand. But do not wait for complete automation before asking people to pay for a valuable result.

Founder-led sales is research with stakes

At this stage, founder-led sales is not optional busywork delegated away as soon as possible. The founder is the person best able to connect customer language to product decisions. Every lost deal should produce a reason code: wrong segment, insufficient urgency, price, missing integration, trust concern, timing, or unclear value.

A simple early outreach sequence can work without spam:

Build a short list of people who visibly match the ICP.
Reference a relevant observation about their workflow, content, store, team, or company—not a generic compliment.
Ask for a 15-minute research conversation, not a purchase.
If the pain is confirmed, offer a concrete pilot tied to an outcome and timeframe.
Follow up with a summary of the problem in the customer’s own words and a specific next step.

A message such as “I’m building an AI tool for anyone who needs better analytics” will disappear. “I noticed your agency publishes monthly client reports. I’m researching how paid-media teams reconcile Meta and Google data before client calls; would you be open to telling me how that works today?” gives the recipient a reason to respond.

A practical plan to get the first 100 SaaS users

The first 100 should not all be acquired in the same way. Early users fall into cohorts: design partners who tolerate rough edges, early buyers who need the outcome now, referral users who trust an existing customer, and later self-serve users who need clearer onboarding.

A useful target is not “100 accounts at any cost.” It is “100 qualified users, including a meaningful group who activate, return, and either pay or show a credible path to payment.” The exact mix depends on price and market. A $500-per-month B2B tool may need 10 excellent customers more than 100 casual users, while a $15-per-month prosumer product can reasonably optimize for a broader base.

Days 1–30: find the wedge

Choose one ICP and conduct 20 to 30 conversations. Build a basic landing page that describes one painful job, one outcome, and one call to action. The page does not need elaborate branding; it needs clarity.

Recruit three to five design partners. Offer hands-on implementation and frequent access to the founder in exchange for candid feedback, permission to study the workflow, and a clear discussion of paid continuation. Avoid offering “free forever” as the default. Free access often creates a weak signal, and it makes later pricing conversations harder.

Days 31–60: deliver value and instrument activation

Onboard users personally. Watch them use the product over a call or review session recordings with permission. Document each point where they hesitate, ask a question, or fail to reach value.

At this stage, fix onboarding friction before adding broad feature sets. If users cannot connect their data, understand the first screen, or see the promised result in the first session, acquiring more users will only increase support load.

Ask activated users one direct question: “What would you do if this product disappeared tomorrow?” Their response reveals whether you are a nice-to-have, a useful tool, or a critical workflow. Follow that with “Who else do you know that has this exact problem?” A referral request works best after a specific value moment, not in the first welcome email.

Days 61–90: repeat one motion

Choose the channel that produced the highest proportion of qualified, activated users—not merely the most clicks. Build a repeatable routine around it. That could be 20 carefully researched outbound messages per weekday, one useful teardown in a niche community each week, a partner webinar every month, or a template library that attracts high-intent search traffic.

Create small proof assets from early wins: a case study, an anonymized before-and-after workflow, a quote, a short demo, or an implementation guide. Proof lowers the trust barrier for people who do not know the founder personally.

By the end of this period, a founder should know the answers to practical questions: Which segment activates fastest? What promise gets a reply? What objection blocks payment? How long does time-to-value take? Which customers retain after the initial novelty fades? Those answers are the beginning of a go-to-market system.

Choose low-cost channels by buyer intent, not popularity

There is no universally best SaaS marketing channel. A channel is effective when it reaches a defined buyer at the point where they can understand and act on your offer. For a low-budget founder, the best early channels tend to be high-intent and labor-intensive rather than broad and automated.

Direct outreach and warm introductions

Direct outreach is often the fastest way to obtain learning because it allows targeting and conversation. It is especially suitable for B2B products with a clear buyer, a meaningful price point, and a narrow niche.

Warm introductions outperform cold outreach when possible, but founders should not wait for an enormous network. Former colleagues, customers from a prior role, community operators, consultants, and complementary software vendors can all provide relevant introductions. The request should be precise: ask for two people who match a defined role and workflow, not “anyone who might be interested.”

Communities and founder-led education

Niche Slack groups, Discord servers, forums, LinkedIn groups, professional associations, and relevant subreddits can be valuable, but only if participation precedes promotion. Answer questions, share a genuinely useful framework, publish a teardown, or offer office hours. A founder who appears only to post a launch link is likely to be ignored or removed.

The source Reddit question itself reflects why communities matter: founders use them to compare channels, pricing, and early mistakes. Yet community posts are most effective when they contain an insight that is useful without buying the product. A checklist for auditing a workflow can attract exactly the people who later need a tool to automate it.

Search-driven content and free tools

SEO is rarely the fastest route to the first ten users, but it can become a durable low-cost channel when the product solves questions people already search for. Start with bottom-of-funnel queries: “[workflow] template,” “[competitor] alternative,” “how to [job] for [niche],” and “best [category] for [specific use case].”

A free calculator, generator, checklist, benchmark, or template can be more useful than generic thought leadership. For example, a SaaS for freelance marketers might publish a client-reporting template that naturally reveals the manual work the product removes. The free asset must serve the same ICP as the paid product; otherwise, it creates irrelevant traffic and support demands.

Partnerships and ecosystems

Partnerships can be disproportionately effective for vertical and workflow SaaS. Agencies, consultants, fractional leaders, educators, and adjacent software providers already have trust with the target customer. Offer a referral arrangement, co-created resource, integration, or implementation package.

Do not treat a partner logo as distribution by itself. A useful partnership has a shared customer, a clear benefit for the partner, an easy handoff, and a measurable next action. Start with one partner and one campaign rather than a broad affiliate program with no activation plan.

Pricing should test value, not hide it

The r/SaaS prompt asks about pricing models, and founders often seek a universal answer: freemium, free trial, monthly subscription, annual contract, usage-based pricing, or a one-time fee. The right choice depends on the product’s value delivery and the buyer’s risk.

For an early product, pricing is an information system. It tells you whether the outcome is important, whether the buyer understands the offer, and whether your market segment has budget authority. Avoid treating price as a final polish layer.

Common early pricing models

Paid pilot: Best for B2B products that require setup, customization, or a measurable operational result. Define a limited scope and outcome, such as a 30-day implementation for one team. A paid pilot filters for commitment better than a free proof of concept.

Free trial: Works when a user can reach value independently and quickly. If setup requires integrations, training, or organizational approval, an unguided trial may produce abandonment rather than evaluation.

Freemium: Works when free users can create natural distribution, such as shareable outputs, collaboration invites, or an ecosystem of templates. It is risky when hosting, AI inference, support, or onboarding costs are significant and upgrades are unclear.

Subscription with a concierge onboarding offer: Useful for a new B2B SaaS with moderate complexity. Charge a recurring fee and personally help the first customers succeed. The service component is temporary learning infrastructure, not necessarily the final model.

Usage-based pricing: Fits products whose value and costs scale with measurable consumption: API calls, documents processed, messages sent, or transactions analyzed. It can reduce entry friction, but customers need predictable billing guardrails.

Price against the customer’s alternative, not the hours spent coding. If the product saves a $100,000-per-year employee several hours a month, reduces a costly error, or improves a revenue-producing workflow, its value may be much higher than an inexpensive tool category suggests. Conversely, an early product with uncertain reliability may need a lower entry point or a pilot structure to earn trust.

Retention is the growth channel that founders underfund

Retention is often discussed as a metric after acquisition, but it should shape acquisition from day one. The best early marketing message is not the one that attracts the most sign-ups; it is the promise the product can reliably fulfill for the customers most likely to stay.

Andreessen Horowitz’s retention-focused coverage makes a valuable distinction between acquiring customers and creating durable usage. For a SaaS founder, retention work means understanding the recurring trigger that brings a user back. Is the product needed every time a campaign launches, every week before a report, every day when a ticket arrives, or only when a rare problem occurs?

Build a retention loop

A basic loop contains four elements:

A trigger in the customer’s existing workflow.
A fast, observable value event.
A reason to return or involve another collaborator.
A prompt, integration, report, or notification that reconnects the product to the workflow.

For a marketing SaaS, a weekly performance digest sent before the team’s planning meeting may be more effective than a dashboard users must remember to open. For an AI writing tool, saved brand context and editorial collaboration can make the second use more valuable than the first. For an operations product, calendar, email, accounting, or CRM integrations may be retention features rather than optional polish.

Talk to churned users, too. A short, non-defensive message can uncover whether they left because the product lacked value, was too difficult to implement, was replaced by an incumbent, had a pricing mismatch, or simply arrived at the wrong time. Churn reasons should influence ICP and onboarding decisions, not just the cancellation flow.

What to avoid when marketing budget is close to zero

A constrained budget forces useful trade-offs. The goal is not to avoid all experiments, but to avoid spending heavily before the product and message can convert attention into durable usage.

Be cautious with the following:

Broad paid ads before activation is working. Ads can create fast traffic and fast false confidence. Without a clear ICP, landing page, onboarding path, and conversion measurement, they mostly purchase ambiguity.
Launching everywhere at once. Product Hunt, social media, communities, newsletters, and directories can create a burst of activity, but a broad launch is difficult to learn from. Pick the place where likely buyers already are.
Building every requested feature. Early users may describe symptoms, not the underlying job. Prioritize improvements that make the core outcome faster, more reliable, or easier to adopt across the chosen segment.
Discounting indefinitely. Founding-customer pricing can be sensible, especially in exchange for feedback and a case study. Permanent bargain positioning can attract price-sensitive users who churn and make future price increases painful.
Treating followers as pipeline. Audience building is useful, but likes and impressions do not equal activated customers. Connect content to a specific audience, problem, and next action.
Outsourcing customer understanding too early. Agencies, contractors, and growth hires can accelerate a proven motion. They cannot substitute for the founder’s early knowledge of customer language and objections.

Lessons from larger SaaS companies, applied carefully

Related SaaS coverage often features large outcomes, including SaaStr’s conversation with Vimeo CEO Adam Gross about operating a profitable public SaaS company and SaaStr’s lessons from Zeta Global CEO David Steinberg. Those companies operate at a scale far beyond a new bootstrapped product, so founders should resist copying enterprise tactics wholesale.

Still, larger companies reinforce several enduring principles: clear customer value, disciplined unit economics, focus on durable retention, and an operating model that matches the market. The early-stage version of those principles is not a complex revenue-operations system. It is knowing exactly why a customer bought, how they achieved value, and what would cause them to renew.

The same caution applies to growth benchmarks. Public-company net revenue retention, sales efficiency, and multi-product expansion are useful later. They should not distract a founder who still cannot explain why five target users would change their behavior next week.

The second-order advantage of focus

A narrow initial market can feel limiting, but it improves nearly every part of the business. Product decisions become easier because edge cases belong to a recognizable workflow. Testimonials become more persuasive because prospects see themselves in the customer. Content gains search relevance. Partners know whom to refer. Sales calls become repeatable.

Expansion should come after the product has a credible foothold. The best signal is not that adjacent markets exist; it is that current customers request the product for a neighboring team, use case, or segment. That expansion is pulled by real behavior rather than pushed by founder anxiety about market size.

A founder operating system for the first 100 users

Early traction is less about finding one perfect tactic than maintaining a rhythm of conversations, delivery, measurement, and decisions. A simple weekly operating system can keep a small team from drifting into feature production without market feedback.

Each week, review:

How many conversations did we have with people matching the ICP?
What exact problem language or objection repeated?
How many new users reached the activation event?
Where did users fail or delay in onboarding?
Which customers returned and got value again?
What did we charge, what did buyers say about price, and what commitments did we receive?
Which one channel produced the strongest qualified conversations?

Then choose one product improvement and one distribution experiment for the following week. Keep the experiments small enough that results are interpretable. Changing the ICP, offer, price, landing page, product, and channel simultaneously makes it almost impossible to know what worked.

The founder who asked r/SaaS where to spend time is asking the central early-stage question. The answer is not “marketing” or “product” in isolation. Spend time where the two meet: direct contact with a narrow group of customers, a demonstrable outcome, and a retention loop that makes each new customer more valuable than the effort required to acquire them.

Conclusion: earn the right to scale

The first 100 SaaS users are won through proximity to the customer. Start with a painful, frequent problem in a segment you can reach. Conduct interviews that examine real behavior, sell a manual or semi-manual outcome, charge early when appropriate, and personally guide users to value.

Once a cohort activates and retains, identify the acquisition source that brought those customers—not just the largest number of sign-ups—and repeat it. Whether the eventual engine is SEO, partnerships, product-led growth, communities, outbound, or paid acquisition, it will work better because the founder first learned what customers truly value.

FAQ

How long should it take to get the first 100 SaaS users?

There is no reliable universal timeline. A self-serve prosumer tool may reach 100 sign-ups quickly, while a higher-priced B2B product may take months to reach 100 qualified users. Prioritize activated and retained users over speed alone.

Should an early SaaS offer a free plan?

Offer freemium only when free users can reach value cheaply and there is a clear reason to upgrade or invite others. For products requiring hands-on onboarding, expensive AI usage, or significant integrations, a trial or paid pilot is often more informative.

What is the best marketing channel for a new SaaS?

The best channel is the one that reliably reaches your specific ICP and creates qualified conversations or activated users. For many early B2B founders, direct outreach, introductions, communities, and partnerships outperform broad paid advertising.

How do I know if users are retained?

Define a meaningful recurring action tied to your product’s value, then measure whether users complete it again after the first session or billing period. Also interview returning and churned users to understand the workflow trigger behind the data.

Should I build more features before charging customers?

Usually, no. Charge when you can deliver a valuable outcome, even if some steps are manual. Early payment or a serious pilot commitment is stronger validation than feature requests or positive feedback alone.

How to Get Your First 100 SaaS Users Without a Big Budget