Claude Design has launched. Here’s what it means for your marketing team.
The launch of Claude Design is prompting a question that a lot of marketing teams are asking right now. What AI tools are actually going to be useful for us, and how do we implement them into our workflow in a way that makes sense?
It’s a good question, and it deserves a straight answer. Not the one Anthropic would like you to arrive at, which is that tools like Claude Design and Claude Code can handle everything from concept to production.
For small websites, there’s some truth to that. For enterprise, the picture is more specific.
Here’s what’s actually useful, what isn’t, and what you need to have in place either way.
What Claude Design actually does
Claude Design is Anthropic’s new visual design tool, launched in research preview for Pro, Max, Team and Enterprise subscribers. Feed it a prompt, point it at your design system, and it generates layouts, prototypes, slides, and one-pagers. It can read your existing codebase and design files and apply your colours, typography and components automatically. Designs can be exported to Canva, PDF, PPTX, or standalone HTML, and there’s a handoff feature that packages everything for Claude Code.
Independent design critics have been measured in their assessment. Writing in Medium, designer Michal Malewicz observed that the output is competent but template-level, not substantially different from what Claude Code already produces, and broadly in the same territory as other generative design tools that promised more than they delivered. The outputs are okay. Not exceptional. Good enough to work from, not good enough to publish without review.
That’s actually a useful framing, because it tells you exactly where the tool fits.
Where it’s genuinely useful: early-stage prototyping
Think about the standard briefing process for a landing page. Someone hands over an A4 document full of copy (almost always too much copy) and a developer or designer has to turn that into something visual. Several rounds of back-and-forth later, you have a wireframe that roughly captures what was meant. That process is slow, and the brief rarely survives contact with the first design.
Claude Design can compress a lot of that. Write your copy, point it at your design system, and ask it to generate a landing page. What comes back will be a competent visual interpretation of your brief, close to your brand, with your components in roughly the right places. Bring that into a room, get feedback, iterate. You can get much further down the line before you involve a developer or a designer, and the brief you hand over at the end of that process will be significantly sharper.
That’s the right use case: early-stage exploration, concept development, and getting to a working brief faster. Not finished design. Not production-ready pages.
One honest caveat on cost: Claude Design runs against your subscription limits, with the option to pay for extra usage beyond that. Early reports suggest that even a handful of pages consumes a significant portion of a week’s allowance. For teams thinking about using it regularly for page creation, that’s worth factoring in before you build a workflow around it.
Get your design system in order first
None of this works well without a well-organised design system as the foundation. Not a loose collection of UI elements. A properly structured system that specifies what exists, how components behave, and how they relate to each other. At Temper, we put all client design systems into Storybook. Before anything else, we get the design system in order, establish who is allowed to make changes to it, and agree who signs those changes off.
The reason this matters: without it, three people on your team making pages with AI tools will produce three subtly different interpretations of your brand. Each of them makes small decisions (adjusting a component here, tweaking a layout there), none of it goes through review, and within weeks you have a website that looks like it was built by three different organisations.
The governance questions are straightforward: who owns the design system, who can change it, and what has to go back through a review process before it goes live? If you can answer those, you’re in good shape. If you can’t, sort that first.
The CMS point worth making
Claude Design includes a handoff feature that packages designs for Claude Code to build. For most enterprise marketing teams, that part is redundant. Your website isn’t built with Claude Code. It is built on an enterprise CMS with a frontend attached to it, managed by a technology partner. Handing a Claude Design prototype to Claude Code doesn’t fit that workflow.
The more useful observation is this: the capability Claude Design offers for page creation (generating layouts from a design system and pushing them into a publishing environment) really belongs in your content management system, not in a standalone AI tool. If your CMS doesn’t support this kind of workflow today, it probably will within the next few months. Before building a process around an external tool, it’s worth asking your CMS provider what’s on their roadmap.
The hype and the reality
Every new AI tool launch comes with the same subtext: maybe now you don’t need designers, developers, or agencies. Claude Design is no exception. Anthropic would like you to think this changes everything about how websites get built.
For small sites, there’s something to that. For enterprise websites with complex CMS setups, governance requirements, and teams of people creating content, the reality is more limited and more specific. Prototyping and early-stage exploration: genuinely useful. Replacing your CMS workflow or your development process: not what this tool is for.
Use it for what it’s good at. Get your design system in order so it has something to work from. And keep an eye on what your CMS can do, because that’s where this kind of workflow will eventually land.