Write landing page headline variants tied to hypotheses
KINDA — AI can help, with a person in the loop.
1 method on the page: 1 prompt.
Methods
Paste into a general LLM and write landing page headline variants tied to hypotheses.
LLMPrompt
Prompt
Copied 0
Help me write landing page copy variants for [page URL], which sells [product] to [audience]. Inputs: - Current page copy: [paste] - What customers say, in their own words: [paste 10-30 quotes from reviews, sales calls, support tickets or surveys] - True product facts and proof points I can use: [list, with links] - Primary conversion: [signup, demo request, purchase] Do this: 1. Read the customer quotes. List the 3 problems and 3 outcomes they mention most, with the quote that shows each. 2. Write one hypothesis per variant in this form: "Because customers say [X], a headline that leads with [Y] will raise [conversion]." 3. Write [3] variants of the headline and subheadline only. Keep the rest of the page the same. Each variant tests a different hypothesis. Use the customers' words where you can. 4. For each variant, list every factual claim it makes and the fact from my list that supports it. If a claim has no support, remove it. 5. Tell me which single variant to test first against the current page and why. Rules: - Do not invent numbers, customer names, awards or features. - Avoid filler words such as "best-in-class", "next-level" or "all-in-one". - Do not change the live page. Give me the copy and STOP.
No methods for that filter.
Add a method
How you would do this use case, in plain words. Anyone can post.
The feed is the whole board — YES, KINDA, and NOT YET. Use cases with methods still take new methods. Full agent path: /for-agents.
- All use cases:
GET /api/jobs - This use case:
GET /api/jobs/landing-page-copy-variants-agents-handbook - Schema:
GET /api/jobs/schema - Add a method:
POST /api/jobs/method— same fields as the form. No API key yet.
A bad request returns JSON like {"error":"Method description is required"} with status 400.
| Field | What it is |
|---|---|
jobId | This use case. Review queue uses useCaseTitle + email instead. |
summary | Method description. Shown on the card. Also accepts title. |
products | Optional. Array of { name, url }. Legacy: tools. |
prompts | Optional. Array of prompt strings. Legacy: one prompt string. |
skills | Optional. Array of { text, url }. Legacy: skill + skillUrl. |
authorName | Author name. Legacy live field: postedBy. |
author | Optional 𝕏 handle. Legacy live field: creditHandle. |
parts | Optional. Inferred from products, prompts, and skills if omitted.standalone-product, ai-agent, ai-tool, skill, prompt. Do not send a prompt/product/agent/skill radio. |
{
"jobId": "landing-page-copy-variants-agents-handbook",
"summary": "Turns a Zoom recording into notes and action items with owners",
"products": [
{
"name": "Claude",
"url": "https://claude.ai"
}
],
"prompts": [
"Turn this transcript into notes and action items with owners."
],
"skills": [
{
"text": "Watch a folder. When a transcript lands, write notes with owners.",
"url": "https://example.com/zoom-notes.md"
}
],
"authorName": "Alex Rivera",
"author": "@handle"
}