Budget, actuals, forecasts
The approved budget, what is actually consumed, and the expected landing. The variance is computed, not rebuilt by hand.
Continuous variance
FinOps module
The IT budget, from the annual mandate to the multi-year trajectory.
FinOps is the entry module of NavOps: the one that answers the questions put to you in committee. How much have we spent, where are we against budget, what will next year cost, and how much of it is already committed.
- Y-1 / Y / Y+1
- Budget · Actuals · Forecast
- Run / Build · CAPEX / OPEX
- Group and per entity
Reading axes
Four ways to read the same data
A spend line is not entered four times. It carries its attributes, and each axis becomes a reading.
Run and Build
What keeps the estate running and what builds what comes next. The Run/Build ratio measures your room to manoeuvre, and is tracked as such.
Room to manoeuvre
CAPEX and OPEX
The accounting nature of each spend is carried by the data. Your conversation with finance starts from the same figures as yours.
Shared language with finance
Multi-year Y-1 / Y / Y+1
The closed year, the current year and the one being prepared, in a single view. The trajectory is read, not guessed.
Three budget years
Consolidated · Per entity
Consolidated and per entity, without double entry
In a group, IT spend is decided in several places. Each entity works its own budget; the consolidated view is built from those budgets, not from a summary file kept on the side. When a subsidiary corrects a forecast, the group view changes the same day.
- Each entity works its own scope, with its own lines and its own owners.
- Consolidation is a reading, not a file to rebuild every month.
- Internal cross-charges between entities are flagged as such and do not inflate the consolidated view.
- An entity created mid-year enters the repository without manually reworking past budget years.
In committee
Questions you answer without preparing a spreadsheet
- Where are we against the IT budget today, for the group and for each entity?
- How much of our spend is committed by contracts already signed?
- What is our Run / Build ratio, and how has it moved over two budget years?
- What will next year cost if we decide nothing new?
- Which applications concentrate the spend, and at what criticality?
- Which forecast-versus-actuals gaps repeat from one year to the next?
The budget is the question you get asked, and rarely the one you have time to answer properly. FinOps takes it from the right end: a spend line carries its entity, its budget year, its accounting nature and whether it is Run or Build. From there, variance against budget, the committed share and the three-year trajectory stop being manual reconstructions and become readings of the same data.
In a group, each entity works its own budget. The consolidated view is built from those budgets rather than from a summary file kept on the side: when a subsidiary corrects a forecast, the group view changes the same day.
Getting started
Where to start
FinOps does not require a full IT inventory before it becomes useful. Three steps are enough to get a readable trajectory.
-
Declare the entities
Headquarters and the subsidiaries you steer. That is the only structure you strictly need up front.
-
Load one budget year
The current year budget and, if you have it, last year’s actuals. The comparison becomes immediate.
-
Attach the large items
The contracts and applications carrying most of the spend. The rest follows over time, without blocking the reading.
Ready to frame your steering?
Open your cockpit, with your own figures.
Subscription and account creation happen inside the application. This site collects nothing: it takes you there.
You are heading to app.navops.cloud — a page hosted by the application.