We write down how your website and systems work, who has access, and how to get them back. Then we check them every five minutes and message you when something stops.
Every plan starts with a short call. Prices are marked as pilot prices because we're still working out how much time each pack takes.
For when you need everything written down, once, by someone who'll ask the awkward questions.
Written down, then watched. When something breaks, the alert points straight at the fix.
You already have your documentation sorted. You just want to know when the site stops.
| Handover | Both | Monitoring | |
|---|---|---|---|
| Systems and accounts inventory | ✓ | ✓ | – |
| Backup and restore steps | ✓ | ✓ | – |
| Escalation contacts | ✓ | ✓ | – |
| Gaps and risks report | ✓ | ✓ | – |
| 5-minute website checks | – | ✓ | ✓ |
| Down and recovered alerts | – | ✓ | ✓ |
| Alerts link to your recovery steps | – | ✓ | – |
| Monthly summary | – | ✓ | ✓ |
| Price (pilot) | $99 once | $99 + $19/mo | $19/mo |
It's what you hand to a new developer, an IT company, or a family member if something happens. We build it from one call and a short form.
When we don't know something, we ask you. Anything still unanswered is marked as a gap, so the pack never pretends to know more than it does.
Click a section to see the kind of thing it holds, or open the full sample pack.
What's covered and what isn't. One shop website, its hosting, domain and booking form.In scope: harborlanebikes.example, booking form, mailboxes
Who owns each account and who else can get in. We record where access lives, never the passwords themselves.Domain registrar · owner: shop owner · also: web developer
What's backed up, how often, where it goes, and when someone last checked a backup actually works.
Plain, numbered steps to get the site back, written for whoever is on hand rather than for the person who built it.
What we check, how often, and who gets the alert.
Who to call first, second and third, with what each person is able to fix.
Things that worried us, in plain language. For example: only one person can log in to the domain registrar.
A short list of fixes, in order, so the risks above actually get dealt with.
Websites hiccup. A single failed check is usually nothing, so we ignore it. Two in a row means something is wrong, and that's when we message you. When it's fixed, you get a second, shorter message.
You don't need to prepare anything technical. If you don't know an answer, that's useful too, because it shows us where the gaps are.
A short call about what you run and who set it up.
We write the pack and send you a short list of questions about anything missing.
Read it, correct anything wrong, approve it. The final copy is yours.
If you chose monitoring, checks start once you approve.
Small businesses whose website or systems were set up by one person, like a freelancer, an agency or a relative, where nobody else really knows how it all fits together.
No. We document what they set up and check it keeps running. If something breaks, the alert goes to whoever you choose, and the pack tells them where to start.
For now, websites. Every five minutes we check that the site answers properly. If you also need backups or a server checked, tell us on the call and we'll say honestly whether we can do it yet.
Slack or email, to you, your developer, or both. Every alert starts with the business name, so it's obvious which client it's about if your developer looks after several.
We're working with our first clients and learning how much time a pack really takes. The price may change as we learn, and we'll be upfront about it.
Here's a filled-in Handover Pack for a made-up bike shop, in a plain version for the owner and a developer version with the technical detail.