I have been playing more with Claude Design, and my take is that people are underrating it in a slightly wrong way. Most of the conversation is still kind of: “can it make a nice landing page?” And yeah, it can. The output has gotten insanely good in my opinion. Better spacing, better sections, better taste, less of that default AI SaaS-card schieße. I was a big fan of Google Stitch, but Claude Design is just on another level. But the part that I care about is what happens after the page exists. For the people I work with, making the page look good is almost never the bottleneck. The real problem is whether the page matches the ad, the form captures the right info, the events fire correctly, and the CRM gets enough context to judge the lead. A landing page made with Claude/Codex can sit inside the same workspace as the repo, tracking plan, ad angles, CRM fields, form logic, design drafts, analytics notes, etc. That changes the job from “make me a pretty page” to “make me a page that actually belongs in the acquisition flow.” Which sounds obvious, but this is exactly where a lot of the work gets weird. For example: the ad promise says one thing the page headline says something slightly different the form asks for the wrong thing GA4 event names are messy the CRM never gets the fields needed to judge lead quality offline conversions do not make it back to the ad account That whole chain is usually split between designer, dev, marketer, analyst, and some half-dead Zapier/n8n workflow nobody wants to touch. And this is boring stuff, but it is also the stuff that decides whether the page actually makes money or just looks nice. This is where Claude design gets interesting to me. If the model can help create the page and Codex can inspect the repo/scripts/tracking files around it, design becomes one piece of the agent stack. That sounds like a tiny distinction, but for me it changes the whole thing. I do not mean “let the model run your business while you sleep.” (although we are honestly getting there ngl) I still think you need human taste and someone who knows the business. A model will absolutely make confident dumb choices if you give it vague context. But if the workspace has real context, it gets a lot more useful: build the landing page adapt it to the actual offer match the ad angle wire the form correctly check if the events actually fire compare page copy against CRM lead quality later create another variation based on what actually happened, not just vibes My current opinion is that people are treating AI design like a toy because they stop at “does this page look good?” The real value is when the design lives next to the code, tracking, ads, CRM, and logs. Curious if anyone else is using Claude this way. Are you mostly using it for prototypes and vibes, or are you letting it touch production pages / tracking / conversion flows with Codex or other agents around it? I have this running for almost all my clients by now. I couldn’t imagine it any other way. submitted by /u/kaancata
Originally posted by u/kaancata on r/ClaudeCode