When should you use it?
- You are about to split test a landing page and only have a handful of headline ideas
- You have customer calls, support chats or ad results that nobody has mined for wording
- A launch or campaign needs fresh angles quickly
Not for: Teams with no real customer material to feed the agents, since the output would be generic; Regulated claims (health, finance) unless every option is checked by someone qualified; Pages with too little traffic to tell winners from noise in a split test
What do you need, and what do you get?
You need
- Exports of customer conversations, such as chat threads and call transcripts, with personal details removed
- Your best performing ads or emails and their results
- The page's offer, audience and any claims you cannot make
You get
- A research summary of customer pains in their own words
- Two independent sets of headline and subheadline options
- A local review page for rating options and adding notes
- A shortlist of about ten options ready for testing
How does it work, step by step?
- Gather the materialPut the transcripts, chat exports and ad results in one folder and strip names, emails and account numbers.
- Run two agents separatelyGive the same prompt to two different agents so you get two independent takes rather than one voice.
- Build the review pageAsk one agent for a single local HTML page that shows one option at a time with keep, drop and note buttons.
- Cut by handGo through the pile, keep about thirty, then edit and trim to the ten you would actually bet on.
- Test and logLoad the finalists into your split testing tool and record which pain point each one targets so results feed the next round.
The prompt
Our own prompt, inspired by James Camp (@JamesonCamp) and written to work in Claude Code and Custom agent. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
Read everything in {research_folder}: customer chats, call transcripts and our best ads with their results. 1. Summarize the top {number} customer pains, quoting short phrases customers actually used, and note how often each appears. 2. For each pain, write as many distinct landing page headlines (under 12 words) and matching subheadlines (under 25 words) as you can without repeating an angle. 3. Do not invent numbers, results or guarantees; we cannot claim {banned_claims}. 4. Save the options as a CSV with columns pain, headline, subheadline. 5. Build one local HTML page that shows one option at a time with keep, drop and note controls and exports my choices as a CSV.
Inspired by James Camp (@JamesonCamp): X post: two agents wrote 250+ landing page headlines from customer research. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Volume is not quality. Most options will be near-duplicates; the value is in the few angles you had not considered.
- Agents can invent statistics or promises. Remove any claim your product cannot back up.
- Customer exports can contain private data. Anonymize before handing them to any agent.
- Testing too many finalists at once spreads traffic thin. Start with a few and rotate.
Our take
What makes Camp's setup work is not the number of headlines; it is where the words come from. Feeding the agents real conversations and the ads that already performed means the options borrow the customer's own language rather than generic marketing phrases. Running two different agents on the same brief is a cheap way to escape one model's habits, and the swipe page is a smart touch: rating 250 lines in a spreadsheet is tiring, while a one-at-a-time view with a keep button keeps you moving. He is also clear that the final cut is human work, which is the right division of labor for anything that goes in front of buyers. Our cautions are practical. Strip personal data before any export leaves your systems, delete claims you cannot prove, and only test as many finalists as your traffic can support. In our dry run with a fictional bookkeeping app's support chats and three ads, the two prompts produced 80 options across six pain points, the review page worked offline, and a third of the options were near-duplicates we dropped quickly.
Where the time goes back: The agents do the reading and drafting that would take a copywriter days, and the review page lets you sort hundreds of options in an hour, so your time goes into choosing rather than writing.
FAQ
Why use two agents instead of asking one for more?
Do I need a coding agent?
How much did it save him?
Source and credit
Inspired by James Camp (@JamesonCamp). We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- X post: two agents wrote 250+ landing page headlines from customer research
- Creator
- James Camp (@JamesonCamp)
- Published on
- X
- Original date
- Nov 4, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Claude Code
- AI dry run
- Nov 5, 2026: passed. Dry-run tested by our AI test agent on sample input. Research grounded in the fixture wording, two independent sets, banned claims respected, working offline review page; near-duplicates expected and easy to drop.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Nov 5, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.