Founder-led sales: your first 10 customers

The first person selling your SaaS should be the person who built it. Not because founders are naturally good at sales. Most are not. It is because the early conversations are where you discover why people buy, what they call the problem, which objection is real, and whether the product solves something worth keeping.

Hand that work to a contractor too early and you get a tidy spreadsheet of objections filtered through somebody else's words. Do it yourself and the product changes in the same week the market teaches you what was wrong with it.

Founder-led sales is not about pretending to be a polished sales department. It is a practical way to get the first ten customers while you are still learning what a customer is.

Your first 10 customers are not a channel contest

There is a version of early sales advice that says you need LinkedIn automation, a cold-email domain, a giant prospecting tool, a CRM, a webinar, and a lead magnet before you can have a conversation.

You do not. You need a small list of people who plausibly have the job you solve, a reason to believe the timing might be relevant, and a thoughtful way to ask about their work.

The list should be narrow enough that you could recognise every name. "Marketing teams" is too broad. "Two-person B2B agencies that build client reports manually after each campaign" gives you a chance to write a message that sounds like it was meant for a human.

If you cannot define the list, start with customer discovery questions. Sales is not separate from research at this stage. The first call may be a discovery call. The next may be a product conversation. Both are useful when you are paying attention.

Find a reason to reach out now

Generic outreach fails because it gives the recipient the job of imagining why your message matters. Do that work yourself.

Look for a trigger that connects to the problem you solve:

• they posted a role that suggests the workflow is growing;
• they launched a new service or product that adds the pain;
• they publicly mentioned a workaround, a deadline, or a customer request;
• they recently changed teams, tools, or responsibilities;
• someone you both know has a concrete reason to introduce you.

This is not an excuse to scrape every public detail about a person. It is a way to make the opening relevant. A short message based on a real trigger beats a long template that claims to have "noticed your impressive work."

Write a first message that earns a reply

Your first message does not need to sell the product. It needs to make a conversation feel reasonable.

Use four parts:

1. A real context or trigger.
2. The one workflow you believe they may recognise.
3. A low-pressure ask for their perspective.
4. A clear exit, so saying no is easy.

Hi Maya, I saw your agency is hiring another client-success lead. I am speaking with small agencies that still build campaign reports by hand after every client call. Is that something your team deals with? I am testing a much smaller workflow for it and would value twenty minutes of context, even if it is not a fit.

Notice what is missing: fake familiarity, a calendar link in the first sentence, a feature list, and the claim that you will "save 10x." The message gives the person enough context to decide whether their own work is relevant.

For warm contacts, be equally specific. "Do you know anyone who would like my app?" creates work for the other person. "Do you know one independent recruiter who runs ten interviews a week and might tell me how they produce scorecards today?" is easy to answer.

Run a conversation before you run a demo

If a person replies, do not reward them with forty-five minutes of every feature you built. Start with their current process.

Ask what triggered the job last time, how they do it now, who is involved, where it breaks, and what it costs. Listen for the terms they use. Then show only the portion of the product that connects to what they said.

This has a nice side effect: a poor fit becomes useful research instead of a failed demo. If their problem is different, thank them and log the difference. You do not need to convert everyone. You need to learn who the product is actually for.

At the end, make a small, concrete next ask:

• try one real workflow with you present;
• introduce the person who owns the problem;
• agree to a paid pilot with a defined result;
• show you the current spreadsheet or process;
• schedule a follow-up after they have used the product.

"Let me know what you think" is not a next step. It is a polite way for both of you to lose the thread.

Sell a pilot, not a forever contract

The first ten customers do not need a complex annual deal. They need a fair way to try a product on a real problem, and you need a chance to see whether it earns its place.

Set a short pilot around a result: two weeks of reports prepared without manual copy-paste, one client onboarding run, one monthly reconciliation, or ten candidate scorecards. Define what you will set up, what the customer will do, the price if there is one, and what happens at the end.

Charging something, even a modest amount, changes the conversation. A paid pilot asks the buyer to decide whether the outcome matters. That is a stronger signal than a free account they may never open. The micro SaaS pricing guide can help you choose a simple first offer.

Do not confuse a custom pilot with permission to build every feature one customer wants. If a request only helps their unusual process, write it down and wait for a pattern. Early customers are valuable. They are not your product roadmap by themselves.

Keep a simple sales notebook

You do not need a complicated CRM for the first ten accounts. A spreadsheet or small database with a few disciplined fields is enough:

Write notes immediately after the call. The way a prospect said "I lose the whole afternoon to this" is useful. Your later summary of what they probably meant is less reliable.

Follow up without becoming a nuisance

Most early sales are not lost because the person said no. They are lost because the founder interpreted no immediate reply as a verdict, then sent either nothing or a sequence of increasingly anxious messages.

Follow up when you have a reason: you fixed the blocker they mentioned, added support for the workflow they described, or promised to send a short recording. Keep it short and make the action obvious.

You mentioned that the approval step needs a client-facing link. I added that version this week. Here is a 90-second recording using the same report flow we discussed. If it is useful, I can set up a test with one client next Tuesday.

One useful follow-up is better than four "just checking in" emails. If there is still no reply, close the loop politely and move on. You will learn more from the next ten good conversations than from trying to force a twentieth message through a closed door.

A two-week founder-led sales plan

Days 1 to 2: Define one narrow segment, one job, and two or three real triggers. Make a list of 25 people, not 500.

Days 3 to 5: Send ten personal messages a day. Research enough to make the opening genuine. Track replies and the language people use.

Days 6 to 8: Run discovery-first calls. Show the smallest relevant part of the product. Ask for a pilot when the job is clear.

Days 9 to 11: Onboard the first pilots manually. Fix blockers that repeat across them. Do not build optional requests in between calls.

Days 12 to 14: Review which segment replied, which message opened a useful conversation, which workflow activated, and what people were willing to pay for. Then make the next list smaller and better.

This work is how you find the path to the first 100 users. It is not scalable in the beginning. That is why it teaches you something before you spend money scaling the wrong message.

Frequently asked questions

When should a founder stop doing sales?

Not after the first few calls. Keep selling until you understand the buyer, the job, the objections, the offer, and a repeatable path to a useful conversation. You can bring in help when another person can reproduce something you actually understand.

How many prospects should I contact each day?

Start with ten carefully chosen people. The quality of the list and the relevance of the message matter more than a big activity number. Increase volume only after you know the message works for a defined segment.

Should I use cold email or LinkedIn messages?

Use the place where the person is likely to see a relevant, respectful note. The channel is less important than the context. Do not automate a message that has not worked manually.

What if I hate selling?

Treat it as structured learning, not performance. You are asking people how they work, showing a possible improvement, and offering a clear next step. The discomfort gets smaller when the product is tied to a problem they actually have.

The honest summary

Founder-led sales is less about charisma than proximity. You stay close to people with the problem, hear what they call it, show them a narrow fix, and ask for the smallest fair commitment that proves whether it belongs in their work.

Make a list of 25 real people. Send ten thoughtful messages tomorrow. Run the first calls as research. The goal is not to become a sales machine. It is to understand the ten customers who can teach you how to build one.

Once you have that sharp message, submit your product on makers.page and give the wider launch something specific to respond to. Distribution works better when the founder already knows who they are trying to reach.

Related reading:

• Customer discovery questions for startup founders
• How to find beta testers for your SaaS
• First 100 users without a marketing budget