How much does IT support cost in Lithuania?
The cost of IT support depends on the number of users and servers, how many offices you have, the service hours you need, your SLA and your security requirements. There is no universal price list – two companies of the same size can pay very different amounts. This guide explains how the price is built, what a good contract should include and how to compare proposals.
What drives the price
| Factor | Why it matters |
|---|---|
| Users and devices | Every computer and phone needs maintenance, updates and support. |
| Servers and systems | Servers, business applications and databases need more senior skills. |
| Offices and sites | More locations mean more network equipment and on-site work. |
| Service hours | Business hours, extended hours or 24/7 need different resources. |
| SLA | Shorter response and resolution times mean more reserved capacity. |
| Security and compliance | SIEM, NIS2 or customer security requirements add work and tools. |
| What you already have | Your own licences, backup or protection reduce the price. |
Why two companies of the same size pay differently
Picture two companies with 25 employees each. The first keeps everything in Microsoft 365, has no servers, one office and works business hours. It mainly needs user support, endpoint protection and patching.
The second runs three servers with an ERP system, has two offices, works weekends, and its customers require NIS2 supplier compliance. It needs server management, extended hours, a stricter SLA and extra security. Same headcount – very different scope and responsibility.
That’s why an honest proposal always starts with an assessment of your environment, not a price per computer.
Pricing models
| Model | How it’s charged | When it fits |
|---|---|---|
| On demand (time & material) | Time actually spent, under an agreed statement of work | Occasional or one-off work; no SLA |
| Monthly fee | Based on the devices, users and systems in scope | Ongoing care with SLA and monitoring |
| Hybrid | Monthly fee + projects separately | When a migration or larger change is coming |
What a good IT support contract should include
Whatever the price, a reliable contract should clearly state:
- every request logged in one system (ServiceDesk), so you can see what is done and when;
- proactive monitoring (RMM) that catches problems before they stop your work;
- scheduled operating-system and application updates;
- backup monitoring and periodic restore testing;
- security basics: endpoint protection, multi-factor authentication (MFA), vulnerability management;
- an assigned responsible specialist and a monthly report;
- a written SLA: response and resolution times and service hours.
Hidden costs worth asking about
The lowest monthly price doesn’t always mean the lowest bill at year end. Ask your provider:
- Are office visits included, or charged separately?
- What does out-of-hours work cost?
- Are onboarding and offboarding included?
- How are projects – migrations, deployments, a new office – charged?
- Will you get a monthly report on what was done?
- What happens if you end the contract – do you get the documentation and admin access?
How to compare proposals
| Question | Why it matters |
|---|---|
| Is the SLA written into the contract? | Verbal promises bind nobody; response and resolution times both matter. |
| What are the service hours? | A cheaper proposal may cover business hours only. |
| What is included, and what is extra? | Compare the same scope, not just the price. |
| Are security measures included? | MFA, protection and backups shouldn’t be “extras”. |
| What does reporting look like? | Without reports it’s hard to see what you pay for. |
| What are the exit terms? | Long lock-ins and no access handover are a risk for you. |
How to get an accurate proposal
The more you share, the more accurate the proposal. Have ready:
- the number of workstations, users and servers;
- the systems you use (e.g. Microsoft 365, ERP, accounting software);
- your list of offices and sites;
- what matters most – speed, security or cost;
- what you already have: licences, backup or protection.
How we build our own proposals – ways to work with us, typical scope and an example SLA – is explained on IThink pricing.
Frequently asked questions
Why don’t you publish prices?
Every client is unique: you may not need some services, or you may already have them. We select the components case by case, so we can’t quote a standard price. We want to offer you only what you need, not what happens to be in a package. You’ll get a written proposal by the next business day.
Can I order just a specific task?
Yes. We can build your service plan from individual components, and we also take on one-off tasks on demand, on a time-and-material basis under an agreed statement of work (SOW).
Does an SLA apply to on-demand work?
No. On-demand work and one-off dispatches without an agreement are done on a best-effort basis. An SLA applies when you have a service agreement, and we agree its terms (response and resolution times, service hours) with each client.
Is the cheapest proposal a bad one?
Not necessarily, but it usually covers less: shorter hours, no monitoring or no security measures. Compare scope and SLA, not just price.
Get a proposal for your company
We don’t charge for what you already have. You’ll get a proposal by the next business day.
