rampstackco/claude-skills / skills/lead-magnet-design
lead-magnet-design
VerifiedDesigning lead magnets that earn the email. The discipline of building gated content (ebooks, templates, checklists, swipe files, mini-courses, free tools) that delivers genuine standalone value while qualifying the lead and warming them for what comes next. Honest about thin-bait (overpromises, underdelivers), kitchen-sink-resource (everything, helps with nothing), and earned-value-magnet (delivers standalone value while qualifying the lead). Triggers on lead magnet, gated content, opt-in offer, ebook, checklist, template, swipe file, mini-course, free tool, content upgrade, freebie, opt-in, list-building offer. Also triggers when an audience is being asked for an email and the offer attached to that ask needs design discipline, when previous lead magnets converted but did not produce qualified leads, or when a lead magnet is being scoped for the first time.
| File | Kind | Size |
|---|---|---|
| README.md | markdown | 359 B |
| SKILL.md | skill md | 24.5 KB |
| references/audience-fit-qualification.md | markdown | 10.1 KB |
| references/common-lead-magnet-failures.md | markdown | 10.3 KB |
| references/delivery-and-follow-up-sequences.md | markdown | 10.2 KB |
| references/format-selection-patterns.md | markdown | 10.0 KB |
| references/format-specific-quality-gates.md | markdown | 11.0 KB |
| references/lead-magnet-anti-patterns.md | markdown | 9.9 KB |
| references/lead-magnet-decision-criteria.md | markdown | 9.5 KB |
| references/title-and-presentation-discipline.md | markdown | 10.0 KB |
| references/would-they-pay-for-this-test.md | markdown | 9.6 KB |
references/would-they-pay-for-this-test.md
View on GitHub# The "would they pay for this" test
The pricing thought experiment that distinguishes earned-value from thin-bait. A single test the magnet either passes or fails before launch.
The question is simple. If the magnet were not free, would someone in the target audience actually pay for it? Not pay enterprise pricing, not pay for a course, but pay something (5 dollars, 25 dollars, 100 dollars) because the value is concrete enough to justify the cost?
The honest answer matters. A magnet that fails the test is signaling that the value is below "I would pay for this," which means the reader's time investment to download and consume is at the edge of "worth it." The unsubscribe rate, the reduced trust, and the wasted email gate all follow from a failed test.
---
## How to apply the test
The test is a thought experiment, not a market study. Run it before the magnet ships.
**Step 1: Imagine a stranger in the target audience.** Not the team's existing customer; not someone already on the list. A stranger who has not yet committed to the brand.
**Step 2: Imagine showing them the magnet (the actual content, not the marketing).** Not the landing page; not the headline; the resource itself in the form they would receive it.
**Step 3: Ask: would this person, having seen this resource, pay something for it?** A small amount, an honest amount.
**Step 4: Be specific about the price.** Would they pay 5 dollars? 25 dollars? 100 dollars? The specific number forces an honest answer.
The test fails when the honest answer is "no, they would not pay for this; they would expect it to be free or to come bundled with something else." The test passes when the honest answer is "yes, this is worth paying for, even at a small price, because the value is concrete."
---
## What the test catches
Three failure modes the test catches reliably.
**The 5-page PDF that summarizes blog content.** Free elsewhere, available without a gate, worth 0 dollars in a paid context. Fails.
**The "Ultimate Guide" that nobody finishes.** Pay-worthy in theory (comprehensive coverage), not delivered in usable form. The reader pays for the resource and never extracts the value because the resource is too long to consume. The test surfaces this when the team imagines whether the reader would actually use what they paid for.
**The template that is so generic it adds no value over starting from scratch.** Pay-worthy framing (templates feel valuable), thin in execution (the template's content is "Insert your value here" 30 times). The test catches this when the team imagines the reader's reaction on opening the template.
The test catches these failures because the question forces honesty about the resource's actual value rather than the resource's marketing claim.
---
## What the test the magnet should pass looks like
A magnet that passes is one where:
- A reader in the target audience would pay for this resource because it produces a result they need.
- The resource is in a usable form (consumable in the time the reader is willing to spend, applicable to their specific situation).
- The resource is hard to find elsewhere or hard to assemble at the same quality.
The first criterion is about value. The second is about usability. The third is about uniqueness or curation. A magnet that hits all three earns the email reliably.
**Worked example: A passing magnet.**
The B2B SaaS founder magnet "the welcome-email template that 4x'd our trial-to-paid rate."
- Pay-worthy: a SaaS founder would pay 25-50 dollars for a template that demonstrably 4x'd a real trial-to-paid rate. The specificity (4x, real metric, real source) makes the payment plausible.
- Usable: 7 emails, copy-paste ready, with sender-side context for each. A founder can implement in 60 minutes.
- Unique: the specific template plus the specific result is not freely available elsewhere.
The magnet passes. It is worth the email.
**Worked example: A failing magnet.**
The "Marketing Trends 2026" PDF.
- Pay-worthy: a generic trends roundup is not worth paying for. Freely available analyses cover the same ground. The specificity is missing.
- Usable: a 30-page PDF of trend descriptions does not produce a result; it produces awareness, which the reader could have gotten elsewhere.
- Unique: marketing trend roundups are commoditized; this one is not differentiated.
The magnet fails. It captures emails that decay because the resource did not earn the relationship.
---
## When the test surfaces "almost passes"
Sometimes the answer is "they might pay 5 dollars but not 25 dollars." This is signal, not failure.
**The action.** Strengthen the resource until the answer becomes "yes, they would pay 25 dollars." This often means adding the specific worked example, the specific case study, or the specific tooling that makes the resource concretely useful.
**The risk of skipping.** Shipping the "5 dollar" version saves time but produces conversion-rate metrics that look fine and lead-quality metrics that disappoint. The strengthened version costs more upfront and pays back in lead quality and downstream conversion.
The test surfaces the gap between the magnet as built and the magnet at value-strong. The work to close the gap is often the difference between thin-bait and earned-value-magnet.
---
## When the test surfaces "this should not be a magnet"
Sometimes the honest answer is that the resource would not be paid for at any price.
**The action.** Do not ship the magnet. Either redesign the resource until it would be paid for, or accept that the resource is content (not a magnet) and publish it ungated.
**The release valve.** Not every piece of content has to be gated. Free, ungated content has its own value (SEO, distribution, brand). Forcing a gate onto thin content costs more than it adds.
The test sometimes leads to "this should not be a magnet at all." That outcome is fine; it prevents shipping a thin-bait magnet that costs list trust.
---
## When the test surfaces "this is so valuable we should sell it"
Occasionally the honest answer is that the resource would be paid for at a meaningful price (200 dollars, 500 dollars).
**The decision.** The team has a choice. Sell the resource (and use a different, more right-sized magnet for list-building) or use the high-value resource as the magnet (which signals exceptional generosity and often produces strong conversion at high lead quality).
**The high-value-as-magnet pattern.** Some brands give away exceptionally valuable resources as magnets specifically to signal expertise and generosity. The conversion to paid offerings often increases because the magnet establishes credibility.
The test surfaces this opportunity. The team's decision depends on the broader strategy.
---
## The team-honesty discipline
The test only works if the team answers honestly. Pressure to ship, sunk cost in production, attachment to the magnet's framing all bias the answer toward "yes."
**The discipline.**
- Have someone outside the magnet's authoring team apply the test. Outside-in honesty often catches what the authoring team rationalizes.
- Show the actual resource, not the marketing. The pretty landing page is not the test; the PDF or the template is.
- Be specific about the price. "Would they pay something" is too vague; "would they pay 25 dollars" forces specificity.
- Take the answer seriously. If the team applies the test and answers no, do not ship the magnet without redesign.
The test's value is in the honesty it surfaces. A team that applies it and ignores the answer is worse off than a team that does not apply it at all.
---
## What to do when the test fails
The magnet fails the test. Now what.
**Option 1: Strengthen the magnet.** Add the specific worked example, case study, tooling, or framework that brings the value to pay-worthy. This is often the right answer.
**Option 2: Redesign as a different format.** The topic might not be magnet-shaped in the current format. A 30-page ebook on a topic might fail; a 2-page checklist on the same topic might pass.
**Option 3: Reframe the audience.** The magnet's value depends on the audience. A magnet that fails for the broad audience might pass for a narrower segment that genuinely needs the resource.
**Option 4: Do not ship.** Some magnets should not exist. Killing the magnet is honest; shipping a thin one costs more in list trust than killing it costs in sunk effort.
The team's response to a failed test is the discipline marker. Strong programs redesign or kill; weak programs ship anyway.
---
## Common test failure modes
**The team rationalizes the failure.** "It is good enough; readers will appreciate it being free." This is the path to thin-bait.
**The team applies the test to the wrong audience.** "Would a generalist marketer pay for this" when the magnet is for SaaS founders. The test must use the actual target audience.
**The team applies the test to the marketing, not the resource.** The landing page sounds great; the resource is thin. The test surfaces this when applied to the actual content.
**The team skips the test under deadline pressure.** The magnet ships, the metrics look fine, the unsubscribe rate quietly climbs. The test was the protection against this; skipping it costs trust.
---
## Methodology-level choices that stay in the public skill
The test as a thought experiment with specific steps. The failure modes the test catches. The criteria a passing magnet meets. The team-honesty discipline. The decision tree when the test fails. The test failure modes.
## Implementation choices that stay internal
Specific magnets the team has tested and the outcomes. Specific price-point conventions for the team's audience. The team's outside-team review process. Specific redesign patterns the team uses for failing magnets. These vary by team and audience.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |