Describe the operational problem
Start with the workflow that is slow, fragmented or error-prone. Show how it happens today and which people are involved rather than prescribing every screen before discovery.
Map users and permissions
Name the user roles and what each must see, change or approve. A useful first version often depends more on clear permissions and records than visual complexity.
List integrations and data sources
Identify existing systems, APIs, spreadsheets and data owners. Confirm whether integration access and documentation are available before promising automated data flow.
Define a first release
Separate essential tasks from later improvements. Choose a small end-to-end workflow that can be tested by real users, then use feedback to shape subsequent releases.
Agree ownership and operations
Clarify hosting, code ownership, support responsibilities, backups, security review and how the system will be maintained after launch.