Here’s what actually happens.
You ask — that’s your whole job. Our team drafts the change, machines and a person check it, and you approve a preview from your phone. Five steps, no hand-waving.
The lifecycle
Every request takes the same path.
No special cases, no ‘submit a ticket and hope.’ One pipeline, five steps, and you only show up twice: to ask, and to approve.
- 01
You ask.
Portal, email, or text — whichever you already use. Plain English, the same words you’d use with an assistant. No ticket forms, no dropdown taxonomy, no “category” field.
- 02
We build it.
Our team edits your actual site code in a sandbox copy — real developers working on a real site. Not a template engine, not a form filler. Your live site stays untouched until you approve.
- 03
A human checks it.
Nothing ships without review. Every change passes automated checks — build, links, visual diff — and then our review desk, before you ever see a preview.
- 04
You approve from your phone.
A before/after preview link arrives in the channel you used. Approve, or reply with tweaks and the change loops back through the same checks.
- 05
It’s live.
We put it live and confirm back to you. Every change is recorded — what changed, when, and who approved it. Full history, kept forever.
Step 1, in detail
Ask the way you already communicate.
Three channels, one pipeline. The request reads the same to us whether it came from your portal, your inbox, or your thumbs.
Portal
A simple request thread — type what you want, attach photos if you have them, watch the status move. Every request you’ve ever made lives here, with its preview and its outcome.
- Tue, 9:14 AM “Swap the hero photo to the new Lakeview listing shots and add Maria to the team page.”
- Tue, 9:15 AM Request logged. Status: in progress. You’re done here.
- Tue afternoon Preview ready — before/after link posted to the thread.
- Whenever you look You approve. Live.
Forward photos, reply to old threads, write three sentences or thirty. The preview link comes back in the same thread, and “approved” in a reply is a real approval.
- Wed, 7:48 AM “Forwarding the new team headshots — replace the old ones on the About page.”
- Later that day Reply lands in your thread: before/after preview link, reviewed and ready.
- Whenever you reply You answer “approved.” We ship it.
Text
For the requests that happen in a parking lot between showings. Text it like you’d text an assistant; the preview comes back as a link you can check from your car.
Turnkey
Your website team
Sat, 10:02 AM
Later that morning
Step 2, in detail
Real developers, working on your real site.
Your site on Turnkey is real code — pages, styles, components. Not rows in a database rendered through someone’s template. That matters, because it means changes aren’t limited to whatever slots a template left open.
When your request comes in, our team opens a sandbox copy of your site’s code and makes the change the way a developer would: reads the relevant pages, edits them, checks the work. If the request is “swap a photo,” we swap a photo. If the request means restructuring a page, we restructure the page.
Two things this is not:
- Not a template engine. There’s no fixed set of editable regions. If you can describe it, we can change it.
- Not a form filler. Nobody is pasting your words into predefined fields. We’re writing and editing code against your actual site.
The sandbox is the other half of the promise. We never work on your live site. Every change is a draft in an isolated copy until it has passed review and you’ve approved it. There is no state of the world where a half-finished change is visible to your visitors.
Step 3, in detail
Nothing ships without review.
This is the step vendors hide. We think it’s the best part, so here’s exactly what stands between a draft and your preview link.
Every change runs three automated checks before a person sees it:
- Build. The site compiles and every page renders. A change that breaks anything stops here.
- Links. Every internal link still resolves. No 404s introduced, no orphaned pages.
- Visual diff. A page-by-page visual comparison against your current site. Anything that changed gets flagged — including things that weren’t supposed to change.
Then our review desk — a person — looks at the result: the diff, the preview, and your original request side by side. Did the change do what you asked? Did it touch anything it shouldn’t have? Does it hold to your brand? Only then does the preview link go to you.
- 10:41 AM Change built in sandbox. Automated checks start.
- 10:43 AM Build passes. 0 broken links. Visual diff: 2 pages changed, both intended.
- 10:58 AM Review desk signs off.
- 11:02 AM Preview link sent to you.
This is why approving from your phone takes thirty seconds. The careful look already happened — twice.
Steps 4 and 5, in detail
You approve. It ships. It’s on the record.
The preview link shows your site before and after the change, side by side, on the device in your hand. If it’s right, approve it — we put it live and confirm back to you.
If it’s not quite right, say so in the same thread: “make the banner red, not blue.” The tweak goes back through the same pipeline — sandbox, checks, review — and a new preview comes back. It loops until you say yes. Tweaks don’t count as new requests.
Once it’s live, it stays on the record. Every change your site has ever shipped — what changed, when, which request it came from, who approved it — is in your history, forever. If you ever want something rolled back, that’s a one-line request like any other.
Watch the pipeline run on your own site.
Send us your URL. We’ll send back a video of your homepage rebuilt on our platform — free, within 48 hours.