The founder has automated development, design, documentation, and the company’s first seventeen social posts. There is now only one manual dependency: somebody who wants the product.
A public discussion on r/ycombinator asked how a solo technical founder could find the first ten to a hundred customers and gather useful feedback. The replies offered different versions of familiar advice about direct contact and learning from users. This is a conversation, not a survey, and its individual acquisition claims are not verified benchmarks.1
The application is easier to contact
Software development offers a relatively cooperative kind of resistance. A test fails. A page breaks. A tool returns an error. The founder can keep working until the visible problem changes.
A prospective customer is less obliging. They may not reply. They may describe the problem inaccurately. They may like the demonstration and never return. They may genuinely want the product while lacking the authority to buy it.
AI tools can intensify the refuge. They make it possible to produce a more elaborate answer before establishing whether anyone asked the question.
The old advice survived the model release
Paul Graham’s 2013 essay argues for manually recruiting and attending to early users rather than expecting a startup to grow by itself.2 The advice is old enough to have survived several declarations that distribution has fundamentally changed.
There is a difference between generating a thousand plausible outreach messages and learning something from five difficult conversations. The former increases activity. The latter can change the product. Either may have a place, but they should not be counted as the same kind of progress.
A polite rejection can be more informative than an enthusiastic social reply. Someone saying the product looks great may simply be a kind person with no intention of changing their day.
The customer is several questions
A hypothetical founder building an administrative tool might begin with a broad claim: small businesses hate paperwork. This is probably insufficiently specific to guide a company.
Which paperwork? Who performs it? How often? What happens when it is late? Who pays for the mistake? What is the current workaround? Is the person feeling the pain also the person who can authorize a new system?
This is one reason customer discovery can feel threatening. It has the power to reduce a founder’s freedom. The beautiful general solution becomes a specific tool with irritating constraints. The pitch becomes less expansive just as the business becomes more intelligible.
Automation is useful after the choice
What it cannot establish by itself is that a person’s problem matters enough for them to change behavior. That evidence comes from the person and what they do, not from how convincingly a model describes the hypothetical customer.
The founder needs an answer the founder cannot approve into existence. A simulated customer can rehearse the conversation; an actual buyer can decline to have it.
A very small market can be a good beginning
The first customers do not have to prove the entire investment thesis. They need to provide evidence of a useful relationship: a recurring problem, a workable solution, and a reason to continue.
That evidence may arrive slowly and unevenly. It may require support that would be impossible at scale. Early learning is allowed to be unscalable, provided the founder understands what is being learned.
A customer returning to use the product changes the argument. So does one refusing to pay. Both are less comfortable, and more useful, than another compliment from the founder’s own tools.
The first customer has inconveniently retained the right to be busy.