Product brief and first-release scope
Identify the customer, their current alternative and the useful task the first version will deliver. Separate launch requirements from ideas for later review.
What a first build can include
Enough product to complete the task and support the customer.
Choose features around a particular customer outcome. Define the operating work alongside the visible screens.
Accounts and permissions
Plan sign-up or invitations, sign-in, account recovery and permitted roles. For business accounts, decide how colleagues join and who manages their access.
Customer task and onboarding
Build a clear path from the first visit to the useful result. Include guidance, validation and the empty or pending states a new customer will encounter.
Billing-provider connections
If the first release charges subscriptions, define plans, access rules, cancellation and failed-payment behavior. Test using controlled provider tools rather than real customer charges.
Staff administration
Provide the agreed tools for account support, record correction and reviewing failures. Decide which actions need a recorded explanation and who may perform them.
Launch and feedback
Release to an agreed group, check the complete task and review relevant usage and feedback. Keep the operating cost, support arrangements and next decisions visible.
Considering an AI feature?
Describe the exact task it helps with and how a person will review an incorrect result. Include the permitted input data, usage cost and a fallback when the feature is unavailable. AI needs a useful role in the product, rather than a separate promise of value.
Discuss the first customer task