Back to blog
Indie Development / Method / Validation

What I validate before building an indie product

The expensive part of an indie product is not the first codebase. It is staying on a direction that never had enough demand. Validation keeps speed pointed at a better target.

01

Validate that the problem is real

I look for the workflow where the problem appears, who repeats it, and what they use today. If the demand only exists in my imagination, it is not yet a product signal.

02

Validate the entry point

An indie product needs a natural path to discovery. That path can be search, community discussion, tool directories, short content or a fixed pain in a workflow.

03

Shrink the first release boundary

The first version should help a user complete one real task. Fewer features are not automatically better. Every feature has to serve the validation.

Actionable takeaways

  • Demand must come from a real workflow
  • Entry points shape cold-start efficiency
  • The first version validates one core action

Read next in this column