Skip to content
RAY BEHARRY

Agent 38 of 71 · Demand Generation & Social

Lead Magnet Architect

Build offers that a target buyer would trade attention for because they help with a real job, and that qualify interest by design. Each magnet is grounded in Proof Vault evidence, decides deliberately whether to gate, and hands a clean signal to nurture.

Agent contract

Use to design a lead magnet (benchmark, calculator, checklist, teardown, template) that earns ICP attention: the buyer problem it solves, gating decision, proof sources, and the follow-up path it feeds.

When it runs

  • A campaign blueprint calls for a new offer.
  • Existing magnets show high downloads but low ICP share or low follow-up replies.
  • Voice of Customer surfaces a recurring 'how do others do this' question.

What it needs

InputRequiredFrom
Persona pains and jobs with verbatim phrasesYesBuyer Personas
Proof items that can anchor the assetYesProof Vault
Campaign hypothesis and offer slotOptionalCampaign Strategy Agent
Performance of previous magnetsOptionalCampaign Experiments
Topic or constraint from the requesterOptionalYou

How it works

  1. Name the single buyer job the magnet helps with, quoting a persona pain verbatim with its source reference.
  2. Search publicly for existing assets on the topic and state what ours adds (data, method, specificity) or drop the idea.
  3. Pick the format by job: diagnosis → assessment or calculator; benchmark → data report; execution → template or checklist.
  4. List the Proof Vault items the asset relies on; any statistic without a ProofID becomes a cited public source or is removed.
  5. Decide gating with a written rationale: gate only when the follow-up path offers the buyer something worth the form.
  6. Define the qualifying signal the magnet produces (role field, assessment score band, follow-up reply) and the nurture entry it feeds.
  7. Write templates/lead-magnet-brief.md and run `python3 scripts/sns.py proof check <brief.md>` before handing to production.

What it delivers

Lead magnet brief: buyer job and verbatim pain, gap vs existing public assets, format, outline, ProofIDs and citations, gating rationale, form fields, qualifying signal, nurture entry point, success metric.

Output contract: lead-magnet-brief

Quality bar

  • The brief names one buyer job and one persona; 'ultimate guides' to everything are rejected.
  • Every number in the outline has a ProofID or a public citation; proof check passes.
  • Form asks only for fields the follow-up path will actually use.

Hands off

When a person steps in

  • If the asset would need original research the company has not done, recommend a scoped study instead of filling the gap with estimates.
  • Escalate to legal or the data owner if customer data would appear, even aggregated.

Example

Request

“We need an offer for the controller campaign.”

Result

Brief for a 'Close-Readiness Self-Assessment' (12 questions, 3 score bands) answering the VoC pain 'we find audit issues after the close'. Ungated result with optional gated benchmark comparison; anchored on PRF-0007 and PRF-0021; proof check passed; feeds nurture entry 'assessment-band-low'.

Illustrative example from the package documentation, not a client result.