One number everyone can actually trust.

The client success team opened three tabs before checking the account record.

Every morning, the client success team pulled a revenue export, a manually updated alerts sheet, and personal call notes before checking the system of record. By the 9:30 standup, everyone named their top 3 accounts at risk, but risk meant something different to each team member: overdue payment, no login, declining revenue.

Reconciling whose numbers were current burned 10 to 15 minutes before the team could even talk about what to do.

The data existed. It just wasn't built to be looked at together.

A five second overview that still leads to the full account story.

The Dashboard gives executives a concise view of revenue movement, risk, and growth. The client success team can scan the same signals, then open Client Profile when they need history, activity, and account detail. One dataset supports two depths of use.

Every account tells its own story once you click in.

Dashboard answers “who needs attention.” Client Profile answers “why.” Overview and Summary bring an account's history, standing, and recent activity onto one page, so a client success team member walks into a call already knowing the story instead of piecing it together live.

Executives and the client success team needed to see the same data in completely different ways.

The first version tried to answer both audiences on one screen. In a standup meeting, I watched a VP of Sales scroll past the alert list and go straight to a single revenue number. They didn't want the workspace, they wanted the answer. Ten minutes later, a client success team member opened the same screen and started scrolling for the account they'd flagged the day before. Same page, two completely different jobs.

I split it into a summary layer, the Dashboard, and a detail layer, Client Profile. Same data, two levels of detail, on purpose.

The alert list started as “flag everything.” The client success team stopped reading it within a week.

The first version gave every change equal weight. A missed payment and a routine login got flagged the same way, same color, same size, sorted only by time. In week one, a senior CS rep told me she'd started ignoring the list entirely and going back to her own notes, because she couldn't tell what actually needed her attention that day.

I gave every event type its own color and label, and added a filter so the team could isolate what mattered that day instead of scrolling through everything. A Client Lost and a first order are now visually distinct before you even read the row.

The revenue ranking answered a question nobody had actually agreed on.

'Rank clients by revenue' sounds simple until you ask: this month, this quarter, or growth rate? I first heard it collide in a standup. Two team members named different accounts as 'our top client' in the same breath, each looking at a different number. Sales and Revenue Ops had been running on separate definitions without anyone flagging it.

I gave the ranking a visible time range toggle instead of a silent default, so it was always clear which number people were looking at.

Watching the client success team build its own workarounds instead of asking members to describe them.

Instead of asking team members to explain their process, I watched them do it: which spreadsheet they opened first, what they copied into a second tab, and what they trusted more than the export.

I also sat in on two weeks of standups, timing how much of that fifteen minutes went to arguing about numbers instead of talking about accounts. The workaround was the real spec.

Goals

1. Find out which numbers client success team members actually acted on, and which they ignored.
2. Understand what “an account needs attention” meant day to day, not just in theory.
3. Measure how much standup time was lost to reconciling data versus real discussion.

What changed once it shipped.

Standup's data reconciliation time dropped from 10 to 15 minutes to under 3. The client success team opened the Dashboard together instead of comparing spreadsheets out loud.