What belongs in your first release?

Start by naming one user, one problem and one outcome. Map the few steps needed to reach that outcome, including the uncomfortable parts such as errors and recovery.

Separate launch requirements from ideas that can wait. A first release should be small enough to learn from and complete enough to be useful.

Write down the questions you expect real usage to answer. Those questions will guide your next iteration better than a long list of features.