Start
4-hour response
From €590 per month + VAT, up to 10 users, Monday to Friday 9:00-18:00. Made for a law practice, an architecture studio or a small advisory firm working in the cloud with no server of its own.
Ask about StartPlenty of IT maintenance contracts promise attention “as soon as possible”. That is not an SLA; it is a phrase nobody can test. At Apply every plan carries a specific response deadline, defined hours and a monthly report built from the very timestamps you see on your own tickets. Below are the figures for all three plans and the rules used to measure them.
One team and one toolset deliver all three plans. The differences lie in response deadline, what gets watched and cover outside office hours. Prices exclude VAT, charged on top at 21 %.
Start
4-hour response
From €590 per month + VAT, up to 10 users, Monday to Friday 9:00-18:00. Made for a law practice, an architecture studio or a small advisory firm working in the cloud with no server of its own.
Ask about StartBusiness
1-hour response
€1,290 per month + VAT, Monday to Friday 9:00-18:00. Brings in server and Microsoft 365 administration, backup verification and a monthly meeting to go over the report.
Work out the costPremium
15-minute response
From €2,490 per month + VAT. Dedicated engineers familiar with your systems, one named contact and a 24/7 on-call line for critical incidents, its number supplied in the contract.
Speak to usYour plan's deadline applies to the first response. The order in which work is tackled comes from priority, and priority comes from business impact, never from whose name is on the email.
Three things stop the SLA clock, and only three. The time falls outside covered hours; we are waiting on an answer or a test from you; or the case rests with a third party such as the fibre provider, the ERP vendor or Redsys. Every pause is noted in the ticket with its reason and time, and the monthly report splits the time that was ours from the time that was not.
You do not need a consultant for this. Half an hour with a spreadsheet gets you to a sound answer, which is then checked against real data.
The three or four systems without which revenue stops: ERP, shop, email, the booking or payroll software.
Lost sales, paid staff hours with nothing to do, appointments to rebook. A rough estimate is fine.
If two or three hours of outage a year cost more than the gap between two plans, the higher plan pays for itself. If not, stay with the lower one.
The first reports reveal how many critical requests arose and how long they took. If speed is short or surplus, the plan is adjusted.
A message from an engineer who has already looked into your case: what they understand, the priority assigned and the next step. The automatic acknowledgement carrying the ticket number does not qualify. Resolution is a separate matter: it ends when your team can work again, and because it sometimes rests with outside parties, it is set as a target per priority rather than a firm commitment.
Thursday has an hour and a half of covered time left; the other two and a half hours run from 9:00 on Friday, so the response is due by 11:30 on Friday. On Business the same message would be answered before 17:30 that Thursday. If such a wait is not acceptable for certain systems, the sensible options are a higher plan or 24/7 IT support for those systems only.
Covered hours are Monday to Friday on working days. Which holiday calendar applies, national, regional or local as well, is written into the contract, since a company in Barcelona and one in Las Palmas keep different days off. On Premium the on-call line for critical incidents stays open on those days too.
You will spot it in the report before we mention it: each miss appears with a written explanation and the step taken to stop it recurring. Contractual consequences of a miss are settled when you sign, so nobody has to negotiate them in the heat of an outage.
Yes, by addendum on a date we agree. A PrestaShop store could step up to Premium from November to January to cover Black Friday, Christmas and the sales, then return to Business. Stepping down works too: if the reports show critical incidents are rare, we will raise it with you ourselves.
Tell us which systems cannot stop and roughly what an hour without them would cost. We will suggest the plan that fits, and not sell you speed you will never use.
Your request is with us
Expect an answer within one working day. A reported fault that has halted your team is handled first.
No match found. Try another spelling, or go with the closest provincial capital: every job is done remotely, so the location makes no difference to what we deliver anywhere in Spain.