Loading...
The playbook Moonrank's Writer Agent uses to write for the reason a buyer hesitated — usually a bad experience with someone who promised what you're promising.
Download the methodology, see the verbatim standard, or run it live inside the Writer Agent.
The Objection Mapping skill is how Moonrank's Writer Agent finds what a page actually has to disarm. It takes the position of a buyer who has already been disappointed by a similar supplier, and produces at least ten rows: the pain point named precisely, the verbatim as that person would really say it, and the atomic proof that answers it.
The standard for a verbatim is the part that makes it useful. "I want to see concrete results" is a category, not a quote. "The last agency sent me forty-page reports where the only readable KPI was the number of backlinks, never crossed with my CRM" is something only someone inside the job would say — and it tells you exactly what the page has to prove.
It's written as a SKILL.md, a plain-language instruction format that people and AI agents can both follow. Read it before writing a sales page, hand it to a sales team as a briefing, or let the Writer Agent map your audience.
“Our landing page converts badly and I don't know what's blocking people.”
Ten objections, and the three that matter are all about the last supplier rather than about you. The strongest: they cannot tell whether reporting will connect to anything they already use, because the previous agency's reports were unreadable and unconnected. Answering it needs a proof, not a paragraph — a named integration and a real dashboard screenshot, placed above the pricing rather than in an FAQ nobody scrolls to.
Role, company size, sector, and any bad experiences they've had before.
Ten pain points named precisely, from the position of a buyer already disappointed.
The quote as that person would actually say it — no sector clichés.
Subject, verb and data — verifiable, quantified, specific to that objection.
Named friction points rather than categories like "wants results".
Quotes only someone inside the role would produce, in their own vocabulary.
Subject plus verb plus data — verifiable claims, never adjectives.
Frequency, blocking intensity, and how much answering it differentiates you.
Case study, calculator, guarantee or FAQ — whichever actually disarms it.
Where on the site each answer belongs, and what it should ask for.