Produces conversion-optimized landing page copy with hero section, problem
statement, solution, social proof, and CTA sections using conversion
copywriting methodology. Use when the user asks to write landing page copy,
create a product page, write a sales page, draft conversion copy, or
write landing page text for a website. Also useful when asked to write
website copy or create a page that converts visitors.
Do NOT use for ad copy (use paid-ad-copy), product descriptions for
e-commerce listings (use product-description), or full website content
strategy (use seo-content-strategy).
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.
Produces conversion-optimized landing page copy with hero section, problem
statement, solution, social proof, and CTA sections using conversion
copywriting methodology. Use when the user asks to write landing page copy,
create a product page, write a sales page, draft conversion copy, or
write landing page text for a website. Also useful when asked to write
website copy or create a page that converts visitors.
Do NOT use for ad copy (use paid-ad-copy), product descriptions for
e-commerce listings (use product-description), or full website content
strategy (use seo-content-strategy).
Use this skill when the user needs conversion-optimized copy for a single-purpose web page designed to drive one specific action. Specific trigger scenarios include:
User asks to write landing page copy, a sales page, or a conversion page for a product, service, course, app, or offer
User wants to create a new landing page and needs a full copy structure (hero, benefits, social proof, CTA)
User has a product or service and wants copy that converts visitors from a specific traffic source (paid ads, email campaign, webinar follow-up)
User asks to rewrite or improve an existing landing page because conversion rates are underperforming (benchmark: below 2% for lead gen, below 1% for e-commerce, below 5% for free trial SaaS)
User wants a "squeeze page" or lead capture page designed around a single opt-in action
User needs a webinar registration page, demo request page, free trial signup page, or product launch sales page
User wants to A/B test their existing landing page and needs a new copy variant
User asks to write a long-form sales letter (VSL page, sales letter page) for a high-ticket offer
Do NOT use when:
User needs short ad copy, headlines, or ad body text for Google, Meta, or LinkedIn ads -- use paid-ad-copy instead
User needs e-commerce product listing copy for Amazon, Shopify PDP, or other catalog pages -- use product-description instead
User needs a full website content strategy, pillar pages, or site-wide SEO copy architecture -- use seo-content-strategy instead
User needs email copy to drive traffic to the landing page -- use email-copy or email-sequence instead
User needs a homepage (homepages serve multiple audiences and multiple goals; landing pages serve one audience and one goal -- these require different structures)
User needs a case study, whitepaper, or long-form content asset -- use long-form-content instead
User needs social media post copy -- use social-media-copy instead
Process
Step 1: Establish the Conversion Context Before Writing a Single Word
The most common failure in landing page copy is writing before understanding the conversion context. Gather all of the following before drafting:
The offer: What exactly is being offered? Free trial, paid course, SaaS subscription, physical product, service package, lead magnet, demo request, consultation booking? The offer type determines copy length, CTA structure, and risk-reversal strategy.
The conversion goal: One landing page = one conversion action. If the user mentions two actions ("sign up or book a demo"), flag this and recommend choosing one primary CTA with the other as a secondary fallback.
Traffic source: This is critical and frequently overlooked. Visitors arriving from a paid Facebook ad have zero context and need more problem-framing. Visitors arriving from a branded Google search already know the product and need validation. Visitors from an email sequence are warm and trust the sender -- hero copy can skip problem-agitation and go straight to benefits. Ask: "Where are most visitors coming from?"
Target visitor: One specific person, not a demographic range. Push for specificity: not "marketing professionals" but "in-house marketing managers at B2B SaaS companies, 5-15 years experience, responsible for pipeline generation, frustrated that their CEO doesn't trust marketing data." The more specific the avatar, the more the copy will resonate with the real visitors.
Primary objection: What is the single biggest reason the ideal visitor would leave without converting? Price? Skepticism about results? Complexity? Time required? The entire middle of the page is built around neutralizing this objection.
Price point and purchase complexity: A $29 impulse buy needs different copy than a $2,000 course or a $50,000/year enterprise contract. Higher price = more copy, more proof, more objection handling, longer page.
Social proof inventory: What exists? Testimonials (video or text)? Customer logos? Review platform ratings (G2, Capterra, Trustpilot, App Store)? Published case study results? Award recognition? Named customer counts? Without social proof, you must write more authority copy in the benefits section.
Guarantee or risk reversal: Free trial? Money-back guarantee? "Cancel anytime"? Risk reversal is a conversion multiplier -- note whether it exists before writing the CTA section.
If the user cannot answer 5 or more of these, ask for them directly before producing copy. A landing page written without this context will miss the audience and underperform.
Step 2: Determine Page Length and Structure
Page length is a function of price, audience awareness level, and offer complexity -- not personal preference. Use this framework:
Short page (300-500 words): Free opt-in, lead magnet download, webinar registration, or a single low-friction action where the visitor arrives already warm. Structure: Hero + 3 bullets + 1 testimonial + CTA.
Medium page (600-1,200 words): Free trial or freemium SaaS signup, low-to-mid-price product under $99, audience arriving from targeted paid ads with good message-match. Structure: Hero + Problem + Solution (3-5 benefits) + Social proof + FAQ + CTA.
Long page (1,500-3,000+ words): Paid courses $100+, high-ticket consulting, B2B demo request with long sales cycle, any offer where the visitor needs to be educated and convinced before taking action. Structure: Hero + Problem (agitation) + Solution (deep benefits) + Social proof (multiple formats) + How it works + Objection handling (FAQ) + Risk reversal + Final CTA.
Long-form sales letter (3,000-8,000 words): Used for high-ticket offers ($500+) sold entirely on the page without a sales team. Uses AIDA or PAS structure extended across the full page. Emotional storytelling and transformation arc are central to the copy.
Determine which structure applies, then build the outline before writing copy.
Step 3: Write the Hero Section
The hero section is the most important section on the page. Visitors decide in 3-8 seconds whether to continue scrolling. Every word in the hero earns its place or gets cut.
Headline: Follow these principles:
Length: 6-12 words optimal. Headlines under 6 words sacrifice specificity; headlines over 15 words lose attention.
Structure options (choose based on offer type):
Outcome-led: "Cut Your Ad Spend by 40% Without Losing Revenue" -- works for any ROI-driven offer
Problem-led: "Tired of Marketing Reports Nobody Reads?" -- works when the pain is acute and widely shared
How-to: "How to Close Enterprise Deals in 90 Days or Less" -- works for skill-based or process-based offers
Who it's for: "For Freelance Designers Who Want to Double Their Rates" -- works when the audience is very specific
Transformation: "From Burnout to Profitable Freelancer in 6 Months" -- works for personal development and coaching
The headline must contain the primary benefit or transformation. It must NOT lead with the product name, the company name, a tagline, or a vague aspirational statement like "The Future of Marketing."
Test the "billboard test": if this headline appeared on a billboard with no supporting text, would a stranger understand what this page is about? If not, rewrite.
Avoid jargon the visitor would not use to describe their own problem.
Subheadline:
15-35 words. Expands the headline with specificity: who it's for, how it works, and what makes it different.
The subheadline should contain a differentiator. "The only [X] that [does Y]" or "The [product] that [specific mechanism] so you can [outcome]."
Never repeat the headline with different words -- the subheadline must add new information.
Hero CTA:
Button text: 2-5 words. Action verb + outcome or object. "Start My Free Trial," "Get Instant Access," "Book My Strategy Call," "Download the Guide."
Never use "Submit," "Click Here," or "Go." These have zero conversion value.
Place the CTA button within the first screenful (above the fold on all major device sizes -- mobile first, since 55-70% of landing page traffic is mobile).
Include below-button micro-copy: "No credit card required," "Cancel anytime," "Free for 14 days," or whatever the most common hesitation is. This micro-copy reduces friction and increases clicks by 8-14% in most A/B tests.
Visual direction (if applicable):
Specify what visual should appear in the hero alongside the copy: product screenshot, lifestyle photo, explainer video thumbnail, illustration.
If a video is present, include a text fallback -- never let video be the only carrier of the core message.
Step 4: Write the Problem Section
The problem section creates emotional resonance. Visitors do not buy products -- they buy escapes from pain or paths to a desired identity. The problem section makes them feel understood before the solution is offered.
The PAS framework (Problem-Agitate-Solve) governs this section:
Problem (P): Name the problem in the exact language the visitor uses, not industry terminology. "Your churn rate is increasing" is industry language. "Customers are canceling and you don't know why" is visitor language. The distinction matters.
Agitate (A): Describe the downstream consequences of the unsolved problem. What is at stake? What does life look like if this problem persists? Do not exaggerate -- be accurate and specific. Agitation that feels manipulative or untrue destroys trust.
Transition: Bridge to the solution with an empathy statement. "There is a better way." "It does not have to be this way." "That is exactly why [product] exists."
Practical guidelines:
2-4 short paragraphs or 4-6 bullet points for medium pages. Long-form pages may spend 400-600 words on problem-agitation.
Write in second person ("you" not "they" or "marketers").
Include sensory and emotional specificity: "the Friday afternoon panic when your boss asks for Q3 numbers" beats "the stress of data analysis."
Do NOT introduce the solution in the problem section. Let the problem breathe. Visitors who feel understood are 3x more likely to continue reading than those who encounter a pitch immediately.
For cold traffic (paid ads), spend more time on problem-agitation. For warm traffic (email list), you can compress this section significantly.
Step 5: Write the Solution Section
The solution section translates the offer into visitor-centric benefits. This is where most copy fails -- companies describe features and assume visitors will infer the benefit.
Feature-to-benefit translation framework:
Every feature or capability must be translated through the "so what?" filter:
Feature: "AI-powered scheduling" → So what? → Benefit: "Your team never misses a follow-up, even during your busiest quarter"
Feature: "Real-time dashboard" → So what? → Benefit: "See exactly what's working in your campaigns right now, not in last week's report"
Feature: "HIPAA-compliant infrastructure" → So what? → Benefit: "Your legal team will stop worrying about patient data liability"
The benefit statement should describe the visitor's life after using the product, not the mechanics of the product itself.
Structure the solution section with 3-5 named benefits:
Each benefit gets a bold headline (5-10 words), a 2-4 sentence explanation with specific detail, and optionally a supporting micro-proof (a single data point or mini-case-study).
Order benefits by importance to the target visitor -- lead with the benefit that directly neutralizes the primary objection.
If the product has a mechanism or methodology that is proprietary and defensible, name it. "The 3-Step Revenue Audit" or "Our SCALE framework" creates specificity that generic benefits lack and is harder for competitors to copy.
Include a "How It Works" subsection for products with a non-obvious process or onboarding flow. 3-5 steps with very plain language. Visitors fear commitment to a complex process -- making it look simple reduces dropout.
Step 6: Write the Social Proof Section
Social proof is not decoration -- it is the primary mechanism that converts skeptical visitors. Place it strategically, not randomly.
The five formats of social proof and when to use each:
Testimonials: Most effective when they address a specific objection or describe a specific, measurable result. A testimonial that says "Great product! Highly recommend!" is worth almost nothing. A testimonial that says "I reduced my customer acquisition cost from $142 to $67 in 60 days using the acquisition module" is extremely valuable. Structure: [Specific result achieved] + [context or situation before] + [recommendation]. For B2B: always include name, title, company name, and company size or industry if possible. For B2C: name and specific context ("a freelance designer in Austin, TX" or "a first-time homebuyer").
Metrics and aggregate results: "2,400+ companies trust [Product]," "Average ROI: 312% in the first year," "4.8/5 from 1,200 verified reviews." Specific numbers always beat vague claims. Never write "thousands" if you can write "2,400." Never write "improved outcomes" if you can write "47% faster."
Logo bars: For B2B, a row of recognizable company logos is a powerful trust signal. Display 6-12 logos. Caption: "Trusted by teams at [Logo 1], [Logo 2]..." If the company is early-stage and logos are not impressive, use industry association logos, certification badges, or press mentions instead.
Review platform badges: G2 stars, Capterra ratings, App Store ratings, Trustpilot scores. These work because they signal third-party validation -- visitors know the company cannot control these ratings.
Case study callouts: A single headline stat from a case study ("How [Company X] grew MRR by 200% in 4 months") with a link to the full case study. These work for high-ticket offers where skepticism is high.
Placement strategy:
First social proof element belongs immediately after the hero section or after the problem section -- not at the bottom of the page where most visitors will never reach it.
Place a second social proof cluster immediately before the final CTA. This addresses last-minute hesitation at the conversion point.
For long-form pages, weave 1-sentence proof snippets ("Used by 400+ growth teams") throughout the copy rather than concentrating all proof in one section.
Step 7: Write the Objection Handling Section
Every unconverted visitor left because of an unresolved objection. This section exists to preemptively resolve those objections before the visitor leaves.
The 6 universal objection categories:
Price: "It's too expensive." → Address with ROI, comparison to cost of inaction, payment plans, or price anchoring against alternatives.
Time: "I don't have time to implement this / learn this." → Address with time-to-value ("you'll see results in the first session"), done-for-you elements, or time-investment quantification.
Trust/Credibility: "I've been burned by products like this before." → Address with guarantee, transparent refund policy, third-party reviews, and specific credentials.
Fit: "I'm not sure this is right for my situation." → Address with specific use-case descriptions, "This is for you if..." and "This is NOT for you if..." lists.
Timing: "Maybe later." → Address with cost of delay, limited-time elements (only if genuine), and what they are missing right now by waiting.
Complexity: "This looks complicated." → Address with "How It Works" (3 simple steps), onboarding support, or guaranteed hand-holding.
Format the objection section as an FAQ:
Phrase each question in the exact words a skeptical visitor would use. "Can I cancel anytime?" not "What is our cancellation policy?"
Keep answers short and direct. 2-4 sentences per answer. If an answer requires more, you may need a dedicated page section for that topic.
The final FAQ item should be the risk reversal statement: "What if it doesn't work for me?" → "You are fully protected by our [X]-day money-back guarantee. Email us at [email], no questions asked."
Risk reversal placement:
State the guarantee twice: once in the FAQ section and once in the final CTA section, immediately adjacent to the "Buy Now" / "Enroll" button.
Frame the guarantee in visitor-benefit language: "You're protected by our 30-day guarantee" not "Our refund policy is..."
The longer and more specific the guarantee, the more it converts. "30-day money-back guarantee, no questions asked" beats "satisfaction guarantee."
Step 8: Write the Final CTA Section
The final CTA is not a repeat of the hero -- it is the close. The visitor has read the full page and needs a final nudge to act.
Open with a 1-2 sentence closing statement that restates the transformation. Remind them who they will be after converting, not what the product does.
Repeat the primary CTA button with identical text to the hero CTA. Consistency in CTA language reduces cognitive friction.
Repeat the guarantee micro-copy immediately below the button.
Add a secondary CTA only if conversion data or user context justifies it. Secondary CTAs ("watch a demo," "read a case study") serve visitors who are not yet ready to commit. They are a fallback, not a feature. Never display the secondary CTA with equal visual weight to the primary -- it should be a text link, not a second button.
Urgency and scarcity: ONLY include if genuine. False urgency ("offer expires in 24 hours" that resets every visit) destroys trust the moment it is discovered and is ethically problematic. Real urgency examples: cohort enrollment closes on a specific date, founding member pricing ends at a specific milestone, limited spots in a live program.
Output Format
## Landing Page Copy: [Product/Offer Name]
### Page Brief
**Conversion Goal:** [Single action: purchase / free trial signup / demo request / lead capture]
**Traffic Source:** [Paid social / email list / organic search / paid search / direct]
**Target Visitor:** [Specific person: role, situation, primary pain point]
**Offer Price/Commitment Level:** [Free / $X / $X/month / quote-based]
**Page Length:** [Short / Medium / Long / Long-form sales letter]
**Available Social Proof:** [Testimonials / logos / ratings / metrics / none]
**Risk Reversal:** [Guarantee type and duration, or "none"]
---
### HERO SECTION
**Headline:** [6-12 words -- primary benefit or transformation, no jargon]
**Subheadline:** [15-35 words -- who it's for, what makes it different, specific outcome]
**Primary CTA Button:** [Action verb + outcome, 2-5 words]
**Micro-copy (below button):** [Friction reducer, e.g., "No credit card required" or "30-day guarantee"]
**Visual Direction:** [Specific description of image, screenshot, video, or illustration]
---
### PROBLEM SECTION
[HEADLINE: Optional bold section header, e.g., "Sound Familiar?" or "You Already Know the Problem"]
[Paragraph 1 -- Name the problem in visitor language]
[Paragraph 2 -- Agitate: consequences of the unsolved problem]
[Paragraph 3 -- Transition to solution with empathy statement]
*OR for bullet-format problem sections:*
**You are probably:**
- [Specific pain symptom 1]
- [Specific pain symptom 2]
- [Specific pain symptom 3]
- [Specific pain symptom 4]
[Transition line]
---
### SOLUTION SECTION
**Section Header:** [e.g., "Here's What Changes When You Use [Product]" or "Introducing [Product]"]
**One-sentence positioning statement:** [What it is, who it's for, what it does]
**Benefit 1: [Benefit headline, 5-10 words]**
[2-4 sentences -- specific outcome, mechanism, and micro-proof if available]
**Benefit 2: [Benefit headline, 5-10 words]**
[2-4 sentences]
**Benefit 3: [Benefit headline, 5-10 words]**
[2-4 sentences]
**Benefit 4 (if applicable): [Benefit headline]**
[2-4 sentences]
**Benefit 5 (if applicable): [Benefit headline]**
[2-4 sentences]
*(Optional) How It Works:*
**Step 1:** [Plain-language description]
**Step 2:** [Plain-language description]
**Step 3:** [Plain-language description]
---
### SOCIAL PROOF SECTION
**Section Header:** [e.g., "Trusted by [X]+ Teams" or "What Our Customers Say"]
**Testimonial 1 (result-focused):**
> "[Specific result or transformation achieved. Emotional resonance. Recommendation.]"
> -- [Full name], [Title], [Company] [optional: company size or industry]
**Testimonial 2 (objection-busting):**
> "[Quote that directly neutralizes the #1 objection]"
> -- [Full name], [Title], [Company]
**Testimonial 3 (aspirational, if available):**
> "[Quote about life/work improvement after using the product]"
> -- [Full name], [Context]
**Trust Metrics:**
- [Metric 1: specific number -- customer count, units sold, etc.]
- [Metric 2: rating from named review platform]
- [Metric 3: aggregate result metric -- e.g., "average ROI" or "uptime"]
**Logo Bar Caption (B2B):** "Trusted by teams at [Company 1], [Company 2], [Company 3], and [X]+ more"
---
### OBJECTION HANDLING (FAQ)
**Section Header:** [e.g., "Questions? We've Got Answers" or "Everything You Need to Know"]
**Q: [Objection #1 phrased as a visitor question]**
A: [Direct, specific, 2-4 sentence answer]
**Q: [Objection #2]**
A: [Answer]
**Q: [Objection #3]**
A: [Answer]
**Q: [Objection #4]**
A: [Answer]
**Q: What if it doesn't work for me?**
A: [Full risk reversal statement with guarantee terms]
---
### FINAL CTA SECTION
**Closing Statement:** [1-2 sentences -- transformation reminder, not feature list]
**Primary CTA Button:** [Same text as hero CTA]
**Micro-copy:** [Guarantee reminder + friction reducer]
**Secondary CTA (optional):** [Text link only, lower visual weight -- "Prefer to talk first? Book a 15-minute call"]
*(Optional) Urgency/Scarcity Note (only if genuine):*
[Specific, verifiable reason to act now]
Rules
Never write copy before establishing the conversion context. You need: offer type, traffic source, target visitor, primary objection, price point, and available social proof. Missing any of these produces generic copy that will underperform. Ask first, write second.
One landing page = one conversion goal. If the user describes two desired actions (e.g., "buy the product or book a call"), identify which is the primary goal and which is the fallback secondary CTA. Two equal CTAs split attention and reduce total conversion by creating decision paralysis (Hick's Law).
The headline must express a benefit or transformation, never a product name, tagline, or feature. "Introducing FunnelMax 3.0" is not a headline. "Close 40% More Deals With Automated Follow-Up" is a headline. The headline exists for a visitor who knows nothing about the product -- it must answer "what's in it for me?" in under 8 words.
Traffic source determines hero copy tone. Cold traffic (paid ads, display) has zero context and requires more problem-framing. Warm traffic (email list, retargeting) already trusts the source and responds to benefit-led, faster copy. Search traffic (branded keywords) is already solution-aware -- lead with differentiation and proof, not problem education. Getting this wrong produces massive message-mismatch, the single largest cause of paid traffic landing page failure.
All benefits must pass the "so what?" test from the visitor's perspective. Every sentence in the solution section should make the visitor's life, work, or situation concretely better. Reframe every feature: "built on enterprise-grade infrastructure" → "so your team never loses work due to downtime." Do not assume visitors will make this translation themselves -- most will not.
Social proof must be specific and credible. Vague testimonials ("This is amazing!") add no conversion value. A testimonial must include at least one of: specific result achieved, specific time frame, specific situation before vs. after, specific aspect of the product. Generic praise without specifics reads as fabricated and may hurt credibility. If the user has no testimonials, suggest collecting them before launch or writing copy that acknowledges early-stage status transparently.
Risk reversal must be stated twice on pages with a price point. Once in the objection handling/FAQ section and once immediately adjacent to the final CTA button. The closer the guarantee appears to the "pay now" action, the more it reduces purchase anxiety. Distance between the guarantee statement and the CTA reduces its conversion effect.
Never manufacture scarcity or urgency. "Only 3 spots left!" that resets on page reload, or countdown timers that restart on refresh, are conversion manipulation tactics that destroy trust when discovered. If the user requests false urgency, advise against it and suggest legitimate urgency alternatives: cohort close dates, genuine limited capacity, founding-member pricing tied to a specific milestone, or live event deadlines.
Mobile-first structure. As of current benchmarks, 55-65% of landing page traffic is mobile. Above-the-fold means "visible without scrolling on a 375px-wide screen." The hero headline, subheadline, CTA button, and micro-copy must all fit in this zone. Do not write hero sections that require scrolling to reach the CTA on mobile. When writing long headlines, check character count: 45-65 characters displays cleanly on mobile without awkward line breaks.
Copy must work without images. Visuals support copy but must never carry the core persuasive argument. A visitor who blocks images, uses a screen reader, or pastes the copy text into a doc to review it should receive the complete persuasive argument from text alone. Never write a section that references a visual as if the reader can see it ("as you can see in the chart above"). Instead, state the insight the chart would illustrate directly in text form.
Scannability is mandatory, not optional. Research on landing page reading patterns (F-pattern and Z-pattern eye-tracking studies) consistently shows that first-time visitors scan, not read. Structure every section so that the bold benefit headline alone communicates the key point. A visitor who reads only the bolded section headers and CTA buttons should still understand the offer, the benefit, and the conversion action.
Match the length and complexity of copy to price and purchase risk. A free opt-in page with 800 words of copy will lose conversions to a shorter, cleaner version. A $1,500 course page with 400 words will lose conversions to a longer, more thorough version. The rule: the higher the perceived risk of the conversion action, the more copy is needed to resolve objections and build trust. Low risk = short copy. High risk = long copy.
Edge Cases
SaaS Free Trial or Freemium Signup Page
The primary conversion risk is not price (it's free) -- it is time and effort. The visitor is asking: "Will I get value from this before I have to commit or learn a complicated tool?" Hero copy should emphasize speed to first value: "Set up in 8 minutes. See your first insight today." The problem section can be very short or omitted for warm traffic. Benefit copy should focus on the experience of using the product, not just the outcome. The top 3 objections to address: (1) "What happens when the trial ends -- will I get charged automatically?" (2) "Do I need a credit card?" (3) "Will it take hours to set up?" The FAQ must answer all three directly. Secondary CTA: "Watch a 3-minute product tour" for visitors who need to see the product before starting.
High-Ticket B2B Product or Enterprise SaaS (No Self-Serve Purchase)
The CTA is never "Buy Now" -- it is "Book a Demo," "Request a Consultation," or "Get a Custom Quote." The conversion goal is a qualified meeting, not a transaction. Copy must establish credibility and ROI before asking for the visitor's time. Social proof here is disproportionately powerful: named enterprise logos, published case studies with revenue or efficiency metrics, and named executive testimonials carry far more weight than star ratings. Include a "Who is this for?" section (company size, team type, use case) to pre-qualify leads and reduce demo no-shows. Add a "What happens after you book?" section (2-3 sentences) to reduce anxiety about a pushy sales call: "We'll send you a pre-call questionnaire. The call is 30 minutes and focused on your use case. No obligation." Copy length should be long -- 1,500-2,500 words -- because the decision-maker reading the page has budget authority and needs thorough justification.
High-Ticket Direct-to-Consumer Offer ($300-$2,000+, Sold on Page)
This scenario requires the longest copy -- often 2,000-5,000 words or more. The structure expands to include: origin story (why this product exists, who created it, what problem they personally experienced), full transformation arc (before/after), multiple testimonial clusters interspersed throughout the page rather than collected in one section, a detailed "What's included" breakdown with perceived value anchoring, an extensive FAQ (8-12 questions), a strong guarantee with specific terms, and a final CTA that restates the complete value proposition. Price anchoring is important: compare the price to the cost of alternatives, the cost of inaction, or the cost of the problem persisting. "Most marketing agencies charge $5,000/month for what this course teaches you in 6 weeks for $997" is a legitimate price anchor.
Lead Magnet / Content Download Page
Extremely short page -- 200-400 words maximum. The friction must be near zero. Headline: what the visitor gets. Subheadline: why it's valuable and who it's for. 3-5 bullet points: specific things they will learn or take away (not vague "you will understand X" -- specific: "the 7-step email sequence template used to generate $180K in 30 days"). CTA: "Send Me the [Resource Name]." Form: ask for email only if possible. Every additional form field reduces conversion by approximately 10-15%. Never ask for phone number on a lead magnet page -- it signals spam and kills conversions. The "social proof" on this page is the quality and specificity of the bullet points -- make the value of the download so obvious that the visitor would feel foolish not downloading it.
Webinar or Live Event Registration Page
The conversion goal is attendance registration. Two unique dynamics: (1) the visitor is committing time, not money -- so the primary objection is "Is this worth 60 minutes of my time?"; (2) social proof should include speaker credentials prominently, since the presenter is the product. Hero copy should include the specific date, time, and time zone in the subheadline -- vague "upcoming webinar" copy reduces registrations significantly. Include an agenda with 3-4 specific things attendees will learn, written as outcomes ("Leave with a completed 30-day content calendar, ready to hand to your team"). Post-registration: mention whether there will be a replay ("Can't attend live? Register anyway and we'll send you the recording") -- this objection is commonly responsible for 20-30% of abandoned registrations.
Existing Page Rewrite or Conversion Rate Improvement
Before writing anything, ask for the current conversion rate and the primary traffic source. Then ask: "Do you have any data on where visitors drop off or what they click?" (Heatmap tools like Hotjar or Microsoft Clarity, session recording, or scroll depth analytics from Google Analytics 4 all provide this.) If the hero has a low scroll-through rate (under 50% of visitors scroll past the hero), the problem is the headline or subheadline. If visitors reach the pricing section and then leave, the problem is price justification or missing guarantee. If the page has a good scroll depth but poor conversion, the problem is the CTA or missing risk reversal. Do not rewrite the entire page -- identify the single weakest section and focus the rewrite there. Recommend A/B testing one variable at a time: a new headline, a new CTA button text, or a repositioned guarantee statement. Rewriting multiple elements simultaneously makes it impossible to determine which change drove the result.
Competitor Comparison or Alternative-Focused Page ("Best Alternative to [X]")
This page type targets visitors who are already using or evaluating a competing product. The tone is confident, not hostile. The hero should name the competitor clearly ("Looking for an alternative to [Competitor]?") -- burying the comparison reduces the page's SEO and conversion value. The solution section should use a direct feature-by-feature comparison table where the product wins on the dimensions the target visitor cares most about. Never fabricate or exaggerate comparison claims -- they are easily fact-checked and create legal and reputational risk. Focus the comparison on the 3-4 dimensions where the differentiation is most compelling. Include a migration or switching guide reference ("Switching from [Competitor] takes under 20 minutes -- we'll import your data automatically") to neutralize the switching-cost objection, which is the primary objection on this page type.
Example
Input: "Write landing page copy for a B2B SaaS product called Operant. It's a workflow automation tool for operations teams at mid-market companies (50-500 employees). It replaces manual spreadsheet-based processes. Price is $299/month. Target visitor: VP of Operations or Operations Manager who is frustrated with their team spending hours on repetitive data entry and process tracking. Primary CTA is to book a demo. They have 3 solid testimonials and a logo bar. 30-day free trial available after the demo."
Output:
Landing Page Copy: Operant -- Workflow Automation for Operations Teams
Page Brief
Conversion Goal: Book a demo call
Traffic Source: LinkedIn ads (cold) + branded search (warm) -- writing for cold-primary
Target Visitor: VP of Operations or Operations Manager at a 50-500 person company; frustrated that their team spends 8-15 hours/week on manual spreadsheet processes and status-tracking that should be automated
Offer Price/Commitment Level: $299/month (demo required before purchase)
Page Length: Long medium (900-1,200 words)
Available Social Proof: 3 testimonials, logo bar, trial offer
Risk Reversal: 30-day free trial post-demo
HERO SECTION
Headline: Stop Running Your Operations in Spreadsheets
Subheadline: Operant automates the repetitive workflows your operations team tracks manually -- status updates, approvals, handoffs, and reports -- so your team spends time on work that actually requires them.
Primary CTA Button: Book a 30-Minute Demo
Micro-copy (below button): No commitment. We'll show you exactly how Operant handles your team's specific workflows.
Visual Direction: A split-screen animation or static screenshot: left side shows a cluttered Excel file with dozens of columns and color-coded cells (labeled "Before"); right side shows a clean Operant workflow dashboard with real-time status indicators, auto-assigned tasks, and a completion rate meter (labeled "After"). Clean, professional aesthetic matching mid-market B2B SaaS design standards.
PROBLEM SECTION
Your Operations Team Is Highly Skilled. They Shouldn't Be Doing This.
At some point, every operations team builds a spreadsheet to track something important -- an onboarding process, a vendor approval workflow, a monthly reporting cycle. One spreadsheet becomes five. Five becomes twenty. Now your team spends Monday morning updating trackers, chasing status from other departments, and reformatting data before leadership can look at it.
You hired operations professionals to find inefficiencies and fix them. Instead, they have become the inefficiency. Every hour spent on manual data entry, copy-pasting between tools, and sending "just checking in" emails is an hour not spent on process improvement, cost reduction, or scaling what's working.
The problem is not that your team is slow or disorganized. The problem is that the tools mid-market operations teams rely on -- spreadsheets, email threads, shared docs -- were not built for repeatable, multi-step workflows that involve multiple people and need an audit trail.
There is a better way to run operations at this scale.
SOLUTION SECTION
Section Header: Operant Replaces the Manual Work, Not Your Team
Positioning statement: Operant is a workflow automation platform built specifically for operations teams at mid-market companies -- the processes that are too complex for basic task tools and too repetitive for your best people to keep doing by hand.
Benefit 1: Every recurring process runs automatically, without reminders
Whether it is monthly vendor reviews, new employee onboarding checklists, or cross-department approval chains -- define the workflow once in Operant and it runs on schedule, assigns tasks automatically, sends reminders, and escalates when deadlines are missed. Your team stops project-managing processes and starts managing outcomes.
Benefit 2: Real-time visibility across every active workflow, in one view
No more asking "where are we on this?" Your dashboard shows the live status of every active workflow: what's complete, what's overdue, and who is blocking progress. Operational bottlenecks that used to take a weekly meeting to surface are visible in 30 seconds.
Benefit 3: Your leadership reports practically write themselves
Operant generates automated progress and completion reports in the format your leadership team expects -- without anyone reformatting a spreadsheet. Schedule weekly or monthly summaries to go directly to your VP or CEO's inbox. Show measurable operational progress without compiling it manually.
Benefit 4: Connects to the tools your team already uses
Operant integrates with Slack, Microsoft Teams, Google Workspace, Salesforce, and Zapier. Workflow triggers, notifications, and data handoffs work across your existing stack. Implementation does not require replacing anything -- it connects the tools you already have.
How It Works:Step 1: In your demo, we map 2-3 of your team's most painful manual workflows.
Step 2: Your Operant account is pre-configured with those workflows before your trial starts.
Step 3: Your team runs the first automated cycle -- usually within 48 hours of onboarding.
SOCIAL PROOF SECTION
Section Header: Operations Teams at 600+ Companies Have Closed Their Tracking Spreadsheets
Testimonial 1 (result-focused):
"We ran our entire vendor management process in a shared Google Sheet for three years. Six people updating the same file, constant version conflicts, and nobody ever knew the actual status. We implemented Operant in one afternoon. Within the first month, our team reclaimed 11 hours per week that was previously spent on tracker maintenance. That time is now going toward supplier renegotiations that have saved us $180K annually."
-- Marcus T., VP of Operations, LogicPath Inc. (220 employees, logistics technology)
Testimonial 2 (objection-busting -- addresses "this will be hard to implement"):
"I was skeptical because we'd tried two other automation tools that required months of setup and IT involvement. Operant was different. Our ops team configured our first three workflows without any technical help, and we were running live processes in the first week. It genuinely felt designed for operators, not developers."
-- Priya M., Operations Manager, Northfield Financial (85 employees)
Testimonial 3 (aspirational -- addresses the leadership visibility benefit):
"The most underrated thing about Operant is what it did for how my team is perceived internally. I can now walk into an executive meeting and show exactly what operations is working on, what's complete, and where there are blockers -- in real time. That visibility changed the conversation about what operations contributes to the company."
-- David H., Director of Operations, Clearwave Technologies (340 employees, SaaS)
Trust Metrics:
600+ operations teams use Operant
4.6/5 rating on G2 (310+ verified reviews)
Average: 9 hours/week recovered per operations team member in the first 90 days
Logo Bar Caption: "Trusted by operations teams at [Logo 1], [Logo 2], [Logo 3], [Logo 4], [Logo 5], [Logo 6], and 594+ others"
OBJECTION HANDLING (FAQ)
Section Header: Common Questions Before Booking
Q: We've tried automation tools before and the setup took months. How is this different?
A: Most automation platforms are built for developers or require deep IT involvement. Operant is configured by your operations team -- no coding, no IT tickets. In your demo, we map your workflows with you. Your account is pre-built before your trial starts. Most teams run their first automated workflow within 48 hours of kickoff.
Q: Our processes are complicated and unusual. Can Operant handle them?
A: This is the most common concern, and it is legitimate. Operations workflows at mid-market companies are almost never simple. That is exactly why we start every new customer with a workflow mapping session -- we look at your actual processes, not generic templates. If a workflow falls outside what Operant handles today, we'll tell you honestly during the demo rather than oversell and under-deliver.
Q: We have a small operations team. Is Operant overkill for us?
A: Operant is built for teams of 2-10 operations staff at companies with 50-500 employees. If you're running repetitive multi-step processes that involve more than one person and need to be trackable, the ROI is almost always clear. We can show you a break-even calculation during the demo based on your team's hourly cost and the processes you'd automate.
Q: What does $299/month include?
A: Unlimited workflows, unlimited workflow runs, up to 10 team members, all integrations (Slack, Microsoft Teams, Google Workspace, Salesforce, Zapier), automated reporting, and dedicated onboarding support for the first 60 days. Teams larger than 10 operators have a per-seat pricing structure -- we will quote that in the demo.
Q: What if we book a demo and it is not right for us?
A: Then it was a 30-minute call and no commitment was made. If you proceed to a trial, you have 30 days to run Operant on live workflows with full access. If it is not delivering measurable time savings by the end of the trial, cancel at no charge. We would rather you not pay than pay for something that is not working.
FINAL CTA SECTION
Closing Statement: Your team is spending hours every week on work that should not require them. Book a 30-minute demo and we will show you exactly which of your processes Operant can automate -- before you commit to anything.
Primary CTA Button: Book a 30-Minute Demo
Micro-copy: No commitment. 30-day free trial available after the demo. Cancel anytime.
Secondary CTA: Not ready for a call? Read how LogicPath recovered 11 hours/week in the first month →
(Urgency/Scarcity: None -- not applicable for this offer type. Do not add false urgency.)
