positioning-fix · v0.1.0 · 2026-10-15 · sha256 be8fa3b2009856fa
positioning-fix v0.1.0A
Immutable. This exact content never changes and is served at /api/v1/blob/be8fa3b2009856fa.
--- name: positioning-fix description: Review a homepage or landing page against the intended buyer and rewrite the headline, offer and proof order so a stranger understands what the product does in five seconds. Use when someone says their site is unclear, conversion is low, or they are changing who they sell to. metadata: author: Ekos Labs version: "0.1.0" --- # Positioning Fix Make the value of a product obvious to the right buyer. The output is a before and after for the top of the page and a reordered outline, each with the reasoning, so the founder can judge it rather than trust it. Execution mode: agent-native. Uses Claude Code or Codex and web reading. No API key needed. Example request: "Here is our homepage. We want to sell to agency owners, not freelancers. Fix the positioning." ## Inputs - The page URL or its copy. Read `product-context.md` if present. - The buyer the founder wants. If unclear, propose one from the context and confirm before rewriting. - Any claims that are off limits (legal, client confidentiality, unverified numbers). ## Method 1. **Five-second read.** Read only the first screen as the buyer would. Write what a stranger would believe the product is, for whom, and why now. Compare with what the founder wants them to believe. The gap is the problem statement. 2. **Diagnose** against the [positioning checklist](references/checklist.md). Name the two or three failures that matter most. Do not list every possible improvement. 3. **Rewrite the top.** Three headline and subhead pairs, each built on a different angle: the outcome, the alternative it replaces, or the specific buyer. Under each, one line on why it fits this buyer. Use the buyer's words where evidence exists. 4. **Reorder the page.** A section outline that leads with proof the founder actually has. Move or cut sections that do not help this buyer decide. 5. **Cut list.** Claims to remove because they are vague, unprovable, or aimed at a different buyer. 6. Read the result back as the buyer once more and state the new five-second read. ## Output ```markdown # Positioning fix: <product> for <buyer> Five-second read now: <what a stranger believes> Five-second read target: <what they should believe> Main problems: <2 to 3> ## Headline options 1. <headline> / <subhead>. Why: ... 2. ... 3. ... ## New page order 1. <section>: <what it proves> ... ## Cut - <claim>: <why> ``` Do not invent testimonials, logos, metrics or customer names. If proof is missing, say what proof to collect. Do not edit the live site unless the user asks for that as a separate step.