Work Customer portal for service clients
Case study
Customer portal for service clients
A secure login area where clients check status, submit requests, and download files — so the team stops answering the same update emails every week.
- Client
- Service business
- Industry
- B2B services
- Timeline
- 7 weeks to v1
- Year
- 2025
- Role
- Build partner — discovery, UX, portal, rollout
- Laravel
- Auth & roles
- File storage
- Email notifications
1
Client self-serve home
3
Core portal jobs
7 wks
Brief to live portal
Less
Status chase email
Overview
Clients kept asking for the same updates. Staff spent hours digging through email and folders. GujjuTicks scoped a focused portal around three jobs — see status, submit a request, download files — then shipped a secure login area the team could administer without building a full product platform.
The challenge
The business looked professional on sales calls, but day-to-day client communication lived in inboxes. Status was hard to find, files went missing, and every “quick update” interrupted real work.
- Clients emailed repeatedly for status they could have self-served
- Files and deliverables lived across shared drives and threads
- No single place for clients to submit structured requests
- Staff lacked a simple admin view of who needed attention
Our approach
We mapped the repeating client jobs — not a wish-list portal — then cut v1 to auth, status, requests, and downloads with a light staff admin.
- Interviewed staff on the emails they answered most
- Locked three client jobs for v1; parked billing and chat for later
- Designed roles so clients and staff see the right surfaces
- Shipped weekly demos with a pilot client group before wide rollout
What we built
A practical customer portal the business could run daily — not a bloated client “community.”
Secure client login
Account access with clear separation between clients and staff.
Status at a glance
Clients see where work stands without waiting for an email reply.
Request intake
Structured submissions replace vague “quick question” threads.
File downloads
Deliverables in one place with staff control over what is shared.
Delivery timeline
A clear path from discovery to launch.
-
Week 1
Discover
Map client jobs, staff pain, and a hard cut for v1.
-
Week 2
Design
Key screens, roles, and notification rules.
-
Weeks 3–6
Build
Auth, status, requests, files, and admin.
-
Week 7
Rollout
Pilot clients, train staff, then widen access.
The outcome
Clients get answers without waiting. Staff spend less time on status theatre. The portal is ready for billing or messaging later — without rewriting v1.
- Fewer repetitive status emails
- Clearer ownership of client requests inside the team
- Files and updates in one trusted place
- A backlog ordered by real portal usage
“Clients stopped asking “any update?” every Monday. The portal became the source of truth.”
More work
Build a client portal
Want a secure place where clients self-serve status and files?