Every client site. Under your brand.
Give each client their own site, model and logins. Keep your agency's name and colors on the CMS, and let your AI draft the busywork.
Sound familiar
Four agency headaches.
Pick one to jump to the step that fixes it.
A different CMS for every client
Logins, plugins and updates multiply with every site you take on.See step 102Clients can see too much
One shared admin means one client’s people can wander into another’s work.See step 403New sites take days to set up
Every launch starts from an empty model and a long checklist.See step 204Content requests pile up
Small edits queue behind real work, and AI writes off-brand.See step 6How it works
Six steps, on the real app.
From the first client site to an AI that writes in that client's voice. The ring marks what to click.
Every client in one suite.
Each client gets a site with its own content model, media, people and MCP endpoint. Switch between them from one sidebar.
Fixes 01: a CMS per client
New client sites
Start from a template.
Four templates, or the structure of a site you already built. Everything stays editable afterwards.
A full product site: features, docs, pricing, blog and changelog.
White label
Your name on the door.
Set your agency's name, logo, icon and colors once. Each client site can carry its own logo and colors on top.
One brand for the CMS.
Your agency’s name, logo, icon and two colors. Text contrast is kept readable for you.
- Sign-in pages and their headline
- The sidebar and page titles
- Emails people get
- What AI apps see over MCP
Members and roles
Clients see only their site.
People join one site with one role. Start with Admin, Editor and Viewer, or make your own.
Simplified. The real matrix sets read, create, update, delete and publish for every content type, plus taxonomies, media, structure, settings and members.
AI per client
Each client's voice, kept.
Every site has its own house rules and banned words, and its own MCP URL. An AI working for one client can't touch another.
Example rules. Each site writes its own in Settings › AI guidelines.
In use
We run our own sites on it.
DeveloperLook runs its own site and its product sites from one Sitessa suite. Real numbers from that suite.
Agency plans
Tell us about your clients.
Business use, including client work, is on the Business plan. Tell us how many sites and people you have.
- Every feature, on every client site
- White label for the whole CMS
- Members and roles per site
Can clients log in to their own site only?
Yes. Invite them to one site with a role. They see that site and nothing else.
Can the CMS carry our agency's brand?
Yes. Set the product name, logo, icon, colors and sign-in text for the whole CMS. Each client site can add its own logo and colors.
How do we set up a new client site?
Pick a template or copy the structure of a site you built, then invite the client's people in the same dialog.
Can each client have its own AI rules?
Yes. Each site has its own AI guidelines, banned words and MCP URL. Super admins also get one endpoint for every site.
What if a client wants their content?
Each site has nightly encrypted backups and an export you can download, and the model is available as JSON and TypeScript.