Dashboards
Role-relevant boards built from configurable widgets and shared with the people who read them. The Monday screen that replaces the Monday meeting.
Inside reporting & dashboards
Every piece that makes this work, and what each one is actually for.
Widgets
Priorities, progress, workload, pipeline, and business signals, each reading live records rather than an export that was stale on arrival.
Saved views
Any filtered list, saved and shared. The lightest report is the view itself.
Know how every client is doing
Contacts belong to more than one account, which is how agency relationships actually work. Calls, email, tickets, meetings, threads, and events all roll up to one account timeline. The health read is derived from that alongside delivery and commercial signal, so it is a calculation with sources rather than a color someone picked in a spreadsheet.
What this removesAccount health as an opinion. Nobody has to assemble a history before a renewal conversation.
See how everything connectsThe questions this actually answers.
The long version, because this is where the category has real objections.
Why is the weekly report always stale?
Because it is built from exports. Someone pulls four CSVs from four tools, reconciles the client names, and presents numbers that were true on Tuesday. Scrambl dashboards read the live records, and because work, customers, finance, and resources share one foundation, the cross-functional numbers agree by construction. The report stops being a document and becomes a screen.
No export step
Widgets read records, not files.
Numbers that agree
One foundation, nothing to reconcile.
Always current
True now, not last Tuesday.
What should each role see first thing Monday?
Their own dashboard. Delivery sees workload, risk, and what is due. Sales sees pipeline movement and stalled deals. Finance sees burn, margin, and what is overdue. Leadership sees the roll-up. Same records underneath, different widgets on top, each shared with the people who should be watching.
How do problems surface before someone goes looking?
Alerts watch thresholds and changes on a schedule and route to the person who can act: the budget crossing 80 percent, the ticket about to breach its SLA, the stock hitting its reorder point. The dashboard is for the questions you know to ask. Alerts cover the ones you forgot.
Can you trust the number enough to act on it?
Yes, because you can open it. Every figure drills through to the records and owners underneath, the entity timeline shows the history in one place, and the audit trail shows who changed what. A number you can interrogate is a number you can take into a hard conversation.
Every module has its own page.
The short version lives here. Each module below has a page of its own with the views, fields, and edge cases spelled out.
Questions people actually ask
Do we still need a separate BI tool?
For most operational questions, no. Dashboards, reports, and alerts read the live records directly, and every number drills through to the work underneath it.
Can dashboards be shared?
Yes. Build a board from widgets and share it with a team or a role, so everyone watches the same screen instead of their own version of it.
What can alerts watch?
Thresholds and changes across the workspace: budget burn, SLA risk, stock levels, and the operational signals your processes care about, each routed to whoever can act.
What can reports cover?
Project delivery, service performance, campaigns, inventory, suppliers, utilization, staffing, and profitability where enabled, scheduled instead of rebuilt.
Can we drill into a number?
Always. Figures open into the underlying records and their owners, so insight turns into a conversation with a name attached rather than a screenshot.
It does not stop at one capability.
Scrambl is one workspace, so the records here are the same records the rest of the platform reads. These pair with it most often.
.svg)
Ready to crack the chaos?
One workspace for projects, clients, finance, and everything in between. Try for free.