Pricing
Two ways of working together
Either you pay for what you consume, or you smooth the budget over a monthly package based on the units under management. Both models cover the same technical skills: what changes is budget predictability and the level of commitment on response times.
Model 1
Time and materials
You pay for the time actually spent, per assignment. No subscription, no minimum term.
How it works
- Time is counted per intervention, based on a detailed record
- Every intervention is traced: date, duration, nature of the work, outcome
- Remote and on-site work follow the same counting logic
- An estimate is provided before any work exceeding an agreed volume
- No tacit renewal: the relationship ends when the assignment ends
Relevant when
- You have an in-house IT team and need occasional reinforcement
- The need is a bounded project: audit, migration, deployment
- Incident volume is low or hard to anticipate
- You want to test the collaboration before committing further
Response times
Handled according to schedule availability, with no contractual response commitment. Urgent matters are taken into account but come after clients on a package contract.
Model 2
Package contract
A fixed monthly amount, calculated on the number of units actually managed. The budget is known in advance, with no end-of-month surprises.
Calculation basis
- Per user. Accounts, mailboxes, access and people support
- Per workstation. Desktops and laptops: updates, security, monitoring, troubleshooting
- Per server. Physical servers and virtual machines: maintenance, monitoring, backups, patching
The scope is inventoried at the start and adjusted as it evolves: a decommissioned machine leaves the package, a new one joins it.
What the package covers
- Continuous monitoring of items under contract
- Preventive maintenance and patch application
- Incident handling within the covered scope
- Backup follow-up and restore testing
- Up-to-date documentation of the managed infrastructure
Response times
Contractual commitment on response times, with priority over out-of-contract requests. Service levels are defined in writing at signature, based on the declared criticality of each item.
What stays outside the package
For transparency, here is what is never included in a monthly contract and is always quoted separately.
Projects
Hypervisor migration, new infrastructure deployment, network redesign, mail platform change. These are scoped and quoted independently of the maintenance package.
Hardware and licensing
Servers, workstations, network equipment, Microsoft or third-party licences. These purchases remain yours, with or without intermediation depending on your preference.
Major incidents
Rebuild after a major incident, response to a security compromise, data recovery. The package covers prevention and follow-up, not disaster remediation.
How to choose
| Criterion | Time and materials | Package |
|---|---|---|
| Budget | Variable, follows actual consumption | Fixed and predictable every month |
| Commitment | None, assignment by assignment | Term agreed in the contract |
| Response times | Subject to availability, no guarantee | Written commitment, priority handling |
| Monitoring | On request only | Continuous within the covered scope |
| Preventive maintenance | Billed per intervention | Included |
| Suited to | Bounded projects, occasional reinforcement | An estate to maintain over time |
Both models can coexist: an estate maintained under package, and one-off projects billed on a time and materials basis. That is in fact the most common combination.
Get a costed proposal
Pricing depends on the number of users, workstations and servers, and on the expected service level. Describe your estate and your priorities: you will receive a detailed proposal, with no obligation.
Request a quote