The product
Five modules, a single repository.
Each module answers a question a CIO must be able to handle on the spot. They share the same entities, the same budget years and the same suppliers: the cockpit stays coherent as you move between them.
01 / 05
FinOps
The IT budget, from the annual mandate to the multi-year trajectory.
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.
What you gain
- Answer "where is the budget" in the room, without preparing a spreadsheet.
- Separate what signed contracts have committed from what is still open to decision.
- Track the Run / Build ratio as a measure of room to manoeuvre, not as trivia.
- Build the Y+1 budget from Y-1 actuals and Y consumption.
- Discuss CAPEX and OPEX with finance from the same set of figures.
What the module tracks
- Budget years
- Y-1 / Y / Y+1
- Reading axes
- Budget · Actuals · Forecast
- Natures
- Run / Build · CAPEX / OPEX
- Altitudes
- Group and per entity
02 / 05
Supplier contracts
No expiry date should ever take you by surprise.
A forgotten contract renews itself, and it is always the one whose price had drifted. The module tracks the dates that matter: period end, notice, termination window, automatic renewal. Expiries surface in order of urgency, with the associated spend and the entity concerned.
Because contracts are attached to suppliers and applications, a renegotiation is no longer prepared blind: you see the cumulative spend, the applications that depend on it and the level of supplier dependency before you open the discussion.
What you gain
- See expiry dates coming early enough to negotiate instead of absorb.
- Catch automatic renewals before the notice window closes.
- Attach every contract to its real spend, not to its headline amount.
- Prepare a renegotiation with supplier dependency in plain sight.
- Know, at any moment, how much of the budget is already committed.
What the module tracks
- Tracked
- Expiry dates and notice
- Alert
- Automatic renewal
- Linked to
- Supplier · Application · Entity
- Budget effect
- Committed share
03 / 05
IT projects
Progress, cost and drift in a single view.
An IT project leads two lives: the one on its schedule and the one in its budget. When those are tracked separately, drift is discovered at the point where it can no longer be recovered. The module holds both in one view: progress, committed, consumed, remaining.
Projects feed the Build share of the budget. Portfolio arbitration therefore happens with the budget consequences visible: deferring a project is no longer an isolated scheduling decision, it is a trajectory change you watch land on Y+1.
What you gain
- Track progress and budget consumption side by side, not in two tools.
- Spot drift while it can still be recovered.
- Tie the Build share of the budget to the projects that actually carry it.
- Arbitrate a portfolio knowing the cost of deferring each project.
What the module tracks
- Tracked
- Progress and milestones
- Budget
- Committed · Consumed · Remaining
- Nature
- Build, tied back to FinOps
- Altitudes
- Portfolio and per entity
04 / 05
Application portfolio
What you run, what it costs, what is about to break.
An application portfolio is steered on three dimensions at once: what the application brings to the business, where it stands in its lifecycle, and what it costs. Taken separately, those dimensions decide nothing. Crossed, they surface the real subjects: the critical application past end of support, the expensive one with residual usage, the duplicate between two subsidiaries.
The cost shown is not declarative: it comes from the contracts and spend lines attached to it. A decommission can therefore be defended with a figure finance recognises.
What you gain
- Cross criticality, lifecycle and cost to prioritise for real.
- Anticipate vendor end-of-support before it turns into an emergency.
- Justify a decommission with the application's real annual cost.
- Spot functional duplicates between entities of the same group.
What the module tracks
- Qualification
- Business criticality
- Lifecycle
- Vendor support and obsolescence
- Cost
- Annual cost per application
- Linked to
- Supplier · Contract · Entity
05 / 05
Suppliers
Spend, dependency and risk, supplier by supplier.
In a group, the same supplier is often contracted several times, entity by entity. Seen from a subsidiary it looks secondary; seen from the group it concentrates a significant share of the spend. The module consolidates that view: what you actually pay each supplier, and for what.
Dependency then reads in both directions: how many contracts, which critical applications, how reversible. That is what lets you negotiate knowing your own weight, and document supplier risk on something other than a hunch.
What you gain
- Know consolidated spend per supplier, across every entity.
- Measure dependency before discovering it has become structural.
- Enter a negotiation with the real weight you represent.
- Document supplier risk for compliance requirements.
What the module tracks
- Spend
- Consolidated across entities
- Dependency
- Concentration and criticality carried
- Risk
- Qualification and reversibility
- Linked to
- Contracts · Applications · Projects
Modules
What the modules share
A cockpit is not a set of tools sitting side by side. All five modules rest on a common foundation.
An entity repository
Headquarters and subsidiaries declared once. Every record carries its entity, so every view can be consolidated or filtered.
Budget years
Y-1, Y, Y+1: the same time frame for budget, contracts, projects and portfolio.
A supplier directory
One supplier, one record. Its contracts, its spend and the applications it carries attach themselves to it.
Consolidated and per-entity reading
The same data at two altitudes. The executive committee and a subsidiary manager do not need two different tools.
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.