Keep permissions proportionate
Ask only for access needed by a defined feature. Explain the reason at the appropriate time and provide a useful path when a user declines an optional permission. Use only the customer information needed for the agreed work.
Define what happens offline, during slow requests, and after reconnection. Prevent repeated submissions from creating duplicate records. Leave the team with a decision, an owner, and a review date.
Integration boundaries
Document APIs, authentication, failure handling, and data ownership. Test slow responses and unavailable external systems, not just the successful path. Agree which tasks are included and which need a separate quote.
Test representative devices, permissions, interrupted connections, and failed inputs. Define acceptance checks with the people who will use the product. Check that a visitor can find the next action without guessing.
- Current accounts and assets
- Verified business information
- Customer questions
- Budget and team capacity
Discuss Your Priorities