What belongs in a first version

Most ideas arrive as the whole product. There are accounts and roles, a dashboard, reports, a mobile app, an admin panel and perhaps a marketplace. Some of that will matter eventually, but very little of it helps you decide what to build in the next few weeks.

The question I start with is narrower: who is the first person who will use this, and what do they need to get done on the first day the product exists?

A useful answer fits in one sentence. "A founder can collect a waitlist and email the people on it" is a good example. Once a sentence like that exists, the scope has clear edges. Every screen and feature either helps that person do that job, or it goes on a list for later.

The later list is not a list of rejected ideas. Once people have used the first version, you will know which items on it matter, and it is usually shorter than you expected. Real usage settles those questions faster and more reliably than planning meetings do.

I have seen this hold in large companies, where I worked on products used by hundreds of thousands of people, and in small tools I built for my own home. The products that lasted were the ones that did one job well from the start and added the rest once there was evidence for it.

If you are working on an idea, try writing down the first user and the one job before anything else. That is enough to start a conversation about scope, and a first version built around it can usually be ready within a few weeks.