The task: see which numbers need attention
The dashboard lists five KPIs with their latest value, their target and whether each is on track. The executive view shows all five. Choosing a department shows only that team’s metric. Pick a KPI to see its twelve monthly values beside the target.
This is a design example, not a customer story or evidence of a live deployment. The numbers are fixture data: in the executive view, three KPIs are on track and two are not.
The five KPIs in the example
A dashboard works when each number has a target and an owner. A number with neither is decoration. Replace these with your own.
Scroll sideways to see all columns. With the table focused, use the arrow keys.
| KPI | Target | Owner |
|---|---|---|
| Revenue against plan | 100% of plan or more | Finance |
| New customers | 40 or more a month | Sales |
| Average resolution time | 8 hours or less | Support |
| On-time delivery | 95% or more | Operations |
| Open purchase requests | 25 or fewer | Procurement |
Download the source and run it
The runnable version is one HTML file with a small build script. Run npm run build, open dist/index.html, and check that the executive view shows five KPIs with three on track.
Change it into your dashboard
Open the folder in your coding agent and describe the metrics you want and where each target comes from. Keep the fixture until the layout is right; real data comes later.
This is a KPI dashboard example with fictional data. Replace the five metrics with ours: [list them, with each target]. Keep the executive and department views, keep using the fixture, and do not add any credentials.Build a dashboard or buy a dashboard product
Both are reasonable. The choice depends on how many numbers you track and who maintains them.
- Buy a dashboard product when you need dozens of data connectors, self-serve charting for analysts and scheduled reports.
- Build when the dashboard is a handful of numbers a team checks daily, the layout is specific to you, and you want the result as code you own.
How SpringRoll helps you run a KPI dashboard for your team
A dashboard is only useful if the right people can open it and the numbers are real. That is the part a coding agent does not build.
The App Portal controls who can find and launch the dashboard. Its own provider address is separate, so a dashboard showing real figures must check sign-in itself.
Scroll sideways to see all columns. With the table focused, use the arrow keys.
| What you need | What SpringRoll does |
|---|---|
| Somewhere to run it | Your agent deploys it to managed Vercel or Cloudflare. Nobody needs a provider account |
| The right audience | You choose the audience for each app, so executives see the dashboard in their App Portal and other teams do not |
| Real numbers without a password in the code | A data owner approves the specific fields the dashboard may read. Source credentials stay on the SpringRoll server |
| Someone to ask when a number looks wrong | Every app shows its owner and support contact |
| Changes you can trust | Each update is a recorded release, with a named approver on the Staged workflow |
Frequently asked questions
What is a KPI dashboard?
A single screen showing a small set of key performance indicators against their targets, so a team can see what needs attention.
Can I use this example for my own company?
Yes. Download the source and change it. The data in the example is invented.
Can AI build a KPI dashboard?
Yes. A coding agent can change this example into your dashboard from a description. You still need somewhere to run it and a way to choose who can open it.
How does the dashboard get real data?
Through SpringRoll Connect: a data owner approves specific fields for the app, and the app never holds the database credential.
