Designing a client portal that doesn't feel like Jira
Why we split internal detail from client-facing status, and what clients actually want to see.
When we started giving clients direct access to project tracking, our first instinct was to just share the board. It was a mistake, and a useful one.
Clients don't want tickets
A backlog full of tags, story points, and internal shorthand is noise to the person paying for the work. They want three things:
What's the current status, in one sentence?
What's shipping next, and when?
Is anything waiting on me?
Two views, one source of truth
So we split the interface. Our team keeps the full board, every ticket, tag, and internal note. Clients get a calm, plain-language view generated from the same data. Nobody maintains two systems, and nobody has to learn Jira to know how their project is going.
The best client portal is the one your client never has to be trained to use.
Tell us the goal, the constraints, and who signs off. We scope it against real delivery capacity and ship the first build in weeks.