The edits you never billed
A new phone number in the footer. A price that changed. Each one arrives by email, costs a context switch, and is written off.
For agencies
Your code goes in. Your client's content stays theirs.
Build the site in your own stack, push it into SnabbSajt, and hand the client an editor that cannot break the design your name is on.
The problem
The build is profitable. The four years after it are not.
The client should be able to change what is theirs — words, pictures, opening hours — and nothing else. Most tools make you choose between giving them everything and giving them nothing.
Their canvas, not your stack
A safe client editor usually means building the site inside the tool that provides it. Your components, your repo and your CI stay outside.
A real CMS is enough rope
Hand over full editing and the design your name is on drifts. Hand over nothing and the site goes stale until someone rebuilds it elsewhere.
How it works
Four steps, none of them new to you
- 1
Build in your own code
Next.js, plain HTML, or an existing WordPress site to migrate. Nothing about how you work changes.
- 2
Convert and validate
The CLI runs the production importer's own checks and writes a checksum-protected package. Your React code is evidence, never runtime.
- 3
Push it into a draft
Sections match on their key, edits the client already made are reported as conflicts and kept, and a restore point is taken first. Nothing is published.
- 4
Hand over, then keep shipping
Invite the client as an editor. They change words, pictures and hours in plain Swedish. You push again whenever you rebuild a section.
npx @snabbsajt/cli admin pair
npx @snabbsajt/cli link
npx @snabbsajt/cli push ./site --dry-run
npx @snabbsajt/cli push ./site@snabbsajt/cli is on npm, currently 0.4.0. The full command reference lives on the developer page. For developers
Where it runs
Two hosting paths, one editor
The client's editing experience is identical either way. What changes is who serves the pages.
Hosted by us
Push the site package into SnabbSajt and we serve it. Domains, certificates, image delivery and uptime are ours. The client publishes from the editor; you never get paged.
Headless, on your own Vercel
Keep the site on your infrastructure and read the published snapshot with a read-only delivery token. A deploy hook you paste into Settings → Developers rebuilds your project when the client publishes.
The read-only delivery token used by the headless path physically cannot write. Pushing content needs a separate, capability-scoped token you approve in the browser.
Per-client control
You decide what the client can do
In Settings → Members → “What your client can do”, the workspace owner picks the client's ceiling: a website-only preset, or per-area switches for the marketing hub, invoices and offers. Switch something off and it is off on the server — the hidden surface refuses the call, so it is not a hidden button someone can find.
The client sees no trace of what you switched off, and the switches are invisible in an ordinary solo account. Bookings, services, domains and AI are not switchable yet — a feature only enters the list once its server function actually refuses.
Claude via MCP
Let Claude build and edit — inside the same limits
Connect Claude to a site over MCP and ask for the change in words. It works on the draft, it is bound by the same permissions you granted, and it never publishes without a human asking. Your terminal agent gets the same surface with the CLI's own skills installed.
Where the money is
The build stays yours. The tail stops leaking.
You bill the build exactly as today. What changes is the four years after it: the small edits stop arriving in your inbox, so the account stops costing you unbilled hours, and the site stays current long enough that nobody proposes a rebuild elsewhere. A retainer for the work you actually still do — new sections, campaigns, structural changes — is a real offer instead of a fiction.
The client pays for their own plan, or you pay and bill it on. Prices are public. See plans and prices
Not yet
Two things an agency asks for that we have not built. Read them before you plan around them.
Wholesale per-site pricing
Approved in principle, not built: there is no price to buy today. Portfolios run on the ordinary plans until it exists.
Your branding in the editor
White-label is scheduled for January 2027. Today the client logs into SnabbSajt and sees SnabbSajt.
Try it on one site before you move a portfolio
Create a builder account, convert one existing client site, and hand it over. Nothing is published until someone presses publish.