One system.Three parts.Yours to run.
Every part ships with the Handover and runs on the Approval Loop. Each service inside a system can also be bought on its own.
From the studio.
Free tools and passion projects we built to make design better for everyone.
The website your team updates by asking.
A site built on a stack you own, with the Approval Loop built in. Your team asks for a change in plain English, gets a preview, approves it, and it's live. No tickets. No developer wait. No Ticket Tax.
The Approval Loop: ask, preview, approve, live.
No tickets. No waiting on a developer. No wondering what changed. Every update to your brand, your site, or your campaigns runs the same four steps.
Ask.
Someone on your team writes what they need, in plain English, in the channel they already use. “Update the Q4 market commentary and swap the team photo.”
Preview.
A link comes back with the change in place. Nothing is live yet.
Approve.
The person you named clicks once. For regulated teams, that person is compliance.
Live.
The change ships and a line lands in your Change Log: who asked, who approved, and when.
The Site System is where the Approval Loop lives. The Brand and Growth Systems plug into it.
Designed to run long after launch.
Design
UX, UI, and prototypes, designed around the content your team will change most.
Build
Sanity CMS, Vercel hosting, GitHub source, in accounts in your name.
Content schema
Every section typed so your team can change it without breaking it.
AEO foundation
Schema markup, FAQ blocks, llms.txt, and semantic HTML so AI engines cite you and Google ranks you.
Analytics
Tracking and reporting installed before launch.
Risk tiers
Every section marked content, layout, or structure. That's what the Guardrails run on.
The Handover, Site System edition.
Your request channel
A form, Slack, or email. Whatever your team already uses.
A preview for every change
See it before anyone else does.
One-click approval
By the person you name. For regulated teams, that's compliance.
The Change Log
Who asked, who approved, and when. Exportable for audits.
Training
An account setup call, a 45-minute team session, and an SOP for every common request.
Build freely. Nothing breaks.
Your team runs
- New pages built from your approved sections
- Copy, images, and section layouts
- New posts, team members, offers, and events
- Anything the Approval Loop can preview
The Guardrails protect
- Fonts, colors, and spacing locked to your brand
- Approved sections that work on every screen
- A preview and sign-off before anything goes live
- Risk tiers on every section: content, layout, or structure
Migrate what you have, or build new.
Migrate.
Your current design, moved onto the Site System with your existing content. Up to about 10 pages and 25 posts. Two to three weeks.
Build.
A new design inside your existing brand, on the Site System. Six to ten weeks.
Brand and Build.
New identity and new site together. Custom. See the Brand System.
All three include the Handover and run on 5Four® Run after launch.
See 5Four® RunThe No-Hostage Rule. You own it. All of it.
The code, the content, the assets, and the hosting live in accounts in your name. We work as an admin on them, never the other way around. If we ever part ways, you keep a complete working site, every template, and every file. You lose the Approval Loop and the assistant upkeep we run for you, and nothing else.
We call it the No-Hostage Rule because most agencies won't put it in writing. We will. It's in every contract.
Work
Common questions, answered.
The Site System is a website built on Sanity, Vercel, and GitHub in accounts you own, plus the Approval Loop, the Change Log, and the training your team needs to update it without a developer. It's the part of 5Four® Systems that the Brand and Growth Systems plug into.
Yes. A migration keeps your current design and content and moves them onto the Site System. It takes two to three weeks. We run an assessment first so the scope and quote are fixed before work starts.
No. Your team writes requests in plain English. The Approval Loop turns them into changes, shows a preview, and waits for approval. Nobody on your side touches code, and nobody has to.
It routes to us. Requests for something new to the system, like a new section design or an integration, land with your 5Four team and get scoped the same day. You always know which side of the line a request is on.
You do. The No-Hostage Rule: your accounts, your name, our admin access. If we part ways, you keep a complete working site and lose only the Approval Loop and the upkeep we run for you.
Ready to run your own site?
Structure creates freedom.
Book a Strategy Call