// case study
A website that updates itself.
This is a teardown of a real system: a client's website that has published its own content every day since launch, unattended — a short seasonal note, written each morning by software from that morning's actual weather. Built in about a week.
The architecture
300+ URLs are generated at deploy time from four data files: towns, services, problems, species. Service hubs, town hubs, cost guides, and a care-guide library, each cross-linked, each with its own structured data. Adding a town is one line of JSON, not an afternoon of copying.
a scheduled job reads live weather signals for the service area, hands them to Claude with a locked voice and hard rules, and publishes a short seasonal note. The build weaves past notes into the guide library so nothing is orphaned. No human has touched it since launch.
reviews re-sync from the business's public listing on a monthly schedule; search stats refresh daily — the parts of a site that usually go stale are on schedules instead.
a small admin page for the things the owner actually changes: photos, phone, service flags. Everything else maintains itself. No WordPress, no plugins to update, nothing to hack.
What it costs to run
Hosting: effectively zero on modern static infrastructure. Model API for the daily writing: single-digit dollars a month — the note is short and the prompt is efficient. The owner's time: none. That's the entire point, and it's why "website maintenance" retainers for static brochure sites should make you suspicious.
The lessons that transfer
When pages are generated from data, adding a town or a service is a one-line change, not a writing project. The voice rules live in the system prompt with hard forbidden-phrase lists, so every generated note sounds the same. And anything that depends on someone remembering to update it runs on a timer instead.
Common questions
Yes. Generated pages from structured data, scheduled AI-written content with a locked voice, and timed re-syncs of reviews and stats produce a site that stays current with no human in the loop. The example in this case study has run unattended since launch.
Near-zero hosting on static infrastructure and single-digit dollars a month in AI usage for daily content. The build is the investment; the running cost is trivial.
studio@anchor163.com
// copied