Choose the style that feels most like your brand. Your code word gets dropped into the build prompt so Claude applies the right colours and fonts automatically. If you have a website, share the URL in your recording instead — colours and fonts will be pulled from there.
If you have already built your AI Content Brain Clone, you are ahead. If you have not — do that first. It will make everything in this guide faster and the copy it produces significantly stronger.
Your Brain Clone stores your voice, your values, your lived experiences, and your way of seeing the world. When you bring that context into your sales page build, Claude is not writing generic copy — it is writing in your voice, drawing on your actual stories.
The part that matters most for this project is your Story Bank. Your Story Bank is a collection of real moments from your life — the struggles, the turning points, the lessons learned the hard way. A headline that references a real moment from your life will always outperform one that is made up. A pain point written from a story you actually lived will always feel more true than one assembled from guesswork.
When you sit down to record your answers in the Copy tab, pull up your Story Bank first. Look for stories that connect to your buyer's frustrations, your own transformation, and the moment this product came to exist.
Already have your Brain Clone? When you upload your transcript in the Build tab, also attach your Brain Clone document and Story Bank. Add this line to the prompt: "I am also attaching my AI Content Brain Clone and Story Bank. Use these to inform the tone, draw on relevant stories, and ensure the copy sounds like me throughout."
You can build your entire sales page on Claude's free plan. The template is a large file so each message uses more of your allowance than a normal chat. The free plan resets every 5 hours — if you run out of messages you can wait for the reset and pick up where you left off.
If speed matters and you want to do everything in one sitting, consider upgrading to the Pro plan ($20/month) for the month.
Either way, same result. The free and Pro plans produce identical output. The only difference is speed.
Every message to Claude processes the entire conversation as context. This guide minimises the number of messages while maximising quality.
Upload the template, transcript, and prompt together. One big message is lighter on tokens than multiple small ones.
After Claude produces V1, download the file and start a fresh chat. Claude only processes the current file plus your new instruction.
Record one voice memo covering the entire page and send it as a single refinement message. One thorough round saves far more tokens than five vague ones.
Pull up your Story Bank before answering these questions. Look for real moments that connect to your buyer's frustrations, your transformation, and why this product exists. Drop those stories into your recording and Claude will turn them into copy that feels human — because it is.
Brain Clone Access HereThe fastest way to answer these questions is to either record directly into an AI transcription tool or use Tella — a simple screen and camera recorder that gives you a clean transcript automatically. No editing, no fuss. Just talk through the questions and let the tool do the rest.
Learn Tella Here in 5 MinutesJust talk naturally. Do not overthink it. Aim for 10 to 15 minutes of recording total. The template combined with Claude will shape your words into polished sales copy.
Just do your best. You do not need perfect answers. If you get stuck on any question, ask Claude to make a suggestion or fill in the blanks — just mention it in your recording.
Don't have a named method yet? Just share what makes your approach different and ask Claude to name it for you.
You can also ask Claude to surface relevant frustrations for your niche. Just mention that in your recording.
This is Message 1. Upload the template file, your voice transcript, and paste the prompt below. Claude will produce your complete V1 sales page.
I am attaching a sales page HTML template and a transcript where I share all the details about my offer. Your job is to take the template and produce a complete finished sales page with all placeholder content replaced by real copy based on my transcript.
My brand palette code word is [paste your code word here]. Apply the matching colour palette and font pairing to the entire page by updating the CSS variables at the top of the file.
Copy rules: Lead every section with the transformation and the result first — what their life looks like after — before addressing the problem or introducing the product. Sell the destination, not the escape route. The one exception is the pain points section, which leads with the problem so the reader feels deeply seen. Write pain points at a 3rd grade reading level — short, blunt, and emotionally direct. Everywhere else write at a 6th grade reading level. Use my tone of voice from the transcript. Conversational and grounded — like a knowledgeable friend explaining something, not a sales pitch. Every sentence must teach something, direct the reader somewhere, or prove a point. No em dashes anywhere. No hyperbolic or salesy language. No repetitive staccato patterns like "Not X. Not Y. Not Z." No filler.
Mobile first: This page must be fully optimised for mobile. All font sizes, padding, grid layouts, and button sizes must work perfectly on a 375px screen. Stack all multi-column layouts to single column on mobile. Ensure all buttons are at least 48px tall and full width on mobile. Text must be readable without zooming.
Systeme.io compatibility: This file will be pasted into a systeme.io custom HTML block. Follow these rules exactly: do not include DOCTYPE, html, head, or body tags — output only what goes inside the body. Convert any Google Fonts link tags to @import statements inside the style block. Do not use localStorage, sessionStorage, or any browser storage APIs. Do not use any script tags — systeme's Raw HTML block rejects them. Instead, place all JavaScript inside the onerror attribute of a hidden img element at the very bottom of the file: <img src="x:" onerror="(function(){ /* all JS here */ })()" style="display:none" alt=""> Do not use position:fixed on any element. All CSS must be in a single style block at the top. Do not reference external images — use CSS backgrounds and gradients only unless I provide image URLs. For current systeme.io requirements refer to: https://help.systeme.io/article/306-is-it-possible-to-insert-html-css-or-js-code
Sections to fill: Fill in every section of the template: the hero, ticker bar, pain points, What You Get stack, How It Works steps, the story section, the comparison section, the FAQ, and every CTA. For the MegaMockup and EditorialMockup sections, generate content that presents my offer based on what I described in the transcript.
Produce the complete finished HTML file ready to paste directly into systeme.io.
After Claude produces V1: Download the HTML file. Open it in your browser and read the entire page top to bottom. Then move on to the Refine tab.
Start a new chat for each refinement message. Download the latest version Claude produced, upload it into the new chat, and give your next instruction. This keeps the context lean and saves tokens.
Open V1 in your browser, start a voice memo or Loom, and scroll through saying what you want changed. If a section is fine, say "the [section] is good, leave it."
Read the headline and subheadline. Does it sound like you? Is the ticker bar right? Is the price badge correct?
"Change the headline to: Stop Guessing What to Post and Start Growing. The price should be $17 not $27."
Read each one. Do they match what your buyer actually feels? Replace any that feel generic.
"Pain point 2 should say: You keep saving other people's posts for inspiration but never actually create your own."
Note: This is the one section where the problem leads — not the transformation. Its entire job is to make your reader think "how did they know that about me?" If it doesn't do that, it needs to go deeper.
Are the feature names right? Do the descriptions match what your product actually includes?
"Feature 3 should be called The Caption Bank, not The Post Library."
Are the 3 steps accurate? Do they describe the real experience from purchase to result?
"Step 2 should say: Open the Notion template and answer the 5 audience questions."
Does it sound like your story? Are the numbers right? Does it capture why you built this?
"Change 200 clients to 180. I was a freelancer first, not in corporate."
Are these the real objections? Are the answers honest? Anything missing?
"Add one that says: Does this work for service providers, not just coaches?"
Comparison section, CTA headlines, guarantee, closing section. Anything off?
"The final CTA headline should say: Start Your Content Engine Today."
Here is my sales page (attached). Below is my voice feedback transcript with every copy change I want. Please go section by section and apply each change exactly as I describe it. Keep everything I did not mention the same. Keep the copy conversational and at a 6th grade reading level. No hype, no em dashes. Produce the complete updated HTML file.
[paste your voice feedback transcript here]
This single prompt does both jobs at once. It fixes every mobile layout issue first, then strips out everything systeme cannot handle. Start a new Claude chat, upload your latest HTML file, and paste the prompt below. Claude returns a clean file ready to paste straight into systeme. No code editing required.
I am attaching my sales page HTML file. Please run a full mobile optimisation check and a systeme.io compatibility check and fix every issue you find. Do not change any copy, colours, or visual design. Fix mobile first, then fix systeme compatibility on the mobile-corrected version so the final file passes both checks.
Mobile fixes:
1. Fully responsive from 320px wide and up. Nothing overflows or causes horizontal scrolling at any width.
2. All multi-column grid or flex layouts stack to a single column below 768px.
3. Hero headline and all large display text scales down gracefully using clamp() or responsive font sizes.
4. All buttons and interactive elements have a minimum tap target size of 44x44px and are full width on mobile.
5. All sections have a minimum of 16px horizontal padding on mobile so content never touches the screen edge.
6. Animations perform well on mobile. Remove heavy CSS filters, complex transforms, or effects that cause lag. Simplify or disable using a media query where needed.
7. The page reads cleanly top to bottom on a 375px screen with no horizontal scroll, overflow, or clipped content.
8. Body text minimum 15px on mobile. Labels minimum 13px. Nothing smaller.
Systeme fixes:
1. Remove any DOCTYPE, html, head, or body tags. Output only what goes inside the body tag.
2. Convert any Google Fonts link tags to @import statements inside the style block.
3. Remove any use of localStorage or sessionStorage.
4. Do not use script tags anywhere in the file. Systeme rejects them. Convert all JavaScript to inline event attributes — onclick, onchange, and so on — written directly on each element that needs them. For any code that would normally run on page load, pre-render it as static HTML instead.
5. Do not use position:fixed anywhere — not in CSS, not in JavaScript, not in inline styles, not in any textarea content. In any JavaScript clipboard fallback, use position:absolute and top:-9999px instead.
6. Ensure all CSS is in a single style block at the top. No other style blocks anywhere.
7. No script block anywhere in the file. No onerror attributes on any element. No javascript: URLs. All interactivity via standard inline event attributes only.
8. Check div nesting. Every opening div must have a matching closing div. Fix any orphan closing div tags or unclosed divs.
9. Do not use the literal string position:fixed anywhere in the file — including inside textarea elements or visible text. Write it as position: fixed (with a space) in any instructional copy.
10. Remove any references to external images that are not provided as real URLs.
11. For current systeme.io requirements refer to: https://help.systeme.io/article/306-is-it-possible-to-insert-html-css-or-js-code
Produce the complete corrected HTML file ready to paste directly into systeme.io.
Run this before every paste. Mobile first, systeme second, one file, one download. Takes 30 seconds and prevents the most common reasons pages break inside systeme.
Once the copy is right and your file has passed the systeme check, do a final pass to wire up all live links. Start a new Claude chat, upload the latest HTML file, and paste the prompt below.
Here is my sales page (attached). Please make the following final updates:
1. Replace every CTA button href="#" with my systeme.io payment link: [paste your systeme payment link here]
2. Update the footer copyright to: © 2025 [your business name]. All rights reserved.
3. Add my privacy policy link: [URL] and terms link: [URL] to the footer.
Produce the complete updated HTML file with only these changes made. Do not alter any copy.
Systeme.io is where your page lives, takes payments, and connects to your email list. You do not need WordPress, a separate website builder, or a third-party checkout. Everything is in one place.
Our recommendation: Start on the free plan to explore. When you are ready to go live, upgrade to the Startup plan. Pay annually at $170 to save the equivalent of 2 months. 97% of our clients never need to go beyond Startup.
Sign up for systeme.io. If you want a full tour of where everything lives inside the platform, watch the training below.
Video Training HereIf you want your sales page on your own domain instead of a systeme subdomain, install it now before building your funnel. Follow the systeme help article for step-by-step instructions.
Systeme Domain HelpClick the button below to install the pre-built funnel template into your systeme account. This gives you the landing page, order form, and thank you page already set up — you just drop your content in.
⚡ Install Funnel TemplateNeed help with this step? Watch the training below.
Video Training HereIn systeme, click Sites, then Funnels, then click on your installed template. Watch the training below to understand how the funnel is structured and how to connect your payment method to the order form.
Video Training HereOpen the first page in the funnel (the landing page) and update these important settings before you paste any HTML. Getting this wrong is the most common mistake — watch the training to avoid it.
Video Training HereOpen the HTML block inside the landing page editor. Paste the file Claude gave you (after running the systeme compatibility check in the Refine tab). Click Save. Your page is now live on your systeme subdomain or custom domain.
Repeat the same process for the order form page. This is also where you add your order bump if you have one. The order form uses systeme's native fields so tags and automations fire correctly on purchase. Watch the training for the full walkthrough including how to brand the form and set up your order bump.
Video Training HereYour thank you page is a gold opportunity — do not waste it with just "thanks for buying." This is the highest-trust moment in your funnel. Use it to upsell something else, affiliate a tool you love, or send people to your community.
Many of our clients include lines like: "If you want to create a free account on the software I used to build this, click here" — that's a systeme affiliate link that pays them a commission every month. Others add "If you'd like to know who taught me how to build this, click here" — that sends people to you and earns them a referral commission.
The thank you page is not the end of the sale. It is the start of the next one.
Stripe and consumer protection laws in most countries require your pages to display terms of service, a privacy policy, and contact information. Set up a master footer in systeme so this appears across all your pages automatically — you only have to do this once.
Video Training HereYour sales page gets the click. Your email sequence gets the transformation — and the retention. A well-built email workflow does three things: it delivers the product experience, it builds belief in the result, and it keeps people coming back. This tab walks you through all three.
Before you can send anything, you need to connect your email to systeme, understand how contacts and tags work, and know how to send both broadcast emails and automated sequences. Watch the full training to get your email foundation set up correctly from the start.
This covers: how to import contacts, how to create and apply tags, how to send a one-off email, and how to connect a domain-based email address so your emails send from you@yourdomain.com through systeme rather than a generic address.
Use the prompt below to generate a 5-day Soap Opera Sequence in Claude or ChatGPT. This sequence works on the Belief Repair System — each email removes a specific limiting belief that stops your buyer from getting results, then leads them to a lesson inside your offer or community that repairs it.
What is a Soap Opera Sequence? It is a 5-email series that reads like episodes of a story — each one ends on a hook that makes them open the next. It builds connection, dissolves doubt, and moves people from "I bought this" to "I believe I can do this."
I need you to write a 5-day Soap Opera email sequence for my offer. This sequence is based on the Belief Repair System — each email identifies one limiting belief that is stopping my buyer from getting results, tells a story that makes that belief visible, then repairs it by pointing them to a specific lesson or resource inside my product or community.
Here are the details of my offer: [paste your offer name, what it does, who it is for, and the core transformation]
Here are the five beliefs I want to repair, one per email: [list your five limiting beliefs — e.g. "I'm not consistent enough", "I don't have anything interesting to say", "My audience is too small for this to work", "I've tried this before and it didn't work", "I don't have time for this"]
For each email follow this structure exactly:
Subject line: curiosity-led, no clickbait, under 8 words
Opening: drop straight into a short personal story or scene that mirrors the limiting belief
Middle: show why that belief is a lie or a misunderstanding, using a specific example or reframe
Belief repair: point them to a specific lesson, video, or resource inside the product or community that proves the belief wrong in action
Close: one sentence that opens a loop for tomorrow's email
CTA: one link only — to the lesson or resource mentioned
Keep the tone conversational, warm, and direct. No hype. No em dashes. Write at a 6th grade reading level. Each email should be 250 to 350 words. Produce all five emails in full.
Once your five emails are written, you install them as an automated workflow in systeme. The workflow triggers the moment someone purchases — so every new buyer automatically starts receiving the sequence without you doing anything manually. Watch the training for the full setup walkthrough.
If your offer is a membership, subscription, or community, the Soap Opera Sequence alone is not enough. You also need an onboarding sequence — a series of emails that holds the new member's hand through their first 7 to 14 days and gets them to their first win as fast as possible.
The fastest way to lose a subscriber is to let them feel lost after they join. The fastest way to keep one is to get them a result in the first week. Your onboarding sequence exists to do exactly that.
I need you to write a 7-day onboarding email sequence for new members of my [membership/subscription/community name]. The goal of this sequence is to get every new member to their first meaningful win within 7 days, build the habit of showing up, and reduce churn by making them feel like they made the right decision.
Here is how my offer works: [describe what members get access to, how it is structured, and what the core transformation is]
Here are the key lessons or resources inside the offer I want to lead them to: [list 5 to 7 specific lessons, videos, or resources with their titles]
Write one email per day for 7 days. Use this structure for each:
Day 1: Welcome and orientation — tell them exactly where to start and what to do first. Remove overwhelm. One clear action only.
Day 2: Lead them to the most important lesson in the offer and explain why it matters more than anything else.
Day 3: Share a quick win — something they can do in 15 minutes that proves the system works.
Day 4: Address the most common reason people give up at this stage and repair the belief using the Belief Repair System.
Day 5: Lead them to a lesson that helps them go deeper and get a bigger result.
Day 6: Share a story or result from someone who was exactly where they are now.
Day 7: Celebrate their first week. Remind them what they now have access to. Point them to where the community lives and encourage them to post their first win.
Keep each email 200 to 300 words. Conversational, warm, and encouraging. No hype. No em dashes. One CTA per email — always a link to a specific lesson or community space. Produce all 7 emails in full.
If you want to restrict access to your sales page — for a beta launch, a members-only offer, or a private funnel — you can add a password gate to your HTML in one Claude message. No plugins, no third-party tools.
I am attaching my sales page HTML file. Please add a standalone password gate to this page. The password is funnelme. When the page loads, show a full-screen password gate that covers the entire page. If the correct password is entered, hide the gate and reveal the page. If the wrong password is entered, show an error and clear the field. Do not change any copy, design, or layout of the page itself. Produce the complete updated HTML file.
Before you paste the prompt: Change the word funnelme to your own password first. Pick something simple that your buyers can remember — you will need to share it with them when they purchase.