That somebody is an agency you pay every month — or nobody, which is worse.
Keep the record once. Hours, services, service areas, licences, contact details — the facts a business already knows by heart. Keep them here, and the site reads them on every visit instead of holding a stale copy.
Not templates with their name dropped in — an application per vertical that converts the visit, keeps the customer, and runs the work behind it.
Your contractors do not need another five-page brochure. Give them a site that shows the postcodes they cover, the licence that earns trust, and the next open window — then takes the booking on the page. Built from the record you keep, so what it promises is what a crew can actually deliver.
Offer your practices a site that answers the only two questions a patient asks before calling: are you in my network, and how soon can I be seen. Insurance lists, provider rosters, and opening hours come from the record — change it once and the page changes with it.
A photo of the price list is not a website. Ship your salons a site where every service, price, and stylist comes from the live record, with a booking button beside it. Clients rebook from the page instead of ringing to ask what a balayage costs this month.
Drivers search for the make, the certification, and how long they will be without a car. Give your shops a site that publishes all three from the record and captures the estimate request on the spot — so the lead arrives as a scheduled job, not a voicemail.
Give your studios a site where the timetable is live, the coach bios are current, and every class shows seats left with a join button beside it. Members check the page instead of the front desk, and a full class becomes a waitlist signup rather than a dead end.
Offer your venues a site carrying tonight's real menu, tonight's real hours, and a reservation link that works — across every location, updated the moment the kitchen changes it. Diners see the food and book the table without leaving the page.
Contractors win work on proof and availability, in that order. Publish trade licences, insurance limits, covered postcodes, and the next free window straight from the record — and let the site take the job request while a competitor is still returning calls.
Give your firms a site that states practice areas, jurisdictions, and who is admitted where as facts read from the record — then routes the enquiry to the right person with the matter details already captured. Fewer calls that go nowhere, more work that fits.
Species treated, vets on duty, and whether tonight counts as emergency hours — that is the whole search an anxious owner runs after dark. Give your clinics a site that answers it from the record and books the morning appointment before the worry passes.
Courses, tutors, term dates, and seats remaining move every intake. Ship your schools a site that reads all four live and takes the enrolment on the page — so nobody applies to a cohort that filled last week and nobody chases a PDF form by email.
Dates, line-ups, and ticket links move right up to the door. Give your venues a site that keeps pace with the booking record and sells from it — instead of a page frozen on the night somebody last had a spare hour to edit it.
Every line below is one field on the client record and the sentence it publishes. Nobody wrote the sentence, and nobody has to remember to change it.
What they type
What the site says
Keep the client’s details here — hours, services, contact, licences — and the site is built from them. The fiftieth business takes the same work as the first, which is filling in a form and pressing one button.
Every business is reachable on its own subdomain the day it is created, then moves to its own domain whenever it is ready. Certificates are issued and renewed for you, and we show you the exact records to add — or take the nameservers and add them ourselves.
Pages are server-rendered close to the visitor and arrive as complete HTML for people, crawlers, and language models alike. Each tenant runs on its own, so one business's traffic spike is invisible to every other.
Same console, same publishing pipeline — the page each vertical needs, built from its own record.
Plumbing, HVAC, electrical, roofing, and landscaping — every crew gets a site built from its own client record.
Licences, insurance, and certifications published as verifiable facts rather than claims typed once and forgotten.
Providers, accepted insurance, and opening hours, straight from the client record you keep.
Service menus, stylists, and prices that never drift, because the page reads one record instead of a retyped copy.
Makes serviced, certifications, bay capacity, and turnaround times published from the record you keep.
Class schedules, coaches, and membership tiers rendered live, so the timetable on the site is the real one.
Menus, holiday hours, and per-location details kept correct across every venue you publish.
Species treated, vets on duty, and emergency hours read live from the record — the answers owners search for after dark.
Small-business websites fail commercially, not aesthetically. Every line below is either revenue you are not billing today or work that stops landing on your team tomorrow.
A revenue line, not a cost centre
Websites you bill for
Live in seconds, not days
No design queue, no delivery team
Nothing for anyone to maintain
The record is the CMS
Never wrong, so never a ticket
Publishing follows the data
Clients that stay longer
Churn gets expensive
Websites stop being the thing you absorb and become the thing you charge for. Every business on your list is a site you can price, bundle, or upsell — with no delivery team standing between the sale and the launch.
There is no template project, no design queue, and no per-client onboarding to staff. Fill in the record, press Start, and the site is live before the call ends — while the roadmap you were going to spend on this stays untouched.
No page editor, no draft state, no content model to migrate. Your customers never learn a second tool to keep their site correct, and your team never inherits a backlog of website tickets from the ones who did not.
Hours change at 4:00 PM on the record. The site says so at 4:00 PM. Nobody was asked to update anything, nobody forgot, and nobody calls you three weeks later about a phone number that has been wrong the whole time.
A business whose website runs on the record you keep has one more reason not to leave. Their web presence, their domain, and the enquiries their site takes all sit with you — so cancelling costs them their front door, not just a subscription.
Anyone responsible for the web presence of many businesses at once: agencies holding more client sites than they can profitably maintain by hand, franchise groups with a location list that keeps moving, and operators who need every business they manage to have a site that stays correct.
Add a client and fill in what you already know — hours, services, contact details, licences — then press Start. The site is live on a subdomain in seconds. There is no template to design per client and no page editor for anyone to learn.
Because nothing is copied. A published page reads the record directly on every visit, so when hours change at 4:00 PM the site says so at 4:00 PM — with no rebuild and no republish. Nobody is asked to update the site separately, which means nobody can forget.
Every site is server-rendered on Cloudflare's network, so crawlers and language models get complete HTML on the first request rather than an empty shell that needs JavaScript. Structured facts come from the record, which is also what makes them citable.
It fits when you are on the hook for a lot of client websites and they are a recurring cost or support burden. It fits poorly when each site needs to be a bespoke design signed off pixel by pixel — this publishes the record and edits by conversation, it is not a page builder.
Yes. Each tenant's site is its own repository and its own build, so custom code lands in one site without touching the rest. Domains, branding, and the customer-facing relationship stay yours.
Every site after the first costs what the first one cost: a filled-in record and one button. There is no template to fork, no design queue, and no per-client setup, so the size of your book stops being limited by how much delivery work your team can absorb.
Pages are built from what exists. A business that has not filled in its service areas gets a site without that section rather than a placeholder or a broken page, and the section appears the moment the field is filled in.
Yes. An API key and two endpoints cover it: one call creates the client, one creates the site. There is no field mapping to configure and no sync to keep running — the site reads the record live, so updating the record is updating the site.