Design Research · 03 / 08

The Client Dashboard

Cutaway of a busy studio workroom wall with one calm, framed viewing window showing a tidy curated subset of the room's contents

What belongs in the client-facing view — and what to leave out. The single most repeated finding across sources: clients want less, not more. Agency dashboards routinely surface 40+ data points; clients look at about 4, and the other 36 read as noise that signals the agency doesn't know what matters.

The Core Job: One-Glance Status

Clients want a single answer to "is this on track?", the ability to drill in without booking a call, and confidence that what they see matches reality. Agencies that ship this report 25–40% fewer ad-hoc client emails within 60 days — strongest when the portal exposes real-time status, approval queues, and invoice history. That's the business case for the Phase 3 client view in one number.

The Access Model to Copy: Basecamp's Clientside

Basecamp is the gold standard for client sees only what's shared:

Everything is private by default; you explicitly promote an item to client-visible
The UI teaches the affordance: blue-with-a-lock = internal, yellow-with-an-eye = client-visible — the studio always knows what the client can see; no accidental leak of internal chaos
Clients never log into "your" account; older Clientside even worked over email with a link + PIN

This validates the "no login friction" preference. (Our Phase 3 decision is invited accounts with share links later — the publish-explicitly model still applies within that.)

The Five Recurring Blocks

Consistent across Noloco, AgencyHandy, Teamcamp, and Copilot-class portals:

Project status / milestones — visual progress that updates automatically; status legible within seconds of opening. This is where the ClickUp sync lands — mapped to a client-legible status vocabulary, not raw internal statuses
Deliverables & files — most-needed at top
Approvals & feedback — comment on a deliverable, approve, request changes, revision history in one place
Invoices / billing — (excluded from our scope for now — financial fields were deliberately left out of the migration)
Next steps / "what we need from you" — an explicit action block for the client. The highest-trust element and the one most agencies forget

Read-Only Design That Needs No Explanation

Plain language over jargon; translate internal states into a client vocabulary: "In review with you," "We're building," "Blocked — waiting on you"
Most-needed items at top; progressive disclosure for detail; mobile-first (clients open these on phones — matches our Phase 3 mobile criterion)
Our current decision set (task names + full Action Process statuses + due dates + list groupings + assignees, no descriptions) should be pressure-tested against this: Action Process statuses are only right if they're client-legible without translation

The Genre Master Class: SaaS Status Pages

Status pages are the best examples of calm status communication in the wild:

Instant overall health in a single view, then color-coded component rows grouped into clusters (GitHub separates Git Ops / API / Actions / Pages — a stalled user gets a precise answer in ~2 seconds)
Cloudflare's 90-day history bar (thin daily segments, green/yellow/red) became the industry standard because it shows whether something is generally reliable, not just up right now — a lovely model for showing engagement health over time
The cultural lesson: users value clarity, honesty, and rhythm over design flair — and silence during trouble does more damage than the trouble itself. A calm client view surfaces problems plainly, with a clear next step, rather than hiding them

Products to Study

Copilot and SuperOkay (design-forward branded portals) · Moxie/Bonsai/Dubsado (freelancer end) · Notion portals (the lightweight calm pattern) · Noloco (no-code branded portal over existing tools — architecturally closest to us).

Net Translation for Collaboration OS

The client view = a Basecamp-style published subset of the internal client entity, rendered in the one-glance, color-coded idiom of a great status page, themed to the client's own brand (see Representing Clients Visually) — with a prominent "what we need from you" block as the single interactive element.