Budgeting software that tells you what it does not know

Blash Budgeting is a driver-based budgeting platform for multi-company professional-services groups. A budget round is forty spreadsheets, six versions of each, and a consolidation somebody rebuilds by hand every time a number moves. Nobody can answer "which is current?" and nobody can prove what is missing.

In short

Every recompute runs the same arithmetic checks and publishes the results on screen, including the ones that fail.

Watch it work

31 checks
arithmetic checks run on every recompute and publish their results on screen, pass and fail
1,000+ tests
automated tests run on every change to the software, each one a rule that was wrong the first time
6 roles
access levels, from department owner to board observer, tested against every screen before a release
Every page, every role
probed in both request shapes a browser uses, asserting on the response body rather than the status code
Every write surface
attempted as every role and asserted against the database before and after
No default rate
a month with no exchange rate blocks rather than converting at 1.0
01

The budget round cannot check itself

The annual budget is the most consequential number a business produces, and almost every business builds it in the one tool that cannot check itself.
A spreadsheet cannot tell you a cost is missing. It cannot show one department its own margin without showing it everyone's salaries. And it cannot be worked on by forty people at once without becoming forty different budgets. So the round takes months, the result is defended rather than trusted, and the finance team spends its time on collection instead of on the decision.
A missing cost is arithmetically indistinguishable from a cost of zero. Nothing breaks, the P&L balances and every check in the spreadsheet passes, because the cost is absent from both sides.
Two errors in opposite directions make a total look right, and a total that nearly matches is the most dangerous state a model can be in.
A renamed row silently zeroes a line. Roll-ups match on text, so changing a category name in one place makes a summary read nil, and nothing turns red.
The consolidation is a second model. Rebuilt by hand, it can disagree with the parts it came from, and then the argument is about the spreadsheet rather than the business.
02

One set of figures, and a clear line between input and output

Each department enters what it owns: its people, its costs, its revenue, its hiring requests. Nobody waits for anyone else and nobody works on a copy. When a department saves, the directorate, company and group results are recomputed from those rows, because they are computed from the department inputs rather than rebuilt from them.
Access is scoped by design. A department head plans their own team and sees their own margin. HR sees people and payroll and never a profit figure. Finance sees all of it.
And the model reports on itself. Every recompute checks its own arithmetic and publishes what it found, separating "this does not add up" from "nobody has told us this yet".
03

Collection and workflow

Budget requests, hiring requests, marketing spend, software, events and infrastructure are all submitted through the platform instead of by email. Each has an owner, a state and a history. Hiring routes through HR automatically. Nothing sits in someone's inbox.
Forty people can be entering at once. There is one set of figures, so there is nothing to merge and no version to be behind.
Each department gets a collection template showing what is required and in what format, with worked examples. Teams that prefer to work offline fill in the same structure and upload it back.
Every change is logged: who, when, which field, the value before and the value after.
04

Access and confidentiality

Six access levels cover the round. Finance and leadership see everything across every company. A directorate lead sees every department beneath them and changes nothing, because their job is to review. A department owner sees and changes their own department only. HR sees people, payroll and hiring. Sales sees the contract register and the pipeline, and no cost screen. A board observer sees the published statements and nothing else.
A department head sees their team's total cost and never a named person's salary, because a headcount of four with a total is a salary. Individual pay is visible to HR and finance only.
Opening a screen is not permission to change it, and permission to change a screen is not permission to change another department's rows.
05

Numbers you can defend

The platform distinguishes two kinds of failure and says which: "this does not reconcile" and "nobody has supplied this yet". The second is listed with the money it represents and the person who owns it. Checks are published on screen, pass or fail, with the amount and the reason, rather than hidden behind a green tick.
Every generated figure is marked as generated, a completion view counts how many are left, and the marker is removed in the same action that replaces the value.
Roll-ups are structural, never text matches, so renaming a category cannot zero a line. Money is held as exact decimals, never floating point.
Costs are stored negative, in statement direction, so actual minus budget is favourable when positive for every account type.
The pipeline is probability-weighted once, and the system knows it, so a weighted figure is never weighted a second time downstream.
Rates and salaries are dated rows, not edits, so a scenario approved in March still computes the pay that was true in March. And the calculation engine reads no database and no clock: the same inputs give the same numbers on any run.
06

Multi-company groups and currencies

Companies, directorates, departments and people are a real hierarchy, not a naming convention. Two companies in a group can each run an Operations department and the system knows they are not the same one.
Shared costs are apportioned and the apportionment is shown: the pool, the basis and each receiving department's percentage, ring-fenced by company. A check asserts that what is charged out equals the pool.
Tax is per company, because that is how it is assessed. One company's loss cannot shelter another's profit. Intercompany trade is a pair, not a line, so the group never books margin on its own internal trade.
A missing exchange rate blocks. It never defaults to 1.0, and the checks name the row, the amount and the currency.
07

Built for businesses that sell people's time

Each department owner states how many months of the year each person will spend on project work. From that one number the platform derives utilisation, bench, and the split of staff cost into the part that earns and the part that does not. Bench cost appears on the P&L on its own line. It is never netted off, hidden inside a blended rate or apportioned somewhere else.
Staff cost is fully loaded: salary plus employer contributions, end-of-service provision, leave, medical cover, insurance, bonus and travel. A bench figure built on base pay alone understates the cost of idle capacity, because none of the loaded costs stop when the work does.
The hiring gate informs rather than blocks. The approver sees the department's bench percentage and bench cost, the same figures for sibling departments, and gross profit at the moment of the request. Above a configurable threshold it asks for a written justification, but it is not refused.
A hiring request carries its own expected utilisation, so the position argues its own case and can be reviewed a year later.
08

Scenarios and reporting

Take a scenario, change the drivers, compare. Uplifts, hiring freezes and rate changes can be modelled without disturbing the approved version. Reporting covers departmental and company P&L, directorate roll-up, group consolidation, the indirect-cost pool and its reconciliation, utilisation and bench by person and by team, headcount and cost bridges, variance analysis, and a standing validation panel.
09

Who it is for

Multi-company professional-services groups: consulting, technology services, engineering, agencies, managed services. Anywhere revenue comes from people's time, several legal entities file separately, and departments own their own numbers.
It fits when more than one legal entity is consolidated for management reporting, ten or more departments contribute to a round, and the finance team is doing collection rather than analysis.
It is not a fit for a single company with three departments, where a spreadsheet is genuinely fine, and not yet a fit for product businesses with no people-utilisation model.
Buyers are CFOs who want a number they can defend, controllers who want to stop chasing and merging, and HR directors who want hiring decided with the bench position visible.
10

What people use it for

Three jobs the platform is built to do.
The annual budget round: templates out, departments entering in parallel, consolidation computed, and a list of what is outstanding. The round ends when the list is clear rather than when everyone is exhausted.
Departmental profitability, per department and per month: revenue, fully loaded staff cost split into utilised and bench, gross margin, apportioned overhead, net margin.
Governing hiring: every position requested in one place, routed to HR, decided with the bench position on screen.
11

Why not a spreadsheet, an ERP or enterprise FP&A

Spreadsheets are excellent at arithmetic and structurally incapable of two things you need: telling you what is missing, and letting forty people work on one model without making forty models. That is not a criticism of anyone's spreadsheet skill. It is a property of the tool.
An accounting system records what happened. A budget is a set of assumptions about what will happen, owned by dozens of people, with a workflow attached. Most ERPs have a budgeting module that stores a budget once it exists rather than a place to build one. Blash Budgeting does not replace your accounting system and is not trying to.
Enterprise planning tools are powerful and general-purpose, and they are scoped to be configured for any function in any industry. Blash Budgeting is narrower on purpose: utilisation, bench, practice areas, directorates and per-entity tax are built in rather than configured. Most of what makes this hard is not the arithmetic anyway. It is the access model, the audit trail, the apportionment that has to reconcile, and the several hundred small decisions about what a budget model must refuse to do.
12

See it against a group shaped like yours

Book a thirty-minute walkthrough and we will run it against a group shaped like yours. Bring your worst spreadsheet.
There is also a live demo with no login: a real model with synthetic data, so you can look at the structure before you talk to anyone.

Common questions

What if our data is a mess?
That is the normal case and the platform is built for it. Gaps are reported with the money they represent instead of being silently filled. You can start with a complete, working model in which every generated figure is visibly marked, and replace them as real data arrives.
How does it get set up?
The structure is loaded from your own records rather than rebuilt by hand: companies, directorates, departments and the chart of accounts. Ask us for a scoped estimate against your actual data.
Do we have to abandon our spreadsheets on day one?
No. Departments that prefer to work offline can use the collection templates and upload them. The platform becomes the system of record for the budget, and the spreadsheet an input form rather than a model. It is not an accounting system and does not replace one.
Can a department head see other departments' salaries?
No. They see their own team's total cost and never an individual's pay. The rules are enforced in one place and tested against every screen before a release.
What happens when someone changes a number?
It is recorded: who, when, which field, the value before and the value after. Every figure downstream is recomputed from the inputs on save.
Is it only for services businesses?
The utilisation and bench model is built for businesses whose revenue comes from people's time. Everything else is general: consolidation, apportionment, scenarios, workflow and access control.
Can we try it before committing?
Yes. The demo needs no login. It is synthetic data on a real model: the structure and the checks are the genuine article, the numbers are invented.
Next step

See it on your own numbers

A short walkthrough with the people who built it.