How to Design a High-Converting Landing Page in Claude Design
Go from a rough brief to a polished, on-brand landing page you can deploy straight from the browser, without opening Figma.
Why the brief is the whole game
The single biggest lever on output quality in Claude Design is not the tool itself. It is the brief you bring into it. Vague inputs produce pretty, generic pages. Specific inputs produce pages that convert.
Before you open Claude Design, find one landing page in your category that you know performs well. For e-commerce, look at high-rated Shopify templates or Amazon product pages. For consulting or coaching, find a page from someone whose positioning you respect. Search 'best [your niche] landing pages' and screenshot the one that feels right.
Then write a brief that answers three questions: Who is this page for and what do they already know? What exactly are you selling, at what price, on what terms? And what is the one action a visitor should take? Stop there. One CTA. No exceptions.
Borrow conversion patterns people already trust
Go one step further than your reference screenshot. Find a conversion pattern from a site visitors already use daily and tell Claude Design to mimic it for your CTA. Amazon's add-to-cart flow and YouTube's subscribe button work because hundreds of millions of people have already trained their fingers on them. You can borrow that muscle memory.
Screenshot the specific interaction pattern you want to reference - not the whole page, just the element. Drag it into the input alongside your brief and tell Claude Design exactly what you want it to do: 'Make the checkout flow as similar to Amazon as possible to take advantage of pattern matching.' Claude Design treats that as a design constraint, not a vague suggestion.
Start with a wireframe, not a full build
Go to claude.ai/design and start a new project. Click 'Create Wireframe' first, not the full site build. There are two reasons for this. Wireframing uses fewer tokens, which matters on longer sessions. And seeing the structure before Claude commits to colors, imagery, and typography makes iteration far cheaper.
Drag your reference screenshot and your pattern screenshots into the input. Paste your brief. Add the URL of a site whose visual style you want to match and Claude Design's web-capture tool will pull its colors, fonts, and components automatically. Then write your prompt. Be specific about variations: ask for three to five, not one.
One file format note: Claude Design does not accept HEIC files, which is the default format when you airdrop images from an iPhone. Convert to PNG or JPEG before uploading or the upload will fail without a clear error.
A prompt you can adapt
This is the structure of the example prompt used in the original Rundown University guide. Adapt the variables for your own offer and make sure you name the specific conversion pattern you want to borrow.
Answer the brief questions, then scroll before you touch anything
After the first prompt, Claude Design will run a short interview. It asks about price, number of clients or customers, review counts, and what specific elements each section should borrow from. Answer concisely. These answers feed into the copy and social proof placeholders.
Then select three to five wireframe variations and hit generate. The first pass takes 60 to 90 seconds.
When results appear, scroll every variation top to bottom before editing anything. The structural decisions - layout, hierarchy, section order - are usually correct on the first pass. What actually needs fixing is copy specificity and CTA wording. Do not start clicking into inline edits until you have reviewed every variation in full.
Refine in the right order
Claude Design gives you two refinement paths. Use them in sequence.
Start with the Tweaks menu in the bottom right. This lets you test different color schemes and layout variations without committing to any change. It is the fastest way to explore without burning tokens on a full regeneration.
Then use inline comments for targeted polish. Click any element on the page and leave a note. You can save the comment for a later batch edit or hit 'Send to Claude' to action it immediately. Useful inline prompts include: 'Rewrite this CTA to be outcome-specific, not generic', 'Add a testimonial placeholder here', and 'Tighten this paragraph, it is three sentences of fluff'.
There is also a Grab Web Element bookmarklet in the tools menu that most users miss. Drag it to your bookmarks bar once, then click it on any webpage to pull any element - a nav bar, pricing card, or hero block - directly into Claude Design. This is the fastest way to incorporate a specific pattern you found after the initial generation.
Export paths and when to hand off to Claude Code
When the page is ready, you have four export options. Standalone HTML deploys to any host. Canva works for team review or additional visual polish. PDF covers stakeholder sign-off. PPTX is useful if the page doubles as a sales asset.
For pages that need real logic - live forms, calculators, booking integrations, or signup flows - the better move is the Claude Code handoff. Claude Design and Claude Code share a project format. You can copy a single command into a local Claude Code session or send the whole project to Claude Code on the web without spinning up a local instance at all.
Claude Design handles the visual shell. Claude Code makes it functional. Treat the handoff as the intended workflow for anything beyond a static page, not a workaround.
Before you ship
- Brief covers audience, offer, and a single CTA
- Reference screenshot and pattern screenshot both uploaded
- Brand URL included so Claude captures colors and fonts automatically
- Images converted from HEIC to PNG or JPEG before upload
- Three to five wireframe variations requested, not one
- All variations scrolled in full before any editing begins
- Tweaks menu explored before inline comments
- CTA copy is outcome-specific, not generic
- Export format chosen based on deployment target
- Claude Code handoff used if page requires forms or integrations
Where to take it next
Once one page is shipping, three obvious extensions follow. Generate three hero variants and A/B test them. Claude Design's variation system keeps the design system consistent across versions, which keeps the test clean and attribution accurate.
Build a page per audience segment. Consultants, agencies, and SaaS products almost always need segment-specific pages. One brief per audience, same brand system, different copy and proof points.
Hand off to Claude Code for anything that requires interactivity. Bookings, payments, and dynamic signup flows belong in the Claude Code environment, not inside Claude Design itself.
Claude Design is still early and the interface will shift over the coming months. The workflow underneath it will not. Specific brief, brand upload, wireframe first, refine in order, export. Get that loop fluent and the tool improvements compound on top of it.
Requirements
- Claude Pro, Max, Team, or Enterprise account
- Access to claude.ai/design
- A reference landing page in your niche
- A clear brief covering audience, offer, and CTA
Best For
- Marketers and growth teams shipping new pages every week
- Solo founders and indie makers without a designer
- Consultants and coaches building lead-capture pages