Work / Client portal
Client portal
A client portal that replaced an inbox full of resent attachments.
Secure sign-in, document management, booking, invoicing and a full learning platform, built end to end for a UK consultancy.
- Sector
- Professional services
- Type
- Web application, client facing
- Built with
- React, Node.js, PostgreSQL
- Covers
- Auth, documents, booking, invoicing, learning
- Status
- Delivered
The problem
Consultancies accumulate a particular kind of overhead: clients asking for documents that were already sent, chasing invoices, and booking sessions over email. None of it is difficult, all of it is constant, and it lands on whoever is least able to ignore it.
What was built
Secure client access
Each client signs in and sees their own material. Permissions are enforced server-side, so what a client can reach is decided by their account rather than by which link they happen to have.
Document management
Documents in one place, versioned, available whenever the client wants them. This alone removes a surprising share of inbound email.
Booking and invoicing
Sessions booked against real availability, and invoices raised and tracked in the same place, so the commercial record and the delivery record do not drift apart.
Learning platform
Course material, progress tracking and completion records, which turns training from a delivered service into an asset the consultancy can resell.
Why a portal instead of better email discipline
Email discipline is a process fix that degrades the moment people get busy. A portal changes the default: the client's first instinct becomes checking their account rather than asking. That shift is where the time actually comes back.
Get started
Need something along these lines?
Describe your version of the problem and I will tell you what building it would involve.