Accounts & access
Sign-in, account recovery and permissions for customers, members and staff.
Client & member portals
Give your customers a place to get things done.
A customer needs a document. A member needs access. Your team needs the details in one place. Bring those journeys together in a web portal built around your business.
A rough idea is enough. We’ll follow up by email.
When email threads stop being enough.
A portal can make sense when customers or members regularly need to interact with your business after the first enquiry.
- Customers need to send documents, follow a request or find information you have already shared.
- Members need access to programmes, resources or their account details.
- Your team keeps answering the same status questions or looking for information across inboxes.
Example workflow · tailored to your business
One request. A clear path from start to finish.
This is an illustration of what a client portal could do. Your first release is shaped around the actual steps your customers and team need.
Customer signs in
They reach their own account and the information they are allowed to see.
Request is submitted
A short form collects the details and documents your team needs.
Your team responds
Staff review the request and update its status in the same place.
Customer sees the next step
They can check progress and provide anything still missing.
Build the parts your customers will actually use.
Choose the modules that serve the first journey. A portal does not need every feature on day one.
Requests & documents
Forms, uploads and a shared record of what has been submitted.
Member resources
Programmes, content or services available to the right members.
Team workspace
A practical view for managing people, reviewing requests and updating information.
Start with one complete customer journey.
The first release should let someone finish a useful task. Work with us to agree what it includes, how you will review it and what can come later.
Define the people and the task
Who signs in, what they need to do and what your team does afterward.
Review a working version
Try the customer and staff journeys as the portal takes shape, then refine the details together.
Prepare for real use
Test access and important flows, prepare the agreed launch and hand over the information needed to run it.
Before you start.
Do customers need to install an app?
A web portal can be used in a browser on a phone or computer. If a feature depends on a device capability or an app-store release, that requirement is evaluated separately.
Can it connect to our existing systems?
Often, yes. The first step is to check the systems, their integration options and available access. Any third-party subscriptions or limitations are identified when the scope is prepared.
How do customer and staff permissions work?
The access rules are part of the design: who can see, edit or share which information. Sign-in, account recovery and the agreed permissions are included in the flows reviewed before launch. Tell us early if the portal handles sensitive information or has specific compliance requirements.
Do we need a detailed specification to start?
No. Describe one task your customers or members need to complete, and what happens today. Example forms, documents or screenshots can help establish the scope.
What determines the cost and what happens after launch?
The number of user roles, workflows, integrations and any data migration shape the build. Hosting, account access, handover and any ongoing support are agreed as part of the proposal, so you can assess both the project and its running costs.
What should your customers be able to do?
Tell us who the portal is for, one task it should handle and how you manage that task today. We can work through the first version from there.
Discuss your portal
Share a few details. No technical brief required.