Web application · Anonymized example
A client portal that takes the work out of the inbox.
A services firm was running client delivery through long email threads. Files went missing, and status lived in people’s heads. The engagement built a web application where each client sees only their work.
Situation
New staff could not reconstruct a client history. Clients asked for updates that had already been sent, buried under later replies.
Approach
I defined two roles, client and staff, and the few screens each role needs. The first release covered status, files, and a single request flow. Extra features waited until that core was in use.
What shipped
A web application with accounts, permissions, a request flow, and a short guide for staff who invite a client.
Outcome
Client history sits in one place. Staff stop searching old threads to answer a status question, and clients see only their own work.