The short answer

An AI landing page builder is not a drag-and-drop tool, it’s Claude AI plus a precise brief. Feed it your business, your customer, and one goal in a structured prompt and it writes a complete, responsive HTML landing page you can paste onto WordPress or Shopify in an afternoon.

  • The tool isn’t the barrier, the brief is. Claude follows instructions literally; vague in, generic out.
  • Structure the prompt with XML tags: context, tone, design, rules, task. Anthropic recommends them when a prompt mixes instructions, context and examples.
  • Give it examples of copy you love and copy you hate. One example beats fifty words of description.
  • Iterate one change per message, stay in the same chat, and preview in codepen.io before it touches your live site.
  • Cost: $0 on Claude’s free plan. Time: about two hours from brief to live page.
Short on time to do this yourself? This is the exact work I set up for service businesses, done for you, and the system is yours to keep.

Get me to do it →

I know a little code, but I’m no developer. Now with Claude AI I’ve built multiple professional landing pages and websites, ones that convert, look sharp, and would cost thousands if you paid someone else to build them. The gap between “I can’t do this” and “I just did this” is almost entirely a prompting problem. This guide closes that gap.

The Real Barrier Isn’t Coding. It’s Briefing.

The most common reason people get bad output from Claude is simple: they open the chat and type something like “build me a landing page for my business.” Claude obliges with something generic: corporate headings, filler copy, beige aesthetics. Then they conclude the tool doesn’t work.

The tool works. The brief didn’t.

Claude follows instructions precisely. It takes you literally. If you give it no information about your business, your customers, or your goals, it fills the gaps with the safest, most generic version of everything. That’s not a failure of AI. It’s the same failure you’d get briefing a human designer with three words.

The output quality is almost entirely a function of brief quality. This guide is, at its core, a briefing guide. The technical side is simple: generating code, iterating, deploying. The part that takes thought is the same part that always takes thought in marketing: knowing what you want and being able to articulate it clearly.

The mindset shift. Stop thinking of Claude as a tool you use. Think of it as a contractor you’re briefing. A great contractor with a vague brief produces average work. The same contractor with a detailed, specific brief produces exceptional work. Your job is to be the best client you’ve ever had.

What You Need Before You Open Claude

Spend 20 minutes answering these six questions before you start. Write them in a notes app or a Word doc. You’re going to paste them almost verbatim into your first message. Don’t skip this step. The time you spend here determines the quality of everything that follows.

1Who you are and what you do.

One or two sentences. Specific. Not “I help businesses grow.” That tells Claude nothing. Be precise about your trade or service, your location, and what makes you different.

Weak: “I run a marketing consultancy.”
Strong: “I’m a bookkeeper in Brisbane who specialises in sole trader tradies (plumbers, electricians, builders). I take over their BAS, payroll, and reconciliation so they stop losing money to mistakes and late ATO penalties.”

2Who your ideal customer is.

Not “small business owners.” That’s the Australian economy. Describe the specific person who is your best customer: their work, their situation, their pain, and what they’re usually worried about.

Weak: “Business owners who need accounting help.”
Strong: “Sole trader tradies, 1-3 employees, $300K–$800K revenue, usually behind on their books, stressed about tax time, don’t have time for paperwork and hate sitting at a desk.”

3One conversion goal. One.

A page that tries to do everything converts nothing. Pick one action you want visitors to take. If you can’t decide between two, build two separate pages, one for each goal.

Options: Book a free 30-min call. Download a checklist. Request a quote. Register for a workshop. Sign up for a free trial. Submit a contact form.

Not: “Learn about my services, follow me on social, and maybe book a call.”

4Your real credibility.

This is where most people undersell themselves. Write down every real result, number, year, or proof point you have. You don’t have to use all of it, but give Claude the ingredients and let it choose what’s most compelling.

Examples: “12 years in the industry. 140+ tradie clients. Average client saves $6,000 in their first tax year. 4.9 stars across 38 Google reviews. Qualified CPA.”

5Tone in plain English.

Describe how you want the page to feel. Don’t use design jargon. Use the language you’d use talking to a mate about how you want to come across to clients.

Examples: “Like I’m a mate who’s been there, not a suit trying to sound impressive.” / “Direct and confident. No fluff. Get to the point.” / “Warm but professional. Trustworthy. Like a GP you’ve known for years.”

6Design references (optional but valuable).

Find 2–3 websites you like the look of. They don’t need to be in your industry. Note what specifically appeals to you: colours, layout, the feel. Claude can search the web, but a site name alone won’t tell it what you like, so describe what appeals to you.

Example: “I like rippedbody.com: clean, lots of white space, big bold headings, very content-focused. I also like how Basecamp’s homepage is direct and doesn’t try to impress you.” Then describe the palette: “Dark navy and white. One strong accent colour, orange or red. Clean, modern, no gradients.”

How Claude Actually Processes Your Instructions

Before we get into the prompts, it’s worth understanding how Claude reads what you write because it directly explains why some prompting approaches produce dramatically better results than others.

Claude’s latest models are trained for precise instruction following. They follow what you write closely, which is powerful when your instructions are clear and useless when they’re vague. Unlike older AI models that would interpret and expand on imprecise requests, current Claude models stay close to what you explicitly say.

This has a practical implication: the more specific your instructions, the better the output. “Make it look professional” means nothing. “Use a dark navy (#0F1D38) background for the header, white body text, and one orange accent colour (#E05A1B) for all buttons and highlighted text” means everything.

It also means that what you don’t say is as important as what you do say. If you don’t specify a word count, Claude will write as much as it thinks is appropriate. If you don’t specify a tone, it defaults to something neutral and corporate. Every undefined variable gets filled in with a generic default. Your job is to eliminate as many generic defaults as possible.

Operator note. Anthropic’s own documentation says: “Being specific about the output you want can help enhance results. If you want Claude to do more than the task strictly requires, explicitly request it rather than relying on the model to infer this from vague prompts.” Read that twice. Vague = generic. Specific = useful.

One more thing worth knowing: context ordering matters. Anthropic says that with long inputs (around 20,000 tokens or more), putting your question at the end can improve response quality by up to 30 percent. If you have long background information to provide (your business details, a design brief, reference examples), put it first, then put your actual instructions at the end. The question comes last, not first.

The First Prompt: How to Brief Your AI Landing Page Builder

Your first message to Claude is the most important one. Don’t be conversational. Don’t ease into it. Give Claude the complete brief in a single message. Think of it like emailing a contractor who needs everything upfront to quote accurately. You wouldn’t drip-feed them information across five emails over three days.

Use AI to do it

The first-prompt template, copy and customise

Here’s the structure that consistently produces professional output. Fill in the brackets and paste it as your very first message to Claude:

I need you to build a single-page HTML landing page for my business.
Here’s everything you need:
<business_context>
Who I am: [1-2 sentences, your service, location, what makes you different]
My customer: [Specific: trade, revenue range, situation, what they’re worried about]
Page goal: [ONE action: book a call / download guide / request quote]
My credibility: [Real numbers: years, clients, results, reviews, qualifications]
</business_context>
<tone>
[Describe in plain language, e.g. “Direct, no fluff, like a trusted tradie
not a consultant. Australian. Gets to the point.”]
</tone>
<design_direction>
Colour palette: [e.g. “Dark navy and white, one orange accent colour”]
Typography: [e.g. “Bold uppercase headings. Clean readable body text.”]
Feel: [e.g. “Clean and confident. Generous whitespace. Not corporate.”]
Reference: [Describe 1-2 sites you like and what specifically appeals to you]
</design_direction>
<page_structure>
Must include:
– Navigation bar with my business name and one CTA button
– Hero section: headline speaking to my customer’s problem, sub-headline,
and [lead capture form / book-a-call button / quote request form]
– Credibility section: [stats / proof points / client results]
– What I do and why it matters: [2-3 core points]
– How it works: [3-step process if applicable]
– Social proof: [reviews / testimonials placeholder]
– Second CTA section at the bottom
– Footer
</page_structure>
<copy_rules>
– Hero headline must speak to the customer’s pain, not my service
– Never use: “look no further,” “we’ve got you covered,” “one-stop shop,”
“we pride ourselves on,” “solutions tailored to,” “passionate about”
– CTA button text must be specific (not “Submit” or “Click Here”)
– All copy should sound like a real person wrote it, not a marketing department
</copy_rules>
<technical>
Output: Single complete HTML file with all CSS embedded in the <style> tag.
No external CSS files. Google Fonts for typography is fine.
Must be fully responsive (mobile-first).
</technical>

One structured message in, one complete single-page HTML file out. Everything after this is refinement.

That <technical> block matters enormously. Asking for a single HTML file with all CSS embedded means you get one file you can paste anywhere. No missing stylesheets, no broken dependencies, no “where does this file go?” confusion. One file. Paste. Done.

XML Tags: How to Prompt Like Anthropic Does

You noticed the <angle_bracket_labels> in the template above. Those are XML tags, and they’re the single biggest structural upgrade you can make to your prompts. Anthropic’s own documentation recommends them when a prompt mixes instructions, context, examples and inputs, because they help Claude read each part without mixing them up.

The reason is simple: when you write a long prompt in plain paragraphs, Claude has to infer where the instructions end and the examples begin, where the rules stop and the context starts. It usually gets it right, but “usually” isn’t good enough when you’re building something important. XML tags eliminate the ambiguity entirely.

❌ Without tags. Everything runs together in one paragraph:

Build a landing page for my bookkeeping business. I serve tradies in Brisbane. They hate paperwork. I want it to look clean and professional with dark colours. Don’t use boring corporate language. Include a form to book a call. Here’s a sample of my tone: “We take the headache out of your books so you can get back on the tools.” Use my results: 140 clients, 4.9 stars, 12 years. Make the headline punchy.

✅ With tags. Every component is labelled and unambiguous:

<context>
Business: Bookkeeping for Brisbane tradies
Customer: Sole traders hating paperwork
Results: 140 clients, 4.9★, 12 years
</context>
<tone_example>
“We take the headache out of your
books so you can get back on the tools.”
</tone_example>
<design>
Dark, clean, professional. Not corporate.
</design>
<task>
Build a landing page with a book-a-call
form. Punchy hero headline.
</task>

Both prompts contain the same information. The tagged version is easier for Claude to read, because each part is labelled. The context doesn’t bleed into the tone. The example doesn’t get confused with the instructions. The task is unambiguous.

Which tags to use. You don’t need a specific set of tag names, Claude understands any descriptive label. Common useful ones: <context>, <customer>, <tone>, <design>, <rules>, <examples>, <task>. Pick labels that make sense to you. Consistency matters more than the names themselves. Use the same tags every time you revisit a prompt and Claude will recognise the structure instantly.

The Single Most Powerful Prompting Technique

Anthropic calls this “few-shot” or “multishot” prompting. It means giving Claude examples of exactly what you want and what you don’t want, rather than trying to describe it in words.

Here’s why this outperforms every other technique: describing tone takes 50 words and still leaves room for interpretation. A single example removes all ambiguity in 15 words. The example communicates what the words can’t: rhythm, word choice, personality, level of directness, what gets left out.

The technique is simple. For every output you want Claude to produce consistently, find two real examples:

  1. Something you love (a headline, a piece of copy, a web section from any site) that captures the feel you want.
  2. Something you hate (generic AI copy, something from a competitor that sounds terrible, anything that captures what you’re trying to avoid).

Then label them explicitly and explain the difference. Anthropic suggests three to five varied examples for best results, so add more if you have them. Don’t just show the examples. Tell Claude what you see in each one. That explanation is what gets carried forward into the output.

<copy_examples>
<good_example>
“Your accountant charges you for every email.
Mine charges you to never worry about tax again.”
Why this works: Leads with the customer’s pain (expensive, reactive accounting),
lands on a specific promise (peace of mind, not just a service). Human voice.
</good_example>
<bad_example>
“Professional Bookkeeping Services for Small Businesses.
Reliable, affordable, and tailored to your needs.”
Why this is wrong: Generic. Could describe any bookkeeper in Australia. No
specific customer. No tension. “Tailored to your needs” is the most overused
phrase in professional services. Sounds like a Yellow Pages listing from 2009.
</bad_example>
<good_example>
“140 Brisbane tradies don’t stress about their BAS anymore.
You shouldn’t either.”
Why this works: Specific number = credibility. Calls out the exact customer.
References the exact pain point (BAS stress). Short. Confident.
</good_example>
</copy_examples>
Write the hero headline and sub-headline for my landing page using
the tone and approach of the good examples above.
Where to find good examples. You don’t need to invent examples from scratch. Start collecting. Screenshot landing page copy you like when you see it, even from industries completely unrelated to yours. The way a property developer writes their hero headline can be the model for your bookkeeping headline. What you’re extracting is the structural approach and the voice, not the content. Build a small file of good and bad examples, 5-10 of each, and you’ll have a reusable asset that makes every future prompt better.

What Good Output Looks Like vs What to Reject

Claude will generate code. You don’t need to read it. Claude usually opens the page in a panel beside the chat so you can see it, or copy the full output and paste it into codepen.io (free, no account needed) to see what it looks like in a browser before it goes near your live site.

Here’s what to look for:

Check Good Output Reject and Iterate
Hero headline Speaks to your customer’s specific problem. Could only be about your business. Could apply to any business in your category. Generic tension like “Take your business to the next level.”
Your results Real numbers are prominent and visible without scrolling far. Results buried at the bottom, or not used at all.
CTA button Specific action text: “Book a Free 30-Min Call” or “Get My Free Quote.” Generic: “Submit,” “Click Here,” “Contact Us,” “Learn More.”
Colours Matches what you described. One clear accent colour used consistently. Default blue links, grey background, no personality. Looks like a template.
Copy voice Sounds like a real person. Specific. Direct. “We pride ourselves on delivering exceptional customer experiences tailored to your unique needs.”
Page structure Each section does a different job. Clear hierarchy from problem to solution to proof to action. Three sections that all say approximately the same thing in different words.
Mobile layout Readable on a phone. Buttons are easy to tap. Text doesn’t overflow. Desktop layout that breaks on mobile. Horizontal scroll. Tiny text.

If the first version passes most of these checks, you’re in good shape. Start iterating from there. If it fails more than two or three, your brief was likely too vague. Go back to the original prompt, add more specificity to the failing areas, and ask Claude to regenerate the whole page.

How to Iterate Without Starting Over

The first version is the starting point, not the goal. Every professional output goes through multiple passes. The advantage of working with Claude is that iteration is instant and free. No waiting on a developer, no additional invoice for revisions.

The single most important rule: one change per message. Don’t say “change the colours, fix the headline, move the form to the top, and add a testimonials section.” Claude will attempt all four simultaneously and introduce new problems while fixing old ones. One request. See the result. Then the next request.

Keep the conversation going. Stay in the same chat tab. Claude remembers the entire page within a single session. Closing the tab is fine. The chat stays in your history. A new conversation won’t see the page, so go back to the original chat or paste the latest code in. Before closing, copy the latest complete HTML from Claude’s last output and save it somewhere.

Here’s how to phrase different types of changes:

1Rewriting copy.

Tell Claude what’s wrong with the current version and what direction to take it. Don’t say “make it better.” That’s meaningless. Say why it’s not working.

Example: “The hero headline is too soft. It’s talking about my service, not my customer’s problem. Rewrite it to lead with the pain (the stress, the time lost, the money wasted) before offering the solution.”

2Design changes.

Be specific. Colours need hex values. Sizing needs actual numbers. Font changes need the exact font name. Visual vagueness produces visual mediocrity.

Example: “Change the primary accent colour from blue to #E05A1B orange. Update every button, link, and highlighted element to use this colour. Keep everything else the same.”

Not: “Make it a bit more orange.”

3Adding new sections.

Tell Claude exactly where to insert the new section and exactly what it should contain. If you want it to match the existing style, say so explicitly.

Example: “Add a new section between the hero and the credibility stats. It should have three short items answering: who this is for, what they get, and what they’ll stop worrying about. Match the existing card styling.”

4Fixing things that feel off.

You don’t need design vocabulary to describe what’s wrong. Use plain English and trust that Claude can translate it into code.

Example: “The spacing between sections feels too tight, everything is crammed together. Add more breathing room between each section.” / “The text is hard to read. It’s too small and too close together. Increase the body font size and line spacing.”

5Structural changes.

If you want to reorder sections or change the overall page flow, describe the desired order from top to bottom.

Example: “Reorder the page sections: 1) Navigation, 2) Hero, 3) Credibility stats, 4) How it works, 5) Testimonials, 6) What I do, 7) Final CTA, 8) Footer. Keep all content and styling exactly the same, just change the order.”

Advanced: Prompt Chaining for Complex Pages

For a simple landing page, a single well-structured prompt usually gets you 80% of the way there. But if you’re building something more complex: a multi-section sales page, a page with detailed service breakdowns, or a page where the copy really needs to be sharp, prompt chaining will get you consistently better results.

Anthropic says prompt chaining is still useful when you want to check each stage before moving on. The idea: break the work into separate prompts where each output feeds into the next. Each prompt has one job. One job done well beats multiple jobs done adequately.

Step What This Prompt Does What You Feed Into the Next Step
01 Strategy “Here’s my business, my customer, and my goal. What are the 3 strongest angles for a landing page headline? What’s the key objection I need to overcome? What proof points will matter most to this customer?” The chosen angle, key objection, and top proof points
02 Copy first “Using the angle and proof points from the strategy, write all the copy for the landing page. Don’t worry about code yet, just the text: headline, sub-headline, section copy, CTA text, stats callouts.” Complete copy for the page, reviewed and approved by you
03 Build the page “Now build the full HTML landing page using this copy exactly as written. Here’s the design direction, structure, and technical requirements.” Complete HTML file
04 Refine Individual iteration messages, one change at a time Final version ready to deploy

The key advantage of separating copy from build: you review and approve the words before any code is written. If the headline isn’t right, you fix it in 30 seconds in step 2, not by digging through HTML in step 3. The copy and the code are two different problems. Solve them separately.

Ask for the assumptions. For the strategy step, add this to your prompt: “Before your recommendations, list your assumptions about my customer: what they’re worried about, what they’ve tried before, what would make them trust someone new.” Current Claude models already think before they answer, and may decline a request to write their reasoning out in tags. Asking for the assumptions gets you the part you need to check. If its assumptions about your customer are wrong, you can correct them before it shapes the rest of the work.

Getting It Live: WordPress, Shopify, and Others

Once you’re happy with how the page looks in preview, here’s how to get it onto your site. This is the part most guides skip, and the part that trips people up. The instructions are platform-specific, so find yours below.

WordPress (With Elementor or Page Builder)

You have two clean options depending on how much control you want:

Option A: Elementor Canvas (cleanest). Create a new page in WordPress. Under “Page Attributes” → “Template”, select “Elementor Canvas” (this gives you a completely blank page with no header or footer from your theme). Click “Edit with Elementor.” Drag an HTML widget onto the canvas. Paste the full HTML code into the widget. Update and preview.

Option B: HTML Block. Create a new page. In the page editor, add a “Custom HTML” block (not the standard text editor). Paste the full code. This works but your theme’s header and nav will appear above it, which may or may not be what you want for a dedicated landing page.

Shopify

Go to Online Store → Pages → Add Page. In the content area, look for a button to switch to the HTML editor (it often looks like </> or “Source”). Switch to HTML view and paste the code. Save and preview. Note: Shopify wraps pages in your theme’s header and footer by default. If you want a standalone landing page without your store nav, tell Claude: “Add a note to the top of the HTML file reminding me to use a theme section or page template that suppresses the store header and footer.”

Squarespace: Use a Code Block. Add a new block on any page and choose “Code.” Paste the HTML. Squarespace will render it within their page structure.

Wix: In the Wix Editor, add an “HTML Embed” element. Paste the code. Note that Wix sandboxes embedded HTML, so some styling may need tweaking. Ask Claude to help if specific elements aren’t rendering correctly.

Webflow: Use an Embed component. Paste the HTML code into the embed. Webflow handles this cleanly and is the best platform for getting pixel-perfect results from Claude’s output.

Tell Claude which platform you’re deploying to. Include your platform in the original brief. Add one line to your <technical> block: “This will be deployed on [WordPress / Shopify / Wix / Webflow]. Optimise accordingly.” Claude will adjust the output, for example structuring the HTML to work cleanly within Shopify’s page wrapper, or flagging Wix-specific rendering issues before you hit them.

5 Prompts You Can Steal Right Now

These are complete, copy-paste prompts for the five most common landing page requests from Australian service businesses. Fill in the brackets and paste directly into Claude. Each one uses XML structure, specific constraints, and tone examples.

01. Service Business Lead Generation Page

For any service business wanting to capture enquiries or book calls: bookkeepers, consultants, coaches, advisors, agencies.

Build a single-page HTML landing page for my service business.
<context>
Business: [What you do, in one sentence]
Location: [City/state]
Customers: [Who specifically, be detailed]
Goal: Book a free 30-minute call
Credibility: [Your real numbers: clients, years, results, reviews]
</context>
<tone>
[Plain English description of how you want to sound]
Examples of what I DON’T want: “We pride ourselves on delivering
tailored solutions.” / “Take your business to the next level.”
</tone>
<design>
Colours: [Your palette, be specific with hex codes if you have them]
Feel: [Clean / bold / warm / minimal / premium / etc]
Font direction: [e.g. “Strong headline font, readable body”]
</design>
<sections>
1. Nav: Business name + “Book a Free Call” button
2. Hero: Headline speaking to customer pain, sub-headline,
inline form (first name, email, business name, phone)
3. Social proof bar: 3 stats from my credibility
4. The problem: What my customer is stuck with (3 points)
5. My solution: What changes when they work with me (3 points)
6. How it works: 3-step process (Discovery Call → Custom Plan → Results)
7. About: 2-3 sentences, photo placeholder, my background
8. Final CTA: Repeat the book-a-call form
9. Footer
</sections>
<copy_rules>
– Banned phrases: “look no further”, “tailored solutions”, “we pride ourselves”,
“passionate about”, “one-stop shop”, “we’ve got you covered”
– CTA button text: “Book My Free Call →” (not “Submit”)
– Hero headline must lead with customer pain, not my service
– Reading level: conversational, not corporate
</copy_rules>
<technical>
Single HTML file, all CSS embedded. Google Fonts okay.
Fully responsive. Platform: [WordPress / Shopify / etc]
</technical>

02. Trades Business Quote Request Page

For electricians, plumbers, builders, painters, landscapers. Anyone whose primary conversion is a quote request.

Build a single-page landing page for a trades business.
<context>
Trade: [Your specific trade]
Location: [City/suburbs you service]
Customers: [Residential / commercial / both, and who specifically]
Average job value: [$X]
Goal: Get them to request a free quote
Credibility: [Years in business, job count, review count and rating,
licences/certifications, any notable projects]
</context>
<tone>
Real tradie. No bullshit. Australian. Short sentences.
Sounds like someone who’s done this a thousand times and knows
it better than anyone, not a salesperson.
NOT: “We’re passionate about delivering premium [trade] services
to residential and commercial customers across the region.”
</tone>
<design>
Dark and confident, navy/charcoal with a strong accent colour.
Bold, clear headings. High contrast. Feels solid and trustworthy.
No stock-photo aesthetic. No pastel. No “friendly” softness.
</design>
<sections>
1. Nav: Business name, phone number prominently displayed, CTA button
2. Hero: Lead with the customer’s problem (not the service).
One dominant headline, short sub-headline, quote request form:
Name, phone, suburb, type of work (dropdown), brief description
3. Trust bar: Years in business + job count + review rating + licence
4. Services: What jobs you take (4-6 items with brief descriptions)
5. Why choose us: 3 specific reasons (no “passionate team” nonsense)
6. Recent reviews: 2-3 review placeholders with stars, name, suburb
7. Second CTA: “Still not sure? Call us directly” + phone
8. Footer with address, phone, ABN, service areas
</sections>
<copy_rules>
– Lead with the job done well, not the business credentials
– Include phone number in at least 3 places, tradies get called, not emailed
– Quote form CTA: “Get My Free Quote →” not “Submit”
– Suburbs served: list at least 5 in the footer for local SEO
– Every claim needs a number behind it
</copy_rules>
<technical>
Single HTML file, all CSS embedded. Fully responsive. Mobile-first,
most trades leads come from phones.
</technical>

03. Lead Magnet Download Page

For anyone using a free guide, checklist, or resource as the conversion. Common for consultants, coaches, and educators.

Build a focused lead magnet landing page.
<context>
My business: [Who you are, 1 sentence]
The lead magnet: [Name of the guide/checklist/resource]
What it solves: [The specific problem it addresses]
Who it’s for: [Exact target person]
What they get: [3-4 specific things inside the resource]
</context>
<tone>
Helpful and direct. Like a knowledgeable colleague sharing something
useful, not a marketer trying to get your email address.
</tone>
<design>
Minimal and focused. Nothing to click except the download form.
No navigation. No footer links. One purpose: get the email.
[Describe your colour preferences]
</design>
<sections>
1. Header: Logo/name only. No navigation links.
2. Hero: What the resource is, who it’s for, why it matters now.
Mockup placeholder (simple box/graphic representing the guide).
3. What’s inside: 4-5 bullet points of specific value
(not “everything you need to know”, actual specific contents)
4. Form: First name + email only. CTA button. Privacy line underneath.
5. Minimal footer: Copyright + “No spam. Unsubscribe any time.”
</sections>
<copy_rules>
– Headline must name the specific outcome, not the document type
(NOT “Download Our Free Checklist”, YES “Stop Paying for Marketing
That Doesn’t Work: 10 Questions to Send Your Agency Today”)
– No navigation links that could pull people away from the form
– Form CTA must reference what they’re getting: “Send Me the Guide →”
– Keep it short, this page has one job
</copy_rules>
<technical>
Single HTML file, all CSS embedded. Fully responsive.
</technical>

04. Professional Services Page (Accountants, Lawyers, Advisors)

Build a professional services landing page.
<context>
Profession: [Accountant / financial advisor / lawyer / etc]
Specialisation: [What specifically you focus on]
Location: [City]
Ideal client: [Who specifically: age, situation, what they’re facing]
Credibility: [Qualifications, years, client count, notable outcomes]
Goal: Book a free initial consultation
</context>
<tone>
Trustworthy and plain-spoken. Like a GP who explains things clearly
without making you feel stupid. Confident but not intimidating.
Zero jargon in the headline and sub-headline.
NOT: “Leveraging our comprehensive suite of financial services to
deliver holistic outcomes for high-net-worth individuals.”
</tone>
<design>
Clean and premium. Generous whitespace. Professional photography
placeholder. Muted, sophisticated colour palette.
Think: GP clinic meets quality law firm. Calm. Authoritative.
</design>
<sections>
1. Nav: Name/logo, key nav items, “Book a Consultation” button
2. Hero: Lead with the client’s situation (not your qualifications).
Form: Name, email, phone, brief situation description.
3. About: 1 photo placeholder, 3-4 sentences, real background,
real credentials, why you do this work
4. Who I work with: 3 client profiles (who they are + what they need)
5. What working with me looks like: 3-step process
6. Credentials: Qualifications, memberships, years, client count
7. Testimonials: 2-3 placeholders (name, role/situation, quote)
8. FAQ: 4-5 common questions and direct answers
9. Final CTA
10. Footer
</sections>
<copy_rules>
– Avoid all jargon in headings, plain English only
– Qualifications should appear but not lead
– The FAQ should answer real objections (cost, process, time, fit)
– CTA: “Book My Free Consultation →” not “Get in Touch”
</copy_rules>
<technical>
Single HTML file, all CSS embedded. Fully responsive.
</technical>

05. The Refinement Prompt (Use This After Any First Draft)

Once you have a first draft, use this prompt to run a structured audit before you start individual iteration requests.

Before I start iterating, audit the current page against these criteria.
Be direct, I want honest assessment, not reassurance.
<audit_criteria>
1. Hero headline: Does it speak to the customer’s pain or just describe
the service? Could this headline belong to any other business?
2. Copy voice: Does any copy use these banned phrases? [paste your list]
Does it sound like a real person or a marketing department?
3. CTA clarity: Is there one clear action? Is the button text specific?
4. Credibility: Are my real numbers prominent? Or buried?
5. Mobile: Will this read cleanly on a phone? Any likely layout issues?
6. Structural logic: Does the page follow a clear problem to solution
to proof to action flow?
</audit_criteria>
For each criterion, give me:
– A verdict (pass / needs work / fail)
– One specific recommendation if it needs work
– A rough priority (fix first / fix second / fix last)
Then list the top 3 changes you’d make in order of impact.
Do not make any changes yet, just audit and report.

Complete Checklist

Work through in order. Don’t skip the prep.

Before You Open Claude

  • Written your one-sentence business description (specific, not vague)
  • Described your ideal customer in detail, not a demographic, a person
  • Chosen one single conversion goal for this page
  • Listed every real credibility proof point you have (numbers, results, years)
  • Described your tone in plain English, how you want to sound to a client
  • Listed 2–3 banned phrases that make you sound like every other business in your category
  • Found 1–2 websites you like and noted specifically what appeals to you
  • Decided on your colour direction, even roughly

Building the First Version

  • Used XML tags to structure the prompt (<context>, <tone>, <design>, etc.)
  • Included at least one good example and one bad example of copy/tone
  • Specified “single HTML file, all CSS embedded” in the technical section
  • Included your platform (WordPress/Shopify/etc.) in the brief
  • Previewed the output in codepen.io before touching your live site

Evaluating the Output

  • Hero headline speaks to customer pain, not just the service
  • Copy doesn’t use any of your banned phrases
  • CTA button has specific action text (not “Submit” or “Contact Us”)
  • Your real credibility numbers are visible above the fold
  • No section does the same job as another section
  • Mobile layout is readable, tested on a phone or in browser dev tools

Iterating

  • Run the audit prompt before starting individual changes
  • One change per message, no multi-request messages
  • Stayed in the same chat tab throughout
  • Saved the final HTML code before closing the tab

Going Live

  • Pasted into codepen.io for a final browser check before deploying
  • Deployed using the correct method for your platform
  • Tested on mobile after deploying to the live site
  • Checked that the form and CTA are working
  • Set the page as a dedicated URL, not just a draft

What This System Gets You

2 hrs
typical time from brief to a live page
$0
developer cost on Claude’s free plan
1 file
complete HTML, paste anywhere

And iterations cost nothing extra, within your plan’s usage limits. The code generation is instant; the thinking is the only thing that takes time, and that thinking is yours.

The Honest Summary

The brief is the bottleneck. Not the tool.

Every time someone tells me “I tried Claude and got rubbish output,” I ask what their first message said. Nine times out of ten it was two sentences. No customer description. No conversion goal. No design direction. No examples. They gave a vague instruction, got a generic output, and called the tool useless.

The people who get real results spend more time on their brief than anything else. They know their customer’s specific pain. They have real proof points. They can describe what they want the page to feel like, not in design jargon, just plain English. That preparation isn’t the AI’s job. It’s yours.

Claude handles the code. You provide the intelligence behind it. Get your side right, and the output takes care of itself.

Straight answers (FAQ)

For a service business, the best AI landing page builder is Claude AI. Give it a clear, structured brief and it writes a complete, responsive single-page HTML landing page you can paste onto your site. The output quality is almost entirely a function of brief quality, not the tool.

No. You never have to read or write the code. Claude generates it, you preview it in a free tool like codepen.io, then paste the single HTML file onto WordPress, Shopify, Squarespace, Wix or Webflow. Your job is the brief, not the code.

Because the brief was vague, not because the tool failed. Claude follows instructions literally, so “build me a landing page for my business” fills every gap with the safest generic default. Specify your customer, one goal, real credibility, tone and design direction and the output changes completely.

Create a new page, set its template to Elementor Canvas for a blank page, edit with Elementor, drag in an HTML widget and paste the full code. Or add a Custom HTML block on a standard page, though your theme header and nav will show above it.

About two hours from brief to a live page, and $0 in developer cost on Claude’s free plan. Most of that time is the brief and iteration; the code generation itself is instant, and iterations in the same chat cost nothing extra, within your plan’s usage limits.

Sources: Anthropic prompt engineering documentation (instruction following, XML tags, multishot prompting, prompt chaining), quoted as published. Time, cost and quote figures reflect the author’s own builds.

Free · 3 Minutes

Not sure where your marketing is leaking?

The free Lead Machine Scorecard checks your traffic, website, lead capture, email and strategy, and tells you exactly what to fix first.

Take the Free Scorecard →

Happy to build it yourself? Everything above is the system, use it. Rather have the whole thing installed and owned by you? That’s what I do →

Get in touch

Prefer to talk it through? Call or text, email, or send a message.

Ty Pryor, small business marketing strategist

Ty Pryor
Small business marketing strategist. The only marketing hire inside a business that grew four times over. The local SEO system in this post is the one that drove 700+ showroom visits a year at zero ad spend.