Your first 10 users: outbound for founders, using the sales skills you already have

Most first-time founders dread this part. You probably don’t. Writing a short message to a stranger, following up without being annoying, and turning a reply into a conversation is the job you already have.

But founder outbound is different from quota outbound in a few important ways, and if you run your usual playbook unchanged, you’ll optimize for the wrong result. Here’s how to adjust it.

What changes when it’s your product

• You’re not trying to close. For the first ten users, the goal is usage and honest feedback. Someone who tries it and tells you exactly why it’s confusing is worth more than someone who pays and disappears.
• Your list is small and personal. You’re not working a territory of thousands. A few dozen well-chosen people is a reasonable place to start.
• You can be honest about being early. “I built this and I’m looking for a handful of people to try it” is a better founder opener than any polished value prop. People like helping builders.
• Your sequence can be short. Two or three touches, then move on. Nobody is measuring your activity.

Building the list

Start with the people you talked to during validation. They already know the problem, they described it in their own words, and some of them asked to see what you build. That’s the warmest list you’ll ever have.

Then widen out in rings:

1. People from validation calls who asked to see it.
2. Colleagues and former colleagues in the same role.
3. Second-degree connections who match your customer profile exactly.
4. Members of communities where your users talk shop: Slack groups, subreddits, industry forums. Read the rules and contribute before you post anything about your product.
5. Cold prospects who fit a narrow profile, found the way you’d find them at work.

Track it in a simple spreadsheet: name, where they came from, date contacted, reply, next step. You know how to run a pipeline. Run a tiny one.

The message

Keep it short, specific, and about their problem rather than your product. A structure that works well for first users:

Hi [Name], you mentioned [specific pain] when we talked in [month]
(or: I saw your post about [specific pain] in [community]).

I built a small tool that [does one thing] for [role].
It's early, and I'm looking for five people to try it this week
and tell me what's broken.

Would you be up for a 20-minute screen share where you try it
and I mostly listen?

Notice what it asks for: a short call where they use the product while you watch. Sending a link and hoping is much weaker. Watching someone use your app for the first time will teach you more than any analytics dashboard can at this stage.

Follow up the way you would at work: once after a few days with something new (a screenshot, a one-line update), and once more a week later. Then stop and mark it closed. Silence is an answer, and your time is better spent on the next name.

Running the first-use call

You’ve run plenty of demos. This isn’t one. The instinct to drive the screen and narrate the value is exactly what you need to switch off.

• Send the link and ask them to share their screen.
• Ask them to do the core task without guidance. When they pause, ask “what are you thinking?” and wait.
• Write down every place they hesitate, misread a label, or click the wrong thing. Don’t explain; just note it.
• At the end, ask: “What would have to change for you to use this every week?”
• If it fits, ask about money directly: “If this worked the way you need, what would you expect to pay?” Treat the answer as a data point, not a commitment.

After the call, fix the one or two things that tripped them up most, then run the next call. Small fixes between calls compound quickly. By the fifth session you’ll usually notice people getting further on their own.

Founding offers

Once a few people are using it, you can offer early users something in exchange for commitment: a lower price locked in, direct access to you, a real say in what you build next. Be specific and honest about what they get, and don’t promise features you haven’t built.

You won’t get ten users from ten messages. Expect most people not to reply, the same as any outbound. The difference is that every person who does reply shapes the product, which makes each conversation worth more than a meeting booked at work.

The sprint’s launch module walks through this list, message, and offer step by step, and BLDR Lite is a free place to start if you’re still validating the problem.