Hire an AI reasons-to-switch landing page writer

Everything it can hand back

Your task sets the actual outputs. The specialist picks the methods that cover them.

• An offer that answers the doubt, its wording and a profit check
• A page with 3 to 7 reasons to switch, proof beside each, and three headline options
• A list of doubts the page still leaves open, with the answer to add and where
• A ranked list of fixes, quick wins first, and a score out of 100

How it does the job well

• Write for one named audience and one action. Each asset has a single job.
• Use the customer's own words from reviews, calls or surveys before inventing language.
• Every claim needs proof the business can show. Leave unproven claims out or mark them.
• Judge results against the business goal, such as profit or qualified leads, not clicks alone.

Mistakes it avoids

• Generic copy that could fit any brand.
• Comparing periods or campaigns that are not comparable, such as different dates, budgets or tracking.
• Calling a test winner before there is enough data.

What a good result looks like

An example, not your task: Your buyers already use a rival or an old habit and your page doesn't say why they should move.

• outputs/step-01-offer-builder.md. An offer that answers the buyer's doubt, with its wording and a profit check.
• outputs/step-02-reasons-to-switch-page-writer.md. The page with three headline options, 3 to 7 reasons with proof, the offer once and a questions section.
• outputs/step-03-customer-question-finder.md. Each customer doubt the page still leaves open, with the answer to add and where.
• outputs/step-04-landing-page-auditor.md. The audit report with a score out of 100 and fixes ranked, quick wins first.
• HAND-BACK SUMMARY. Each step's file, any step not run and why, and every MISSING line in one list.

How the work is checked

• The offer answers one named doubt and passes its profit check.
• Each reason has a fact or a review beside it. Check three.
• The offer appears once, after the reasons, with every condition stated, and its price and terms match what you gave.
• Each open doubt names a customer question and the section where its answer goes.
• States which checks passed, failed or could not run, and names missing inputs.

These checks have not been run against a model yet. Your AI uses them to check its own work.

A second opinion

Before it hands back, your AI reviews the draft the way Alex Hormozi and Claude Hopkins would. This is a way of reviewing the work. It does not mean they wrote or endorse it.

Capabilities

• Builds the offer. Uses the offer builder skill to put the buyer's doubt on one lever, build the offer, check the profit and word it.
• Writes the page. Uses the reasons-to-switch skill to pin the buyer and the old way, choose 3 to 7 reasons, put proof under each and place the offer once.
• Finds open doubts. Uses the unanswered question skill to check each customer doubt against the page and say where each missing answer goes.
• Audits the page. Uses the landing page auditor to read the page as a glance, a skim and a doubt, check phone basics, count the open doubts from the step before as findings and rank the fixes.

How the role works

1. Checks your task, context and available tools.
2. Picks the methods needed and prepares a work plan.
3. Carries out supported tasks, with each method's limits and review gates.
4. Checks the real deliverables and corrects supported faults.
5. Hands back files, evidence and unresolved gaps.

Your specialist's working setup

Download the base specialist without a task form or account. README.md and SETUP.md explain how to use the folder. SOUL.md defines its scope. INTAKE.md asks missing questions inside your AI. PLAYBOOK.md, SKILLS.md, BEST_PRACTICES.md, CHECKS.md and HANDOFF.md guide the work and its checked deliverables.

Complete associated skills, supporting files and licences are included. Choose only the methods needed for the actual task. Keep context, working files and accepted feedback in your AI project.

Use this specialist through MCP or the API

Call prepare_specialist with role_id reasons-to-switch-page only. No task is required to load it. Your AI asks what job you need done, what you want back and which relevant context it can use.

For task-led hiring, call find_specialist, explain the suggested specialists and let the user accept or change the team.

Complete ZIP: Download base specialist. API: GET /api/v1/specialists/reasons-to-switch-page/pack. The host AI supplies its own model, tools and execution; a pack does not connect accounts or run a task.

Inputs and helpful context

The specialist starts from the task brief. Only active methods require their inputs.

For the primary method, when used

• The buyer and their biggest doubt, in their words
• Your product facts and what the offer costs you
• Customer questions or reviews, copied as written
• Your brand file, if you have one (optional)

Helpful context (optional)

• Support tickets or pre-sale questions, to find real doubts
• Your costs per order, so the profit check is honest
• Screenshots of the current page on a phone

Tools and access

• Claude: Holds the offer terms, the reasons and the doubts straight across four steps.
• PageSpeed Insights: Free Google check of a built page for phone speed and tap target problems.
• Shopify: If you sell on Shopify, it exports every order with totals, line items, discounts and shipping, which the profit check needs.
• Google Sheets: Keeps the profit check as formulas, so you can change a cost and see what one order keeps.
• Any good chat AI: Any current chat AI can match the doubt to a lever and word the offer.
• Any good chat AI: Any current chat AI can sort the facts and write the reasons. Give it the full facts so it adds nothing.
• Hemingway Editor: Marks hard sentences in yellow and red, so long reason bodies get cut before the page goes live.
• Any good chat AI that reads images: It can check your phone screenshots for where each answer sits, not just the page text.
• Google Sheets: Holds the doubt table so you can sort it, add new reviews, and tick off fixes.
• Any good chat AI: Any current chat AI that reads screenshots can run the three reads. Give it phone screenshots, top to bottom.
• PageSpeed Insights: Shows your page's real-user speed against Google's 'good' marks, so the phone check has numbers.
• Evan Miller's sample size calculator: Tells you how many visitors a test needs, so you know if it can finish in about a month.

Functions and deliverables

• Reasons-to-switch landing page writer: Share buyer doubts, product facts and costs. Get an offer draft, reasons-to-switch page, unanswered questions and ranked page improvements.
  • An offer that answers the doubt, its wording and a profit check
  • A page with 3 to 7 reasons to switch, proof beside each, and three headline options
  • A list of doubts the page still leaves open, with the answer to add and where
  • A ranked list of fixes, quick wins first, and a score out of 100
• Customer offer builder: Build an offer that answers your buyer's main doubt and still makes a profit. Give it one buyer, your prices and costs. Get up to three offers.
  • Up to three offers, each on a different lever, with who it's for, what they pay and what makes yes safe
  • The line for the page, the line a person would say aloud, and the terms
  • A profit check, or the formula when a cost is missing
  • What you must arrange first, the five checks, and a test plan
  • Any of the five checks an offer still misses, one line each
• Reasons-to-switch page writer: Write a reasons-to-switch page for buyers comparing options. Give it your facts and offer. You get 3 to 7 reasons, the offer and headlines.
  • Your facts sorted into push, pull, doubt and habit
  • Three headline options with a pick, and 3 to 7 reasons with titles, bodies and proof
  • The offer block, one question per doubt, a closing and the button text
  • Layout notes, a MISSING list, and any check it couldn't meet
• Unanswered customer question finder: Find the customer questions your product page leaves unanswered. Paste reviews and phone screenshots. Get a doubt table, fixes and a score out of 100.
  • A table of doubts, each with a quote, its source count, where the page answers it and how visible that is
  • The fact or proof each answer needs, and a proposed answer and place
  • The top five fixes and a list of facts to collect before writing
  • A coverage score out of 100 (how many doubts the page answers where buyers can see them), now and with the new answers in
• Landing page conversion reviewer: Share your page and screenshots. Get conversion problems ranked by impact, with recommended fixes and a score.
  • The page's job, a one-line verdict, and whether the page matches its ad
  • What a buyer takes from a five-second glance and from a skim
  • A ranked findings table, each with a severity from 0 to 4 and where it sits
  • Up to five quick wins, up to three tests, and what the page can't tell you
  • A page score out of 100 worked out from the severities, now and after the quick wins
• Brand profile builder: Share your website. Get a reusable profile covering your products, customers, voice and approved claims, with sources.
  • A folder of eight plain files, from a start file for your AI to a claims list and a change log
  • A tag on every fact, and every claim marked approved, pending or banned
  • A two-sentence diagnosis of your biggest gap, and a list of what's missing and who can answer it
  • A short slice for your next step, if you name one
• Alex Hormozi: Improve an offer, price or lead plan using Alex Hormozi’s recorded frameworks. Check buyer needs, costs and honest promises before adding more leads.
  • Your problem worked on the way Alex Hormozi would: their questions, their method, their push-back
  • The answer or the work, in Alex Hormozi's voice, using their ideas by name
  • Anything that goes beyond their public record, marked
  • One suggested next step
• Claude Hopkins: Write specific ads or plan a small buyer test using Claude Hopkins’s recorded approach. Replace vague praise with facts and track cost per customer.
  • Your problem worked on the way Claude Hopkins would: their questions, their method, their push-back
  • The answer or the work, in Claude Hopkins's voice, using their ideas by name
  • Anything that goes beyond their public record, marked
  • One suggested next step

Tasks you can use it for

• Your buyers already use a rival or an old habit and your page doesn't say why they should move.
• Buyers keep asking the same question before they buy and your page doesn't answer it.
• You want an offer and a page made together, so the page carries an offer that answers the doubt.

Limits to check before starting

• Your buyers have no rival or old habit to leave: use the Article-style landing page writer to tell the story instead.
• You already have a page and only want it reviewed: use the Landing page conversion reviewer on its own.
• You only want customer questions turned into answers: use the Customer FAQ writer.

Best way to use this role

Give it one clear outcome, the actual files and a definition of done. Keep the work in one AI project so it can reuse checked context and earlier files.

• Download the handoff pack. It's a zip with HANDOFF.md and every skill file this workflow uses.
• Give the folder to Claude (in Claude Code, or as files in a Claude Project) and say "Follow HANDOFF.md".
• Have your inputs ready. Your buyer's doubt, your product facts, your costs, and real customer questions if you have them.
• It works step by step and saves each result. Check the offer first, including the profit check. The page carries it from then on.
• Add the answers from step 3 to the page, then work through the fixes from step 4.

Read it as data

Read the complete role setup as JSON. Connect your AI to the AI Blocks MCP library and read aiblocks://roles/reasons-to-switch-page for its role instructions and pinned sources.

This is a prepared AI role. No task has run. Your AI carries out authorized work using its available tools and reports the actual deliverables and checks.