- Industry
- IT Company
- Department
- Finance
- Team
- Planning and Compliance
- Kind
- Investigator
- Approver
- CFO
- Code
- FIN-09
It builds budgets for delivery practices, the SaaS business and support functions from headcount plans, billable utilisation targets, blended rates, cloud costs and ARR assumptions, and each month explains the variances between actuals and budget. It tells volume causes (fewer billable hours, bench) from rate, mix and cost causes, and recommends a reforecast when variances persist. **The problem it solves:** Why actuals differ from budget: whether volume, rate, mix, headcount, bench or cloud cost drives each variance, and whether it will persist.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the professional services automation (PSA) system: billable hours, utilisation, rates and headcount by practice, with the ledger actuals and budget..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Works it through
Weighs competing explanations against the evidence and shows which one holds up.
- 05Asks a person
Hands the work to CFO with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the project management tool: it files the variance review for each budget owner with actions. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The budgeting method: practice and cost-centre structure, utilisation and rate assumptions, headcount plan, cloud cost drivers, variance thresholds and the reforecast policy.
Reads from
the professional services automation (PSA) system: billable hours, utilisation, rates and headcount by practice, with the ledger actuals and budget.
Acts in
the project management tool: it files the variance review for each budget owner with actions.
Hands back
An object with month, lines (a list with line, actual, budget, variance and variance_percent), explanations (a list with line, cause volume, rate, mix, cost or one_off, evidence and confidence) and reforecast_recommended (true or false).
Asks a person when
The review recommends a reforecast, or a practice's gross margin is below budget by more than 10 percent.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Budgeted billable utilisation (%) | 78 | The utilisation assumed in delivery budgets. |
| Explain variances over (%) | 10 | Lines off budget by more than this are explained. |
| Explain variances over (USD) | 25000 | Lines off budget by more than this amount are explained. |
| Reforecast after (months off) | 2 | A line off budget this many months running triggers a reforecast recommendation. |
| Salary increase assumption (%) | 4 | Used when the plan names none. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Explain lines off budget by more than 10 percent or 25000 USD.
- Split delivery revenue variances into volume (billable hours against 78 percent utilisation), rate and mix, and cost variances into headcount, bench and cloud.
- Recommend a reforecast when a line is off budget 2 months running.
- Assume 4 percent salary increases when the plan names none.
- Separate one-off items from run-rate.
See the Budgeting Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.