Updates tested somewhere else first
Core, plugin and theme updates run on a staging copy before they touch production, so a breaking change is found by us and not by a customer.
If you want long-term retainers Partnership and pricing
Updates, backups, monitoring and a named person who answers when something breaks, handled by the people who build sites rather than by a ticket queue in another time zone.
For owners of a live site the business now depends on and nobody is actually looking after. It is not the route to a redesign: if what you need is a rebuild, that is a project with a start and an end, and stretching a monthly plan around it serves nobody.
Core, plugin and theme updates run on a staging copy before they touch production, so a breaking change is found by us and not by a customer.
Backups are stored off the server that made them, and we actually restore one, because a backup nobody has ever restored is a guess.
Uptime, certificates, domain expiry and error rates are watched, and the alerts go to someone on the team rather than into an inbox nobody opens.
Logins, file permissions and the usual entry points are tightened, malware scans run on a schedule, and the steps for a compromised site are written down before you need them.
What was updated, what broke, what we changed and what we are watching, written so a non-technical owner can read it quickly.
Small content and layout changes are part of the plan, so a price change or a new team member does not need a quote and a queue.
Retail here runs on dates everyone already knows: paydays around the middle and the end of the month, and the double-date sales that Shopee and Lazada have trained shoppers to wait for. Updates get scheduled away from those, and we work Philippine hours, so a plugin update happens at a quiet local time and someone is awake when it misbehaves rather than a shift later in another country. If you hold a .ph or .com.ph domain we track its renewal next to your hosting, because those are administered separately from a .com and are easy to lose sight of. And the live chat widget your team answers enquiries on counts as part of the support desk, so it goes on the monitoring list instead of being treated as a nice-to-have.
Usually yes, once we have audited what is actually in it. If the site sits on something we cannot safely update, such as an abandoned builder plugin or a licence nobody has renewed, we will tell you what it would take to make it maintainable, and what the risk is until then. Taking a monthly fee for work the platform will not let us do would help neither of us.
A site that is down, a checkout that is failing, or a suspected compromise. Those are worked on immediately, inside the response window written into your agreement, and you get told what happened and what we changed. Everything else is scheduled, because interrupting a controlled update queue is how small problems turn into outages.
Yes. The hosting, the domain and any third-party accounts stay in your name with you as the owner, and we work under our own access. If you leave, you keep all of it, along with the documentation and the backup history. Nothing about the arrangement depends on us holding an account you cannot get into.
Clicking update is the easy part. The work is knowing which update to hold back, spotting the plugin whose author has walked away, taking a restore point before anything changes, and noticing that the contact form quietly stopped sending mail some time last month. A site can be completely up to date and still be broken in ways nobody has looked for.
No, and for a mainly domestic audience an origin close to your visitors is an advantage. What we do check is who actually holds the domain and the registrar login, because .ph and .com.ph domains are administered separately from a .com and renewals get missed when the only contact on file is a staff member who has left. Those dates go on the same calendar as your hosting and your certificates.
Yes, on the notice period in the agreement. A care plan is monthly work, not a lock-in, and the reason to stay should be that the site is visibly being looked after. All we ask is that you tell us before a busy period rather than during one, so the monitoring and the backup history can be handed over cleanly.
Tell us what you are building and we will tell you honestly how we would approach it.