A slow portal does not, by itself, show whether replacement is needed. Annex’s ActewAGL example involved an existing self-service portal running on outdated Sitecore and JavaScript, alongside work to develop an accessible web app for customer account tasks. Annex’s published approach suggests first understanding what works, what is causing difficulty, and how the current technology and its dependencies affect the service. Whether improvement or replacement makes sense depends on the condition of the portal and the needs of its users.
Public Q&A
If our portal is slow, how would we know whether to improve it or replace it?
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 …
