The First Customer — Archive

Your first customer is not a revenue event. It’s a proof-of-concept for everything.

What the First Customer Proves

Someone has the problem badly enough to pay for a solution
You can communicate the value clearly enough to close
The product is real enough to deliver
You’re capable of doing this with strangers, not just friends

The first customer resets your relationship with the idea. Before them, it’s a theory. After them, it’s a business.

Who the First Customer Should Be

Not your most supportive friend. Not someone who pities your effort.

The right first customer is someone who has the problem, has tried to solve it another way, and is still frustrated. They’re paying not because they like you, but because your solution is the best option they’ve found.

This matters because they’ll tell you what’s wrong. Supportive early adopters tell you what’s good. The former is more valuable.

How to Find Them

Go where the problem lives, not where you’re comfortable.

If you’re building for developers → communities, GitHub discussions, Discord servers
If you’re building for small businesses → forums, Facebook groups, industry associations
If you’re building for creators → Twitter, YouTube comment sections, newsletter communities

Don’t pitch. Ask about the problem first. The pitch earns the right to happen after the problem is confirmed.

The Handoff

The first 10 customers are a founder’s responsibility, not a sales team’s. You need to hear the objections, the confusion, the delight, and the disappointment directly.

Delegate too early and you lose the signal that shapes the product.

See: [[product-market-fit]] for what you’re building toward with each customer conversation.