How to Find Your First Ten Customers
Finding the first ten customers is a practical learning target, not a guarantee or proof of product-market fit. Start with a narrow group you can reach personally, make a specific offer and learn from actual buying and usage behavior. The objective is to discover why suitable customers commit and what it takes to serve them.
Define who belongs on the list
Describe the customer by problem and buying situation, not only company size or age. Identify the trigger that makes the issue urgent, the person who experiences it and the person who can approve payment.
Build a small, researched list from legitimate public information, introductions and communities where outreach is permitted. Record why each prospect might fit. Avoid buying an indiscriminate contact list and calling the resulting messages customer research.
Include current alternatives in your notes. A spreadsheet, an employee’s manual work or tolerating the problem may be a more important competitor than another startup. The competitive-market guide helps turn this information into a focused entry offer.
Make a small, clear offer
Describe the problem you address, the result the customer can reasonably expect, the work included, the price basis and the limits. If the product is unfinished, say what exists and what remains manual. Do not describe a prototype as an established service.
A paid pilot can create stronger evidence of willingness to pay than a compliment, but only if the buyer understands the scope and receives appropriate value. Free research sessions can still be useful; keep their purpose distinct from sales.
For outreach, explain the specific reason for contacting the person and make the next step easy to decline. Use truthful identity and subject information. U.S. commercial email falls under CAN-SPAM requirements, including business-to-business messages; other jurisdictions may impose different consent and privacy obligations. Check the rules that apply before launching an outreach sequence.
Worked example: a manual acquisition pilot
Illustrative example. A fictional founder offers maintenance scheduling for small gyms. She researches 30 potentially suitable operators and records the evidence of fit for each. She asks a few existing contacts for introductions and sends individual messages through appropriate business channels to the rest.
Her offer is a paid four-week pilot for one location, with setup and one review meeting. She states that the product currently handles recurring inspections but does not manage payroll or contractor payments.
Twelve operators agree to a conversation, five buy and four complete the first scheduled maintenance workflow. These invented counts are not expected response rates. They show why the log must include more than the number of messages sent. The founder investigates why one paying customer did not activate before expanding the list.
She then changes one part of the process based on evidence: the next pilot requires a named onsite owner before setup. If later pilots activate more reliably, she records the change and remaining uncertainty rather than claiming a controlled causal result.
Use conversations to discover the buying process
Ask about the last time the problem occurred, its consequence and how it was handled. Ask who else must approve a purchase and what would prevent adoption. Demonstrate the relevant workflow using safe sample data. A vague “would you use this?” usually leaves too many conditions unstated.
End with a concrete next step: a proposal, a paid pilot, a later check-in with permission or a clear decision not to proceed. Respect a refusal. Do not keep chasing someone because the spreadsheet has not reached ten customers.
Work toward ten in stages
Use the first few customers to investigate whether the offer can be delivered, then use later customers to test whether the path repeats beyond friendly introductions. These are learning stages, not prescribed quotas or response-rate benchmarks.
At the beginning, prioritize a clear problem and willingness to work through an honest pilot. After a few deliveries, look for independent customers who buy for the same reason without requiring a completely different product. By the time you approach ten, you should have a better explanation of the segment, offer, buying process and service cost.
Do not exclude a difficult result to keep the story tidy. Record refunds, inactive purchasers and customers who received unusually extensive founder assistance. Ten names on an invoice list can represent very different evidence depending on what happened after payment.
| Stage of learning | Question to answer | Useful record |
|---|---|---|
| Initial commitment | Will a suitable buyer take a concrete step? | Offer, terms and reason for buying |
| First delivery | Can the customer obtain value? | Outcome, assistance and failures |
| Repetition | Does another buyer need the same thing? | Similarities and differences |
| Less founder dependence | Can the path work with a documented process? | Labor, exceptions and handoff |
| Next acquisition batch | Is another small investment justified? | Costs, quality and remaining uncertainty |
Build a prospect worksheet you can act on
For each prospect, record business or person, evidence of fit, problem trigger, appropriate contact route, current alternative, status and next action. Include the source and date of public information. Keep personal data limited to what the task reasonably needs and apply the relevant obligations.
A good “why this prospect” note might say that the business has several sites and publicly recruits a maintenance coordinator. That suggests a question to investigate, not proof of pain. Avoid writing speculative personal claims as facts.
Ask contacts for introductions with a clear explanation of whom you want to meet and why. Do not make the introducer imply experience with a product they have not used. Let them decline, and avoid treating an introduction as an endorsement or a commitment to buy.
Write a specific, honest outreach message
Fictional example, to adapt only with verified facts and applicable compliance requirements:
I am building a maintenance scheduling service for small gym operators. Your public site shows several locations, which is why I thought the workflow might be relevant.
The current pilot helps a named manager schedule recurring checks and record completion for one location. It does not arrange emergency repairs or pay contractors.
I would like to understand how you coordinate those checks today and show the current workflow if it seems relevant. A pilot is paid and has a defined scope; I can explain the details before any commitment.
If this is not relevant, I will not pursue it further.
This is a content example, not a complete legally compliant email template. U.S. commercial-email requirements also concern matters such as identity, postal address and opt-out handling. Other jurisdictions may require consent or another basis for contact. Use the linked official guidance and appropriate advice for the actual activity.
A useful follow-up adds context or answers an outstanding question. Repeating the same request indefinitely does not create fit. Record a refusal and stop the relevant outreach.
Structure the conversation around recent behavior
Begin with the situation: when did the issue last occur, who handled it and what happened? Then investigate the current workaround, its cost or consequence, and the conditions for change. Ask the person to show a nonconfidential example if that is practical.
Only then demonstrate the part of the offer connected to their task. Avoid a full feature tour that obscures whether the central workflow fits. Ask what would prevent use, who else must approve and what a successful pilot would look like from their perspective.
Do not argue every objection away. “We already have a solution that works” may be a valid reason not to buy. Distinguish poor fit from missing evidence, unclear explanation and a genuine product gap. Use the pattern across conversations to decide what to change.
Make the first sale a clear agreement
Specify scope, duration, customer inputs, price, payment timing, support and the decision at the end. State what remains manual and what the product cannot do. Obtain appropriate contractual advice where necessary; a friendly pilot still creates expectations.
Agree an observable first outcome and name the person responsible on each side. Schedule the review before the pilot drifts into an undefined free service. A customer who buys but never starts deserves investigation, not a celebration counted as completed validation.
Use the experiment plan template to record the pilot hypothesis and the go-to-market template for the acquisition path. After each delivery, update the practical procedure so the next customer benefits from what you learned. A credible first-ten process ends with evidence you can repeat, improve or reject.
Keep a learning and delivery log
Record fit, source, problem evidence, objections, agreed action, payment, activation, service time and later use. Separate friendly contacts from independently acquired customers when assessing repeatability. Heavy founder assistance may be useful for learning while still being expensive to sustain.
After each small batch, decide whether to continue, revise the offer or change the segment. Use the go-to-market plan to organize the next batch and the KPI guide to keep counts consistent. The first customer list is complete only when somebody owns delivery after the sale.