Next quarter
your first capacity trade-off, not in 18 months.
You are no longer the transformation champion chasing buy-in. You are the one who proves, benefits in hand, that transformation delivers on its promises. AirSaas gives you both levers: take control of demand so the portfolio reflects the strategy, and prove the benefits to embed new ways of working.
Already adopted by 100+ CIOs of mid-market companies and large groups
Kiabi · Valrhona · Leroy Merlin
The queue of qualified, scored requests. Realistic data: named projects, amounts in euros.
your first capacity trade-off, not in 18 months.
you send us your files, we deliver the portfolio.
if the ritual does not take, you walk away at no cost.
more projects delivered
of capacity recovered
fewer meetings
Let us be clear about your role: a transformation department does not own all the delivery teams, and its main impact is not producing the projects. Its first value is making sure that what gets launched serves the strategy, and that what gets delivered creates the value expected. Day-to-day delivery belongs to the contributing teams.
AirSaas gives you the two levers of this job: taking control of demand so the portfolio reflects the strategy rather than the balance of power, and measuring the benefits to prove, numbers in hand, that transformation delivers on its promises. You are not steering teams, you are steering the coherence between what is decided and what actually happens.
requests arrive through a corridor, an executive committee, an email to the CEO. Everything is a priority, so nothing is. Every project moves, none of them lands, and your transformation spreads thin instead of moving forward.
six months after each delivery, nobody checks the benefit that was promised. Transformation cannot prove its return, and every budget decision turns back into a battle of opinions.
A request qualified before it exists. A trade-off every 90 days.
Benefits measured after delivery. The three pieces fit together: your portfolio becomes a strategy again, and you walk into the ExCom with results, not justifications.
The request, trade-off, benefits loop in 3 steps.
The loop as a frieze (submission, qualification, assessment, trade-off), with one request open.
GIF of the brief generated from two sentences.
The promised vs realized view, with one gap owned. Realistic data: named projects, amounts in euros.
Two transformation scenarios side by side. Realistic data: named projects, amounts in euros.

Thomas Poitau, former Transformation Director at Carmila, joined the AirSaas team in 2022.
His convictions about the processes that change working life come from more than 200 interviews with CIOs and transformation leaders, on top of the 15 years he spent transforming large organizations.
A transformation request only becomes a workstream if it clears clear qualification gates. You define the gates, their criteria and their vocabulary; AirSaas enforces the path, so that the portfolio reflects a strategy and not the balance of power.
is the idea aligned with the transformation objectives? An executive sponsor commits, otherwise the idea stays an idea. The first filter against ghost workstreams.
expected value, estimated workload, dependencies, risks. The request becomes a case comparable to the others, ready for the trade-off.
capacity is reserved, the benefits and their owner are agreed. The workstream enters the portfolio with a value contract, not just a budget.
after delivery, the promised benefit is set against what was realized. The loop closes, and the next qualification is fairer for it.
Some transformation departments want an objective score to separate requests, others prefer judgement in the room.
AirSaas does both: scoring is available, configurable, and never imposed.
A request scored against a custom grid, with the score recalculating as a criterion is adjusted; next to it, AI Brief turning two sentences into a structured case.
of requests tied to a strategic priority before entering the portfolio. No more workstreams orphaned from strategy.
workstreams running in parallel: capacity is concentrated on what serves the strategy, instead of launching everything.
of workstreams with a benefit measured and verified one year after the process was put in place.
Requests arrive through every corridor
A portfolio that reflects the balance of power
Benefits invisible six months after delivery
Every budget is a battle of opinions
One way in: qualified, or it does not exist
A portfolio that reflects a strategy, decided every 90 days
Promised against realized, project by project
Your budgets defend themselves, with results
“We cut the number of workstreams running in parallel, and put real benefits tracking in place. The result: business cases are better qualified up front, because everyone knows they will be looked at.”
Transformation Director, services group
fewer workstreams in parallel, more value delivered
Full case studies on the customer stories page.
“When you have 120 projects for a head office of 270 people, you either get organized properly, or you question the project.”
Guillaume MarloisIndustry
Food & beverageHeadcount
850“It was still about trust, but trust with a process behind it.”
Chantal GuilmainIndustry
RetailHeadcount
2,500“It is not a tool. It is an approach, a discipline, a practice.”
Industry
Eyewear, retailHeadcount
3,000This is the Achilles heel of every transformation department: projects get delivered, but six months later nobody knows whether they returned what they promised. Without proof, every budget decision turns back into a battle of opinions, and transformation is the first thing cut when times get tight.
AirSaas closes the loop. Every workstream declares its expected benefit (an amount or an indicator, a deadline, an owner), and the post-delivery review sets the promise against what was realized, in session. You walk into the ExCom with a view of realized benefits: here is what transformation cost, here is what it returned. At that point you are no longer defending a budget, you are presenting a return on investment — and the next budget defends itself.
Rollout with a contracted method: configuration, projects and PMs on board, first review co-facilitated by our teams.
No user licences: everyone gets access to the tool, from the project manager to the ExCom. Stop a pointless project and your bill goes down.
If the ritual does not take, you walk away at no cost. We take the risk with you.
That is the case for most of our customers. One way in and capacity by department, with the trade-off at whole-portfolio level.
A benefit, an indicator, a deadline, an owner. The method provides templates by type of benefit (savings, revenue, risk avoided).
The form is what brings them in: no declared sponsor, no assessment. The ritual makes sponsorship visible, and therefore binding.
The first Quarter Plan happens in the quarter following the rollout. That is usually where the first projects get stopped or postponed.
A 30-minute demo on your own context. We show you the ritual, you judge.