Supportand growth
An unattended site ages fast: forms break, certificates expire, small fixes pile up and never get done. A subscription handles that in advance, rather than after the enquiries have already been lost.
What's included
Copy, images, prices, new blocks — within the day
Availability checked every 10 minutes, alert on failure
Current versions and security patches
Daily, with the ability to roll back
I watch that it doesn't degrade over time
A monthly look at the numbers and what to improve next
How the work runs
- 012–3 days
Taking the site on
I look at what's inside: what it's built on, what's been updated, where the fragile parts are. This is free and commits you to nothing. If the site is put together so that every fix breaks something adjacent, I'll say so plainly — rebuilding is cheaper than maintaining it.
- 021–2 days
Monitoring
The site is polled every ten minutes, along with the enquiry form, the certificate expiry and disk space. Alerts come to me, not to you: the point of a subscription is that you hear about an outage together with the news that it's fixed.
- 031 day
Backups
Daily, with history and — critically — with a restore test. A backup nobody has ever restored isn't a backup; you find that out on the worst possible day.
- 04continuous
Ongoing work
Copy, prices, images, new blocks — within the working day. Updates and security patches I apply myself, without reminders and without taking the site down.
- 05monthly
Monthly review
A short report: visitors and enquiries, what changed, where the site loses people and what I suggest fixing next month. Without this, support degenerates into repairing whatever broke.
What moves the price
"from $300/mo" is the floor, not bait. Here's what pushes the number up, so you can place your own case before we talk.
A couple of small things a month, or a steady stream
A one-pager and a store with data sync need different levels of attention
Within the working day, or around the clock including weekends
Keeping it running, or also improving it against the numbers
Who it's for
- →The site brings enquiries and downtime costs money
- →Nobody inside the company can look after it
- →You need regular changes, not one-off jobs
Questions
Will you take on a site you didn't build?
Yes, but I'll look inside first — that's free. If it's sensibly built, I take it on straight away. If it's assembled so that every fix breaks something next to it, I'll tell you plainly: rebuilding is cheaper than maintaining.
What's included, and what counts as a separate job?
Included is everything that doesn't change how the site is built: copy, prices, images, news, products, new blocks assembled from existing ones, updates, backups, monitoring. Charged separately is anything that is really new development: a new section with its own logic, an integration with someone else's system, a page redesign. The line is simple — if a task takes more than a working day, I say so before starting, not afterwards on the invoice.
What if there's barely anything to change some months?
Then you don't need a subscription, and I'll say so myself. We work on one-off tasks instead, and I'll set up availability monitoring and certificate renewal separately — that costs little and needs no retainer.
Can I pause the subscription?
Yes, any month and without explanation — no cancellation penalties. On pausing I hand over fresh backups and credentials, and monitoring is switched off. The only thing I ask is a week's notice, so I can hand things over properly rather than leave the site unattended mid-switch.
How fast do you respond?
Small changes within the working day. If the site is down or a form has broken, I start immediately: the monitoring tells me about a failure before you notice it.
Shall we talk?
Half an hour on a call and you'll have an estimate and a plan. Free, and it commits you to nothing.