Retainer or Break-Fix: What Each One Actually Costs

Two different things being sold

"Website support" gets sold two fundamentally different ways, and the difference is not really about price — it is about who is watching, and when. A retainer buys ongoing attention: something is being checked, patched or monitored on a schedule whether or not anything has gone wrong yet. Break-fix buys attention only after something already has — you call, describe the problem, and pay for the specific work of fixing that one thing. Both are legitimate commercial arrangements. They just suit genuinely different situations, and treating them as interchangeable is where businesses tend to pick the wrong one.

What break-fix actually costs, beyond the invoice

The invoice for a single break-fix job is usually the easiest number to compare — an hourly rate, or a quoted fee for a specific piece of work, paid once. That is a real advantage for a site that rarely needs anything done: no ongoing commitment, no monthly line item for a site that has been quietly fine for a year. But the invoice is not the whole cost, and three things tend to sit underneath it that a single per-incident number does not capture.

No one is watching between incidents

Under a retainer, a provider is checking for problems — an expiring certificate, a plugin with a known vulnerability, a backup that silently stopped running — before they become the reason you are calling. Under break-fix, by definition, nobody is looking at your site until you have already noticed something is wrong, which usually means a customer noticed first. The gap between a problem starting and someone actually addressing it is structurally longer under break-fix, not because the people involved are less capable, but because the arrangement itself has no mechanism for catching anything early.

No accumulated context

A provider who has been maintaining a site for months has context that is not written down anywhere: which plugin caused trouble last time, how the site's traffic pattern behaves on a normal day versus an unusual one, what the hosting setup actually looks like under the surface. A break-fix engagement, especially with a different person or firm each time, starts from zero on every call. Some of that gets rebuilt quickly by a competent developer reading logs and code; some of it — the tacit knowledge of "this site does this odd thing sometimes and it is fine" — genuinely does not exist anywhere for a new person to find, and gets rediscovered the hard way.

Slower diagnosis under pressure

Diagnosing an unfamiliar site while it is actively broken, with a business owner waiting and orders possibly failing, is a worse environment for careful work than diagnosing the same problem calmly, with time to check rather than guess. This is not a knock on break-fix providers specifically — it is true of anyone stepping into an unfamiliar codebase under time pressure. The practical effect is that the same underlying fault often takes longer to actually resolve under break-fix than it would for someone who already knew the site, even when the billed hours look similar or lower.

None of this means break-fix is a bad model. It means the per-incident invoice understates the real cost by leaving out the time a problem sat unnoticed, the context that had to be rebuilt from scratch, and the extra hours diagnosis takes under pressure — none of which show up as a line item, but all of which are real.

What a retainer actually costs, and what it buys

A retainer's cost is more visible up front — a fixed monthly figure, paid whether or not anything happens that month, which can feel like paying for nothing during a quiet stretch. What it buys in exchange is the thing break-fix structurally cannot offer: someone checking before you would otherwise notice, a provider who already has context on your specific setup when something does go wrong, and — depending on what the retainer actually includes — a defined, if modest, allowance of ordinary content work handled without a separate quote each time.

Whether that trade is worth it depends entirely on what a problem going unnoticed for a few extra days would actually cost your business. For a site that takes orders, handles logins, or is the main way customers reach you, that gap has a real cost even when it is hard to put an exact figure on it in advance. For other sites, it genuinely does not.

Where break-fix is genuinely the rational choice

It is worth saying plainly: break-fix is the right call for a real category of website, not a fallback for businesses that have not gotten around to a retainer yet. A small, mostly static brochure site — a handful of pages, no e-commerce, no login, no form doing anything business-critical, content that changes a few times a year at most — has very little for ongoing monitoring to actually catch, and very little downside if it is offline for a few hours while someone gets to it. Paying a fixed monthly sum to watch a site that almost never needs watching is a reasonable thing to skip.

The honest test is not the size of the business — a one-person consultancy and a fifty-person company can both run a site simple enough that break-fix suits it fine. The test is closer to this: if this specific site went down, or a form silently stopped working, for three or four days before anyone noticed, would that meaningfully cost the business anything? If the answer is genuinely no, the ongoing-attention part of a retainer is not buying much, and paying only when something needs doing is the more rational spend.

A rough way to decide

Look honestly at three things: how often the site actually needs changes made, how bad it would be if a problem sat unnoticed for several days, and whether losing accumulated context on your specific setup — because the last person who fixed something is not the person fixing the next thing — would slow anything down that matters. A site that scores low on all three is a reasonable candidate for break-fix. A site that scores high on any one of them is quietly paying an unpriced cost every time something breaks, even if the invoices along the way look smaller.

It is also worth revisiting the answer periodically rather than assuming it holds forever. A brochure site that starts taking bookings, or a hobby shop that starts processing real payments, has usually crossed from one category into the other — and the trigger is rarely a single dramatic event, just a business that has quietly grown past the assumptions its original support arrangement was built on.

---

If ongoing attention is worth it for your site, JagaWeb Care (RM450/month, excluding SST) covers monitoring, verified backups and patching on a single site, and Care + Changes (RM1,500/month) adds a running allowance of content updates on top of that. If it is not worth it, that is a reasonable conclusion too — this is not a case for one model over the other, just for choosing deliberately rather than by default. Details at jagaweb.my or sales@jagaweb.my.