133. First 10 Customers Playbook

The first 10 customers are not only revenue. They are your laboratory.

Your goal is to find customers who are close enough to the problem, willing enough to engage, and honest enough to teach you what must become repeatable.

What kind of customer counts?

Not every early user should count as one of the first 10. Count customers who create useful proof.

Customer type	Count?	Why
Exact ICP with real pain and a next step	Yes	Strong learning and commercial signal.
Paying customer outside ICP	Maybe	Useful cash, but may distort the product.
Friendly user with no buying power	No, unless learning is specific	Good for discovery, weak for business proof.
Free pilot with clear success criteria	Maybe	Counts if they commit time, data, access, or reference.
Free signup with no usage	No	Attention is not customer proof.
Custom services client	Maybe	Count only if the work reveals repeatable product patterns.

The first 10 should teach you who to pursue next, not only make the customer slide look less empty.

What the first 10 should prove

The first 10 customers should answer:

Who buys fastest?
What pain creates urgency?
What promise gets a meeting?
What proof is missing?
What must be manual?
What price conversation is possible?
What value must be delivered before asking for references?

Define ICP

Write a narrow ideal customer profile:

Field	Example prompt
Customer type	What kind of company or person?
Size/stage	Revenue, employees, users, transaction volume, or maturity
Trigger	What makes the problem urgent now?
Buyer	Who can say yes?
User	Who must use it?
Current workaround	What do they use today?
Pain proof	What measurable cost exists?
Access path	How can the founder reach them?

Do not say “startups” or “SMBs” if you can say “bootstrapped B2B SaaS founders with 5 to 30 employees selling to US customers.”

Build a warm list

Create 50 to 100 names.

Sources:

Former colleagues
Customers from past work
Founder friends
LinkedIn second-degree connections
Industry WhatsApp or Slack groups
Communities
Investors and advisors
Agencies or consultants serving the segment
Existing waitlist or newsletter

Score each prospect:

Score	Meaning
3	Exact ICP and warm path
2	Good fit but colder path
1	Adjacent fit or uncertain urgency

Start with 3s. Early sales is hard enough; do not make access harder than necessary.

Write outreach

Use a short, specific message.

Hi [Name], I am working on [specific problem] for [specific segment]. I noticed [reason they fit]. I am trying to understand how teams like yours handle [workflow/problem] today. Could I ask for 20 minutes this week? Not a generic demo. If it is not relevant, I will still learn quickly.

Follow-up sequence:

Initial message
Practical follow-up with one sharper problem statement
Value follow-up with a short insight or example
Close-the-loop message asking if someone else is better

Do not spam. Personal relevance beats volume for the first 10.

Founder follow-up system

Most first customers are not lost in the first message. They are lost in weak follow-up.

Use this system for every serious prospect:

Follow-up	Timing	Purpose
1	Same day as call	Summarize problem, next step, owner, and date.
2	2-3 days later	Share the promised material or ask for the missing artifact/stakeholder.
3	5-7 days later	Reconnect to the business cost or trigger.
4	After silence	Close the loop politely and ask whether timing, priority, or fit is the issue.

Example close-the-loop note:

I do not want to keep chasing if this is not a priority. Should I close this for now, or is there a useful next step around [specific problem]?

A real prospect will often clarify timing. A weak prospect will disappear, which is also useful information.

Run discovery calls

Your call flow:

Confirm context
Ask about the last real instance
Map current workflow
Understand cost and urgency
Ask who owns the decision
Only then show the rough solution or promise
Ask for the smallest serious next step

The first 10 customers should not be won by polished demos alone. They should be won through problem understanding and founder trust.

Early customer contract

For each of the first 10, write the informal contract even if the legal document is simple.

Field	Answer
Problem promised	What did we say we would solve?
First value event	What should happen first for the customer to feel progress?
Customer commitment	Time, data, access, stakeholder, payment, feedback, or reference.
Founder commitment	Setup, support, product change, reporting, or review call.
Success criteria	What would make the customer say this worked?
Review date	When will we evaluate?

This prevents the first 10 from becoming emotional promises in the founder’s head. Write it down so delivery, learning, and reference asks are grounded in the same expectation.

Qualification gate

After each call, decide whether the prospect deserves active pursuit.

Gate	Strong signal
Pain	They describe a recent, specific, costly problem.
Fit	They match the ICP tightly enough to teach repeatable lessons.
Access	You can reach the buyer or decision path.
Urgency	There is a trigger, deadline, loss, compliance need, or active workaround.
Commitment	They agree to a next step that costs time, data, money, or reputation.
Learning	Even if they do not buy, the conversation improves ICP, product, price, or message.

If fewer than three gates are strong, learn politely and move on. The first 10 phase dies when founders chase every lukewarm conversation.

Close a pilot

A good pilot has:

Clear problem
Clear owner
Clear start date
Clear success metric
Clear scope
Clear price or commercial next step
Clear end date

Weak pilot:

Try it and tell us what you think.

Strong pilot:

In 30 days, we will help your team reduce invoice follow-up time by 50 percent for these 100 accounts. If we hit that, we discuss a paid monthly plan.

Deliver value

For the first 10, founder involvement is allowed. Hiding founder effort is not.

Track:

Setup time
Manual work needed
Support questions
Moment of first value
Repeated usage
Buyer feedback
User feedback
Payment friction

Turn manual work into learning. Which steps should become product, documentation, onboarding, or sales qualification?

Ask for references

Ask only after value is delivered.

Reference ask:

It looks like this helped with [specific outcome]. I am trying to speak with more founders/operators who have the same problem. Is there one person you would feel comfortable introducing me to?

Ask for:

Referral
Testimonial
Case study permission
Logo permission
Internal expansion
Review call with another stakeholder

First 10 tracker

Customer	Segment	Source	Pain	Status	Value delivered	Payment	Reference
				Contacted / Call / Pilot / Paid / Churned

Customer commitment ladder

Treat the first 10 as a ladder of commitment, not a logo hunt.

Commitment	What it proves
Gives 30 minutes	Problem is relevant enough for attention
Shares current workflow	Trust and pain are real enough to open the process
Introduces another stakeholder	The problem may matter inside the organization
Gives data or a sample task	They want practical help
Runs a pilot	There is willingness to change behavior
Pays	Value, budget, and urgency are becoming real
Refers you	Trust is strong enough to risk reputation

Do not skip the early rungs. A founder who jumps from “nice conversation” to “close customer” often mistakes friendliness for demand.

First 10 learning memo

After every two customers, write a short memo:

Question	Answer
What did these customers have in common?
What was different?
What did they buy: product, founder trust, urgency, or price?
What manual work was required?
What should we change in the pitch?
Which customer should we avoid next?

The first 10 are not only revenue. They are a data set. If you do not write down the patterns, the founder’s memory will rewrite the story.

Pilot delivery board

For the first 10 customers, sales and delivery are the same learning loop. Track delivery with the same seriousness as acquisition.

Customer	Promise made	First value event	Manual work needed	Support issue repeated?	Payment status	Reference potential	Decision
					Not asked / verbally agreed / invoice sent / paid	Low / medium / high	Keep / narrow / avoid

Review the board every Friday. Ask:

Which promise was easiest to deliver?
Which customer reached value with the least founder pushing?
Which manual step repeated across good customers?
Which support issue should become onboarding, documentation, or product?
Which customer paid, referred, or expanded after seeing value?
Which customer created custom work that should not be repeated?

The early company should not only ask “Can we close them?” It should ask “Can we make them successful without lying to ourselves?”

First 10 decision gate

Do not rush from 10 customers to hiring sales or increasing marketing spend. First run a decision gate.

Gate	Green signal	Red signal
ICP	6-8 customers share a similar profile	Every customer is different
Pain	Same urgent workflow appears repeatedly	Customers like different minor benefits
Delivery	First value is repeatable	Every customer needs custom founder work
Payment	Buyer path is becoming clear	Revenue depends on favors, discounts, or chasing
Reference	Happy customers can introduce similar buyers	Customers are happy but not willing to refer

If two or more gates are red, do not scale yet. Tighten the ICP, change the promise, or redesign onboarding before adding volume.

India field notes

In India, the first 10 customers may buy because of founder credibility, a warm introduction, local trust, or the promise of personal attention. That is not bad. It is often how early markets open. But separate founder-trust demand from product demand.

Ask:

Would this customer still buy if a salesperson, not the founder, handled the call?
Is payment possible without repeated chasing?
Is the use case similar enough to repeat?
Does the customer expect custom service that cannot scale?

Reference design

Do not wait until the tenth customer to think about references. Design for references from the beginning.

For each customer, ask:

Question	Why it matters
Would we want ten more customers like this?	Prevents bad-fit revenue from shaping the company.
Can this customer introduce a similar buyer?	Reveals network quality and trust.
Would their story persuade the next buyer?	Helps positioning and proof.
Can we deliver value without heroic founder work?	Protects repeatability.
Are they willing to be honest with us?	Improves product learning.

A reference is not only a logo. A useful early reference can be:

A warm intro.
A private reference call.
A quote.
A case study later.
A workflow artifact.
A testimonial inside a specific community.

The first 10 should create learning, revenue signal, and trust assets.

Pilot close script

When the prospect has real pain, move from conversation to commitment.

Use this close:

“It sounds like [problem] is costing you [cost/risk/time]. We can run a small pilot focused only on [outcome]. It would take [time], require [customer effort], and cost [price or commercial structure]. At the end, we will decide whether this should continue. Is this worth doing now?”

If they hesitate, diagnose:

Hesitation	Ask
Value unclear	”What outcome would make this worth it?”
Price concern	”Is the concern budget, ROI, timing, or trust?”
Authority unclear	”Who else needs to agree before this can start?”
Timing weak	”What happens if you do nothing for 60 days?”
Trust weak	”What proof would make you comfortable trying this?”

Do not bully customers into pilots. But do not hide from the money question. Commitment is the difference between interest and demand.

First 10 postmortem

After the first 10 customers or serious pilots, write a postmortem.

Question	Answer
Which three customers were best and why?
Which three were worst and why?
What did the best customers have in common?
What promise made them act?
What manual work repeated?
What objections repeated?
What price/payment pattern appeared?
What should we stop selling?
What should the next 20 customers prove?

The first 10 are not the end of founder sales. They are the raw material for a sharper go-to-market system.

First customer quality scorecard

The first 10 customers should not be judged only by whether they paid. Some early customers make the company sharper. Others create revenue but distort the product, consume founder time, and teach the wrong lessons.

Score each customer from 1 to 5:

Dimension	1 = weak	5 = strong
ICP fit	Adjacent or random buyer	Exact target segment
Pain urgency	Curious but not urgent	Active pain with clear cost
Buyer access	Only friendly user	Decision maker or strong champion
Commitment	Free advice or vague pilot	Payment, PO, signed pilot, data access, or time commitment
Delivery repeatability	Bespoke work	Same workflow as other target customers
Reference value	Cannot speak publicly or privately	Can introduce similar buyers or become credible proof
Learning value	Teaches little	Reveals repeatable objections, workflow, price, or onboarding needs
Payment quality	Slow, unclear, or politically difficult	Clear payment path and commercial owner

Use the score like this:

Average score	What to do
4.0-5.0	Actively seek more similar customers.
3.0-3.9	Keep learning, but identify what must improve before scaling.
2.0-2.9	Treat as custom learning, not proof of repeatability.
Below 2.0	Do not let this customer shape the roadmap.

Add one note after each score:

We would/would not want ten more customers like this because [reason].

This sentence is powerful. It forces the founder to separate money from strategy. Early revenue is good, but not all early revenue is equally useful. A customer who pays a little, activates quickly, introduces peers, and uses the product every week may be more valuable than a large logo that requires custom work and never becomes repeatable.

First 10 operating board

Run the first 10 customers from a visible board. The founder should be able to look at it every morning and know what must move today.

Column	Meaning	Founder action
Target account	Named person or company that matches the first ICP	Confirm why they fit before outreach.
Contacted	Outreach sent	Follow up with a useful reason, not “checking in.”
Discovery scheduled	Call booked	Prepare a problem hypothesis and research brief.
Qualified	Pain, buyer, and urgency look real	Define next step and success criteria.
Pilot/proposal	Commercial or usage commitment is being discussed	Keep scope narrow and dated.
Active customer	Product or service is in use	Watch activation and support load.
Reference/referral	Customer can help find more similar buyers	Ask specifically and respectfully.
Closed lost / not now	Not a fit or no current urgency	Record the reason without shame.

Review the board twice a week:

Which accounts are stuck because of founder follow-up?
Which are stuck because the pain is weak?
Which are stuck because the buyer is missing?
Which active customers are teaching repeatable lessons?
Which customer type should be removed from the target list?

The board is not for vanity pipeline. It is for learning velocity.

Commitment ladder

Early founders often jump from “interested” to “will you buy?” too quickly, or they avoid commitment completely. Use a ladder.

Commitment	What it proves	When to ask
Second call	The problem deserves more time	After a strong discovery conversation.
Artifact/data share	The customer trusts you with workflow context	When current process matters.
Buyer/user intro	The problem crosses roles	When the first contact is not the decision maker.
Pilot success criteria	The customer can define value	Before any serious pilot.
Paid diagnostic	The pain is worth money before full product maturity	When the solution needs manual work.
Paid pilot or subscription	Commercial demand exists	When value and success criteria are clear.
Reference/referral	Trust and value are real enough to risk reputation	After activation or first value.

Do not make every customer climb every step. The ladder helps you notice when a relationship has stopped moving.

Referral and reference system

The first 10 customers should help you find the next 20, but only if you ask well.

Ask after a concrete win:

It looks like [specific outcome] is working for your team. We are trying to speak with 5 more [same segment] teams who have a similar [workflow/problem]. Is there one founder/operator you would feel comfortable introducing us to?

Make the referral easy:

You can forward this if useful:

"I have been speaking with [Founder] at [Company]. They are working on [specific problem] for [specific customer type]. If [problem] is relevant for you, it may be worth a 20-minute conversation."

Track:

Who referred whom.
Whether the referred account matched the ICP.
Which customer stories created trust.
Which references are private only versus public.
Whether the customer is comfortable being quoted, anonymized, or introduced.

Do not pressure customers for public logos too early. A private reference can be enough for early sales.

First 10 quality review

The first 10 customers are not equally valuable as evidence. Some customers create learning and reference power. Others create distraction, custom work, and false confidence.

Review each customer:

Customer	Strong evidence	Weak evidence
Segment fit	Matches the customer you want more of.	One-off buyer outside the intended wedge.
Pain	Has a repeated, urgent, costly problem.	Bought because of founder relationship or curiosity.
Buyer clarity	Buyer, user, approver, and blocker are visible.	Only one friendly contact exists.
Delivery fit	Can be served with a repeatable process.	Needs custom work that does not generalize.
Payment quality	Pays or commits on clear terms.	Free, heavily discounted, delayed, or unclear payment.
Reference value	Can explain the value to similar customers.	Cannot be named, quoted, or used even privately.
Expansion signal	Has a logical next use case or broader team.	One narrow use with no repeat path.

Then sort the first 10:

Customer type	What to do
Ideal repeatable customer	Study deeply and ask for references.
Useful learning customer	Keep if learning is high and delivery cost is controlled.
Strategic logo but heavy support	Be careful; define scope and success criteria tightly.
Revenue but wrong segment	Serve responsibly, but do not let it steer roadmap.
High-customization customer	Charge appropriately or decline future similar work.

The first 10 should teach you which next 100 you want. If they only create revenue and chaos, the phase is not complete.

Warm Network Expansion Plan

Most founders exhaust their obvious warm network in the first week. The mistake is to then switch to generic cold outreach without learning how warm access actually worked. Treat warm access as a system.

Map every useful conversation into three possible next paths:

Path	Ask	Why it works
Same-role referral	”Who else owns this same workflow?”	Finds similar users or buyers.
Buyer-path referral	”Who signs off when this becomes a paid tool?”	Finds authority and procurement reality.
Adjacent-segment referral	”Which type of company feels this problem more painfully?”	Improves ICP when the current segment is weak.

Use this referral tracker:

Source person	Segment insight	Referral asked	Referral received	Fit score	Follow-up date
		Same-role / buyer-path / adjacent		1-3

Ask for one referral at the moment of highest clarity, not at the end of a vague call. The best moment is after the customer has described a real workflow, current workaround, or painful trigger.

Referral message:

This is very helpful. I am trying to speak with 5 more people who directly handle [workflow] when [trigger] happens. Is there one person you trust who sees this problem often? A short intro is enough; I am not asking them to buy anything.

If every good conversation produces zero relevant referrals, that is also evidence. Either the segment is not networked, the problem is not important enough to share, or trust is not yet high enough.

Bad-Fit Revenue Firewall

Early revenue is exciting, especially in India where a paying customer may feel like proof after months of uncertainty. But the first 10 phase can be damaged by customers who pay while pulling the company away from its intended wedge.

Before accepting a customer outside ICP, fill this firewall:

Question	If yes	If no
Can we deliver without custom roadmap damage?	Consider accepting.	Decline, charge high, or make it a services engagement.
Will this teach something useful for the target ICP?	Capture learning deliberately.	Treat as cash only, not validation.
Can we set tight scope and review date?	Put it in writing.	Do not proceed casually.
Is payment clear and timely?	Good cash signal.	Risk of distraction plus collection pain.
Would we want five more like this?	It may be an ICP clue.	Keep it away from roadmap decisions.

Use this language when declining or containing bad-fit work:

This is a little outside the narrow problem we are focused on right now. We can either keep it to [specific limited scope] for [price/timeline], or I can point you toward a better-fit option. I do not want to overpromise.

The goal is not to be arrogant. The goal is to protect learning quality. Bad-fit revenue can keep the lights on, but it should not quietly become strategy.

Common mistakes

Trying to make the first 10 look scalable before learning why they bought
Taking any customer who will pay, even if they distort the product
Giving away pilots without asking for commitment
Confusing founder trust with product demand
Forgetting to ask happy customers for references

Done when

The first 10 phase is done when you know:

Which customer type buys with least explanation
What promise creates urgency
What manual delivery is required
What price conversation is possible
Which customers you want more of
Which customers you should stop pursuing