MOD.06 — Services
Support & Optimisation.
Monitoring, patching and small improvements every month. Launch day is the start, not the handover.
What the module includes
- I-01Monitoring & uptime
We know your site is down before you do, and usually before your customers.
- I-02Updates & security
Core, plugins and dependencies patched on schedule, tested before they touch production.
- I-03Monthly improvements
A standing block of hours for the small fixes and ideas that otherwise never get scheduled.
- I-04Plain-language reporting
What changed, what it did, what we recommend next. No vanity dashboards.
How the module runs
Watch continuously
Uptime, speed and security monitoring with alerts we act on before you notice.
Maintain on schedule
Updates, backups and audits on a fixed cadence, logged where you can see them.
Improve deliberately
Each month gets a small, measured improvement, not just maintenance. Sites should compound.
Seen in production
True-to-colour captures from the registry. Open the case file for the full build sheet.
Proof in the registry
Every claim above is checkable: the related builds in the panel ran this module in production. Open a case file, then the live site.
Quick answers
Do you support sites you didn't build?
Yes, after a short audit so we know what we're taking responsibility for.
What does support cost?
Scoped retainers by site complexity, fixed monthly, cancellable. The invoice matches the quote, as always.
What response times do you commit to?
Same working day acknowledgement, with severity-based fixes agreed in the retainer.
What happens if the site goes down at 2am?
Monitoring picks it up before you do. Critical-outage response is part of every plan, and because each site has a documented runbook, whoever responds isn't guessing.
Are we locked into a contract?
Plans are month to month after the first quarter. If we're not visibly useful, leave — everything is documented for whoever comes next.