IT support for your firm: in-house, outsourced or hybrid? Costs, SLAs and selection criteria
Summary
TLDR
- Choosing a model: in-house support offers a physical presence but comes with fixed costs and the risk of absences; outsourced support provides broad expertise and continuous coverage; the hybrid model pairs an internal point of contact with a specialized partner for infrastructure and security.
- True costs: the financial comparison is not between a gross salary and a vendor's fee, but must use the total annual cost, including payroll charges, training, vacation, sick leave, software licenses and the cost of downtime.
- Essential SLA parameters: a service level agreement must specify guaranteed response and resolution times by criticality level, coverage windows and dedicated support channels.
- GDPR and security: every IT vendor that accesses the firm's data must be formally appointed as a data processor (Art. 28 GDPR) under a written agreement, an essential safeguard that also matters for corporate clients' security questionnaires.
- Protected transition: changing IT management requires full control of administrative credentials, an up-to-date inventory of systems and licenses, and a handover period to prevent any operational disruption.
Index
When a computer freezes an hour before a hearing, or the digital signature stops working on the day of a notarial deed, there is only one question: who responds, and how fast? The choice between in-house IT support, outsourced or hybrid is made well before that moment, and it affects costs, continuity and risk. This guide compares the three models for a professional firm, looking at what to really count in the costs, what an SLA contains and which clauses to check. For the basic definitions, see our articles on help desk and managed IT services; here the goal is to give you the elements you need to decide.
In-house, outsourced, or hybrid IT support: what's the difference?
In-house support assigns IT to an employee, outsourced support to a provider under contract, and hybrid support splits the tasks between the two; for example, an internal point of contact for daily requests and a partner for infrastructure, security and peak workloads. Skills, coverage, costs and responsibilities therefore change.
| Aspect | In-house | Outsourced | Hybrid |
|---|---|---|---|
| Skills | Those of one or a few people | A team with diverse skills (networks, security, cloud) | Internal point of contact plus external specialists |
| Coverage | Limited to working hours and presence; uncovered during vacations and sick leave | Defined by the contract, even with multiple technicians | Internal for day-to-day needs, external for continuity |
| Knowledge of the firm | Very high | Grows over time; depends on the provider | High, thanks to the point of contact |
| Costs | Staff cost, fixed | Monthly fee plus any extras, often variable | Cost of both, but reduced for each |
| Main risk | Dependence on a single person | Dependence on a provider with unclear rules | Overlaps and unclear responsibilities |
| Best for | Firms with highly customized infrastructure and many users | Small and mid-sized firms that want continuity and broad expertise | Larger firms that want an on-site presence and specialist support |
The outsourced model takes different forms depending on the provider, from simple on-call assistance to an ongoing service with monitoring. One example is Lanpartners' IT CONCIERGE®, a remote help desk and monitoring service with a specialist assigned to each client, which aims to spot malfunctions before they cause downtime, as described on the services page.
What does an in-house technician really cost compared to an external partner?
The cost of an in-house technician includes much more than salary: payroll charges, vacation and sick leave to cover, training, tools, licenses and the cost of downtime when they are absent. The cost of an external partner includes the fee, extras and any time the firm spends coordinating them.
| Cost item | In-house technician | External partner |
|---|---|---|
| Salary and payroll costs | Yes, fixed | Included in the fee |
| Vacation and sick leave coverage | Not covered, or must be replaced | Guaranteed by the team, if provided for in the contract |
| Training and updates | Paid by the firm | Paid by the provider |
| Tools (monitoring, remote support, licenses) | Paid by the firm | Often included in the fee, to be verified |
| Specialist skills (security, cloud) | Must be hired or purchased separately | Available in the team or on a project basis |
| Out-of-scope work | Not applicable | To be defined in the contract (extras, emergencies, projects) |
| Cost of downtime | High if the technician is absent | Depends on the SLA |
To compare fairly, calculate the total annual cost of both scenarios and divide it by the hours of coverage actually available. Then add an estimate of the cost of downtime: working hours lost by staff and activities blocked per incident, multiplied by the historical frequency. There are no values that fit every firm, but you need the numbers for your own.
A common mistake is comparing a salary with a fee. A salary is only one part of the cost, while a well-structured fee includes skills, coverage and tools that would otherwise have to be added.
What is an SLA and what parameters does it include?
The SLA is the part of the contract that defines the guaranteed service level. It sets out coverage hours, acknowledgment and resolution times for each priority level, request channels, reporting and the consequences if the level is not met.
| Parameter | What it means | To define in the contract |
|---|---|---|
| Coverage hours | Days and time slots when the service is available | Standard hours, extensions, on-call availability |
| Response time | How quickly a request is picked up | For each priority |
| Resolution time | How quickly an issue is resolved or a workaround is provided | For each priority |
| Priority levels | Classification by urgency and impact | Assignment criteria and who decides |
| Contact channels | Phone, email, portal, chat | Channel for emergencies |
| Reporting | Summary of requests, times, and recurring issues | Frequency and content |
| Penalties and remedies | What happens if the deadlines are not met | Amounts, service credits, limits |
| Exclusions | What falls outside the SLA | After-hours work, unmanaged hardware, external causes |
On its services page, Lanpartners describes the IT CONCIERGE® service and states that the historical average acknowledgment time is under two hours; this is a past performance figure, not a contractual commitment: guaranteed values are defined in the contract, by priority, based on the firm's needs. The same applies to any provider, and we advise being wary of anyone who promises an "immediate response" without clearly specifying what that means and the scope of the intervention.
How do you set priorities in a professional firm?
In a professional firm, the priority of a request depends on what it blocks and when the deadline falls. A failure before a hearing, an electronic filing or a notarial deed has a far greater impact than one the following week. The SLA must be able to tell the two cases apart.
| Priority | Example in a firm | What to ask for in the contract |
|---|---|---|
| Critical | Server or practice management system down; unable to file or sign with a deadline approaching | Acknowledgment within a short, defined time and resolution within tight timeframes, with a dedicated channel |
| High | A professional cannot work; digital signature or PEC not working | Fast acknowledgment, same-day resolution |
| Medium | Slowdowns, network printer, non-blocking issues | Acknowledgment and resolution within standard timeframes |
| Low | Configuration requests, new workstations, improvements | Scheduling by agreement |
For activities closely tied to the process, such as Consolle Avvocato and electronic filing, it is advisable to state explicitly in the contract that issues close to a deadline are handled as a priority. Exact times must be agreed, since the tables show the structure, not the values.
Which contract clauses should you check before signing?
Before signing, check the scope of the service, SLA, limitations of liability, security and data protection, subcontractors, term and exit from the contract. These are the points where most disputes arise, and also the ones corporate clients ask you to verify.
- Scope: what is included in the fee (users, devices, servers, cloud) and what is extra.
- SLA: response times by priority, hours, channels, reporting, penalties and exclusions.
- Limitations of liability: compensation caps, indirect damages and specific exclusions.
- Data processing agreement (Art. 28 GDPR): the provider accesses the firm's data and must be appointed as data processor with written instructions.
- Provider security: measures in place, certifications, management of privileged access to the firm's systems.
- Subcontractors: who else is involved and with what safeguards.
- Continuity: what happens if the provider has an outage or an incident.
- Term and termination: lock-ins, notice periods, exit costs.
- Exit and handover: documentation, credentials, data and configurations returned at the end of the relationship.
These same points often appear in the security questionnaires of corporate clients, which ask the firm how it vets its own vendors. A well-written contract with your IT partner is therefore part of the answer.
When does the hybrid model make sense?
The hybrid model suits firms with enough users to justify an internal point of contact, but that cannot afford all the security, cloud and continuity skills on their own. The internal contact handles daily requests, and the partner covers the rest.
- Internal point of contact: knows the firm's people and workflows, manages the relationship with the provider, collects requests.
- External partner: monitoring, security, updates, projects, coverage during absences.
- Written division of tasks: who does what, who decides, who answers to the professional.
- Shared tools: a single ticketing system and a common inventory, to avoid duplication.
- Periodic review: a meeting at least quarterly to review recurring requests and priorities.
The main risk is overlapping responsibilities: when something doesn't work, the internal contact assumes it's the partner's job and vice versa. The solution is a written list of responsibilities and a single point of contact for emergencies. The article on the IT roadmap shows how to fit the chosen model into a multi-year plan.
What questions should you ask an IT support provider?
Before choosing a provider, it is worth asking a few precise questions: about response times, people, security and exit. The answers, and the way they are given, say far more than a brochure.
| Check | |
|---|---|
| ☐ | What are the acknowledgment and resolution times for each priority, in writing? |
| ☐ | Who steps in: a team or one person? Who covers during absences? |
| ☐ | Is support remote, on-site or both? In which cases and at what cost? |
| ☐ | What is included in the fee and what is extra? |
| ☐ | How is privileged access to the firm's systems managed? |
| ☐ | Is there a security certification (for example Lanpartners' ISO/IEC 27001:2022, whose certificate can be viewed on the website) and what does it cover? |
| ☐ | Which monitoring tools are used and what is reported to the firm? |
| ☐ | How is reporting done and how often? |
| ☐ | What happens at the end of the contract: documentation, credentials, data? |
| ☐ | Are there references from similar firms? |
A reliable provider will also tell you clearly what is not covered by the service. For example, if an answer is ambiguous, ask for it in writing. What is written can be proven; what isn't is left to interpretation, and that's where disputes begin.
How do you switch from one model to another without disruption?
Moving from one model to the other is planned in phases: inventory, documentation, side-by-side support and a gradual switchover. The goal is for your firm not to notice the change, except through better service.
- Inventory: devices, users, licenses, access, vendors, active contracts.
- Documentation: network diagram, securely stored credentials, procedures.
- Definition of roles and SLAs under the new model.
- Overlap period: the two parties work together for a few weeks.
- Phased transition: the least critical activities move first, then the rest.
- Review: after 60-90 days, compare requests, response times and satisfaction against expectations.
Following this structured path lets you make the transition smoothly and without putting your firm's business continuity at risk. Lanpartners is based in Milan and supports law firms, notary firms and accountants through this process, providing IT consulting and support and IT CONCIERGE® services. If you are considering changing your support model, you can contact Lanpartners to review your firm's current situation, starting with what is truly critical for your daily work.
Related articles
- IT CONCIERGE®: the partnership that turns technology into value
- Managed IT services for law and notary firms
- IT help desk: what it is and how it works
- IT Roadmap for law firms
- Consolle Avvocato and the telematic civil process
- Lanpartners services
Frequently asked questions
Is an in-house technician or an external partner better for a firm?
It depends on size and complexity. An external partner offers broader expertise and continuous coverage; an in-house technician knows the firm better but leaves gaps whenever they are away. Many firms choose a mixed model.
What is an SLA in IT support?
It's the part of the contract that defines the service level: coverage hours, response and resolution times by priority, channels, reporting, penalties and exclusions.
What response times is it reasonable to ask for?
There is no one-size-fits-all value: times should be set by priority and agreed based on the firm's needs. What matters is that they are written into the contract, along with the criteria for assigning priorities.
Does the IT provider have to be appointed as a data processor?
Yes, when it accesses the firm's personal data: Art. 28 of the GDPR requires a written agreement with instructions and safeguards. Corporate clients often ask for the same agreement in their security questionnaires.
How do an in-house technician and a support fee compare?
Calculate the total annual cost of both, including payroll charges, coverage for absences, tools, training and the cost of downtime, and divide it by the hours of real coverage. Don't compare a salary with a fee.
Does Lanpartners offer IT support to firms in Milan?
Yes: it is based in Milan and offers professionals IT consulting and support and the IT Concierge service, with help desk and remote monitoring. Response times and service levels are defined in the contract, based on the firm's needs.
