A solo founder's first ten customers usually require a narrow customer definition, direct conversations and hands-on help reaching a useful outcome. Treat ten as a learning milestone, not a promise that one outreach script will produce ten buyers.
A broad launch can generate attention without teaching you why anyone purchased. The first customer work is more valuable when you can connect a person's situation, the reason they tried your product and the work required to help them succeed.
Define one buying situation
Describe a customer in terms of a job and a trigger. A small agency manager preparing the same client handover every week is more actionable than small businesses. The trigger explains when your offer becomes relevant.
Write who uses the product, who approves spending and who grants access to necessary information. Those may be three different people. If your outreach reaches only enthusiastic users without buying authority, you need to learn how an internal purchase happens.
YC: How to Get Your First 10 Customers emphasises locating buyers and doing early acquisition personally. Apply that as a research principle, not a universal preference for any one channel.
Choose one channel for a defined learning cycle
List legitimate routes to the segment: relevant introductions, an industry event, an opt-in group discussion, a suitable public post or a carefully targeted business enquiry. Pick the channel where you can understand context and respond personally.
Do not equate a public profile with permission for unlimited follow-up. Read platform rules and community expectations. If a person declines or does not want further contact, stop.
For one cycle, keep the segment and offer reasonably stable. Constantly changing audience, channel and message makes it hard to interpret results. The purpose is not to prove your original choice correct. It is to see where a real buying conversation can begin.
Use an introduction that makes sense without a funnel
A useful first message names the context, explains why the person is relevant and makes a small request. For example: I am exploring how small agencies handle incomplete client handovers. You mentioned that problem in a public discussion. Would you be comfortable describing the last time it happened?
That is a research request. Do not disguise a sales demo as an interview. If you already have a product and intend to sell it, say so plainly and connect the offer to the observed problem.
Avoid an entire founder biography, an unexplained calendar link or a request that asks the recipient to do your positioning work. Specificity is more useful than manufactured familiarity.
Keep a customer learning ledger
Use one row per prospective account with these columns:
| Field | Why it matters |
|---|---|
| Buying situation | Shows whether the segment is coherent |
| Route to conversation | Identifies a channel you can repeat legitimately |
| Recent problem | Separates real events from general enthusiasm |
| Next commitment | Makes progress observable |
| Blocker | Reveals access, timing, value or trust problems |
| First useful outcome | Shows whether onboarding worked |
| Delivery effort | Exposes the cost behind an apparent sale |
Do not count a booked meeting as a customer. Define customer consistently, such as an account that has paid for a stated offer. Record free users separately so the commercial picture stays clear.
A hypothetical first-account sequence
Imagine a solo founder building a project-document checklist for small design studios. This example is hypothetical. The founder asks an existing professional contact for an introduction to a studio manager who handles handovers.
The first conversation reveals a specific recurring gap. The founder offers a bounded pilot on one project and explains the manual preparation involved. The manager introduces the person who can approve the fee and grants access to a redacted sample.
After the pilot, the founder documents what the studio actually used, what still required help and whether another project presents the same need. A second introduction should be requested only if the first customer is comfortable making it. One successful account is evidence worth exploring, not permission to claim the whole industry needs the product.
Make onboarding part of acquisition
Paul Graham's essay on unscalable work advocates recruiting initial users manually. For a solo founder, that can include helping a customer reach the first result and learning where setup fails.
Log every intervention. If you secretly clean data, fix configurations and prepare outputs, your product may appear easier to adopt than it is. That labour is useful research when visible and a misleading growth signal when hidden.
Schedule time for delivery before promising more pilots. Ten customers who each need constant founder intervention can exceed your capacity before they establish a repeatable business.
When to change the plan
If conversations happen but nobody sees a reason to try, revisit the problem and offer. If customers try but cannot reach value, fix onboarding or delivery. If you cannot reach the segment, investigate the channel before assuming there is no demand.
Set a review date and a learning question rather than a guaranteed conversion target. Stop repeating a channel when it produces no relevant conversations or requires behaviour people do not welcome. The first ten are useful when they reveal a repeatable buying and delivery pattern, not merely a number for a launch announcement.