
Co-managed IT vs managed IT vs break-fix: which model fits your company
Compare co-managed IT, fully managed IT and break-fix support: who does what, what drives cost and the questions to answer before you choose a model.
Managed IT services
Bring everyday support, maintenance and longer-term improvements into one agreed arrangement, with help available in English and Spanish.

Managed IT services turn the scattered tasks of keeping technology running into one agreed arrangement: who users contact when something breaks, who applies updates, who checks that backups work and who decides when something needs to change. For a small or midsize company this usually replaces a mixture of favours, ad-hoc suppliers and one overstretched colleague with a defined way of working. We offer managed IT services for organisations with people in Europe, with support in English and Spanish.
A managed service provider (MSP) is an external team that takes responsibility for defined IT work under one agreed arrangement. In our managed IT services, that arrangement covers everyday IT support for your team, routine maintenance and updates, monitoring and backup checks where they are in scope, and regular reporting. Scope, responsibilities and any service commitments are agreed in writing for your organisation, not assumed in advance, and support is available in English and Spanish. Because scope is agreed per organisation, our guide to managed IT pricing models explains how providers charge and what drives cost.
Informal IT support tends to work until the day it does not. A person leaves, a supplier is slow to respond, a laptop fails before a client presentation, or a security update is postponed for months because nobody owns it. In each case the problem was not technical complexity but unclear responsibility.
A managed arrangement makes responsibilities explicit. It describes which systems are covered, how requests are raised and prioritised, which routine maintenance is carried out and what is reported back to you. For businesses operating in several countries, it also gives every office the same route for help, in a language the team is comfortable with, rather than a different supplier and process in each location.
Colleagues can raise questions and problems about their laptops, accounts, email, printers and business applications through a single route. Requests are logged, handled and followed up so that recurring issues are visible and not repeatedly fixed in isolation. Support conversations are available in English and Spanish, from Monday to Friday, 09:00–18:00 CET/CEST. We do not provide support outside those hours. If you are unsure whether business-hours cover is enough, read 24/7 IT support versus business hours. To compare providers on request intake, escalation and reporting, see our help desk support guide.
Many incidents come from systems that were never updated. We agree how operating systems, applications and devices are kept up to date, how changes are scheduled around your working hours and how exceptions are handled when a business application cannot be updated immediately. Servers on premises can be managed per project: patching, planned replacement and monitoring, in published hours. See the on-site, cloud or hybrid server guide.
Where it is in scope, we help keep an eye on the health of key systems and check that backups run and can be restored. What is monitored and how problems are escalated is agreed upfront, so there are no false assumptions about what is being watched. To plan for a major failure, see our disaster recovery plan guide for small businesses.
New starters need accounts, equipment and access; leavers need them removed promptly. We document these steps and carry them out in the agreed way. If your team uses Microsoft 365, user and licence administration can be part of the same arrangement. Our IT onboarding and offboarding checklist lists the steps worth agreeing.
You receive regular, readable summaries of what has been requested and done, what keeps recurring and what deserves a project rather than another quick fix. Periodic reviews give you a chance to adjust scope and priorities as the business changes.
Every client receives a personalised service. What does not change is the start: a standard protocol of initial discovery and documentation, which keeps the essentials the same for everyone so that nothing important is skipped, while everything built on it is shaped around your size, sites, tools and in-house IT.
We record people, sites, devices, applications and suppliers, and we set up the support channels. People come first, because every other record is only useful if it says who relies on it. Things that tend to surface: an application one colleague depends on and nobody else understands, a supplier whose contact nobody can locate, shared accounts, and devices on no list. The biggest gap is knowledge that exists only in one person’s head, which this step moves onto paper.
A remote management tool is installed on the devices, which gives an inventory and a status that come from the devices themselves, not from a list that was correct when it was written. Lists drift as people change laptops and leave, so the inventory taken from the devices is the better basis for planning updates and replacements.
When another provider is leaving, we receive their documentation, credentials and the state of the systems, with a handover record. It works best early, while the outgoing provider is still engaged. Worth asking: in whose name each account, licence and registration is held, and what is running that nobody has written down.
We begin with support for users and move to maintenance and backups afterwards, so that not everything changes at once. If everything changes in the same week, a problem is hard to trace to its cause; in phases, each layer settles before the next is added.
The main deliverable is the documentation of your environment, and it belongs to you. It is an up-to-date description of four things: systems, accounts, devices and suppliers. The systems entry says what each system is for and who depends on it; the accounts entry says who holds each account, and not the passwords, which belong in a password manager and not in a document; the devices entry follows from the inventory; the suppliers entry says who provides what. See a sample outline of that documentation (illustrative example).
Ownership matters: you can change provider, or bring IT in-house, without losing what is known about your environment. The description is kept up to date as the environment changes, because documentation that was accurate once is a common source of wrong decisions. A simple test, offered as an illustration: could someone new find out who holds the domain registration without asking the person who wrote the document? Our guide to what to keep, where, and who owns IT documentation goes through the full set.
We describe tools by category, not by brand, because the categories are what you need to understand when deciding scope. Which of them are in scope is agreed per organisation.
One tool covers patch management, inventory and alerts through the agent installed on each device. Patching is a scheduling problem more than a technical one: updates are planned around your working hours, with exceptions agreed for applications that cannot be updated at once. Alerts are only as useful as the agreement about who acts on them and when. Because there is no support outside our published hours, an alert raised in the evening waits until the next working morning.
A central console applies settings and updates to laptops and phones in the same way. Consistency is the point: a fleet in which every device is slightly different is harder to support and harder to secure.
Standard protection on devices and for email, used as a baseline. It addresses common threats; it is a starting layer, not a complete security programme.
Credentials need a managed place instead of spreadsheets and messages, and multi-factor authentication is the basic control on accounts. Our Microsoft 365 security baseline checklist lists the account settings worth reviewing.
There is no support outside our published hours, Monday to Friday, 09:00–18:00 CET/CEST. Plan around that in advance: decide who in your organisation acts when something fails in the evening or at a weekend, and what can wait until the next working morning. If your business depends on cover outside those hours, say so at the start. Co-managed IT, run jointly with your own IT team, is one way of dividing the work; our guide to co-managed IT, managed IT and break-fix explains the differences.
This service suits companies that depend on IT every day but do not want, or cannot justify, a full internal team. Common situations include:
If your priority is security rather than day-to-day support, start with cybersecurity, which can later be combined with an ongoing arrangement.
If you would rather hand over a defined block of IT work than a whole support arrangement, compare it with IT outsourcing. If you are weighing outsourcing against an internal team, read how to decide between outsourcing and in-house IT.
Remote support across Europe: IT support in Spain, the United Kingdom, Germany, Italy, the Netherlands, France and Portugal. On-site work is confirmed per project.
We do not make assumptions about response times, coverage or availability: any service commitments are discussed and agreed in writing for your organisation. This keeps the arrangement realistic for both sides and avoids surprises when you need help most. If your needs change, scope can be widened or narrowed at the periodic reviews instead of being renegotiated from scratch.
If you want to reduce repetitive manual tasks in daily operations, our Automation and AI service looks at which workflows are worth automating.
To describe your team and discuss what support you need, contact us and we will suggest a sensible starting scope.
We learn about your people, locations, devices, applications and current suppliers, and listen to what frustrates your team today.
We agree which systems and activities are included, how requests are raised, who approves changes and which working arrangements apply to your organisation.
We document the environment, set up the agreed tools and routes for support, and introduce the arrangement to your team.
Support, maintenance and checks are carried out as agreed, with changes planned around your working calendar.
We review reports and recurring issues with you, and adapt scope as the business grows or changes.

Compare co-managed IT, fully managed IT and break-fix support: who does what, what drives cost and the questions to answer before you choose a model.

Changing IT provider? Collect admin accounts and licences in your name first, then documentation, tickets and close old access. A practical checklist.

IT documentation for small business: the records to keep, where to store them, who should own them and how to keep them current as things change.
Tell us what your team needs today and what you would like to improve.