CARE · QUARTERLY, NOT MONTHLY
What keeps a site running after it ships
Custom builds need less maintenance because there are no plugins to update and nothing breaks on someone else's release schedule. Care exists for the residual work, monitoring, security patching and hosting, billed quarterly because that is how often there is actually something to do.
Quarterly, not monthly. Around
Hardened servers, atomic releases, one-command rollback, backups tested by restoring them.
Monitoring and incidentsWatched from the same Command Centre every maintained site reports into, around the clock.
STRAIGHT ANSWERS
Questions about care
The ones that come up once a project is close to launch.
Because a custom build does not generate monthly work the way a plugin-based site does. There is no theme update to apply, no plugin conflict to resolve, nothing breaking on someone else’s release schedule. Quarterly billing matches how often there is actually something to do.
Not always. A custom build carries no plugin ecosystem, which is the biggest source of ongoing maintenance on the rented-platform sites we usually see. Some clients take no care plan and simply call if something comes up. A care plan buys monitoring and priority response, not a subscription you need to justify.
Monitoring from our own Command Centre, security patching, and priority response within support hours, for around
Priced by agreement rather than a flat quarterly figure, because the operational complexity varies far more than a website does. We scope it the same way we scope the build itself: in writing, before anything is agreed to by either side.
Building something new? Care is scoped once the build is.
There is no need to decide on a care plan before a project starts. We revisit it at handover, once you know what you actually built.
Care sits alongside the quick services for a site you already have and the free audit that usually starts both conversations.