KPI dashboard: the numbers, and what they mean this month

A few numbers with their changes and the reasons behind them, sent to the same readers on a schedule.

2 live examples

The example: Bareroot's November numbers for the team and investors

Five numbers, one chart, four reasons

Bareroot's November numbers for the team and investors

Open the exampleThe names and numbers are made up.

What to notice

  • The line under the title is the month in two sentences: revenue up 5.3% to $88,680, and eleven customers gone, five of them nurseries closing for winter.
  • The written part ties two tiles to one cause. The import shipped on 4 November lifted activation to 58%, and 46 of the 318 support tickets were about it.
  • The header says the figures run to 30 November and were typed into the page on 8 December, so nobody takes it for a live feed.

The prompt that starts one like it

Make a monthly KPI dashboard as a single HTML page that works on a phone, for [company]'s team and investors. Use these figures for the last twelve months: [paste revenue, new and lost customers, activation, support tickets]. Give each number a tile with its change on last month and a small trend line, add one main revenue chart, and write 'what changed and why' from my notes: [paste]. Say the figures are typed in, not live. Then publish it on sharable.link so only [these email addresses] can open it.

The example: Pennant Packaging's Monday sales numbers

Target bar, pipeline, five reps, five deals

Pennant Packaging's Monday sales numbers

Open the exampleThe names and numbers are made up.

What to notice

  • A black tick on the target bar marks today's pace, $126,316, so the $131,500 won reads as a little ahead, which 55% alone wouldn't tell you.
  • The paragraph under the bar does the sum for the team: $108,500 to go, $52,600 of it in verbal yeses, so just under half of the $118,400 in quotes has to sign.
  • Each of the five deals that need a push has a "What's wrong" and a "This week", and every "This week" has a name and a day in it.

The prompt that starts one like it

Turn this morning's CRM export into a Monday sales dashboard as a single HTML page: [paste deals with stage, value, owner and last activity]. This month's target is [amount]. Show won so far against target with a marker for today's pace, open pipeline by stage, each rep against their own target, and the five deals most at risk, each with what's wrong and who does what this week. It must read well on a phone. Then publish it on sharable.link so only [our company's domain] can open it.

Most dashboards tell you what the number is and leave you to guess why it moved. The two on this page put the reason next to the chart, in sentences. Both are snapshots: the figures are typed into the page, and each one says so near the top.

Who it's for

Founders, heads of product and team leads who send the same numbers to the same people on a schedule: a month-end note to staff and investors, a Monday rundown for a sales team. Those readers don't log in to your analytics tool, and wouldn't know which chart mattered if they did.

If your readers need to filter, drill down or see this morning's figure, they need a reporting tool wired to the data. A page sent as a link shows the export you pasted in, until you replace it.

What a good one contains

  • A sentence before any chart. Bareroot's page opens with revenue up 5.3% and eleven customers lost, in one breath. A reader who stops there still knows the month.
  • Few numbers, each against the last period. Five tiles, each with its change on October and a twelve-month line. On its own, 318 support tickets means nothing.
  • Bad news labeled as bad. Lost customers went up, and so did revenue. The tiles that need attention carry the word "watch", so nobody has to decode a color.
  • One main chart. Twelve months of recurring revenue with a dashed line at $1M a year. Give a reader six small charts and they'll skim all of them.
  • The reasons, written out. "What changed, and why" is four short paragraphs. Five of the eleven lost customers were nurseries closing for winter, which no tile could say.
  • What happens next, with a name or a date. The sales page gives each stuck deal an owner and a day. The monthly one lists three jobs for December and one ask of investors.
  • How each number is counted. Activation here means a first order within 7 days. One paragraph of definitions saves the same question every month.

Before you send it

Add up everything that can be added up. In the monthly example, October's $84,200 plus new customers and upgrades, minus downgrades and losses, comes to November's $88,680, and a table shows each step. In the sales one, five reps' targets make the team's $240,000.

Keep the same tiles in the same order every time. People learn where to look, and a number that vanishes the month it turns bad gets noticed. Write the reasons yourself. An export shows that tickets rose, not that the new import caused it.

How to send it

To named people. It shows revenue, lost customers and who is behind target. The readers are a short, fixed list, so open it to those addresses and leave everyone else out.

Every page you publish gets one link that opens in any browser. You choose who can open it: anyone with the link, anyone with the password, or only the people and company domains you name, who sign in with Google or Microsoft. Change the page later and the link stays the same.

Make yours in Claude

Add the connector once, then publish from any Claude conversation and get a link to send.

Add Claude Connector

Already have the file? Upload it here.

More in product and engineering

  • Product roadmap: What a product team is building now, next and later, by theme, for customers and colleagues.
  • Data visualization: One dataset drawn as a few interactive charts, each with a sentence that says what to see.
  • Flowchart: A process or user flow drawn as steps, questions and outcomes, for the people who have to follow it.
  • Product requirements document: The problem, the requirements and what's left out for one feature, for the people who will build it.
  • App prototype: A clickable phone app in one page, sent to a few people to try before anyone writes real code.
  • Release notes: What's new, better and fixed in this version of your product, written for the people who use it.
  • All use cases

Keep reading