ISO 270011/3
more projects completed
We don't install a tool. We install
a process that grows inside your organisation.
The question isn't "how do I configure AirSaas", but "which process do you want to anchor": the Quarter Plan, demand management, or benefits tracking. We start there, install it with a former peer who has already done it, and grow it inside your organisation. The tool follows — it isn't the point.
Already adopted by 100+ CIOs of mid-market companies and large groups
Kiabi · Valrhona · Leroy Merlin
Visual coming soon · Diagram / illustration
Three entry doors (Quarter Plan, Demand management, Benefits tracking) leading to the same support, with the maturity curve rising.
15%
of capacity recovered
80%
fewer meetings
Most PPM rollouts fail for one single reason.
They install a tool instead of installing a process. You configure, you train, and six months later the tool is empty, because nothing changed in the way people work.
Tooling up before having a process
Setting up a project portfolio register is fine, but it's thin. Without a real process behind it (arbitration, demand, benefits), the tool becomes just one more database.
Not surfacing the real pains
The point of a rollout isn't ticking configuration boxes. It's surfacing teams' real difficulties and structuring them. That's where adoption is won.
Support from installers, not peers
A consultant who knows the software isn't enough. You need someone who has already lived through installing this process in an organisation like yours, and knows where it gets stuck.
"We don't set up AirSaas. We set up the process you want to grow. The tool comes to serve that process."
Our conviction about rollout
We start from your process, not from our screens.
Depending on your top priority, the rollout is organised around a process to anchor. That process structures everything else.
The Quarter Plan — Arbitrate at the quarter's rhythm
Install the capacity-arbitration ritual: team capacity, scenarios, quarterly review, gap measurement.
Demand management — Control what comes in
Set the entry point, qualification and scoring, so the portfolio reflects strategy and not power struggles.
Benefits tracking — Prove the value
Install benefit declaration and the promised / observed review, to anchor a culture of evidence.
One process at a time — The secret to adoption
We focus on one process and make it live, rather than deploying broadly and diluting adoption.
The support
Supported by a former transformation director or CIO. Not by an installer.
What makes the difference is who supports you. At AirSaas, they're peers who have already deployed this process in their own organisations.
→ Someone who has already done it
A former transformation director or CIO who has set up this process at their own clients. They speak your language and know the traps.
→ Surface and structure the pains
The real work is here: gathering teams' actual difficulties and structuring them into a process that holds. Far more than configuration.
→ Grow the process
The goal isn't to install, it's to mature the process inside the organisation until it runs on its own and creates value.
Visual coming soon · Photo
A peer supporter (former CIO / transformation director) in a workshop with the teams, structuring the surfaced pains.
More than 100 rollouts in four years. From 200 to 10,000 people.
We don't discover your situation: we've already met it. In four years, AirSaas has supported more than a hundred rollouts, in organisations from 200 to 10,000 people, and in international contexts: France, Switzerland, Canada, Spain. The constant across every successful rollout: a genuine will to install a process, not just a tool.
Once that condition is met, it works very well. That's also why we prefer to focus on a clear, high-value process (arbitrate, control demand, prove benefits) rather than a vague goal like "gaining visibility" or "keeping a project register" — useful but thin.
The rhythm
Six weeks to launch, three cycles to autonomy.
The process installs fast and transfers gradually, until your teams hold it on their own.
→ The scoping workshop
Your governance bodies, your criteria, your teams, and above all the pains to address. We start from your reality.
→ The first co-run review
Your first cycle of the process (Quarter Plan, demand review or benefits review) run with our teams. That's the go-live.
→ Three cycles to autonomy
We co-run, then we step back. Go/No-Go clause at three months: if the process doesn't take hold, you leave at no cost.
Visual coming soon · Diagram / illustration
The timeline: scoping, co-run go-live, 3 cycles, autonomy, with the Go/No-Go milestone at 3 months.
Visual coming soon · Product screenshot
The integrations screen: Jira, Asana, Monday, Teams, ERP connection. Realistic data.
Connected to your tools
The tool adapts to the process, and to your ecosystem.
AirSaas doesn't replace your execution tools: it sits on top, at the steering level, and connects to them.
→ Your execution tools
Jira, Asana, Monday: teams keep them, AirSaas consolidates at portfolio level and connects to them.
→ Teams at the core
The native Teams integration syncs projects and channels and pushes notifications where teams already work.
→ API and ERP connection
A public API to plug in your data (including the ERP for budget), with ready-to-use templates.
The numbers of the rollout
100+
rollouts supported in four years, from 200 to 10,000 people, in international contexts.
6 weeks
from the scoping workshop to the first co-run review. The process starts within the quarter.
Go/No-Go 3 months
the no-cost exit clause if the process doesn't take hold. The risk is on our side.
KIABIVALRHONALEROY MERLINCHIESIINTUISGT SOLUTIONS
"We didn't deploy software, we installed a way of working. Being supported by someone who had already done it changed everything: they knew how to surface our real issues."
CIO, industrial mid-market
100+
rollouts in 4 years, from 200 to 10,000 people
questions about the rollout Frequently asked
The one that answers your sharpest pain: the Quarter Plan if you're suffocating under too-many-projects, demand management if the portfolio fills up on its own, benefits tracking if you can't prove your value. We install one at a time, well.
A former transformation director or CIO who has already deployed this process in an organisation comparable to yours. A peer, not a software installer.
No. Teams keep their execution tools (Jira, Asana, Monday). AirSaas installs the steering process on top and connects to them.
It's possible and it has value, but it's thin. The real return comes when you install a process that changes decisions: arbitrate, control demand, prove benefits. We'll tell you frankly.
We look together at whether the process has taken hold: are the reviews happening, are decisions followed, is the data up to date? If not, you leave at no cost.
Which process do you want to install?
Quarter Plan, demand management, benefits tracking: we start from your challenge, not the tool. Let's talk.