Osequencing OutreachYou can build a genuinely useful lead magnet and still get almost no takers.
Usually the asset is fine. The words around it are doing nothing.
This is the companion piece to How to Create a Lead Magnet Your Prospects Actually Want. That article covers what to build. This one covers how to talk about it so people actually claim it.
None of what follows is a trick. Every one of these works because it makes a real thing easier to see.
Start with the four things every line has to do
Before the individual patterns, there is a frame. Any piece of lead magnet copy — the headline, the button, the DM, the results email — should be doing at least one of these four jobs, and the strongest lines do all four at once.
1. Name the result they want. Not "save money." Not "improve your process." Something they would actually say out loud: "find out what this project will cost before you talk to anyone." Vague benefits are invisible. Specific ones stop the scroll.
2. Make it believable. A promise nobody believes is worse than no promise. Belief comes from specificity — exact numbers, their own inputs reflected back, a real source, a real name attached. The more personal the output, the more they believe it before they even get it.
3. Cut the wait. "Get your number in 60 seconds" beats "we'll send it over shortly," which beats "book a call to find out." Every hour between the ask and the answer costs you people.
4. Cut the effort. Five questions, not twenty. One form field, not six. Every input you ask for is a small toll, and some people turn around at the toll booth.
If a line you have written does none of the four, it is decoration. Cut it.
Frame it as what they're losing, not what they'd gain
People work harder to avoid losing something than to gain the same thing. That is not cynicism, it is just how the wiring goes.
So the same number lands twice as hard depending on the sentence around it:
- "You could save $47,000 a year." — nice, filed away, no action
- "You're losing $47,000 a year." — that one itches
Note that these can be literally the same figure about the same situation. Nothing was exaggerated. One version describes a hypothetical future, the other describes what is happening right now, and only one of them feels urgent.
Use the loss frame when the problem is genuinely ongoing and costly. Do not use it when you would have to invent the loss to make it work — people can smell a manufactured emergency, and you will spend trust you cannot get back.
Break the pattern, then reframe
There is a well-known test where a charity asked for "a penny a day" instead of "$3.65 a year." Same money. The unfamiliar framing forced people to actually think about the number rather than skim past it, and donations went up.
The mechanism: an unexpected phrasing interrupts the autopilot, and for a second the reader is genuinely evaluating instead of pattern-matching. Whatever you say next lands in that gap.
In practice, this means taking a number your prospect has stopped seeing and putting it in unfamiliar units:
- "That's not a $60,000 tool budget. That's eleven hours a week you are buying back."
- "23% of payroll" instead of "a lot of wasted time"
- "Six weeks of your team's output, gone to copy-paste"
You only get one of these per page. The effect comes from the surprise, and surprise does not survive repetition.
Give the reader a label worth living up to
If you assign someone a trait and then ask them to do something consistent with it, they are noticeably more likely to do it. People like to stay consistent with who they were just told they are.
This is why "For founders who already know the spreadsheet is a problem" works better than "For founders." The first one hands the reader an identity — someone perceptive, already ahead of it, not in denial — and claiming the lead magnet is how they confirm it.
Some that work:
- "For teams that are past guessing"
- "If you have already tried fixing this with process and it did not hold"
- "For operators who would rather see the number than argue about it"
The label has to be flattering and true, and it has to be one the reader would apply to themselves. Get it wrong and it reads as presumptuous, which is worse than saying nothing.
Put small, honest proof right next to the ask
Two forces do most of the work here: people trust experts, and people follow crowds. You do not need much of either — you need it in the right place.
The right place is directly beside the button or the field. Not on a separate page. Not in the footer. The moment of hesitation is at the ask, so the reassurance has to be at the ask.
What counts, in rough order of strength:
- a specific number — "Used by 340 agency owners"
- a named person with a real result
- your own credential, plainly stated — "Built by someone who does this for a living"
- a logo bar, muted so it supports the button instead of competing with it
If you have nothing yet, say something true and small rather than something impressive and vague. "I built this because the same question came up on eleven calls in a row" is real proof. "Trusted by industry leaders" is noise, and experienced buyers read it as noise.
Never let your proof validate doing nothing
This one gets missed constantly, including by people who are otherwise good at this.
Consider two true sentences:
- "Most teams never get around to fixing this."
- "Most teams who run this fix the biggest leak within a month."
The first one is meant to sound urgent. What it actually communicates is that not fixing it is normal, everybody does it, you are fine. It gives permission to close the tab.
Always frame your social proof around the behaviour you want. If the honest version of your data is that most people do nothing, then talk about the ones who did, and be specific about them.
Where this shows up in the app
There are two working lead magnets inside Outreach Sequencer you can read as a prospect would.
The Scope Headache Eliminator is built almost entirely on points 1 and 3 above — a specific dollar range and a week count, delivered in about two minutes, with the email asked for only after the answer already exists. Look at the button too: "See What My Project Will Cost" instead of "Submit." It finishes the sentence I want to… from the reader's side, which is the whole difference between a button that describes your database operation and one that describes their intention.
The 23% Leak opens on a loss frame with a real source behind it — SMBs spend roughly 23% of payroll on automatable work — and reframes it into a per-company dollar figure two sentences later. That is the disrupt-then-reframe move in its natural habitat.
The short version
Say what they get. Make it believable. Make it fast. Make it easy.
Then, where it fits naturally: frame the cost as ongoing rather than hypothetical, put one surprising reframe on the page, hand the reader an identity worth confirming, and set your proof right next to the ask.
Use the ones that fit. Forcing all six onto one page produces something that reads like it is trying to sell you a timeshare.