For Agencies

Idiate, create, ship and deliver, all in the in same tool

Build your clients website in a

Keep the craft. Lose the coordination tax.

Client-safe editor

Give clients a visual editor without teaching Git or Markdown.

Stop design drift

Stop design drift when marketers and AI tools edit the same brand.

A tool you own

Instead of renting access to be able to manage your client sites, you own Splitleaf for ever.

Where agency hours get lost

The CMS is either too heavy or too technical

Hosted builders and headless CMSes solve different problems. One often owns the client relationship. The other usually needs developers. Neither feels right for AI-generated static sites that still need ongoing edits by people with little knowledge of the web.

Clients cannot update without opening a ticket

Email threads, design screenshots, and "can you change this headline" messages eat retainers. The update is simple. The handoff is not. This eats time from other projects.

AI pages live outside the system

One-off AI pages look fine alone. Put six of them on one brand site and the design language frays. Agencies need components and classes that hold the line.

Handoff becomes a second project

Moving a site to the client often means reconfigure hosting, new workspace plan and slow transfers. With Splitleaf you switch owner in seconds.

Look more professional while staying portable

Design system that survives client edits

Components, brand panel and class-based styles keep agents and marketing from inventing a new aesthetic on every page.

Visual editing

Edit your site visually with shared classes and components. Fullt support for all modern HTML elements and CSS targeting.

Splitleaf handles Git for you

When several people edit the same site, Splitleaf reconciles before publish. Same-item conflicts become a simple choice: keep mine or use theirs.

Local asset libraries

Link local asset folders so brand libraries stay on disk, not in another upload queue.

How a typical agency project runs

1

Open the client site as a real folder

The site lives on disk as HTML, CSS, content files, and .opt-one/ config. Clone is your export button.

2

Build pages inside a shared design language

Use the Designer for layout and classes. Use Content for collections, drafts, and ready-to-publish items.

3

Invite the client as a site collaborator

They edit copy and media. They do not need a GitHub account. Auth is application-level. Git stays invisible.

4

Publish, then hand off when ready

Connect the host once. After that, publish is one deliberate step. When the engagement ends, move the site to the client workspace. They own the files. You keep the relationship option.

Common questions from agencies

Can clients update content without learning Git?
Yes. That is the point. Git backs every publish. Clients never see it.
What happens when we hand a site to the client?
Sites belong to workspaces. Moving a site is a workspace ownership change. Content stays in the repo. Hosting stays the client's choice.
How is this different from hosted builders for agency work?
Splitleaf does not host your site or lock content into a proprietary runtime. You bring your own host. Output is clean static HTML/CSS. You can leave with git clone.
How does pricing work for multi-client shops?
Build as many sites as you want. Each person who runs the app buys a one-time license. Collaboration beyond the included two free users per site is metered on the workspace. Six client sites with one collaborator each cost $0/mo; a client site with three collaborators costs $6/mo.
Will AI-generated pages stay on-brand?
They stay closer when you edit through classes and components instead of one-off hard-coded pages. Splitleaf is built for that maintenance problem, not only the first ship.

Spend less time coordinating. Keep more of the craft.

Use Splitleaf when you want client content work to feel clean, repeatable, and portable — without putting another landlord between you and the content your agency creates.

Launching soon