Define the user and problem

Describe who experiences the problem, how they handle it today, and why a new product would be worth adopting. Avoid beginning with a long feature list before the core workflow is understood.

Scope the first useful release

Identify the smallest complete workflow that delivers value. Include the administration tools needed to operate the product, not only the customer-facing screens.

Decide the commercial model

Document account structure, plans, billing rules, trials if relevant, cancellation, support, and who owns customer operations. These decisions affect the product architecture.

Prepare for learning

Choose measurable signals such as activation, repeated use, completion time, and support demand. The first release should make it possible to learn what customers genuinely need next.