You ask. It drafts. You approve.
No page builder to learn and no ticket to raise. Here is what actually happens between the sentence you type and the page your customers see.
Week one: we take over what you already have
You do not start from a blank page. RapidXM is pointed at your current website, reads what is there, and rebuilds it as typed sections in a theme that matches your brand. Your words, your images, your pages — restructured so they can be edited by asking.
Before anything is switched over you get a preview link to the whole rebuilt site. Nothing about your live site changes until you are happy with what you see.
Every day after that: the loop
You ask
In plain English: “put the new price list on the services page”, “our Saturday hours changed to 8 until 2”, “add a page for the Ogden branch”. You do not need to know which page it lives on, which section it is, or what a template is.
It drafts
The change is made everywhere it applies and saved as a draft. If the request needs something that does not exist yet — a new kind of section, a new page — that gets built too, in the design your site already uses.
You approve
You get a preview link showing exactly what a visitor would see, chrome and all. Read it. Send it to whoever signs things off. Ask for changes. When it is right, you click Deploy.
It ships
The site compiles to static HTML and goes out to Cloudflare's network. There is no build to babysit and no cache to clear afterwards.
What you never have to do
- Learn a page builder, or remember where a particular setting is hidden.
- Update plugins, or repair the site after an update breaks it.
- Wait for an agency to fit your one-line change into next month's sprint.
- Guess whether a change worked. You see it before anyone else can.
When something is wrong
Ask it to check. The audit runs across every page and answers in plain language: broken links, pages with no description, colour contrast that fails accessibility standards, images heavier than they need to be. Then ask it to fix what it found, and approve the result the same way you approve anything else.
If a change turns out to be wrong after it has gone live, every page and layout keeps its history. Putting back an earlier version is one instruction, not a support ticket.
Nothing goes live until you click Deploy.
The assistant can change anything. It cannot publish anything. Every edit lands in a draft you can open, read and reject — and the site the public sees does not move until you say so.
It is the one thing we refuse to automate.
See the loop on your own site.
Half an hour, on your website rather than a slide deck. We run the audit first, so the call starts with findings.