Description
Software does not stand still. Systems get updates, extensions get
vulnerabilities, dependencies reach end of life, and eventually someone
notices that the last working backup is six months old. A maintenance plan
takes that work off your hands — not as a vague retainer, but with a
defined scope per tier.
What every tier includes
Updates are applied and then checked — an update that
breaks the site is not a finished update. Backups run automatically and are
restored on a test basis at regular intervals, because a backup nobody has
ever restored is a guess. On top of that: availability monitoring and a
contact who answers.
What separates the tiers
Mainly two things: how quickly a report is responded to,
and how much working time is included for changes that go
beyond maintenance. The table below puts that side by side.
Term
The plan runs monthly and can be cancelled at any time, taking
effect at the end of the month you have paid for — no minimum
term, no notice period. Unused working time expires at the end of the
month; it does not accumulate, because a balance that carries over is a
liability nobody can account for cleanly.
For work that exceeds the included scope, you get an estimate first.
Nothing is billed that you have not agreed to.