The provider commits to applying the agreed means with due diligence, without guaranteeing the result. The burden of proof lies with the client: it must prove the fault.
Where pylotik fits The levels of commitment.
What makes an organization a fit for pylotik is neither its size, nor its sector (industry, construction, engineering, IT, government or public service), nor its legal status: it is its responsibility for delivery and its commitment mode. Two conditions are enough: your organization is responsible for carrying out a service, a project, a contract or an intervention, and it has commitments to keep towards a client (a result, a deliverable, a milestone, a deadline, an intervention), whether they are written into the contract or simply felt to be due. The client can be another company, or another team in yours: pylotik also works inside a single company. pylotik does not change the level of commitment you have chosen: it makes manageable, traceable and enforceable what really binds the relationship, the contractual commitment as well as the perceived one.
The legal basis
Means, result, and what the law does not name
"Obligation of means" and "obligation of result" (obligation de moyens and obligation de résultat in French law) are not types of contract: they are the two legal qualifications that run through every mode. A single contract often mixes both, clause by clause: a maintenance contract is a result obligation on service levels and a means obligation on upstream advice.
The provider commits to a defined result: a compliant deliverable, a deadline met, a quantified service level. Failure to deliver raises a presumption of fault; the provider is released only by force majeure or by the client's own act.
The third dimension, which the law does not name. Announced dates, milestones mentioned in meetings, roadmaps presented: the client remembers them as commitments, whatever the qualification of the contract.
It cannot be argued. It has to be managed.
Case law also recognizes reinforced means obligations and attenuated result obligations: most real contracts are mixed, clause by clause.
Without a trace, the perceived commitment becomes a reproach
With dated governance, it becomes a trade-off. Two cross-cutting obligations confirm it, whatever the mode: the provider's duty to advise, strictly assessed, and the client's duty to cooperate, whose breach releases the provider. In a dispute, everything turns on written, dated proof of who knew what, who decided what, and when. That is exactly what governance traced through immutable time-stamped records produces.
The scale
From consulting to managed services: where pylotik fits
The modes are ranked from the production risk carried by the client (top) to the risk carried by the supplier (bottom), and grouped into three blocks. The target of pylotik is the central block: where supplier-led steering and project-type commitments add up.
| Mode | Obligation | Client exposure | Supplier exposure | Type of dispute | pylotik position | Type of tool |
|---|---|---|---|---|---|---|
| A Steering stays with the clientThe client directs the service itself, with no project trajectory carried by the supplier, or the assignment is too short for a routine to take hold. Out of scope. | ||||||
| Consulting / audit · production risk: client | means | duty to advise | out of scope | ERP | ||
| Time and materials / technical assistance · production risk: client | means | requalification | out of scope | |||
| Capped time and materials · production risk: client | capped means | cap | borderline | |||
| B The pylotik targetThe central, contiguous block: supplier-led steering and project-type commitments (milestones, deliverables, deadlines). Fixed price is its economic center of gravity. | ||||||
| Dedicated team · production risk: shared | means + perceived dates | implicit commitment | core target |  | ||
| Service center · production risk: shared | mixed + perceived dates | work-unit measurement, penalties | core target | |||
| Agile fixed price · production risk: shared | hybrid | scope, definition of done | core target | |||
| Classic fixed price · production risk: supplier | result | acceptance, change orders | core target | |||
| Maintenance contract · production risk: supplier | result (service levels) + regulatory deadlines | penalties, compliance, reversibility | core target | |||
| C Pure operationsContinuous availability commitments, with no dated trajectory of deliverables, handled as they come by an incident tool (ITSM). Out of scope; the projects that follow from them (remediation, migrations) fall under the project modes, and the planned interventions of a steered maintenance contract fall under the central block. | ||||||
| MCO / MCS (operational and security maintenance) · production risk: supplier | result (service levels) | availability, security | out of scope | incident ticketing ITSM | ||
| Managed services · production risk: supplier | result (service levels) | penalties, reversibility | out of scope | |||
The central block is the ground of pylotik: the supplier steers the service there, and project-type commitments matter (milestones, deliverables, deadlines, interventions). Consulting and time and materials, where the client steers itself, as well as pure operations (MCO, managed services), follow other rules. A maintenance contract, on the other hand, is a core target: pylotik holds its volume, its catalogue, its committee and its interventions, validated by the client. See maintenance contract management. Each of these modes can be replayed internally, between two teams of the same company: see internal clients and suppliers.
Along the gradient, the risk changes carrier, never nature. Scope drift, financial drift, human drift and date drift exist everywhere. What changes is who pays for it.
The stronger the commitment, contractual or perceived, the more each week without commitment steering costs (margin, penalties, relationship), and the more decisive dated proof becomes.
The perceived commitment overflows the contractual one: the client remembers the dates announced, not the qualification of the contract. When the relationship moves away from the contract, only commitment steering still protects it.
Product and associated service
Selling a product, and taking on its installation, its training, its maintenance.
A company that sells equipment, products or software is not out of scope because it sells a product. As soon as it takes responsibility for delivering the service that goes with it (installation, commissioning, training, maintenance, after-sales service), it has commitments to keep towards its client, and that is the part pylotik manages.
An equipment manufacturer
It sells equipment with its installation, its commissioning, user training and a maintenance contract. Installation is a project, with its milestones and committees; maintenance is a contract, with its period, volume and catalogue. See project management for industry.
A technical distributor
It delivers, installs and provides after-sales service at its clients. Installations are tracked as projects, the after-sales contract is managed like a maintenance contract, and interventions are scheduled then validated by the client, with the Interventions module, from the Business tier.
What stays in your tools
Orders, stock, production and legal invoicing stay in your ERP and MES, the equipment base in your CMMS. pylotik manages the commitment made to the client and the teams that keep it. See the enterprise software landscape.
A managed maintenance contract
A period, a volume in days, a catalogue, interventions scheduled and validated by the client (Interventions module), a committee, a history. See maintenance contract management.
Support handled incident by incident
A flow of requests and incidents to resolve within deadlines, with no dated trajectory of deliverables: that is the job of an incident ticketing or ITSM tool. See project ticketing or ITSM.
A company that only sells, without carrying out, installing or maintaining, has no delivery commitment to manage: it is not the ground of pylotik.
Internally too
One company is enough: internal clients and suppliers.
The ground of pylotik does not stop at the company's borders. As soon as one team delivers projects for another, there is a supplier and a client, and dates that one considers owed to the other.
Internal suppliers
An IT department, an in-house design office, a works or maintenance department, a shared service center, a product team: teams whose job is to deliver for others, with their milestones, their committees and their workload.
Internal clients
Business units, subsidiaries, sites, other teams: those who order, expect a date and judge the result. They follow their projects and approve what is submitted to them, from their account in your organization.
The same mechanics, without a contract
No purchase order and no penalty, but dates announced in committee that become owed. Internally, the perceived commitment alone holds the relationship together, which is why making it explicit matters. Same engine, same rights, same history as with an external client.
The same team can also be the supplier of its business units and the client of an external provider. See internal project management and project management for IT departments.
Two separate questions
Billing mode and steering mode are not the same thing.
"Fixed price" or "time and materials" says how the service is billed. What places a service in the ground of pylotik is who steers it, and whether project-type dates matter.
Steered by the supplier, whatever the billing mode
A project or a maintenance contract that the supplier frames, with milestones, deliverables and committees, whether it is billed at a fixed price or on time and materials. pylotik supports both modes: a schedule tied to milestones for fixed price, a monthly schedule calculated on the days produced for time and materials. See project financial tracking.
Steered by the client, or with no trajectory
Pure time and materials and technical assistance, where the client frames people itself and buys days with no project trajectory carried by the supplier; continuous operations, handled incident by incident. It is not the time spent that rules them out, it is the absence of steering on the supplier's side.
Five steering needs
What runs through every mode in scope
The same five needs come back from one mode to the next, at varying intensities. Together they outline what operational commitment management must produce.
- Continuous financial visibility Drift is paid for in net margin and in the relationship: under-billing and non-billable overruns must show from the first month, before the billing milestones, not after. Maximum intensity on fixed price.
- Trading off dates The dates the client considers owed must be made explicit, shared and traded off before they turn into implicit commitments that nobody set. Maximum intensity on dedicated teams and service centers.
- Dated proof Acceptance, service levels, regulatory deadlines, change orders and reversibility are decided on proof: immutable weekly time-stamped records, historized decisions, frozen minutes. Maximum intensity on fixed price and maintenance.
- Committee work without the effort Project committee, steering committee, monthly review: costly to produce by hand, they must be prepared natively from the structured history. Maximum intensity on service centers and maintenance contracts.
- Built-in human signals A team's workload and strain often come before the drift of the project. People must be able to speak up and be heard, within the health of the project rather than in a separate tool, so that the gap becomes visible and gets dealt with. Maximum intensity on dedicated teams and recurring commitments.
Vocabulary notes
What is not a level of commitment
Four notions come up often in calls for tenders and blur the picture. None is a commitment mode: they are vehicles, delivery models or purchasing frameworks, which combine with the modes above.
- AMOA Client-side project assistance (assistance à maîtrise d'ouvrage): time and materials on the client's side, as a means obligation with a strong duty to advise. It is not a mode of the delivery supplier; AMOA is, on the contrary, a natural user of pylotik, on the client side.
- Framework agreement and purchase orders A contractual vehicle, not a level of commitment. A framework can carry time and materials as well as fixed price; each purchase order sets the mode.
- Offshore, nearshore, BOT Delivery and location models, not levels of commitment. They combine with the modes above.
- Public procurement A purchasing framework, not a mode. The French CCAG-TIC (the standard terms for IT public contracts) mostly organizes result obligations (fixed price, tranches, acceptance of operability and of regular service); pylotik natively handles public-procurement milestone models.
Frequently asked questions
What we are asked about the ground of pylotik.
Can a company that sells products and associated services use pylotik?
Yes, for the delivery part. If you install, commission, train or maintain what you sell, and you have commitments to keep towards the client, pylotik manages those projects and contracts. Selling the product, stock and production stay in your tools. A company that only sells is not within the ground.
Can a mixed company use pylotik for only some of its activities?
Yes. An organization where part of the business is pure staff augmentation, or continuous operations handled incident by incident, can use pylotik on its projects and commitment-based contracts, without equipping the rest. A managed maintenance contract, with its scheduled interventions, is within the ground; support handled incident by incident belongs to an incident ticketing or ITSM tool.
Which commitment mode
are you in?
We start from your real contracts and routines, not from a generic demonstration, to place where operational commitment management changes something for you. pylotik is used without a consulting engagement: see the firm and the product.
To go further: what drift really costs, and where your data lives.