Make the website.
Take the bookings.
Get paid.
PageWebPro is a website builder with the business end already in it: forms, bookings, tickets, a shop and cookieless statistics, on a site you edit yourself or hand to an AI agent.
Most websites describe a business.
This one runs one.
Not add-ons and not third-party embeds. Each one has its own settings, its own records, and a widget the published page draws at runtime.
Ask a question
An enquiry, validated in the browser and again on the server, stored and emailed to you.
Take a slot
A table, a cottage for four nights, or forty minutes with a named person, allocated against a real resource.
Buy the thing
Physical, digital and subscription products in one catalogue, paid through hosted checkout.
Come on Friday
Ticket tiers on a dated occurrence, into the same cart the products use, with a QR on the door.
Everything a visitor did
lands in one inbox.
Enquiries, bookings and orders are three different modules and one list: merged per site, newest first, each one still linked to the record it came from.
Four modules,
already in the box.
Each one has its own settings, its own records, and a widget the published page draws at runtime. There is no module on this website that is an upsell.
Forms & enquiries
Build the fields on the page. Submissions are validated in the browser and again on the server against the same spec, screened by a honeypot and Cloudflare Turnstile, then stored and emailed.
Bookings & tickets
Tables, rentals or appointments. Three modes with their own pricing and availability rules. Events carry occurrences, ticket tiers and QR check-in.
Every mode needs a resource of the right kind behind it: a table, a unit, a person. Without one the calendar draws and offers nothing.
Selling online
Physical, digital and subscription products, a cart shared with ticket sales, and hosted checkout through Mollie or Stripe, so card details never touch your site.
Visitor statistics
First-party and cookieless: a rotating daily salt instead of an identifier, so there is nothing to consent to and nothing to hand to a third party.
A design system,
not a pile of overrides.
Colour, space, type and radius are named tokens. Change the brand and every block that referenced a token follows, because it referenced the token, not a colour you typed.
Every node carries its own desktop, tablet and mobile styling, not a single layout that shrinks. Hover and focus are separate, and both are expected on anything you can click.
A sentence on the left.
What the platform ran on the right.
Every editor action is also a tool an agent can call over MCP, with the same access checks and the same validation. This site was written that way, from a terminal.
Read before it writes, validate before it writes, write narrowly. Then render the page through the platform's own renderer and look at what it just made.
Four kinds of business,
four different jobs.
Each of these is written against what the platform actually does for that kind of business: which modules carry the weight, and what the setup looks like.
Covers booked while the kitchen is running. Table allocation, holds and deposits, without the phone.
Physical, digital and subscription products, one cart, and hosted checkout through Mollie or Stripe.
Occurrences, ticket tiers and QR check-in, with availability drawn at runtime, never cached.
Enquiries that arrive validated and sorted, and a calendar for the call that follows.
What we are reading,
and what we shipped.
Your account is the only thing
standing between you and a site.
Create one, pick a starting point, and change anything on the page. Attach your own domain when it is ready, not before.