What a client dashboard should have: 7 keys

A client who pays you every month doesn't see your effort: they see a dashboard, an email or a report. If the work doesn't show up there, for them it doesn't exist, and at renewal time the last problem weighs more than the whole year. Building XY Task, our multi-company operations platform, I learned that a client dashboard is won or lost on seven things. None of them is the color.

1. It answers "is everything OK?" in five seconds

Opening the dashboard has to answer that question before the person reads anything. If everything is fine, they move on. If not, the dashboard shows where the problem is, and one more click shows why. You get there with a grid of cards (not a long row of identical numbers), the most important metric at the top left and navigation with five groups at most.

2. Every number says when it's from and what it's compared to

"143 tickets" tells you nothing. "143 tickets in the last 30 days, 12% fewer than the previous 30" does. Three rules almost nobody follows:

• The previous period has the same number of days: September is compared with the previous 30 days, not with August, which has 31.
• Days are cut in your business's time zone. If the server cuts in UTC, September's report counts tickets from October 1.
• Whatever is "current state" (open, overdue) is calculated as of today, and the card says so.

3. Every number opens

A total you can't open breeds distrust. If the bar says "11 tickets have waited 8 to 14 days", one click has to show which ones, who is handling them and how long they've been waiting. It's the card that drives the most action: old work becomes visible, and what's visible gets done.

4. The report produces itself

If getting the monthly report takes an afternoon of copy and paste, nobody does it, or it's done badly. The dashboard has to print as a PDF with a report header (company, period, date and logo), always in light mode, and export to Excel with the same filters as the screen. That PDF is what your client forwards to their boss: it sells for you in meetings you don't attend.

5. The client sees their company and nothing else

You don't solve this by hiding buttons. The server decides who sees what, denied by default, and every route applies the same rule. The forgotten ones are the dangerous ones: the export, the search box, the menu counter, the Telegram alert and attachments. A client who changes the company number in the URL must get a 403, not someone else's data.

6. Internal data doesn't travel, not even hidden

The team's internal note, the cost, the hour estimate or who logged each hour can't reach the client's browser "even if they aren't shown": anyone can see them in the network tab. The response is built from a whitelist of fields per role, on the server. And your team needs a client view: a switch that shows the dashboard exactly as the client sees it, to check it before sending a PDF.

7. It's tested before and after publishing

A small change can open another company's data without anyone noticing. That's why there are automated tests that try what a curious client would (see another company, request the team view) and, after every deploy, a check in production: without a session, everything answers 401.

And the landing page that sells it

The same care applies to the page that sells your product: the real product in screenshots and video (never stock photos), each feature explained with a diagram you get in three seconds, one URL per language so Google finds your Spanish version, and a first screen that doesn't wait for JavaScript. You can see all of that working at xytask.com.

The free skill to build it with Claude Code

I put all of this into a skill for Claude Code: How to build a dashboard and its landing page with Claude Code. It includes the design, reporting, multi-company security and landing page guides; the code that decides who sees what, with its tests; and a demo dashboard you open with a double click to try the date range, the click-through detail, the client view and the PDF before you build yours.

Download it instantly by leaving your email, unzip it into ~/.claude/skills/ and tell Claude Code: "Use the dashboard-y-landing skill". It asks you the questions and builds with you, step by step.

If you'd rather have us build it for your company, book a conversation.