How to scope a web platform or SaaS
A useful first release solves a small number of important workflows well. Scope those workflows before debating every feature.
Map users and their tasks
Name each user role and the actions they need to complete. Sketch the critical journey from sign-up to the result the user came for, including admin and support tasks.
Choose the first release
Rank features by value and risk. Keep the first release focused on what must be tested with real users, and move non-essential reporting and integrations to later phases.
Plan data and security
List the data you collect, access permissions, external services and any migration needs. Discuss hosting, backups, monitoring and privacy requirements before development starts.
Agree delivery and ownership
Ask for a clickable prototype, milestones, demos, acceptance criteria, documentation and a clear handover of code and intellectual property. Confirm what support is included after launch.