Sales Page is a Claude AI skill — researches your buyer's frustration before writing a word, then builds the page architecture around making them feel seen first and sold to second.
You read back the draft. It's clean. The headline names the benefit. The bullet points list what's included. The testimonial section has three quotes. The CTA button says "Get started today." You know, reading it, that it sounds like a sales page — and you know that's not quite right, but you can't name what's missing.
What's missing is the moment before the headline. The specific situation a buyer is in when they arrive on your page — the thing that's been going wrong, the cost of that thing going wrong, the exact words they would use to describe it to someone who asked. That's not in the draft because nobody researched it. The AI wrote the page about the product. A buyer lands on it looking for evidence that someone understands the problem.
When they don't find that evidence in the first two sentences, they make a decision so fast they don't notice making it. The page becomes one of the thirty other tabs they'll close without buying from. Not because your product is wrong — because the page didn't speak to them before it tried to sell them something.
The Problem Section Is Where Every Generic Page Fails
Ask any AI to write a sales page and it will produce a recognisable structure: a benefit headline, a problem section, a features list dressed as benefits, social proof, a CTA. That structure isn't wrong. The problem section is.
Generic problem sections describe frustration from the outside. They read like a narrator explaining a character's pain rather than the character living inside it. "Are you struggling to convert your traffic into customers?" is accurate — and it describes nobody specifically enough to create recognition. A buyer reading that sentence knows it was written for anyone who sells anything. It does not make them feel seen. It makes them feel categorised.
Compare that to a problem section that opens: "You built the thing. You launched it. You got the 'this is exactly what I needed' replies. Then the follow-up silence." That's written from inside the experience. A founder who has lived that sequence reads the second sentence and feels something shift — this page knows what the past three weeks have felt like. That shift is the mechanism that earns the scroll. Without it, a buyer reads the offer section with crossed arms. With it, they read it already half-convinced.
AI writes sales pages about products because products are what you brief it with. Buyers don't arrive on your page looking for a product description — they arrive carrying a specific frustration. The page that names that frustration before anything else is the one that keeps them reading.
This isn't a copywriting instinct most founders develop naturally, because it requires deliberately stepping out of product knowledge — the thing founders have most of — and into buyer language, which requires research that happens before the page is written.
That gap is exactly what the Sales Page & Landing Page Copy skill for Claude was built to close.
What Changes When Buyer Research Comes First
When the Sales Page skill runs, it surfaces buyer language before it touches page structure. That means pulling how people in your buyer's situation describe the problem in their own words — not the polished version they'd write in a case study, but the raw version: the forum post, the sales call objection, the message a prospect sends the week before they decide not to buy.
That language becomes the problem section. Not a paraphrase of it — the actual words, the actual situation. A SaaS founder whose offer is pipeline coaching doesn't open with "struggling to close deals?" The buyers who need pipeline coaching are opening their CRM every morning and seeing the same three opportunities that have been sitting at the proposal stage for forty days. That's the problem section. That specific sentence is why they're on the page at all.
Category research runs alongside it — what the highest-converting pages in your offer type are doing structurally right now. Where proof lands harder, how the offer is scoped and sequenced, which CTA framing earns the click versus which creates resistance. Page architecture follows from both inputs: buyer language determines the opening, category patterns determine the order.
The first sentence of your problem section is a test. Buyers pass or fail you on it before they've read your headline.
What that research unlocks isn't better writing — it's a page that passes the test. A buyer who recognises their own situation in the first paragraph reads every subsequent section differently. Scepticism is a posture that forms after you feel like you're being sold to. Recognition disarms it before it forms.
How the Sales Page Skill Builds the Copy
Three calibrating questions establish the offer, the specific buyer this page is written for, and the primary objection that loses deals before any output is produced. The research flows from those answers.
The Problem Section That Fails vs The One That Earns the Scroll
A freelance strategist is launching a productised offer: a four-week go-to-market sprint for early-stage SaaS founders. Same offer, two ways into the problem section.
Getting early traction is one of the hardest challenges for SaaS founders. Without a clear go-to-market strategy, even the best products fail to reach the people who need them.
That's where I come in. With 10+ years of experience helping early-stage startups find product-market fit, I offer a proven, step-by-step approach to building your GTM strategy — tailored to your specific market and stage.
Let's build your growth engine together.
Then nothing. The follow-up goes unanswered. Or they reply once and go quiet. Or they say they need to "think about it" and you never hear from them again.
Your product didn't fail those calls. Your path from interested to paying did — and that path is a go-to-market problem, not a product problem.
That's the only thing we work on in four weeks. Not positioning theory. Not a deck. The specific sequence of moves that turns "this is exactly what I've been looking for" into a payment confirmation.
The first version is written for a category — "SaaS founders with GTM problems." The second is written for a specific person in a specific moment: someone who has experienced the "this is exactly what I need" call followed by silence, and who has started to wonder whether the product is the problem. That doubt — the product, not the path — is the exact objection the page needs to address. It's addressed in the third paragraph, before a service is mentioned, before any credentials are listed. A founder reading that page who has lived that sequence doesn't encounter the offer with scepticism. They encounter it with relief.
Who This Is Actually For
Founders and solopreneurs launching a new product, service, or course who need conversion copy before they drive traffic. Anyone with an existing page that's getting visitors but not converting — and can't name exactly why. Freelancers scoping a new offer who want the copy shaped alongside the offer design, not after it.
The skill is most useful when you know the offer well but keep writing about it from your perspective rather than your buyer's. That's not a failure of effort — it's a natural consequence of having built something. You understand the product better than anyone on earth. That depth is precisely what makes it hard to write the first paragraph a cold stranger needs to feel understood before they'll read further.
It's the wrong fit if the offer itself isn't defined yet — if what's included, who it's for, and what outcome it delivers are still being worked out. The skill builds copy architecture from a clear brief. It sharpens and accelerates that process; it can't generate the product clarity the brief requires.
What You Actually Get
One complete sales page: problem section in buyer language, hero headline and subheadline, offer presentation with scoped deliverables, proof block, objection-handling woven through the body, and a CTA built around the specific action the page needs to drive. Section order is determined by the research outputs — if your buyer type needs proof before the offer, the page reflects that rather than following a fixed template.
From open to page: load the skill in Claude, answer three questions about your offer, your specific buyer, and the objection that most often loses you the sale — then receive copy ready to drop into your page builder. The quality gate runs before output arrives: problem sections that describe from outside the experience, benefit bullets that restate features, and CTAs that push before desire is established are all caught and rewritten first.
Understanding your product deeply is not what makes a sales page convert. Knowing how your buyer describes the problem before they've found the solution — and opening with that, word for word — is what makes a sales page convert. Most founders never learn the second thing because they spend their time building and selling, not listening to the language of the not-yet-customer. That's a research problem. It has a research solution.
The next piece most people tackle from here is job descriptions that attract the right candidates. If you're working across the full Founder workflow, the Founder bundle covers everything in one place.
Put this to work: the Sales Page & Landing Page Copy skill for Claude turns everything above into one guided workflow you run in a normal Claude chat. Not ready to buy? Start with a free Claude skill and see how it works first.