Team analytics, minus the portal nobody visits

Your dashboards are correct. That's not the problem.

Lumenboard gives your team real usage, health, and account data through a clean API — so the insight can live where your team already works, instead of a destination they have to remember to open.

Read the API docs See the problem

What your team sees inside Lumenboard

Same data as the API below — real accounts, real health scores, the at-risk list surfaced automatically. On a narrow screen, scroll the panel sideways to see the rest — same as panning a real screenshot.

Accounts
15 accounts · updated moments ago
Accounts
15
MRR
£9,615 /mo
Weekly active users
652
At-risk accounts
3
At-risk accounts health score under 40, worst first
AccountHealthPlanMRRRenews16-week usage
Hollowbrook Freight 19 Enterprise £1,890 21 days
Palewell Logistics 24 Starter £45 28 days
Thistlewood Capital 31 Enterprise £1,260 34 days
Health score distribution 15 accounts
0–20
1
21–40
2
41–60
1
61–80
5
81–100
6

The problem we built Lumenboard to fix

Most teams sign up, look around once, and never come back. Not because the data is wrong — because a dashboard is a destination, and destinations get forgotten. Meanwhile the accounts that are quietly drifting toward churn don't send up a flare on their own; someone has to go looking, and by the time they do, it's often too late to do much about it.

"We had good data and a weak habit. The fix wasn't a prettier chart — it was getting the signal in front of people without asking them to go somewhere for it." — Naomi Ren, Head of Product, Lumenboard

What's actually in the API

Users & accounts

Every user and account in your workspace, with plan, seats, MRR, and a live health score — the raw material for any retention view.

Usage & events

Per-account usage time series and a recent product-events feed, so trend and momentum are visible, not just a single snapshot number.

Built for building on

Modern REST, JSON, per-team API-key auth, a published OpenAPI spec, and honest pagination/error handling — the same discipline we'd want from a vendor.

Where this goes next

The API is the floor, not the ceiling. We're specifically interested in whether the insight can live inside the tools our team already has open — a connector, not another tab — rather than one more dashboard competing for attention. If you're building against this API, GET /accounts and GET /accounts/{id}/usage are the fastest way to find the accounts that need attention first.