CMS technologies
Content systems your team will actually use.
The best CMS is the one your editors don't need training to operate twice.
A CMS choice is really a choice about who edits the site and how often. We weight editor experience heavily, because a content system nobody uses means every change comes back to a developer.
What we use
And why we picked each one.
WordPress
The most widely used content system in the world.
WhyWhen your team publishes constantly and needs a large plugin ecosystem. We build custom themes, never page-builder sprawl.
Payload
TypeScript-native headless CMS.
WhyRuns inside a Next.js app with no separate service or SaaS bill. Our default recommendation for self-hosted content.
Sanity
Hosted headless CMS with a customisable editor.
WhyExcellent editing experience and real-time collaboration. The right call when you'd rather not self-host.
Strapi
Open-source headless CMS.
WhyMature and flexible, with a large plugin ecosystem. A good option where Payload's Next.js coupling doesn't fit.
MDX
Markdown with embedded components.
WhyFor developer-authored content in the repository. Zero infrastructure, but no non-technical editing.
Shopify
Hosted commerce platform.
WhyFor conventional retail, it's cheaper and faster than building. We say so rather than selling a custom storefront.
How we choose
Four criteria, in this order.
Fit
Does it solve your actual problem, or a more interesting one?
Hiring pool
Could you hire for it in India if you took the project in-house?
Total cost
Licences, hosting and the operational time to run it — not just build cost.
Exit risk
How hard would it be to leave? We don't build things you can't walk away from.
Services
What we build with it.
WordPress if your team publishes daily and wants plugins. Headless if performance and design control matter more, or if content feeds several channels. Both are legitimate — the wrong answer is choosing on fashion.
Payload for self-hosted, because it runs in the same app and uses your existing database with no SaaS bill. Sanity if you'd rather someone else operated it.
Not always. If content changes a few times a year and you have a developer, files in the repository are simpler and faster. A CMS earns its complexity when non-technical people publish regularly.