Skip to main content
Customer Acquisition, Marketing & Growth

Your First 100 SaaS Customers: Interviews, Founder-Led Sales and One Channel

By Obaid Tariq, Founder & Lead Engineer · Published

Disclosure: AI Dev Planner offers an idea validation tool and builds SaaS products, so we have an interest in this question. Nothing here requires our tools or services, and we say where a cheaper route is fine. See our disclosure policy.

The short answer

Your first 100 SaaS customers almost always come from the founder doing unscalable work: choosing a narrow group of people with a specific, painful problem, interviewing them about how they handle it today, and selling to them one by one. Once around ten customers are paying, look at what they have in common and where they came from, then commit to the one marketing channel where more people like them already gather. Launch platforms such as Product Hunt and communities such as Indie Hackers can help, but they work best as moments that feed your main channel rather than as the plan itself.

How do I get my first 10–100 paying SaaS customers?

Get the first ten by hand: pick a narrow group of people you can actually name, talk to them one at a time, and ask them to pay before you automate anything. Get from ten to a hundred by studying what those first customers have in common and repeating whatever found them, through one channel, with a homepage and onboarding that no longer need you in the room. It is slow and manual at first, and that is normal rather than a sign that something is wrong.

Why the first customers come from you, not from marketing

The channels that scale, such as search, paid ads and partnerships, all depend on things a new product does not have yet: a message you know works, a page that turns visitors into signups, a budget to learn with, and months of time. Your first customers buy for a different reason. They buy because a founder understood their problem well enough to describe it back to them, and was willing to set the product up for them. That same work gives you the exact words customers use, which later becomes your homepage, your ads and your content.

Step 1: Narrow the target until you can name people

"Small businesses" or "marketing teams" is not a target you can sell to; you cannot find them, and your message has to be so general that it means nothing. Narrow by industry, size, role and situation until you could write a list. "UK bookkeeping practices with two to ten staff that still chase client documents by email" is narrow enough. A useful test, in our view: if you cannot write down 30 named people or companies who fit by the end of the day, the definition is still too broad. The next section covers how to define and test this ideal customer profile properly.

Step 2: Founder-led sales, step by step

  1. Build a list by hand. Collect a few dozen prospects from places they already show up: LinkedIn, industry directories, member lists of associations, conference speaker pages, people who have publicly complained about the problem in forums. A spreadsheet is enough.
  2. Send short, personal messages one at a time. Reference something specific to them, say in one sentence what problem you are working on, and ask for a 20-minute conversation about how they handle it today. Ask for their experience, not for a demo. Rules on unsolicited email and messages differ by country and by whether you contact a business or an individual, so check what applies to you before sending at any volume.
  3. Run a discovery conversation. Learn their current workflow, what it costs them and what they have already tried. The interview outline in the next section works for sales calls too.
  4. Show the product against their workflow. Only once you understand how they work now, show the product, or a prototype, doing the specific job they described. A tour of every feature is less persuasive than one problem solved.
  5. Ask for money. Name a price and ask whether they would like to start. A founding-customer price in exchange for regular feedback is reasonable; free indefinitely is not, because payment is the clearest signal that the problem matters. Send a payment link the same day.
  6. Onboard them yourself. Set up the account with them on a call, import their data, and check in after the first week. This is sometimes called concierge onboarding, and it shows you exactly where self-serve onboarding will break later.
  7. Write down every objection and question. These become your FAQ, your homepage copy and your onboarding checklist.
  8. Ask for introductions once they get value. "Who else do you know who deals with this?" is the most natural referral programme there is.

From ten to a hundred: what changes

Once roughly ten customers are paying, stop and look for patterns. Which messages got replies? Which customers set up fastest and use the product most? Where did they come from? The answers usually point to a sharper target and to one channel worth committing to, which is the subject of the question on owning a channel below. At the same time, start removing yourself from the process:

  • A homepage that explains who the product is for and what it does without you on a call. Our guide to SaaS conversion optimisation covers the elements that matter.
  • Self-serve signup, billing and the first steps of onboarding, based on what you did by hand for the first customers.
  • Published pricing, or a clear route to a price for larger accounts; see our SaaS pricing strategy guide.
  • A short written answer to each repeated question, which can live in the product, the help centre or a blog.
  • A habit of asking every new customer "how did you hear about us?" so you know which channel is working.

A weekly rhythm that keeps it moving

Founders who are also building the product tend to let sales slip, because code feels like progress and outreach feels like rejection. A rhythm we would suggest: block fixed time every week for new conversations, follow up with everyone you spoke to the previous week, review the objections you heard, and change one thing on the website or in onboarding based on them. Keep a simple pipeline with columns for contacted, spoke, trialling, paying and lost, and note the reason for every loss.

When a different approach makes sense

  • You already have an audience. If you run a newsletter, community or following in the niche, start there; one-to-one outreach is then a supplement rather than the engine.
  • The price is very low. If the plan costs a few pounds a month, personal sales calls cost more than the customer is worth. Lean on communities, content and self-serve onboarding instead, and keep conversations for learning rather than closing.
  • You sell to large organisations. Early customers are often design partners with long buying cycles, security reviews and procurement. Expect fewer, larger deals and plan for the paperwork.
  • Nobody replies or nobody pays. After a fair number of honest conversations, silence is information. It may be the message, but it may be the idea. Our seven-day SaaS validation method is a structured way to check before you build more.

How do I identify and interview my ideal customer profile (ICP) early?

Start with a written hypothesis of who has the problem most painfully and can pay to fix it, then test it in conversations about what people actually did in the past, not what they say they would do. Avoid pitching or asking leading questions, look for evidence that they have already spent time or money on the problem, and revise the profile after every handful of interviews.

What an ideal customer profile actually is

An ideal customer profile (ICP) is a description of the type of customer who gets the most value from your product, with the least effort to win and keep. It is not a persona with a stock photo and a name. For a B2B SaaS, a useful ICP describes the organisation and the situation, and separates the person who feels the pain from the person who signs off the purchase. Write a first version before any interviews, knowing it will be wrong in places.

Fields to include in an early ideal customer profile hypothesis
FieldQuestion it answersExample
OrganisationWhich kind of company, by industry, size and location?Independent veterinary clinics with one to three sites
SituationWhat is true about them that makes the problem acute?Booking by phone, no practice manager, staff shortages
TriggerWhat event makes them look for a solution now?Opening a second site, or a receptionist leaving
UserWho feels the problem every day?Reception staff and the head vet
BuyerWho decides and pays?The practice owner
Current workaroundWhat do they use today?Paper diary, a spreadsheet, a general booking tool
DisqualifiersWho looks similar but is not a fit?Corporate groups with central IT and existing systems

Finding people to interview

Use the same sources as early sales: your own network first, then LinkedIn, industry groups, forums and communities where the problem is discussed. Ask each person you speak to for one or two introductions to others like them; this is usually the fastest route to more interviews. Be honest that you are researching a problem, not selling. A reasonable starting point, in our view, is 15 to 20 conversations, continuing until new interviews mostly repeat what you have already heard.

Interview principles

Rob Fitzpatrick's book The Mom Test is the best-known treatment of this, and its central idea is simple enough to put in our own words: people will be kind about your idea, so do not ask them about your idea. Ask about their life. Specifically:

  • Ask about the past, not the future. "Tell me about the last time this happened" produces facts. "Would you use a tool that..." produces polite guesses.
  • Ask for specifics. Which day, which tool, how long it took, who was involved, what it cost.
  • Look for money and time already spent. Someone who has tried three tools, built a spreadsheet or hired help has a real problem. Someone who has never looked for a fix probably does not.
  • Do not pitch. If you describe your solution in the first half, everything after is shaped by it. Save any demo for a separate, clearly labelled part of the call, or a later meeting.
  • Treat compliments as noise. "That's a great idea" is not data. "Can I try it next week?" is.
  • Talk less. Aim for the customer to speak most of the time, and let silences run.

An interview script outline

  1. Context (2 minutes). Thank them, explain you are researching how people in their role handle a specific area of work, and ask permission to take notes.
  2. Their role. "Walk me through what a normal week looks like for you." Note where the problem area appears without prompting.
  3. The last occurrence. "Tell me about the last time you had to [do the task]." Follow up: what triggered it, who was involved, how long it took, what went wrong.
  4. Current solution. "How do you handle it today? What tools or people are involved?"
  5. Past attempts. "Have you tried anything else to fix this? What happened? Why did you stop?"
  6. Cost. "What does this cost you, in time, money or mistakes? Has it ever caused a real problem with a client or your boss?"
  7. Priority. "Where does this sit compared with the other problems on your list this quarter?"
  8. Buying process. "If you decided to pay for something to fix this, how would that decision get made? Who else would be involved?"
  9. Close. "Is there anyone else you think I should talk to?" and, if it fits, "Can I show you an early version when it's ready?"
Leading questions to avoid and what to ask instead
AvoidAsk insteadWhy
Would you use an app that automates your invoicing?How did you send invoices last month?Past behaviour is evidence; hypothetical use is a guess
Do you think this is a big problem?What happened the last time it went wrong?Lets them show the size of the problem instead of rating it
How much would you pay for this?What do you spend on this today, including people's time?Current spending anchors realistic value
Don't you hate doing this manually?How do you feel about the way it works now?Removes the answer you are hoping for from the question
Would this feature be useful?What have you tried to solve this so far?Shows whether they act on the problem at all

Making sense of what you heard

After each interview, write up the facts within the hour: their situation, the last occurrence, the current workaround, what they have spent, and any commitment they offered. Every five or so interviews, compare notes. Which types of organisation had the most painful version of the problem? Which had budget? Which had a trigger that made it urgent? Update the ICP table and drop segments that keep producing polite but uncommitted conversations. If you want a structured way to turn these notes into a validated idea and a build plan, the AI Dev Planner platform walks through the problem, audience and scope step by step, though a spreadsheet works too.

When a different approach makes sense

If you are your own target customer and have done the job for years, you can lean more on your own experience, but still interview others to check you are not a special case. If the market is regulated or technical, a few paid expert calls can save weeks. And if you already have a product with users, behavioural data from the product and short in-app surveys can replace some interviews, though not the conversations about why people chose you or left.

Is launching everywhere at once still effective, or should I focus on owning one marketing channel?

In our view, a launch everywhere is a useful one-off event but a poor strategy. It produces a short spike of attention that is hard to repeat. For steady SaaS customer acquisition, choose one channel where your ideal customers already spend time, commit to it for a fixed period, measure it honestly, and treat launches as bursts that feed it.

This section is about focus at the earliest stage. For a fuller comparison of each channel's fit, cost shape and time to results, see our B2B SaaS marketing strategy guide.

Why launching everywhere feels effective

Posting on launch sites, directories, social networks and every relevant community in the same week creates a burst of visits, signups and congratulations. It is genuinely useful for collecting early feedback and for testing which messages land. The problem is what happens the week after. Most launch traffic arrives in a day or two and fades, and much of it comes from other founders and the curious rather than buyers. If you then wait for the next launch, growth becomes a series of spikes with nothing between them.

What owning a channel means

Owning a channel means you understand it well enough to get predictable results: you know what to publish or send, how often, what it costs in time or money, and roughly what it produces in signups and customers. That takes repetition. Spread across ten channels, a small team never gets enough repetitions in any of them to learn. Concentrated in one, the same effort compounds: posts improve, a following builds, search pages gain authority, outreach templates sharpen.

Choosing a primary channel for early SaaS customer acquisition
ChannelGood fit whenTime to first resultsWhat it needsMain risk
Direct outreach (email, LinkedIn messages)B2B, clear buyer role, price high enough to justify a conversationDays to weeksAccurate list, personal messages, follow-up disciplineLooks like spam if it is not personal; local rules on unsolicited messages
Communities (Reddit, Slack and Discord groups, forums)Your customers already discuss the problem in publicWeeksGenuine participation over time; reading each community's rulesBans and lost trust if you promote too early or too often
Launch platforms (Product Hunt, directories)Product appeals to early adopters, makers or tech-curious buyersA day, then fadesPreparation, assets, time to respond on the dayAudience may not match your buyer; one-off spike
SEO and contentPeople search for the problem or category in words you can targetMonthsConsistent, genuinely useful writing; a technically sound siteSlow; no guarantee of rankings
Founder content on LinkedIn or similarB2B buyers who follow practitioners in their fieldWeeks to monthsA point of view, regular posting, real examplesEasy to drift into posting for other founders, not buyers
Partnerships and integrationsYour product sits next to a tool your customers already useMonthsSomething the partner gains; often an integrationDepends on someone else's priorities
Paid adsA message and page that already convert; known value per customerDaysBudget to learn with; tracking to paid customers, not clicksSpending before the basics work

How to choose your one channel

  1. Go back to your interviews. Where did customers say they look for answers, which communities or newsletters did they mention, and what words did they use? The channel is usually where the problem is already being discussed.
  2. Look at your first customers. If most came from personal outreach, that is a channel. If several found you through one community, that is a channel.
  3. Check the economics. A product priced in the hundreds per month per account can support sales conversations; a low-priced product generally needs channels that reach many people per hour of effort.
  4. Check your strengths. A founder who writes well has an advantage in content; one who enjoys conversations has one in outreach. Pick a channel you will actually keep doing.
  5. Commit for a fixed period. A reasonable starting point is 8 to 12 weeks with a weekly target for effort (for example, posts published or conversations booked) and a measure of outcome (qualified signups or paying customers). Effort targets keep you going while outcomes lag.
  6. Review and decide. At the end, keep going, adjust, or switch. Switching after a fair test is fine; switching every fortnight is not a test.

Supporting channels are fine, within limits

Owning one channel does not mean ignoring everything else. A simple website, a basic presence where customers might look you up, and replying when people mention you are table stakes. The discipline is in where you put the bulk of your weekly effort. Our guide to B2B SaaS marketing strategy compares the main channels in more depth, including Reddit and webinars.

When a different approach makes sense

A team with dedicated marketing staff can run two channels properly. Some developer tools reach their audience across several overlapping communities, where a coordinated launch is the normal way to get noticed. And if your product depends on network effects or virality, you may need a broader burst of attention to get past the empty-room stage. Even then, we would still name one channel as the primary one and measure it separately.

How do I attract customers from Product Hunt, Indie Hackers and online communities without an existing audience?

Earn a small audience before you need it: take part in the communities your customers use for several weeks, help people without linking to yourself, and share what you are building honestly. Then launch with preparation, read each platform's rules first, and spend the day answering every comment. Product Hunt says makers can post their own product and must not ask people directly for upvotes.

Communities reward contribution, not announcements

Without an audience, a launch post is a stranger asking for attention. Communities respond to people they recognise. The practical answer is to start participating before you launch: answer questions in your area of expertise, share useful things you have learned, and be visible as someone who knows the problem. This takes weeks, which is why it should start while the product is still being built.

Product Hunt: what its own guide says

Product Hunt publishes a launch guide, and a few of its rules and recommendations are worth knowing before you plan, though you should check the current guide because platforms change:

  • You can post your own product. Product Hunt's launch guide says makers can hunt their own products and that there is no discernible advantage to using a third-party hunter.
  • Use a personal account. The guide says company accounts are prohibited.
  • Do not ask for upvotes. You may share your launch link, but the guide says you cannot ask people directly to upvote; it recommends asking for feedback and comments instead, including in your first comment on the post.
  • Timing. Product Hunt says its homepage runs on a 24-hour cycle based on Pacific time and suggests scheduling for 12:01am Pacific if you have no other constraints, while also saying the best day to launch is the day you are most prepared. Posts can be scheduled up to a month ahead.
  • Not every post is featured. Product Hunt's help centre says featured posts are those that follow its guidelines, bring value to the community and are on topic; posts that are not featured stay live and visible in the "All" feed.
  • You can launch again. The guide says you can launch as often as you have significant new iterations of the product.

Prepare the assets in advance: Product Hunt's preparation guide asks for a thumbnail and at least two gallery images before the gallery shows on the post. Write a short tagline that names the problem, a first comment that explains why you built it and what feedback you want, and plan to be online for the whole launch day to reply to every comment.

Indie Hackers and founder communities

Indie Hackers and similar founder communities are made up largely of people building their own products. That makes them a good place to learn, find early testers, share honest progress updates and get feedback on pricing or positioning. They are a strong customer channel mainly if you sell to founders or small software teams. Posts that work tend to be specific and generous: what you tried, what happened, what you would do differently. A bare link with "check out my product" rarely does.

Niche communities where your customers are

The highest-value communities are usually the unglamorous ones your customers use for their work: an industry forum, a professional Slack group, a subreddit for a trade, a Facebook group for a type of business owner. Rules vary widely, and many are strict about promotion. Reddit's help centre, for example, says promotional content is not automatically spam but that some communities ban it entirely and moderators decide what counts as spam in their community. Our guide to promoting on Reddit without getting banned covers this in detail.

A community launch plan

  1. Pick three to five communities where your interviews say customers spend time, and read every rule, sidebar and pinned post.
  2. Participate for several weeks before mentioning the product. Answer questions; do not link to yourself.
  3. Share the build honestly where the community allows it: the problem you found, what you are trying, what you are unsure about. Ask for feedback, not signups.
  4. Prepare one strong launch post per platform, written for that audience, never the same text pasted everywhere.
  5. Give people a reason to stay in touch: a waitlist, a free tier, a useful template or a newsletter.
  6. Reply to everyone on the day, and follow up personally afterwards with people who showed real interest.
  7. Measure customers, not upvotes. Track signups and payments by source, using links you can attribute or a "how did you hear about us?" question.

When a different approach makes sense

If your customers are not active online in public, communities will be slow, and direct outreach or partnerships with trusted suppliers will usually work better. If your product is still unclear, launching publicly can lock in a confusing first impression; more interviews and a private beta may be the better next step. And if you would rather spend your time on customers than on building the product itself, an agency such as our MVP development team can handle the build, though for a simple first version a no-code tool or a single freelancer is often enough.

Frequently asked questions

How long does it take to get the first 100 SaaS customers?

There is no reliable universal timeline; it depends on price, market, how narrow your target is and how much time you spend selling. In our view founders should plan in months rather than weeks, and judge progress by whether each month brings more paying customers than the last.

Should I give my first users the product for free?

We would avoid indefinite free access. A discounted founding-customer price, or a paid pilot with a clear end date, tells you whether the problem is worth paying to solve. Free access can make sense for a short beta, provided you agree up front when paid plans begin.

Do I need a hunter to launch on Product Hunt?

No. Product Hunt's own launch guide says makers can post their own products and that there is no discernible advantage to using a third-party hunter. It also says company accounts are prohibited, so post from a personal account.

Is cold outreach acceptable for early SaaS sales?

Personal, relevant one-to-one messages are a normal part of founder-led sales, especially in B2B. Keep them specific, easy to decline and low in volume, and check the rules on unsolicited email and messaging in the countries you contact, because they differ and can depend on whether the recipient is a business or an individual.

Sources

  1. Product Hunt Launch Guide — Makers can hunt their own products; no discernible advantage to a third-party hunter; company accounts prohibited; you cannot ask people directly to upvote; suggested 12:01am Pacific launch time; best day is when you are most prepared; you can relaunch with significant new iterations. Accessed 19 October 2026.
  2. Product Hunt: Prepare for your Product Hunt launch — Homepage runs on a 24-hour cycle based on Pacific time; posts can be scheduled up to one month ahead; thumbnail and two or more gallery images required; ask for feedback, not upvotes, in the first comment. Accessed 19 October 2026.
  3. Product Hunt Help Center: Why is my post not on the homepage? — Featured posts follow guidelines, bring value to the community and are on topic; non-featured posts remain live and visible in the All feed. Accessed 19 October 2026.
  4. Reddit Help: Spam — Promotional content is not inherently spam; some communities prohibit promotion; moderators decide what counts as spam in their communities. Accessed 19 October 2026.

Recommendations without a source are AI Dev Planner’s own engineering opinion. Platform features and prices change; check the linked pages for the current position. Found an error? See our corrections policy.

Related guides

Browse all 50 questions in the SaaS & web development guide.

Validated the problem and ready to build?

If your interviews point to a product worth building, we can help you scope a first version that your early customers can actually use. If a no-code tool would do the job for now, we will say so.

Talk through your plan MVP development services