How design and brand agencies can use Craft CMS to say "yes" to more briefs
We work with design and brand agencies as their development partner, helping them say "yes" to more briefs.
"Ah, no"
You design a brilliant site, the client loves it, users love it, it's a big hit. But then, inevitably, you receive an email, like "Can we add a login portal?", "We're moving to this weird CRM nobody's heard of", etc. and you become stumped "ah, no, we can't do that".
In this post, I'll share my thoughts and experiences after working with brand agencies for over a decade, and how you can say yes to more.
The problem is the platform
Webflow and WordPress are both really good tools and can help you get up and running quickly. However, they can both become a bit of a ceiling and ambitious clients (read: the ones who pay the most money) tend to find that ceiling rather quickly. It's not necessarily that they can't do it, even, but that doing it becomes really hard work and a bit of a bodge.
Webflow is great for getting a polished marketing site live quickly. And you've probably found that designers love the visual control. The trouble starts when a site needs to do more than display content. Its CMS has hard limits on how many items, fields and references you can have, and there's no way to write your own server-side logic, so when a client asks for something outside what Webflow offers, the honest answer is often "we can't", or "we can, if we bolt on three third-party services".
WordPress is more malleable, but usually through plugins. A complex WordPress site can end up relying on dozens of them, each with its own updates, security patches and quirks. Content gets forced into a model of posts and pages that was built for blogging, and themes or page builders often work against the design rather than with it.
A better platform would still allow you to do Day-1 excellently, but scale up for years to come.
Enter, Craft
Craft CMS is a content management system built by Pixel & Tonic. The simplest way to describe it is that it gives you a blank canvas rather than a starting template.
There's no theme to adapt and no visual builder generating markup behind the scenes. Developers define exactly what content a site needs, then build the front end from scratch to match the design. Every page, component and interaction is built the way it was designed, not the way a platform prefers. The detail you agonised over in the Figma is the detail that ends up on the live site.
It's a bit more work upfront, so is slower than implementing in Webflow, but it lays a real foundation you can build on.
You CAN do that
Craft is built to be extended. Developers (like us) can write custom modules and plugins that add almost any functionality a project needs: booking systems, member areas, gated content, calculators, integrations with CRMs, ERPs and booking engines, or logic unique to a client's business.
That means a site can grow with the client. When they come back with a new idea, the conversation is about how best to build it, not whether it's possible.
Content that fits the client
In Craft, the content structure is designed around each project. A university, a property developer and a fashion brand all get a content model that reflects how they actually work.
Editors also get flexible page-building through Craft's Matrix fields, letting them mix and arrange content blocks freely while the design stays intact.
They get freedom where it helps and guardrails where it matters.
We've written a bit about how we make page builders in Craft, it's worth a read.
Clients love it
Craft's control panel is clean and uncluttered. Live preview, drafts, revisions and scheduled publishing come as standard. Clients feel in control without being able to accidentally break the layout you designed, which means fewer panicked support emails and a site that still looks right a year after launch.
Room to grow
Craft handles multi-site and multi-language setups from a single install, so a group of brands or an international client can be managed in one place.
It can run headless via GraphQL when a project needs an app or a separate front end (which, by the way, we can also help with). And Craft Commerce brings genuinely bespoke e-commerce for clients who've outgrown off-the-shelf shops - or Shopify integration for those who haven't.
The catch: you need expertise
Craft isn't a drag-and-drop tool, and you can't hand it to a designer and expect a site at the end. It needs experienced developers who know PHP, Twig templating and Craft's own way of doing things.
For most design studios, building that capability in-house is a big step. You'd need to hire, train and retain developers, then keep them busy between projects. That's a big overhead, and a risky one if your work comes in peaks and troughs.
Partnering with us on Craft builds changes what your studio can sell. You can pitch confidently for larger, more complex projects that would otherwise go to full-service agencies or get turned down.
You keep creative control and the client relationship, without the cost and risk of an in-house development team. You only pay for development when there's a project to build.
And because Craft sites grow rather than hit a wall, there's room for ongoing work after launch. New features, campaign pages and integrations become retainers rather than awkward conversations.
Craft isn't always right
Craft isn't the answer to every brief, and we'll always tell you when it isn't. A simple brochure site of a few pages with a tight budget and a short shelf life might be better off on Webflow.
Craft earns its place when a site is expected to evolve, needs to connect with other systems, carries complex or structured content, or has to serve several brands, regions or languages.
If a client is likely to come back next year with bigger plans, it's worth building on something that can keep up.
If you're not sure which side of the line a project falls on, that's a good conversation to have with us early.
Let's chat
If you're interested to see how Craft CMS could work for your agency, and how we could be a development partner for you, contact us on hello@mutual.agency
Andrew is Technical Director at Mutual, a Craft CMS Partner agency. He has been building with Craft CMS since its public beta in 2012 — working through every major version from Craft 1 to Craft 5 — and has delivered over 100 sites for clients including Apple, Transparency International, and Arts University Bournemouth.
He writes about Craft CMS on the Mutual blog and has contributed to net Magazine. At Mutual, he leads development of Mutual One, a marketing platform built on Craft CMS as its foundation.
He has spoken about Craft CMS to undergraduate students at the University of Brighton and Canterbury Christ Church University, and appeared on the Devmode.fm podcast. He has also trained other developers on working with the platform.
More from the blog
The Best Craft CMS Learning Resources in 2026
Where we'd send a developer learning Craft CMS in 2026: the official docs and tutorial, CraftQuest, the Discord, the newsletter and the conference talks.
Common Accessibility Problems to Avoid in 2026
The accessibility problems we still see most often, what WCAG 2.2 and the European Accessibility Act changed, and how to catch what automated tools miss.
Should you be worried about the rise in high-severity Craft CMS security updates?
Craft has had a huge increase in security patches this year. But don't be alarmed, it's a sign of the times and that Craft is dealing with things responsibly.