Some businesses need a website the way they need a sign over the door: one page, the right facts, and the phone number where a thumb can find it. Malvern Motor Services, an independent garage in Malvern Link with forty years of trading behind it, is one of them. Its site says what the garage does, when it opens, what an MOT costs and how to get in touch, and that is the whole of the job. The engineering question is not how much such a page can do, but how little it can cost, how fast it can be, how little it can collect, and how cleanly it can be handed back.
We had built and hosted the garage's previous site, and we look after its domain. In August 2026 the site was rebuilt from a managed content platform into a static page: the same copy, photographs and logo, a refreshed layout, a still image in place of the carousel, a contact form with a number-plate field, and a map link on the address. The design was approved on a Monday, the page was built that evening, and the audits, the form tests and the paperwork followed within the week. The agreement and its data-processing schedule were signed on the Wednesday morning and the site went live that afternoon, which is the order these things are supposed to happen in.
What the garage has now
A single page, with a privacy page beside it, served as plain files from an edge network with no build step and no content system behind it: nothing to patch, no plugins to expire, no login to forget. It sets no cookies and runs no analytics of any kind, so there is no banner to click through, and the cookie policy was retired rather than maintained. The fonts are self-hosted, the images are sized for the screens that ask for them, and the only request the page makes beyond its own domain is the spam check's own script, which loads only when a visitor nears the form. Every address the old site had redirects to its new home, so nothing anyone had linked stops working, and the page carries the structured data a search engine expects of a local business.
Enquiries go through a form that keeps nothing: a submission is relayed straight to the garage's inbox and stored nowhere on the way, and a reply from the inbox goes to the customer. The number-plate field takes a registration the way a garage would type it, and without scripting the form still posts. On a throttled phone the page paints its first content in about a second and a half and its largest in under two and a half, weighs about a third of a megabyte on first load, and scores one hundred for accessibility, with all twenty-nine of its text colour pairings measured above the threshold rather than sampled.
Proven on the way out of the door
The form was tested the way a customer would use it rather than the way a harness would. Three consecutive submissions reached the inbox with every authentication header passing, and one of them was sent with the browser's autofill deliberately switched on, because the spam trap had been found, during testing, to be a field that autofill was happy to fill. It was renamed to something no autofill recognises, and the test that would have dropped a real customer now passes. A bot-style submission is still swallowed silently, a submission with no spam token is still refused, and none of that reaches the inbox.
Mail from the domain is authenticated end to end, and the policy for mail that fails authentication is reject, but it did not start there. The domain had never sent mail before the form existed. It went live at quarantine, with the aggregate reports that receivers publish routed to us, and sat there while the reports came in. Every report showed only the garage's own mail, aligned on both checks, and nothing else had tried to send as the domain. Three weeks after launch the policy went to reject, a test submission afterwards passed every check, and the ticket stayed open for another fortnight of reports before anybody called it finished. The reports stayed clean. Straight to reject is right for a domain with nothing to break; a domain that sends real mail earns it.
— On leaving —The site was built to be handed back. Thirty days' notice either way, a complete copy of the files, and a licence that does not end when the arrangement does.
A switch in working hours
The new zone was built and checked record by record before the nameservers moved, with the three records the form's mail depends on carried over verbatim and the old host's mail records, which nothing had ever used, deliberately left behind. The switch was made on a Wednesday afternoon, in working hours, with the old host left running so that reversing it would have been a single change. Within the hour the page was serving from the edge on both hostnames with valid certificates, the old addresses redirected, and the form had been tested on the live domain. The search console had the sitemap the same day and both pages indexed within three days. On the Saturday, with every public resolver answering with the new nameservers and nothing left pointing at the old host, the old shared hosting was cancelled, once a final copy of the old site and its database had been archived.
Since October two external monitors fetch the site every five minutes: one the page itself, the other an endpoint that answers only when the site's server-side code is actually running and both secrets the form depends on are present, though never what they are. If either is missing it answers 503, a state in which the form is broken and nothing on the page would show it. The endpoint was verified on production before its monitor was created, since a monitor pointed at an endpoint that is not there yet alerts at once.
Built to be handed back
The arrangement is written down in plain terms, and a one-page summary sits beside the agreement saying the same things in fewer words, because it was written for the garage to read rather than for a lawyer. We run the site and look after the domain; the garage's name, logo, photographs and wording are its own; the code is ours, and the garage holds a perpetual licence to it that does not end when we part. Either side can end the arrangement on thirty days' notice, and if it ends the garage receives a complete copy of the site, which is a folder of files any developer can host anywhere. That is a design decision as much as a legal one. A static site has no database to export, no platform to migrate off and no account the garage cannot be given, so the exit is as cheap as the running, and the arrangement does not depend on either side needing the other.
What the garage has, then, is a page that is faster, plainer and quieter than the one it replaced, with no cookies, no analytics and no form entries left lying anywhere; a mail domain that earned its reject policy over a month of clean reports; two monitors watching from outside; and the knowledge that if it ever wanted to take the whole thing somewhere else, it could, in an afternoon.