What must work before customers depend on it?

The customer task

• A new customer can understand how to begin.
• The agreed task finishes with the correct saved result.
• Invalid, empty and pending states explain what to do next.
• The representative task works with a keyboard and on relevant mobile screens.

Accounts and records

• Each role can perform its permitted actions.
• Restricted users cannot read or change another customer's records or files.
• Invitations, recovery and account changes follow agreed rules.
• Important staff corrections can be traced.

Connected services

• Successful, rejected and delayed responses are checked using controlled services.
• Repeated notifications do not create an unintended second business action.
• If billing controls access, cancellation and failed-payment rules are tested.
• Tests do not send real customer messages or create live charges without specific approval.

Release and support

• The tested release and deployment instructions are recorded.
• Data changes have an agreed recovery plan and limits.
• Someone owns error review, account support and the initial customer questions.
• The first audience and the learning question are clear.

Keep the results and outstanding gaps with the release record. Review the development sequence or discuss the launch scope.