Budgets
A fee side and a cost side on every project budget, with lifecycle states and a true-up at close, so the plan and the outcome meet on the same record.
Everything you can do with financials & insights
The money layer that reads everything else and tells you where to look.
Inside financials & insights
Every piece that makes this work, and what each one is actually for.
Funding links
Budgets draw on named contract deliverables, which makes coverage a computed number and unfunded work visible before it happens.
Change requests
Budget increases travel through an approvals inbox, with who asked, who approved, and what changed kept on the budget itself.
Budget alerts
Thresholds checked on a schedule, so the overrun conversation happens at 80 percent and not at 130.
Client budgets
A per-client envelope for the fiscal year, sitting above project budgets so the account view and the project view agree.
Budgets that match reality
A project budget carries a fee side and a cost side, and draws its funding from named contract deliverables, so coverage is a computed number rather than an assumption. Burn comes from the same approved time and expenses that drive invoices, alerts fire when a threshold is crossed, and an increase travels as a change request through an approvals inbox. At close, a true-up reconciles the plan against what actually happened, on the record.
What this removesThe budget spreadsheet living beside the project, and the overrun nobody saw until the invoice argument.
See how everything connectsThe questions this actually answers.
The long version, because this is where the category has real objections.
Did the project actually make money?
Every project budget carries a fee side and a cost side, funded by named contract deliverables, with committed cost flowing in from real allocations and real approved hours. At close, a true-up puts the plan and the outcome on the same record. Margin reads by client, project, deliverable, and role, so you learn not just whether you made money but where and on whom.
Fee and cost, side by side
The two numbers most tools keep in different apps.
Funded by deliverables
Coverage is computed. Unfunded work is visible.
Margin by role
Find out which kind of work actually pays.
When do you find out about the overrun?
At 80 percent, not at 130. Budget alerts check thresholds on a schedule, and an increase travels as a change request through an approvals inbox, with who asked, who approved, and what changed kept on the budget itself. The overrun stops being a surprise in the month-end pack.
Which clients are quietly going wrong?
Client health combines delivery, commercial, and relationship signal into a read you can defend, recalculated on a schedule from records the work already runs on. The account that has gone quiet, slipped its dates, and paid late shows up as a number moving, months before it shows up as a cancellation.
What is the revenue actually going to be?
Forecasting weights the pipeline with probability drawn from your own win history, and revenue bands hold committed, likely, and possible over time, snapshotted so the change between last month’s view and this one is itself visible. The number moves for reasons you can point at.
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
How are project budgets structured?
With a fee side and a cost side, lifecycle states, and a true-up at close. Budgets fund from named contract deliverables, so coverage is a computed number.
When do budget alerts fire?
On thresholds checked on a schedule, so the conversation happens at 80 percent burn. Increases route as change requests through an approvals inbox.
What goes into the client health score?
Delivery, commercial, and relationship signals, combined on a schedule from the records the work already runs on, into a read you can defend line by line.
Can we see margin by role?
Yes. Profitability reads by client, project, deliverable, and role, from live cost and bill rates, with recognized, invoiced, and collected kept apart.
Where does the forecast probability come from?
From your own win history rather than a gut feel, with revenue bands holding committed, likely, and possible over time, snapshotted so drift is visible.
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.