Let customers complete common tasks without emailing your team.
We build secure customer portals for requests, files, messages, payments, approvals and account details, with each customer seeing only the features and information they need.
Typical first version
6-12 weeks
Access
Private customer accounts
Features
Selected for your service
Timelines are indicative.
Choose the tasks customers should complete in their account.
Each portal includes only the features required for that service. You can start with one customer task instead of building every option at once.
Submit and track requests
Collect the right details at the start and show the current request status.
Upload and download documents
Keep agreed files with the relevant customer, request or service record.
Read updates and send messages
Give customers one place for service updates and selected conversations.
View invoices and make payments
Show selected invoices and use an established provider for online payments.
Approve quotes, work or documents
Ask the right customer user to confirm an agreed next step.
Manage bookings, orders or appointments
Show or change the service records included in the portal scope.
Update account and contact details
Let customers maintain the fields you allow them to change.
View service history and current status
Keep past activity and current work visible where the service requires it.
We agree the selected tasks, customer types, access rules and staff controls before confirming the portal scope.
Start with one useful task or connect a wider customer service.
Source access, payment requirements, customer roles, process complexity, historical data and selected features affect the final scope and timeline.
Focused self-service portal
For one repeated customer task that currently creates email or phone admin.
- Secure customer sign-in
- One main task, such as requests or documents
- Customer status view
- Staff controls for the selected task
Connected customer portal
For several customer tasks that need to work with existing staff software.
- Several selected customer tasks
- Connections to existing staff software
- Selected messages, documents, payments or approvals
- Different access for customer users and staff
Customer account platform
For several customer or account types and a broader set of connected records.
- Several account or customer types
- Selected requests, orders, payments, documents and service history
- Detailed staff controls and customer rollout
- Historical data import where feasible
Give customers a direct route to the task they need to complete.
These examples show different portal uses. A project can include one example or a selected combination, depending on the service.
Report a repair
A property customer reports a repair, uploads photos and tracks progress.
Approve the next stage
A professional-services client reviews a document and approves the next stage.
Pay an invoice
A service customer downloads invoices and pays an outstanding balance.
Maintain an account
A member updates contact details and views service history.
Check an order
A trade customer checks order status and downloads documents.
Change an appointment
A booking customer changes an appointment and sees confirmation.
Keep the request and its next steps in one account area.
Before
Requests split across calls and email
- Customers email requests to shared inboxes
- Staff ask for missing information
- Documents are spread across message threads
- Customers call for status updates
- Payments and approvals require separate follow-up
After
Selected tasks stay with the customer record
- A clear form requests the right information
- Requests, files, messages and status stay together
- Staff update one record instead of several email threads
- Customers can check progress without calling
- Selected approvals or payments happen in the same account area
Plan who can see each record and what they are allowed to do.
Private accounts need clear customer separation, staff controls and tested permissions. The exact controls depend on your users, data and risks.
Separate customer records
Account and permission rules are designed and tested so customers can access only their own agreed records.
Staff-controlled access
Staff can manage customer accounts, available features and access to the selected service records.
Customer user roles
One customer can have several users with different permissions where the service requires it.
Dated activity history
Important actions such as approvals, messages and status changes can keep a dated history.
Existing software connections
Connections are confirmed only after we check the software access, available data and connection limits.
Provider-handled payments
Where payments are selected, an established payment provider handles card details rather than the portal storing them directly.
Agreed file rules
Allowed file types, sizes, retention periods and sensitive-data requirements are agreed before build.
Requirements planned separately
Formal legal, security, certification or industry requirements need separate review, planning and scope.
Security choices are based on the agreed account structure and data. Formal compliance or certification is not included unless it is separately scoped.
Map the customer task, build the account and test it with real examples.
A typical first version takes 6-12 weeks. Stages can overlap, and selected features, account roles, source access and testing needs affect the overall timeline.
What we need from you
Bring the real request, rules and people who handle it
- A named process owner
- Real customer request examples
- The staff steps that follow each request
- Customer and account types
- Customer and staff access rules
- Current files, forms and messages
- Payment or software-connection requirements
- Representative data and available testers
Use a customer portal when customers need to complete tasks.
If the main need is viewing reports, staff operations or a public checkout, one of these services is a clearer starting point.
Practical answers before you plan a portal.
Show us the customer task your team handles repeatedly by email.
Send us one common request, the information customers provide, the staff steps that follow and the updates customers usually ask for.