Monitoring
The site, the phone system, and every integration are checked on a schedule, and a failure raises an alert to us before a customer finds it.
Capability 05 / 05 · Support & protection
Someone answers after launch.
A monthly service plan covering monitoring, security patching, backups with a tested restore, and changes on request, with a written summary every week. You text us directly, and the same studio that built it answers. There is no queue.
Fixed-scope installations · Monthly service plans · A reply within one business day
01 / 04 What’s included
Six things included. Nothing you will not use.
One plan per installed system. Nothing here is an add-on tier.
Security and patching
Certificates, dependencies, and access are kept current, and anything with a known problem is patched on the plan rather than billed as an emergency.
Backups and tested restore
Backups run on a schedule and the restore is actually exercised, because a backup nobody has restored from is a hope, not a backup.
Changes on request
Text the change. Text and photo edits, new pages, wording changes, and small adjustments land inside the plan.
Weekly summary
One message every week: what ran, what failed, what was changed, and what is worth your attention next week.
A direct line to us
The number on this page reaches the studio that wrote the code. No ticket portal, no account manager, no middle layer.
02 / 04 How it works
Four steps, in the same order every time.
This applies to systems we built and to systems somebody else left behind.
Step 01 / 04
Take over
We inventory what exists, take custody of the accounts in your name, document where everything runs, and record what is already broken.
InventoryDay one
Accounts and renewalsListed
Where each system runsDocumented
Already brokenRecorded
AccessIn your name
The runbook is yours from the first week
Step 02 / 04
Monitor
Checks go on the parts that matter: uptime, certificates, the integrations, and the message paths customers actually touch.
ChecksOn a schedule
The siteWatched
CertificatesWatched
Every integrationWatched
A failureAlerts us first
You should not be the one who notices
Step 03 / 04
Change
Requests come in by text, go out within two business days, and every change is recorded against the system it touched.
Change logBy text
New hours on the contact page, and swap the truck photo.Sent from your phone
ReceivedBy text
LiveWithin two business days
RecordedAgainst the system
Step 04 / 04
Report
Each week’s summary states what ran, what failed, what changed, and what we recommend. The same format every time, good news or bad.
Weekly summarySame format every week
What ranListed
What failedNamed
What changedLogged
What we recommendOne thing
Good news or bad, it arrives either way
03 / 04 Proof
Working software, not a slide.
One internal build that evidences how we treat running systems. No client results are claimed.
Internal build
Deploy pre-flight and publishing infrastructure
The most common way a small site breaks is a person publishing something half-finished with no check between the edit and the public.
- A deploy script with a pre-flight that refuses to publish while placeholder tokens remain
- DNS cut over by API, with apex and www records and mail authentication set deliberately
- HTTPS enforced, with sitemap, robots, and structured data maintained as part of the deploy
Hand-written HTML/CSS · GitHub Pages · registrar DNS API · shell deploy script
See the build04 / 04 Who it’s for
If this is your week.
Three situations we are called about most. If none of them are yours, the assessment is still free.
Your site went down on a Saturday and you found out from a customer.
Nobody was watching it. By the time anyone looked, it had been down since Thursday.
The person who built your systems has moved on.
Nothing is documented, two accounts are in their personal email, and nobody knows which renewal is coming next.
A small text change has been on a list since spring.
It is a ten-minute job. It has been waiting three months because there is nobody whose job it is.
Questions
What we are asked first.
Will you support something you did not build?
Often yes. We start with an inventory and an honest assessment: some inherited systems are supportable as they are, and some need a fixed-scope repair before a plan makes sense. We tell you which before you commit to anything.
What counts as a change on request, and what becomes a new project?
Text and photo edits, wording, new pages on the existing structure, and small adjustments are in the plan. New systems, new integrations, and anything needing design work are quoted as their own fixed scope. The line is written into the plan so it is not an argument later.
What is your response time?
A reply within one business day, every time, and faster in practice for anything customer-facing. An outage gets worked immediately, not queued for the next scheduled window.
Can I cancel?
Month to month, no long-term contract. On the way out you keep the accounts, the domain, the source, and the runbook, because they were in your name the whole time.
Start here
We will inventory what you already have.
Accounts, renewals, hosting, backups, and what is currently unwatched. One page, yours either way, whether the next step is a plan or nothing at all.
Received.
A reply within one business day, from the studio that would build the system. If nothing arrives, call or text (616) 227-4477.