How to get your first 10 SaaS users when your audience is tiny

Define a buyer you can actually find

“Small businesses” is not a usable market. Neither is “creators” or “founders.” Define a group by role, situation, and trigger. A strong early segment sounds like: solo SaaS founders who launched in the last 30 days and are manually combining Stripe and analytics data.

The trigger matters because it explains why the person might care now instead of someday.

EARLY BUYER
Role: [who they are]
Situation: [what is happening now]
Painful workaround: [what they currently do]
Trigger: [why this matters this week]
Visible place: [where you can identify them]

Build a list of 30, not a database of 30,000

Collect thirty names manually. Use launch directories, focused communities, LinkedIn, X, GitHub, newsletters, or people already in your network. Add one sentence explaining why each person plausibly fits.

Manual research is appropriate at this stage because the goal is to learn what makes a prospect qualified. Automating before you understand qualification only scales irrelevance.

• Name and product
• Why they fit
• Relevant recent signal
• Best contact channel
• Date contacted
• Expected response date
• Outcome and follow-up

Ask for a useful next step

Do not open with a feature list or ask strangers for a 30-minute “brain-picking” call. Mention the relevant observation, name the problem plainly, and make a small request. Depending on the product, the ask might be a blunt first impression, permission to send a 60-second demo, a short test, or a paid pilot.

Personalization means relevance, not writing a biography about the prospect.

OUTREACH
Hey [name] — noticed [specific situation or trigger].
I built [product] for [buyer] who are tired of [painful workaround].
It helps them [specific outcome] without [costly alternative].
Would it be useful if I sent a [60-second demo / example / blunt teardown]? No pitch deck.

Treat replies as a funnel of learning

Separate activity from outcomes. Track sent, replied, conversation, activated, and paid. If nobody replies, change the target or opening relevance. If people reply but do not try, inspect the promise and ask. If they try but do not activate, watch the onboarding path. If they activate but will not pay, investigate urgency, trust, and price.

Each stage tells you what to fix next. Without this separation, founders often respond to weak outreach by rebuilding the dashboard.

• No reply → target, relevance, channel, or timing.
• Reply but no trial → promise or next step.
• Trial but no activation → onboarding or time-to-value.
• Activation but no payment → urgency, trust, differentiation, or price.

Ask every useful user for one adjacent introduction

When someone gets value, ask who else has the same problem. Do not ask for a generic social share. Request one relevant introduction and provide a short forwardable explanation.

Ten users do not need to arrive at once. Two good users can reveal the language that earns the next four, and those four can reveal the blocker that earns the next ten.

INTRO ASK
Glad [specific result] was useful. Do you know one other [buyer type] dealing with [problem]? If yes, I can send a two-line note you can forward. No pressure if nobody comes to mind.

Define what counts as one of the first ten

A signup is not automatically a user. Count someone when they match the target segment and reach the product’s first meaningful outcome. Track paid customers separately; combining curious visitors, activated users, and buyers hides the exact stage that needs work.

For a reporting product, activation might be importing real data and generating a useful report. For a scheduling product, it might be publishing a link and receiving a booking. The event should prove value happened, not that onboarding was completed.

• Visitor: encountered the promise.
• Signup: accepted the cost of creating an account.
• Activated user: reached the first useful outcome.
• Retained user: returned for the same job or a second result.
• Paying customer: committed money to keep or expand the value.

See the first-ten loop in practice

A founder selling a proposal-review tool begins with “freelancers.” Manual research reveals that small web agencies send higher-value proposals and visibly complain about slow client decisions. Thirty agency owners become the list. The first ask offers a teardown of one recent proposal rather than a generic free trial.

Three owners reply, two share a proposal, and one reaches the first result. The founder notices that nobody cares about writing speed; they care about whether a client can compare options. The promise narrows, onboarding starts with an existing proposal, and the activated user introduces a second agency. The list, conversation, product change, and referral all reinforce the same segment.

FIRST-TEN BOARD
Qualified names: [30 target]
Contacted: [number]
Replies: [number]
Conversations: [number]
Activated users: [number]
Retained users: [number]
Paying customers: [number]
Repeated blocker: [exact words]
Next introduction ask: [one adjacent buyer]

Turn ten users into a repeatable acquisition clue

After ten qualified activations, compare the users who moved fastest. Look for the trigger, source, promise, and workflow they share. The goal is not a perfect persona; it is a sharper hypothesis about where the next twenty similar buyers can be found.

Do not scale a channel because it produced accounts. Scale only when a recognizable segment repeatedly reaches value and at least some users show retention, referrals, or payment behavior.