Why should the founder do the first sales?
Early sales are research as much as revenue. In the first conversations you learn which problem people will pay to fix, the words they use for it, who signs and what nearly stops the deal. A hire or an agency cannot learn that for you, and they cannot change the product when a prospect says something important.
Buyers also react differently to a founder. A note from the person who built the product, asking a specific question, gets more patience than a polished sales sequence. Use that while it lasts: it fades once there is a sales team between you and the customer.
Paul Graham's essay Do Things That Don't Scale describes founders recruiting users one at a time, long after it feels efficient. In B2B that manual work pays twice: each conversation also shows you who signs, which you need when you write your sales process down.
Who should you target first?
Pick the segment where the pain is sharpest and the sale is simplest, not the biggest market. Good first segments share four traits:
- Frequent, painful problem: they hit it every week, not once a year.
- Buyer close to the user: in a 10 to 100 person company, the person who feels the problem can often approve the purchase.
- Reachable: you can name where they gather, online or offline, and find 200 of them without a paid database.
- Quick to try: they can start without a security review, a procurement process or a six-month integration.
Where do you find your first 10 to 100 customers?
Each stage needs different sources. The first ten usually come from people you can reach directly; the next ninety need a channel you can repeat every week.
| Stage | Where to look | What works |
|---|---|---|
| Customers 1 to 10 | Your network, former colleagues, investor portfolios, early-access signups | Personal notes asking for a 20-minute conversation about the problem, not a demo |
| Customers 10 to 30 | Communities where buyers ask for help, launch sites such as Product Hunt, niche directories | Answering questions in public, then following up privately with people who described the problem |
| Customers 30 to 100 | Buying signals, partners who serve the same buyers, integration marketplaces, focused outbound | A repeatable sequence written with the words your first customers used |
What does a 12-week founder playbook look like?
The plan assumes one founder spending about half of each week on sales, and a product people can use in some form, even a rough one. The targets are examples to pace yourself, not benchmarks: set your own before you start, so you cannot move them afterwards.
Track every person in one sheet: name, company, source, first contact date, stage, the exact words they used for the problem, and the next step with its date. The "exact words" column is the one founders skip and later miss most: it becomes your subject lines, your website copy and your pitch.
Weeks 1 and 2: write the hypothesis and fill the calendar
Write your ICP hypothesis in one paragraph, with three disqualifiers. List 50 people who fit or know someone who does: former colleagues, your investors' portfolio companies, early-access signups, people who commented on your launch. Send personal notes and introduction requests (scripts below). Goal: 10 problem interviews booked. If you cannot get 10, the segment is hard to reach, which is better learned in week two than in month six.
Weeks 3 and 4: run problem interviews, not demos
Hold 10 to 15 conversations of 20 to 30 minutes about the problem: when it last happened, what it cost, what they tried. Show the product only if they ask twice. Log their words and rate the pain from 1 to 3 after each call. You are done when one problem comes back in similar words from several people, with a workaround they already pay for in time or money.
Weeks 5 and 6: offer three design partnerships
Go back to the five to eight people with the sharpest pain and propose a time-boxed pilot with a success measure and a written price for afterwards. Aim to sign three. If nobody accepts a price, ask the people who declined what would have changed their answer.
Weeks 7 and 8: run the pilots and open one public channel
Hold a weekly call with each partner and fix whatever blocks real usage first. In parallel, start one repeatable source of conversations: answer questions in two communities, launch on a directory, or write to people who posted about the problem or asked for a tool like yours, using the cold email templates as structures. Aim for 20 new conversations.
Weeks 9 and 10: ask for the money
Hold each decision meeting on the agreed date and ask for the contract. Quote the founding-customer price to new prospects. Every no is useful if you learn the reason, so write it next to the name.
Weeks 11 and 12: write the playbook down
One page: who bought, the event that made them look, their words, the three most common objections with your answers, and the accepted price. Ask each paying customer for one introduction, then pick the source with the most conversations per hour spent and run it every week.
How do you reach out when nobody knows you?
Without a brand you have three assets: relevance, honesty and speed. Write to people who have just shown the problem, say plainly who you are and what stage you are at, and answer replies fast.
A first email that works without a brand
A fictional founder of an invoice-matching tool writes to a finance lead who posted about month-end close:
Subject: your month-end close post
"Hi Priya, I read your post about spending four days every month matching payouts to invoices. I am building a tool that does the matching automatically, and I am looking for five finance leads to try it on real data before launch. The pilot is free for six weeks, then $400 a month if it saves you the time. Open to a 20-minute call on Thursday to see if it fits?"
It names the trigger, admits the stage, states the price up front and asks for a small, dated next step.
What to avoid
- Pretending to be bigger than you are ("our team", "our enterprise clients") when it is you and a co-founder.
- Attaching a pitch deck to the first email.
- Asking for a demo before you know they have the problem.
- Sending automated volume from your main domain before you know which message works.
Reach companies with a reason to buy this week
Startories finds the buying signal, verifies the decision-maker and runs the outreach until they book a call.
Which scripts can you use at each step of the playbook?
Reword them to sound like you; keep the structure. Names and numbers are fictional, and curly braces mark facts you fill in.
Asking for a warm introduction (weeks 1 and 2)
Send the connector a short request plus a note they can forward unedited, so they can ask the other person before sharing an address.
To the connector: "Hi Sam, I am building {product} for {role}s at {company type} who {problem}. You know {name} at {company}. Would you be comfortable asking whether they would give me 20 minutes on how they handle it today? I am trying to learn, not sell. A note you can forward is below, and no worries if the timing is wrong."
The note to forward: "{Your name}, founder of {product}, is talking to {role}s about {problem} before deciding what to build next, and would value 20 minutes of your experience. No demo."
The problem interview (weeks 3 and 4)
Ask about what people did, not what they think of your idea. People are kind to founders and will call an idea great; what they did last month is harder to dress up. Rob Fitzpatrick's book The Mom Test is built on that rule. Questions that work:
- "Walk me through the last time {problem} happened. What did you do?"
- "How often does it come up, and who deals with it?"
- "What have you tried? What did you dislike about it?"
- "What does it cost you today, in hours, money or mistakes?"
- "If you fixed it, who else would have to agree? How was the last tool like this bought?"
- "Who else should I talk to about this?"
- Skip "Would you use a tool that…?" and "How much would you pay?". Both invite polite guesses.
Proposing a design partnership (weeks 5 and 6)
Subject: the Friday reconciliation pilot
"Hi Marcus, thanks for walking me through how your team reconciles payouts by hand every Friday. I would like to propose a design partnership: eight weeks from {date}, on your real data. Success means the Friday work drops from about four hours to under one, which we measure together in weeks four and eight. During the pilot you pay nothing and get a weekly call with me. If it works, the price is {amount} a month on an annual plan, locked for two years as a founding customer. In return I ask for the weekly call, honest feedback and, if the numbers hold, one reference call. Does {date} work for a kickoff?"
The measure uses their numbers, not yours, so the week-eight conversation is about a result you both saw.
Converting the pilot on the decision date (weeks 9 and 10)
"Hi Marcus, we are at week eight. Last Friday the reconciliation took 50 minutes, against about four hours before the pilot. As agreed, the next step is the annual plan at {amount} a month, and I can send the order form today. If something stops you from going ahead, tell me what it is and we will decide together whether it is worth fixing."
Asking for a referral after the first win (weeks 11 and 12)
"Glad the first month went well. Who else do you know who spends their Fridays on {problem}? If someone comes to mind, I will send you a two-line note to forward, so it takes you one minute." Ask once the customer has a result to describe, not on the day they sign.
How do you tell real interest from politeness?
Early conversations are full of false positives. The test is whether the person gave something up: time for a second call, an introduction to a colleague, access to data, or money. Compliments cost nothing and tell you little.
| What you hear | What it usually means | What to do next |
|---|---|---|
| "Really interesting, keep me posted." | A compliment, with nothing committed | Ask for one dated next step; if they decline, move them to a monthly update list |
| "Send me some information." | Often a polite way to end the call | Send one page and ask one question about their situation in the same email |
| "Can you show this to {colleague} next week?" | They are spending reputation inside their company | Book it before you hang up, and ask what the colleague will care about |
| "Can we try it on our real data?" | They are committing time and access | Offer the design partnership terms in writing, with a decision date |
| "We would pay for that if it did {feature}." | A hypothetical, useful but not a commitment | Ask how they handle {feature} today; build it only if several buyers say the same |
How do design partners work?
A design partner is an early customer who gets influence over the product and close support, and gives you real usage, weekly feedback and, if it works, a reference and a paid contract. Three to five partners in one segment is a manageable number; with more, you cannot serve each one well.
Agree on the problem and how success is measured
Write down what "working" means in their numbers: hours saved, errors avoided, revenue recovered.
Set a time box
Six to twelve weeks, with a weekly check-in and a decision date at the end.
Fix the price after the pilot
Put the post-pilot price in writing at the start, even if the pilot itself is free. It turns the pilot into a sales process instead of a favor.
Ask for something in return
Weekly calls, access to real data, and a case study or reference call if the results are good.
Decide on the date
Convert, extend once for a clear reason, or end it. Open-ended free pilots tend to become permanent free users.
How should you price your first deals?
Charge from the start. A paying customer tells you the problem is real; a free user tells you much less. Price against the value of the problem, not your costs or how unfinished the product feels to you.
A worked example: if your tool saves a finance team about 30 hours a month and their loaded cost is $60 an hour, the problem is worth around $1,800 a month to them. A price of $400 to $600 a month leaves them a clear return and leaves you room to raise prices later.
- Choose one value metric that grows with the customer (per location, per seat, per volume processed) and keep it.
- Offer a founding-customer price below your planned list price in exchange for an annual commitment, feedback and a reference, and give it an end date.
- Name a number on the first call when asked, then stop talking: "For a team your size it is {amount} a month, billed annually; founding customers get {lower amount} for two years. Is there an approval step I should know about?" Hesitation reads as doubt.
- If nobody pushes back on price, it is probably too low. Raise it for the next prospect.
- Avoid custom work for one customer unless it is something you want in the product anyway.
When should you hire a salesperson or automate outbound?
Hire or automate once the motion repeats, not before. Signs you are ready: you can state your ICP in one sentence, one message books meetings at a steady rate, you know the main objections and your answers, and closing has become the bottleneck rather than finding people to talk to.
Automate prospecting before you hire. Research, list building and follow-ups are where founders lose the most hours, and they are the easiest part to hand off. Keep the calls yourself until you have closed enough deals to write down how you do it. AI SDR vs human SDR and what an SDR really costs lay out the trade-offs.
Startories fits this stage: it finds companies that just showed a buying signal, checks them against your ICP, verifies the decision-maker and drafts the email from the event, and you can approve every message before it goes out. More in lead generation for startups.
How to start this week
Start week one today: write your ICP hypothesis, open the tracking sheet, list 50 people you can reach and send the first ten introduction requests. Hold ten problem conversations before you write a sales email. In parallel, register a separate sending domain so it is warmed up by weeks 7 and 8; the cold email deliverability guide covers the setup.
When you want a steady flow of conversations without spending evenings on research, look at the Startories plans: Starter includes one funnel and one ICP, and the first project starts with a 3-day full-access trial for $1.
Frequently asked questions
How do I get my first B2B customers with no network?
Go where your buyers ask for help: communities, launch sites, niche directories and public posts about the problem. Help in public first, then send short, honest notes to people who described the problem, asking for a conversation about it rather than a demo.
Should my first customers pay?
Yes, as early as you can. A short free pilot with a written end date and an agreed price afterwards is fine; open-ended free use is not. Payment is the clearest proof that the problem matters to the buyer.
What is founder-led sales?
Founder-led sales means the founder personally runs the sales process, from prospecting to closing, until it is repeatable. It is how a founder learns who buys, why and at what price, before handing parts of the process to salespeople or software.
How many design partners should I have?
Three to five in one segment is a manageable number. Fewer gives you too little evidence; more and you cannot give each one the weekly attention that makes the arrangement worthwhile for them.
When should I hire my first salesperson?
When the motion repeats: a clear ICP, a message that books meetings steadily, known objections with answers, and closing as your bottleneck. Consider automating prospecting first and hiring for closing once you can write down how you sell.
How long does it take to land the first paying B2B customer?
It depends on who signs. A manager buying a tool from their own budget can decide within weeks; a company with procurement and security reviews can take months. Plan the first quarter around interviews and design partners, and agree on a payment date before any pilot starts.