We collect evidence that clarifies the problem and user needs: current user journeys, friction points, and what success looks like for customers and administrators. Technical and operational evidence includes the existing portal or CMS estate, data models, integrations, performance baselines, accessibility status, security considerations, and governance and delivery constraints. We also map content inventory, multilingual requirements and deployment risks to shape the approach. When useful, we run quick prototypes or proofs of concept to validate ideas before moving into full build.
Public Q&A
What early evidence would you gather before starting Web Apps work?
Useful next steps
Use this answer as a practical starting point. Current scope, specifications, compatibility, availability, pricing, timing and next steps should be confirmed directly with Annex where they affect a decision.
Related visual examples
Web Applications & Customer PortalsA customer using a secure modern self-service portal across laptop and smartphone while a product te…
Visual exampleLaptop screen showing Australian Government Health Workforce Locator webpage
Visual exampleLaptop screen showing map search results for a specific address
Customer Portal Service ActionA user completing a practical task in a secure customer portal—such as updating details or managing …
