How to get your first users without a network

Pick a group you can actually reach

"Small businesses" is not a group you can reach. "Independent UK physio clinics with two to six practitioners" is, because you can search for them, name twenty of them, and work down the list.

The test is simple: can you write down ten specific people or organisations who have this problem today? If you cannot, narrow it again. You can widen later, and widening is far easier than starting from a market you cannot address.

• Name ten real prospects before you write any outreach.
• Prefer groups that already gather somewhere: a forum, a trade body, a local meetup, a subreddit for their job, not for startups.
• Prefer people you have some honest reason to contact, past work, a shared problem, a community you are already part of.

Recruit them manually

Y Combinator's standing advice to new founders is to launch early, talk directly to users, and get the first customers by hand rather than waiting for a channel to work. Paul Graham makes the same point at length in Do Things that Don't Scale: the first users have to be recruited individually, and that is not a sign something is wrong.

Manual recruitment feels slow because it is slow. It is also the only stage where you get to hear the exact words people use about their problem, which is what later marketing is built from.

Approach one person at a time

Stripe Atlas's guide to your first ten customers frames outreach the way experienced salespeople do: identify prospects individually, start by providing value, and make a specific small ask rather than a vague big one. That structure works whether the message is an email, a DM or a comment.

• Say who you are and why you are contacting this person specifically.
• Lead with something they can use whether or not they reply: a finding, a fix, a short teardown.
• Ask for one small thing. Fifteen minutes, or one test run, not "any feedback".
• Make declining easy. It costs you nothing and it protects the relationship.
• Follow up once. Once.

Turn a first conversation into a first user

Set the product up for them if that is what it takes. Import their data yourself, sit on a call while they try it, fix the thing that broke that afternoon. At ten users this is affordable, and it buys you the detail no analytics dashboard will give you.

Then look at behaviour rather than sentiment. Did they come back unprompted? Did they put real data in? Did they tell a colleague? Praise is not usage.

What to do when nobody replies

Silence usually means the group was too broad, the ask was too big, or the message was about you rather than them. Change one of those at a time so you can tell which one mattered.

Repeated silence across a run of targeted approaches is a signal to revisit the audience, the problem or the message. It is not proof the idea is wrong, but it is worth acting on in a fortnight rather than a year.

A first-user request that gets replies

Specific person, something useful up front, one small ask.

**Testers wanted, 3 independent physio clinics**

Who I'm looking for: clinic managers at UK physio practices with 2-6 practitioners who currently handle bookings by phone and paper diary.

What I've built: a scheduling tool that sends reminders and tracks no-shows. Rough, but working.

What I'm offering first: a one-page summary of the no-show reduction tactics I found while researching this, useful whether or not you try the tool.

The ask: 20 minutes on a call while you try booking a week of real appointments. I'll do the setup and the data import myself.

Happy to be told this isn't for you.