Developers, Not a Ticket Queue
Your request goes to an engineer who can read the code, not a first-line agent working from a script who escalates anything non-obvious.
Every plan covers the fundamentals: core, theme, plugin, and dependency updates tested on staging; security monitoring and malware scanning; automated offsite backups; uptime and performance monitoring; and a monthly report. Plans also include a set allowance of development time each month for content changes, fixes, and small improvements — the size of that allowance is what mainly differs between plans.
Yes, and it's a large part of what we do. We start with an audit of the site, its hosting, and its codebase so we know exactly what we're taking on. If we find issues that need fixing before ongoing maintenance makes sense, we'll quote that separately and up front rather than absorbing it quietly or discovering it mid-incident.
It depends on the platform, the complexity of the site, and how much development time you want included each month. A brochure site needs far less than a WooCommerce store or a custom application with active users. After a short audit we'll recommend a plan and quote it clearly, with no long-term contract required.
Response times are agreed as part of your plan, so you know what to expect before you need it rather than reading the fine print during an outage. Site-down and security incidents are always treated as urgent and jump the queue ahead of routine requests, regardless of plan.
We're usually alerted by monitoring before you notice. From there we take the site to a safe state, restore from a known-clean backup where needed, find and close the entry point, and then tell you plainly what happened and what we changed. Cleanup on sites already compromised before onboarding is handled as a separate recovery project.
Yes. Alongside WordPress and WooCommerce we maintain custom applications built in Next.js, React, Node.js, and Laravel — keeping frameworks and packages patched, watching error logs, and handling upgrades before versions reach end of life. If we built it, we already know it; if we didn't, the onboarding audit gets us there.
Yes. Plans are month to month and can be moved up or down as your needs change. If you leave, your backups, documentation, and access are handed over — we don't hold hosting, domains, or code hostage as a retention tactic.
You can, and for a simple site with few plugins that's a reasonable choice. The risk is that updates occasionally conflict with each other or with custom code, and the failure often shows up somewhere you weren't looking — a form, a checkout step, a mobile layout. Maintenance is really about testing before deploying and having backups that have been proven to restore, which is the part that's easy to skip until the day it matters.
