Control the maintenance burden
Frameworks, libraries, devices, and operating systems change. Document dependencies and update responsibilities so ongoing compatibility is part of the plan rather than an unexpected expense. Identify the most useful correction before adding another feature.
Test both platforms where supported, including navigation, permissions, notifications, and accessible controls. A working build on one device is not enough. Confirm that forms, phone links, and replies reach the right person.
Data and permissions
Collect only data needed for the task, document access roles, and plan deletion and recovery. Security should be considered while designing the workflow. Use only the customer information needed for the agreed work.
Document APIs, authentication, failure handling, and data ownership. Test slow responses and unavailable external systems, not just the successful path. Separate essential work from optional additions in the proposal.
- Current accounts and assets
- Verified business information
- Customer questions
- Budget and team capacity
Discuss Your Priorities