Most founders think the hard part of SaaS is building the product. For many, the harder part is that nobody arrives after launch. A beautiful app with no customers is an expensive hobby.

The good news is that your first ten customers rarely come from advertising or clever growth tactics. They come from conversations. This guide walks through a practical, founder-led approach, and explains why it also makes your build cheaper and safer.

Start before you build

The strongest signal you can have is a prospect saying, before the product exists, that they would use it and pay for it. Commitment can take several forms: a signed letter of intent, a deposit, a paid pilot or a firm agreement to be the first user. Interest alone is not commitment. See our idea validation checklist.

Step 1: Be specific about who it is for

“Small businesses” is not a customer. “Accounting practices with five to twenty staff in the UK that still collect documents by email” is. A narrow definition makes outreach easier, messages sharper and the product more focused.

Step 2: Build a list of 50 prospects

• People you already know or who know someone in the target group.
• Members of professional associations and online communities where your audience gathers.
• Contacts of past colleagues, clients or suppliers.
• People who recently posted about the problem you solve.

Step 3: Have problem conversations, not sales pitches

Ask how they handle the task today, what it costs them in time and money, what they have tried and what frustrates them. Listen far more than you speak. The aim is to learn whether the problem is painful enough to pay to solve.

Step 4: Offer a founding-customer deal

Invite the most engaged people to be founding customers: a discounted or locked-in rate, direct access to you and a say in what gets built, in return for feedback and, later, a testimonial. It rewards early belief and gives you a handful of real users.

Step 5: Deliver by hand if you must

Before the software is polished, you can deliver the outcome manually, a method often called a concierge approach. It proves value, shows exactly what the software should automate and keeps early customers happy.

Step 6: Turn happy customers into the next ones

• Ask for introductions to peers.
• Publish a short case study with permission.
• Invite customers to talk about results in their own words.
• Keep notes on objections and use them to refine your message.

A simple weekly rhythm

These are starting points, not rules. Adjust to your market and capacity.

How this changes what you build

Customer conversations tell you what to include and what to leave out, which directly lowers cost. A first version built around three or four validated workflows is cheaper, faster and far more likely to be used. See what to cut before you build and how to avoid scope creep.

Common mistakes

• Building for months before talking to anyone.
• Treating polite interest as demand.
• Targeting everyone.
• Giving the product away without asking for commitment or feedback.
• Ignoring the customers you have to chase new ones.

Planning the build

Once you have conversations and early commitments, you are ready to turn them into scope. A Discovery Sprint does that: a $345 PRD with scope, flows, architecture and cost within 24 hours, credited toward the build. Builds start at $3,500, with the final quote based on scope.

Frequently asked questions

How many conversations do I need?

Enough to hear the same problems repeated. Many founders find patterns after ten to twenty.

Should I build a prototype for the conversations?

A simple prototype or mock-up can help, but do not wait for it. Conversations come first.

What if nobody will commit?

That is valuable information. Revisit the problem, the audience or the offer before spending on a build.

Do I need a marketing budget?

Not at this stage. Direct outreach and referrals usually beat paid advertising for first customers.