Status of work
Let clients follow the progress and milestones of their project or request.
APPS/003Client portals
Your client, informed.
Your team, connected.
We create private areas where customers can check progress, share documents and make requests, with account-based access and a clear connection to your team’s work.
A clearer relationship.
One place to keep it going.
Clients need to find their information and know what to do next. Your team needs requests with context and control over access.
Shared documentation
Organise deliverables and files with access based on the relevant account or case.
Requests and enquiries
Collect structured requests and pass them into the team's workflow.
Private services
Provide information or features that require an identified client and defined permissions.
From your client
to the way you support them.
The portal connects to the process behind it. We define what clients can see, what they can do and what your team receives next.
Starting point
- Clients
- Documents
- Applications
Private portalOutcome
- Consultation
- Exchange
- Management
A tool of your own.
A specific delivery.
These are the elements we define in the proposal. The final scope depends on your starting point and business priorities.
/001Roles and access
We define accounts, access recovery and permissions for each type of user.
/002Client journeys
We design screens for viewing information, uploading files or starting a request.
/003Development and connections
We build the agreed features and connect them to the planned data sources or systems.
/004Access separation tests
We check that each account can access only its authorised information and actions.
/005Handover and continuity
We hand over the access, documentation and guidance covered by the agreed scope. Follow-up or maintenance is defined separately if commissioned.
From your customer
to a shared workflow.
(4)Define what customers can do
We choose the customer enquiries and actions to support and the information needed to complete them.
Design access and screens
We prepare journeys, sign-in and permissions by account or user role.
Connect the internal workflow
We implement documents, requests and statuses, defining what your team receives after each action.
Test with different accounts
We review information separation, account recovery and mobile use before launching the portal.
Designed for your team.
Sustainable for your business.
Agreed scope
A custom application needs priorities and limits. We document features, user journeys and acceptance criteria before development.
Data and access
We define the profiles, actions and information each person needs, along with the planned backups, recovery and access management.
Operation and ongoing development
We define where the application runs, its recurring costs and who maintains it. Later versions are prioritised according to actual use.
Before we start.
(5)Will each client see only their data?
That is a core requirement. We design permissions and test information separation using the agreed user profiles before launch.
Can clients use it on a phone without downloading an app?
Yes. We can build a responsive web portal for mobile use. Device-specific or offline features are assessed explicitly if required.
Does everything have to be defined from the beginning?
We need a clear goal and scope for the first version. Further features can be prioritised after testing; changes are assessed before they are added.
Can we connect the tools we already use?
We review the integration interfaces, permissions and terms. If a connection is not feasible, we explain alternatives and their limitations before committing to development.
What happens after delivery?
We agree on hosting, support, maintenance and documentation. The proposal distinguishes operation of the delivered version from extensions and recurring services.
Engineering × Design.
For the next step.