The first source of added value is not creating new value: it is ceasing to destroy it. The effort is smaller (projects already won, clients already acquired, teams already in place), the impact on clients is better, and this work runs alongside the search for growth, without competing with it.
"Value" is the word product committees use most. Roadmaps, quarterly objectives, portfolio trade-offs, sales pitches: everything is expressed in added value. We measure what we add, present what we add, applaud what we add.
The value of a services organization is not the sum of what it adds: it is the difference between what it adds and what it destroys along the way. A team can deliver a very useful feature and, in the same quarter, destroy more value than it produced: through a margin that erodes, a client relationship that strains, an employee who leaves.
As long as only the first term is measured, the organization steers half an equation and is surprised by the result.
Vocabulary is not a matter of style, it is a management instrument. An organization with no word for what it loses can neither measure it, nor put it on an agenda, nor assign it to someone. The subject does not exist, so it is not handled.
Putting the term lost value next to added value turns an accepted backdrop into something to steer: something that can be dated, quantified, assigned and corrected. It is the first step, and it costs nothing.
If the loss were visible, it would be dealt with. It is not, for three reasons.
The first act of pylotik is therefore an act of revelation: turning an accepted backdrop into a signal that can be followed, dated and corrected.
Six reference studies draw the same reality from different angles. Taken together, they do not say that projects are hard: they say that destroying value is the statistical norm.
The most interesting PMI figure is not the waste rate, it is its dispersion: organizations mature in their steering practices waste up to twenty-eight times less than the others. Twenty-eight times. With comparable technical skill, in the same markets, with the same production tools.
A team built in three years, a company that doubled its headcount in two financial years, a service center set up for one contract: these organizations do their job very well, but they have not yet had time to build the steering maturity that goes with it. This is not a flaw, it is a stage.
It comes neither from a seminar, nor from a posted charter, nor from a framework filed in a binder. Coaching produces a real leap, then the effect fades as soon as it stops, for lack of daily tooling that holds the framework when no one is looking anymore.
A cycle that comes back, meetings that produce a trace, a review that prepares itself because the data is already there. The organization does not follow a method: it practices it, week after week, and discovers after a few months that it has become mature without having taken any training.
It is not a single hole, it is a self-sustaining loop, and each link feeds the next. That is why attacking a single symptom is never enough.
And the loop starts again, a notch lower. The classic mistake is to treat profitability as a CFO topic and engagement as an HR topic, in two tools and two meetings. The spiral shows they are the same problem: a slipping margin puts the team under pressure, a team under pressure degrades the margin. Bringing them together on one data set is the only way to see the circle form, and therefore to be able to reverse it.
Loss is not a fatality of the trade. It is a steering gap.
That is what makes it tractable: a gap can be measured, closed and held. Two questions remain, and they are those of the next two sections: where exactly does it leak, and how much is recovered.
These leaks are not sector-specific: they come from the fixed-price contract mode. They are found identically in industry, construction, an engineering firm, a public administration, an agency, a software publisher or an IT department.
| The leak | The mechanism | What pylotik changes |
|---|---|---|
| Scope | Every small addition not turned into a contract amendment chips away at the margin without leaving a trace. When the supplier finally asks for an amendment, the client contests it: the one-off favor has become the tacit norm. | Every request becomes a dated trace; the amendment relies on the gap observed, no longer on a discussion from memory. |
| The theater committee | A slide prepared over two days, a one-hour committee, minutes never formally approved. Three years later, there are three versions and nobody knows which one is authoritative. | The deck is generated from live data, the minutes are frozen on the date of the committee and approved through a client workflow. Preparation time drops accordingly: roughly divided by four, according to our modeling. |
| Dead actions | Ten to twenty actions stated orally at each committee. Three weeks later, nobody knows who was supposed to do what. One-sided reporting creates an illusion of progress. | The requester, not the assignee, closes the action, and an action running late on the client side becomes as traceable as on the supplier side. |
| Invisible teams | An employee resigns and the whole team says "we saw nothing coming". The manager may even underestimate the signals, out of optimism or for fear of raising an alarm about their own scope. | Cross double reporting, what the manager observes and what the employee lives, reveals the gaps. HR goes from late arbiter to sentinel. |
| Late margin | The drift is detected at invoicing, when the client refuses to pay. This is not a flaw of method, it is a missing link between the operational view and the financial view. | Margin is calculated continuously, as soon as production is entered, not at closing. |
| Black boxes | A subcontracted work package whose only reporting is a monthly email. Everyone cultivates their own truth, and they meet at the moment of conflict, that is, too late. | Commitment steering applies in both directions of the contractual link, subcontracting included. |
| Shadow IT | Without a sovereign tool end to end, each team deploys its own Drive, its own Trello, its own Notion. Data lives everywhere and nowhere, often on accounts of people who left long ago. | Project data enters a sovereign, governed and auditable framework. See the security page. |
Each leak, taken alone, seems manageable. It is their accumulation that tips profitability, which is why pylotik does not treat a leak in isolation, but the whole chain.
We do not sell created value: we give back the value the organization loses, and knows it loses.
| Profile | Revenue assumption | Value recovered / year | Per employee |
|---|---|---|---|
| Micro-business · 10 people | 1 to 1.5 M€ | 120 to 165 K€ | ≈ 14 K€ |
| SME · 30 people | 4 to 6 M€ | 545 to 565 K€ | ≈ 18 K€ |
| SME · 80 people | 12 to 15 M€ | 1.68 to 1.72 M€ | ≈ 21 K€ |
| Mid-sized company · 250 people | 50 to 80 M€ | 4.15 to 4.25 M€ | ≈ 17 K€ |
Efficiency peaks for the mid-sized SME, where complexity is already real but the structure is still agile.
Compared with what it helps recover, the subscription is under 5% of that value, in every profile. See the pricing grid.
| Profile | Composition | Subscription excl. VAT / year | Value recovered / year | Share of the value |
|---|---|---|---|---|
| Micro-business · 10 people | 3 Pilots · 7 Contributors | €2,100 | ≈ 142 K€ | 1.5% |
| SME · 30 people | 8 Pilots · 22 Contributors | €10,032 | ≈ 555 K€ | 1.8% |
| SME · 80 people | 18 Pilots · 62 Contributors | €25,272 | ≈ 1,698 K€ | 1.5% |
| Mid-sized company · 250 people | 50 Pilots · 200 Contributors | €129,000 | ≈ 4,200 K€ | 3.1% |
Every figure attributed to a third-party study is listed below with its source. The economic assumptions specific to pylotik are internal models, flagged as such, not audited.
| Figure | Source |
|---|---|
| 9 to 11% of every project euro wasted; mature organizations 28× less | PMI, Pulse of the Profession 2017-2021 |
| Scope creep on 52% of projects | PMI, Scope Patrol |
| 31% successful, 50% delivered late, over budget or below the expected result, 19% abandoned or never used | The Standish Group, CHAOS 2020 |
| +45% budget, −56% value delivered; 17% threaten the company's existence | McKinsey & University of Oxford (2012), 5,400 projects |
| $2.41 trillion of poor software quality cost (US, 2022) | CISQ, Cost of Poor Software Quality 2022 |
| Disengagement ≈ 9% of world GDP; 70% of engagement comes down to the manager | Gallup, State of the Global Workplace 2026 |
| Replacing an employee: 50 to 150% of annual salary | INSEE / Cegos; Gallup (0.5 to 2 times) |
| +5% retention = +25 to +95% profit | F. Reichheld (Bain), via Harvard Business Review |
| Cost of a management controller: 35 to 45 K€ a year fully loaded | Apec / Robert Walters |
Method note. The PMI figures come from successive editions of the Pulse of the Profession; they vary slightly from one year to the next and are quoted here as orders of magnitude.
We start from your fixed-price portfolio and your current rituals, not from a generic demo.