Freelancer or IT services company for business application maintenance?
Compare support arrangements through required capacity, planned backup and the uses to cover.
Start with the coverage required
An IT services company, known as an ESN in France, can organise a team; a freelancer generally works in their own name. In either case, does your activity require several skills simultaneously or intervention during absences? That question helps choose a maintenance arrangement. The provider's status alone does not tell you what backup is actually available.
The following comparison is a proposed decision framework, without vendor ratings. A freelancer may suit a controlled scope and hours compatible with their agreed availability. A team may be necessary when several interventions must progress in parallel or continuity exceeds what one person can provide.
Compare explicit situations
- Internal application used during the day, requests prioritised weekly: consider a direct relationship with an identified specialist, checking skills and reserved capacity.
- Application open continuously, with outages blocking sales: request an organisation with effective backup and an escalation procedure; check the proposed commitments and their cost.
- Interface redesign and Java changes simultaneously, with a tight schedule: plan for several skills and a person responsible for coordination.
- Poorly documented application: compare assessment and knowledge-transfer arrangements before comparing the support price.
An IT services company does not necessarily assign several people to the contract. A freelancer can work with agreed backup. Ask for the names or roles actually available, the replacement mechanism and conditions for accessing context. Avoid inferring those capabilities from the size displayed on a website.
Ask candidates the same questions
- Who reads a report, during which hours, and how is its handling confirmed?
- What happens during a planned absence or when the usual person is unavailable?
- Who knows the deployment process, and how can someone else take over the procedure?
- How are requests estimated, prioritised and accepted? Who decides when capacity is exhausted?
- Who owns the technical accounts, and which information is handed over at the end?
Ask for an anonymised report example or fictional template instead of a vague promise. A useful response also states exclusions: user workstation support, hosting or external services may belong to other contacts.
Record trade-offs before starting
Service objectives make expectations measurable. They must connect to the hours and resources actually offered. On-call coverage requires organised backup; it cannot be inferred implicitly from a maintenance contract.
To compare proposals, give candidates the same scenario: an export is blocked and the usual specialist is absent. Who receives the alert, what can they check, and who informs the business? If answers remain vague, ask for clarification before selecting the provider. For focused support, direct contact can simplify communication; when expected coverage exceeds that scope, the team and its coordination must be evaluated explicitly.