Your customers already
wrote their website
The record is the website
The record
The facts your customers already maintain to operate
One mapping
Point us at your schema once, for every tenant you have
The agent
Generates, builds, and verifies the site — then does it again when the record moves
A live site per tenant
Server-rendered at the edge, on its own subdomain or the customer's own domain. No CMS, no login, nothing for the business owner to keep up to date.
What they type. What the site says.
Every line below is one field in your platform and the sentence it publishes. Nobody wrote the sentence, and nobody has to remember to change it.
What they type
What the site says
- hours.friday 07:00–19:00 Open today until 7:00 PM
- service_areas Tempe · Mesa · Chandler Serving Tempe, Mesa, and Chandler
- license.state ROC 284119 Licensed and bonded — ROC 284119
- techs.certified 4 Four certified technicians on call
- booking.next_open TUE 08:00 Next opening: Tuesday at 8:00 AM
Built for the businesses your platform already serves
The same operating record, published as the web presence each vertical actually needs.
Home services
Service areas, licence numbers, and crew counts are already in the dispatch record. Publish them as pages that rank locally and never contradict the schedule.
Dental and medical practices
Practices update providers, accepted insurance, and appointment availability to run the day. That is the whole website — so it should be the website.
Salons and spas
Service menus and prices change constantly and go stale everywhere else. Here the price on the site is the price in the booking system, because it is the same field.
Auto and specialty repair
Certifications, makes serviced, and current turnaround times come straight off the shop record — the details customers actually search for before they call.
Fitness and studios
A class timetable that is wrong is worse than no timetable. Publish the live schedule, and let it change the moment the studio changes it.
Restaurants and food service
Seasonal menus, holiday hours, and per-location details stay correct across every site you publish, without anyone opening a page editor.
Want to wire it yourself?
We have the API.
One integration. Every tenant. No per-site setup.
Map your schema once and the whole book is addressable — the fifty-thousandth business costs the same integration work as the first, which is none. New tenants are publishable the moment their record exists.
Subdomains now, custom domains when they are ready.
Every business is live on its own subdomain immediately, so it is reachable before anyone thinks about DNS. Businesses that already own a domain point it at their site, with certificates handled for them.
Server-rendered at the edge, isolated per tenant.
Each site is its own worker on Cloudflare's network, so the first response is complete HTML and one business's traffic is invisible to every other. Crawlers and language models read the page without executing anything.
We map your schema with you,
then get out of the way.
Your data model is not the same as anyone else's, and it should not have to be. We sit with your team, work out which field means what, and hand back a mapping that covers every tenant you have and every one you sign afterwards.
Four things that stop being
your problem
Small-business websites fail by being wrong, not by being ugly. Every one of these exists because the site was disconnected from the system the business actually runs on.
No CMS to maintain
The record is the CMS
Never stale
Publishing follows the data
One integration, every tenant
Map your schema once
Every tenant, on the edge
Server-rendered, globally
No CMS to maintain
Your customers never learn a second tool to keep their site correct. There is no page editor, no draft state, and no content model to migrate — the operational record they already keep is the only source the site reads from.
Never stale
Hours change at 4:00 PM in your platform. The site says so at 4:00 PM. Nobody was asked to update anything, nobody forgot, and no support ticket was filed three weeks later about a wrong phone number.
One integration, every tenant
You wire your platform to The Biz Layer a single time. Every business on it gets a site that stays true to its own record — the ten-thousandth tenant costs the same integration work as the first, which is none.
Every tenant, on the edge
Each site is server-rendered on Cloudflare's network, so crawlers and language models get complete HTML on the first request. Fast pages that are actually readable by the systems your customers are found through.
A site for every kind of business you hold
Same integration, same publishing pipeline — the page each vertical needs, built from its own record.
Home services
Plumbing, HVAC, electrical, roofing, and landscaping — every crew gets a site built from its own dispatch record.
Trades
Licences, insurance, and certifications published as verifiable facts rather than claims typed once and forgotten.
Dental
Providers, accepted insurance, and next available appointment, straight from the practice management record.
Salons and spas
Service menus, stylists, and prices that match the booking system because they are read from it.
Auto repair
Makes serviced, certifications, bay capacity, and turnaround times pulled from the shop's own system.
Fitness
Class schedules, coaches, and membership tiers rendered live, so the timetable on the site is the real one.
Restaurants
Menus, holiday hours, and per-location details kept correct across every venue you publish.