Good fit when
- Teams agree that a portal is needed but not what users should do in it
- Stakeholders need to review journeys before approving development
- An existing portal is being replaced and requirements are fragmented

Define the users, information architecture and testable interaction model for a customer-facing portal.
We turn a portal idea into a testable product definition before development. The work identifies users and permissions, organises content and transactions, prototypes the principal journeys and produces a build plan with clear decisions still to be made.
Interview users and owners
Prioritise portal tasks
Structure content and navigation
Test the interactive prototype
Prepare the implementation plan
Before work begins, the written proposal confirms the selected service, timetable, client inputs, taxes, third-party charges, travel and any requested work outside the published package.