Get Your First 10 Paying Customers

Proof required

Submit: payment evidence for your first paying customer — a Stripe transaction screenshot, PayPal receipt, or invoice with a payment confirmation. Include a one-paragraph note describing who the customer is (role and context, no full name required), how you reached them, and what specifically they said they were paying for.

What gets checked

• Payment evidence shows a real transaction — a Stripe link to a payment intent, a PayPal receipt showing sender and amount, or a bank confirmation; a screenshot of a 'payment pending' or 'invoice created' state does not pass; the money must have actually moved
• Customer is described with enough context to confirm they match the target profile — 'my friend' or 'a person' does not pass; 'a freelance graphic designer who runs a one-person studio and was spending 4 hours per week on invoicing' does; the context confirms this is a real target customer
• The note explains how the customer was reached — cold outreach, referral, inbound from the landing page, direct message — without this, there is no acquisition channel to replicate for customers 2–10

Common mistakes

• Counting family members or close friends as first customers — a payment from someone with a strong personal relationship to support the founder is a favour, not a customer acquisition; it does not teach anything about real demand; the test is: would this person have found and paid for this product if they had never met you?
• Offering the product for free to 'build the user base' before charging — free users are not customers; this milestone specifically requires payment because the conversion from free to paid is where most early-stage products fail; start charging from the first conversation
• Not asking directly — many founders wait for customers to volunteer to pay; the first customer almost always requires a direct ask: 'I'd like to bring you on as a paying customer at $X per month — can we do that today?' Indirect signals of interest without a direct ask do not convert

Resources

What a verifier looks for

• Open the payment evidence — verify a real transaction occurred: Stripe shows a charge ID, PayPal shows a confirmed transaction, bank shows a cleared transfer; 'invoice sent' or 'payment link created' without a corresponding confirmation does not pass
• Check the customer description — ask 'how did this person find out about the product?' and 'what problem were they paying to solve?'; if the answers are vague or the customer turns out to be a family member, note the signal weakness
• Ask about the acquisition path — the specific channel that produced the first customer is the most important learning from milestone 1; 'they just reached out' is not an answer; 'I sent 30 cold LinkedIn messages and this was the 7th reply' is the kind of specificity that confirms a real acquisition effort

You'll sign in first, then come straight back here.

Proof required

Submit: (1) payment evidence for customers 2–5 (Stripe export, PayPal receipts, or invoices), and (2) a one-page acquisition log showing how each of the 5 customers heard about you and what they said when agreeing to pay. Include a 50-word note identifying which channel produced the most customers and why you think it is working.

What gets checked

• Payment evidence covers 5 distinct customers — not 5 payments from the same customer, not 5 payments from the same company; 5 separate individuals or organisations each with their own payment record
• Acquisition log names a specific source for each customer — 'word of mouth' is too vague; 'referred by customer 1 on Slack' or 'responded to cold email via LinkedIn on day 12' is specific; the log must support the acquisition channel analysis
• Channel analysis names the top-producing channel with a specific reason — 'LinkedIn worked because our target customers are active there and I had a warm intro from a mutual connection' is an analysis; 'various channels' is not

Common mistakes

• Not tracking how customers heard about you — the acquisition log is not an optional extra; without it, the founder cannot identify what is working and cannot build toward 10 customers deliberately; start the log at customer 1 and update it at each conversion
• Treating all 5 customers as equally informative — the customers who came in easily and the customers who took 20 follow-ups are different data points; note in the log which customers were easy to close and which were hard; the pattern in that difference points toward ideal customer profile refinement
• Discounting the customers who said no — for every paying customer, there were probably several who declined; the reasons for declining are as important as the reasons for converting; keep a 'nos log' alongside the acquisition log

Resources

What a verifier looks for

• Verify 5 distinct customers with payment evidence — open the Stripe export or invoices and count unique names or organisations; if there are 5 payments but only 3 distinct customers, the milestone has not been met
• Open the acquisition log and check that sources are specific — 'referral' without naming who referred is not specific enough; ask 'who referred customer 3?' and expect a name; the specificity confirms real tracking was happening
• Ask about the channel analysis — 'which acquisition channel produced the most customers and what are you going to do to get more from it?' A founder who cannot answer this question with specifics has not yet extracted the core learning from milestone 2

You'll sign in first, then come straight back here.

Proof required

Submit: (1) payment evidence for all 10 customers (Stripe export with 10+ rows, or a list of invoice confirmations), (2) the updated acquisition log showing how each customer found you, and (3) a 200+ word post-mortem covering the repeatable acquisition path, the ideal customer profile that emerged from the data, and the one thing customers consistently pay for.

What gets checked

• 10 distinct paying customers with payment evidence — the Stripe export must show 10 different customer names or email addresses, or 10 distinct invoices must be listed; the count must reach 10 regardless of churn — customers who later cancelled still count if they paid at least once
• Post-mortem addresses all three questions with specific evidence — each answer must be grounded in specific data from the acquisition log; 'our ideal customer is a busy professional' does not pass; 'our 4 fastest-closing customers were all heads of operations at companies with 10–50 employees who had already tried a spreadsheet approach and found it unmanageable' does
• Post-mortem acknowledges what did not work — an honest 10-customer post-mortem names at least one channel or message that was tested and did not produce results; a post-mortem that reports only successes is incomplete

Common mistakes

• Treating customer 10 as the endpoint rather than the start — 10 customers is a proof of concept, not a business; the value of this outcome is the learning and the acquisition pattern, not the number; if the post-mortem does not include forward-looking implications ('based on what we learned, the next 10 customers will come from X'), the founder has not yet extracted full value from the exercise
• Not distinguishing between customers who churned and those who stayed — all 10 count for the milestone, but the post-mortem must flag any customers who cancelled and why; early churn is a product signal that is more important than the customer count itself
• Outsourcing the first 10 sales to a team member or agency — the first 10 customers must be acquired by the founder personally or in the founding team; this outcome builds the knowledge of what works, and that knowledge cannot be acquired by watching someone else sell

Resources

What a verifier looks for

• Open the payment evidence and count 10 distinct customers — if using a Stripe export, check that there are 10 different email addresses or customer IDs; if any row is a duplicate (same customer, second charge), it does not add to the count
• The post-mortem must be grounded in the acquisition log data — ask 'how did you identify the ideal customer profile?' and expect an answer that references specific patterns from the log; if the profile was determined by intuition rather than data, it is not yet a validated ICP
• Ask one forward-looking question: 'based on what you learned from customers 1–10, how will you acquire customers 11–20?' A specific, channel-grounded answer demonstrates that the milestone generated usable insight; 'I'll keep doing what worked' without naming what specifically worked is not sufficient

You'll sign in first, then come straight back here.