/data-apps
Build the tool you need, on your own data.
Describe it in a sentence: a dashboard, a review queue, a board story that stays current. It gets built against your data and opens with fresh numbers every time.
01 · Build
Tell it what the tool is for.
“Compare three copay designs and show plan-paid for each.” Or attach the spec you already wrote, and the app is built from that.
Compare three copay designs and show plan-paid for each.
Agree on the plan. Then build.
Before it writes anything, the builder checks your data and shows you the plan: the controls you get, what it leaves out, and what it assumed. Say “build it,” or change the plan.
The plan
- Controls you get
- Copay by visit type for designs A, B, and C. A member cohort.
- Leaves out
- Pharmacy claims
- Assumed
- 2026 claims, by paid date
02 · Use
Change an input. Watch it respond.
Apps run on live data, never a stale copy. Pick a cohort, toggle what counts, and every number responds. Save a set of inputs and come back next month: it recalculates on that month’s data.
Cohort
Plan-paid PMPM$412
Members4,120
Inputs saved. Next month, it recalculates on that month’s data.
03 · Dashboards
Live numbers. Nothing moves without you.
A dashboard is a data app you watch. Before it saves, it confirms the entity, the source table, and how each number is counted. Open any panel to see its source, its filters, and the query behind it. Change it in plain words, and each change lands as a new revision.
Live rev #1 · data from 32d · · built from demo_ind_ma
$16.0MTotal lab plan paid
$3.3MCarve-out eligible
783,758Lab lines
5.6%Denial rate
$655.7K2026-06 · −25.1% vs 2026-05
Fresh data on your schedule.
Refresh hourly, daily, or weekly. When the numbers hold, the update goes live on its own. When a number moves, the update waits for you, with each change laid out as was, now, and change.
Schedule
Sat · every number held
| Was | Now | Change |
|---|---|---|
| $412K | $415K | +1% |
| $52K | $51K | −2% |
| $18K | $18K | 0% |
Demo data
05 · Trust
It reads your data. Nothing else.
Every app runs in a sealed frame. It can’t reach the internet, and it can only run the queries it declared when it was built. Before you see the app, the builder runs each query and opens the app to check that it works.
Checked before you see it
- Query 1 ran
- Query 2 ran
- Query 3 ran
- The app opened
No internet. Only the queries it declared.
Start with the tool your team keeps asking for.
A dashboard, a review queue, a board story. Describe it in a sentence, and see it built on your own data.