You do not need to run a server
Site ownership means deciding, not administering. Four jobs are yours, and the rest belongs to whoever hosts the site.
Your four jobs
1. read
once a month, read the report somebody sends you
ask what changed, not how the traffic compares to last year
2. answer
reply to real enquiries inside your own promise
mark the spam, so the inbox stays useful
3. decide
choose one change from the list you were given
say no to the others, so the list stays short
4. escalate
site down, certificate expired, data missing: send it to the host
A filled month
Foxglove Bakery, one owner, 40 minutes across the month.
what arrived
- one report, 4 pages, with the numbers and their sources
- three enquiries, one of them spam
- two review comments from the team
what I did
- read the report on the 3rd, 15 minutes
- replied to two enquiries, and marked one as spam, 10 minutes
- chose the cake page title as the change for this month, 5 minutes
- said no to the blog for now, and wrote down why, 5 minutes
- sent one escalation: the certificate expires in 30 days, 5 minutes
what I did not do
- open the hosting control panel
- change anything in the site myself
- read a dashboard daily
What is worth automating
Reading the site on a schedule, checking pages answer, and watching for a page that stops loading. Those three catch most surprises.
Acceptance: the routine is working when
- the monthly read happened on a date you can name
- every real enquiry was answered inside your promise
- one decision was made, and the rest were declined with a reason
- anything needing a terminal, database or admin login was escalated
- the month took under an hour
Troubleshooting
| Symptom | Likely cause | What to do |
|---|---|---|
| You are reading dashboards daily | No one owns the report | Ask for one monthly update |
| Enquiries go unanswered | They land in one inbox | Add a second recipient |
| You keep fixing things yourself | The escalation list is not written | Write it, and send the first item |
| The report is unreadable | No sources on the numbers | Ask for the source beside each number |
| Nothing changed this month | A stable site | Accept it, and close the month |
Limits
This routine keeps a small site healthy. It cannot rescue a site with no backups, and it does not replace a developer for project work.
A backup you have never restored is not a backup. Restore one before you need to.