Who Fixes It: Vendor Support, In-House or MSP
Every hardware purchase carries an unstated assumption about who fixes it when it fails. That question is answered late more often than it is decided, and the answer should shape what you buy rather than the reverse.
Three models, three different purchases
Vendor support means a contract with the manufacturer: they diagnose, they supply parts, they attend within a defined response time. You are buying a commitment.
In-house means your own people hold the knowledge and you hold the spares. You are buying parts and accepting the diagnosis burden.
Managed service provider means an external team responsible for keeping things running, with their own arrangements for parts and escalation.
Each implies different hardware decisions. A vendor-support model favours current platforms that are still eligible. An in-house model favours standardised, well-understood equipment with obtainable parts — which is where refurbished fits naturally. An MSP model depends on what they will support.
What vendor support is actually buying
Worth being precise, because it is frequently bought without examining it.
You are buying guaranteed response and guaranteed parts. On a current platform where you have no in-house depth and downtime is expensive, that is genuinely valuable.
Three things to check before assuming it applies.
Eligibility. Secondary-market hardware may not be eligible, and support on older platforms may have ended entirely regardless of who owns it.
What the response time means. Response is not resolution. A four-hour response commitment with a part that takes two days to arrive is a four-hour response.
Whether it covers what fails. Some contracts exclude consumables, and printheads, cutters and batteries are the things that actually wear out.
Also check whether keep-your-drive is included — without it, failed media leaves your control with data on it. Our sanitisation guide covers why that matters.
What in-house support actually requires
Cheaper on paper and it has real prerequisites.
Spares on the shelf. The support contract is replaced by inventory. Our spares guide covers building a position weighted by consequence rather than evenly.
Diagnosis capability. Somebody has to establish what failed. Our decision guide covers how often the wrong component gets blamed.
Documentation. Part numbers, firmware levels, configurations and rack layout, stored somewhere that survives the loss of the systems documented. Our documentation guide covers this.
Cover. The model depends on a person, and people take holidays and leave. A single point of knowledge is a real risk and the one most often ignored.
Where these exist, in-house is frequently better as well as cheaper — nobody responds faster than someone in the building with the part in hand.
Where an MSP fits
Two situations where it is clearly the right answer.
No in-house capability and no appetite to build it, particularly for smaller organisations where a full-time technical person is not justified.
Many sites with no local staff, where the alternative is travelling to every incident.
Four things to establish before signing. What is actually covered — hardware, software, network, or some of each. Who supplies parts, and whether you or they hold spares. Response and resolution commitments, separately. And whether they will support the platforms you have, including anything older, since some providers decline equipment outside a support window.
That last one determines whether the arrangement fits your estate or requires replacing it.
Mixing the models
Most organisations end up split, and that is usually correct rather than indecisive.
Vendor support on the few systems where downtime is genuinely expensive and the platform is eligible. In-house spares and capability for everything else, particularly platforms past support where the market is the only recovery path.
The exercise worth doing: list what you run and, for each, write what an hour of downtime costs and who currently fixes it. That usually reveals that most of the estate does not need a contract and one or two things do — and occasionally that something important has no answer at all.
What to decide before buying
Four questions, and answering them changes the purchase.
What does an hour of downtime cost for this system? That is what response commitments are worth.
Who diagnoses it? If nobody in-house can, either buy support or accept that failures start with a phone call.
Where do parts come from? Vendor, your shelf, or the market — and if the market, is availability thinning.
What happens out of hours? Alerts reaching nobody at the weekend is a support model, just not a good one. Our monitoring guide covers why the alert path is the whole thing.
Common questions
Does a four-hour response mean a four-hour fix?
No. Response is not resolution. A four-hour response commitment with a part that takes two days to arrive is a four-hour response. Check response and resolution commitments separately.
What does a support contract typically not cover?
Frequently consumables — and printheads, cutters and batteries are the things that actually wear out. Also check eligibility, since secondary-market hardware and older platforms may not qualify, and whether keep-your-drive is included.
What does in-house support actually need?
Spares on the shelf, someone able to diagnose, documentation stored where it survives the systems it describes, and cover for when that person is unavailable. A single point of knowledge is the risk most often ignored.
What should I check before signing with an MSP?
What is covered, who supplies parts and holds spares, response and resolution commitments separately, and whether they will support the platforms you already have — some decline equipment outside a support window.
How do I decide which model to use?
List what you run and, for each, write what an hour of downtime costs and who currently fixes it. That usually shows most of the estate does not need a contract, one or two things do, and occasionally that something important has no answer at all.
Decide who fixes it before buying — the answer should shape the purchase rather than the other way round.
