For agencies
Hand it over without handing over the maintenance.
Build the site once, then let the client add collections and fields themselves. What they do cannot break what you shipped, so the handover actually ends.
A collection is a table: entries are rows, the fields marketing added are columns, and everyone editing it can see everyone else.
What changes.
- The support queue shrinks
- "Can you add a field for us" stops being a line item. The client adds it, and the site keeps working because a model change can never fail a build.
- Your stack, not ours
- Stet serves content through an API and a typed client. Whatever you build in, and wherever you deploy it, stays your decision.
- One CMS across the roster
- The same tool for every client instead of whichever CMS each of them arrived with. Your team learns it once.
- Per-client hosting
- Put each client on their own hosted workspace, or self-host on infrastructure you or they control when the contract requires it.
- Cost you can quote
- Ten dollars per person per month, with no per-project fee and no jump to enterprise pricing the moment a client needs a second locale.
The parts you will live in.
Everything is on every plan, but these are the ones that will matter to you first.