Data apps
The tools your team works from. Built by asking.
Not another report to glance at — live operational apps. Renewal queues, collections workbenches, account scorecards: built from a prompt, fed by every system you run, and current all day.
From prompt to app
Describe the tool. Get the tool.
Internal tools usually mean a spreadsheet somebody maintains by hand, or an engineering project nobody has time for. In Synopsis, you describe the app — what's in the queue, how it ranks, what counts as done — and it's built on your warehouse, where the data already lives joined.
- A sentence is the spec. "A queue of renewals ranked by risk, with usage and open tickets on each row" is a working app.
- No build queue. Teams get their tool in days, not on next quarter's roadmap.
- Change it by asking. Add a column, change the ranking, split the queue by owner — the app evolves the way it was built.
Done — 31 overdue invoices, ranked, each row joined to the account's support activity. Two of your five largest balances have open escalations, so you may want to route those to success first.
Sources: billing · support desk · CRM
Live and cross-system
The queue re-sorts as reality changes.
A spreadsheet is a photo of last Tuesday. A data app is a window: rows come from the warehouse, where every system lands on shared keys, so a payment posting or a support ticket opening reshuffles the queue on its own. Your team works the top of the list and trusts that the top is right.
- Rows are live. When the underlying data moves, the app moves — nobody refreshes an export.
- Every row is cross-system. One line shows the renewal date, the usage trend, and the unpaid invoice — from three different systems.
- Ranked by what matters. Risk scores draw on all of it, so urgency is computed, not eyeballed.
Joined from: billing · support desk · product events
Work happens here
Act from the app, not around it.
An operational tool should absorb the work, not just display it. Assign a row to an owner, mark it handled, dismiss the ones that don't need attention — the state lives in the app, so Monday's standup starts from what's actually left, not from memory.
- Assign. Put a name on a row so nothing sits unowned.
- Resolve. Done means done — cleared rows leave the queue and stay counted.
- Dismiss with a reason. Not every flag deserves work; waving one off is a decision the team can see.
What your team gets
Built for the teams doing the work.
Queues
Renewals, collections, follow-ups — ranked lists that tell each person what to do next, and re-rank themselves.
Workbenches
Everything about the account on one row: the balance, the tickets, the usage. No tab-hopping to build context.
Scorecards
Per-rep, per-region, per-product views that stay current — the same numbers the dashboard shows, at working altitude.
No exports, no copies
Apps read the warehouse directly. There's no stale spreadsheet fork for the truth to drift away from.
Owned states
Assigned, done, dismissed — the queue carries its own status, so handoffs survive vacations.
Ask about any row
Every app sits on the same warehouse as chat. "Why is this account flagged?" is one question away.
Keep exploring
Data apps are one surface of the platform.
Retire the spreadsheet your team runs on.
Describe the queue, the workbench, or the scorecard your team maintains by hand — and see it come back live, joined, and ranked, on your data.
