Frequently asked questions
Do you offer support after launch?
Launch is the midpoint, not the finish line, so yes. Support is offered as a monthly retainer sized to your systems: monitoring, updates, small changes and a rolling improvement backlog. If something breaks at two in the morning, the alert reaches an engineer who knows the stack, and you get a clear report of what happened and what we changed.
What does a maintenance retainer include?
A predictable monthly scope: 24/7 uptime and performance monitoring, security and dependency patching, tested off-site backups with periodic restore drills, and an allowance of small change requests from a shared backlog. You see what was done and what we recommend next in a plain-language monthly report. No surprise invoices, and nothing critical waits behind a ticket queue.
Do you monitor uptime around the clock?
Yes. Uptime alerting runs 24/7 on retainers, checking availability, response times, SSL expiry, disk and error rates from outside your network, so a problem is caught the way your customers would meet it. Alerts page an engineer directly instead of drowning an inbox. Monitoring data also feeds the monthly report, which is how quiet weeks prove the system is calm.
Can you take over an existing project?
Often. We start with a technical audit: architecture, code quality, dependencies, security and hosting, with a written assessment and a prioritised list of what needs attention. If the risk is manageable we take it on; if it is not, we say so plainly and help you plan a rebuild. Either way you get honest ground truth before you commit.
How do you report progress?
In a language you can act on. During projects you get a short weekly note: what moved, what is next, what we need from you. On retainers the monthly report covers uptime, patches applied, changes made, budget used and our recommendations, with a plain-language status. Detail lives in the shared tracker; the report is the summary, not the noise.