We started cmsworkshop because every team we worked with had the same problem: a CMS that fought the editors, fought the engineers, and fought the content. We fix that — once, properly, for one fee.
Three things we will not compromise on.
Editors first
A CMS that confuses editors is a failed project, regardless of how clean the code is. Schema choices start with how content is created and reviewed.
You own everything
Repos, credentials, schemas, docs — every artefact is yours. We do not lock anything behind a retainer.
Documented decisions
Every meaningful decision (cardinality, locale strategy, role split, preview flow) is written down so the next person to touch the project knows why.
CMS engagements shipped
Strapi, Sanity, and Contentful builds for solo founders, agencies, and product teams.
Engineering-first
Every studio member has shipped real frontend code. We design schemas around APIs, not the other way around.
Boutique by design
We take a small number of engagements at a time, so you get the attention your project deserves.
A studio engagement that doesn't behave like a typical agency.
No "discovery sprints" that go nowhere. No retainers. No deliverables held hostage. Here is what's actually different.
- Six-week discovery before anyone touches the CMS.
- Retainer required to maintain the build.
- Repo and CMS credentials live in their account.
- Schema decisions made for "future flexibility".
- You file a ticket; they bill an hour.
- Brief in, work starts within hours.
- One-time engagement. No retainer, no recurring fees.
- You own the repo, the CMS account, and every credential.
- Schema decisions made for the editors who use it daily.
- You message us in the order chat; we reply same day.
Six things that show up in your inbox, every time.
Some plans bundle more, but no plan ships less. If any of these is missing on delivery day, that's a refund — no questions asked.
CMS admin access
Your team logs in to the CMS environment with the role they need from day one.
Content model PDF
Every type, every field, every relationship — written down so the next dev knows the why.
API endpoint list
REST or GraphQL endpoints, sample queries, and authentication notes in one document.
Migration log
When migration is in scope, you get a per-record map of what moved, what changed, and what got skipped.
Editor training video
A Loom walkthrough plus a one-page PDF cheat sheet, embedded in your order chat.
Handover note
A short doc covering what we changed, why, what to monitor, and how to extend it without our help.
Want to see the deliverables before you commit?
Reach out via the contact form and we will share a sample content model document, an editor walkthrough Loom, and an API endpoint list from a recent engagement.