Why most gated assets collect nothing, and how to build one that produces qualified conversations.
Written for Marketing teams at legal, SaaS and professional services firms whose pipeline depends entirely on people already ready to buy.
The bottleneck
A lead magnet fails when it is a brochure behind a form. The visitor can tell within one screen whether the document was written to help them or to capture them, and a brochure trains them not to trust the next thing you offer.
The second failure is downstream. Most gated assets have no sequence behind them, so a download produces a name in a list and nothing else. The asset gets blamed when the absent follow-up was the problem.
Why it happens, five levels down
- Downloads are low or the leads are poor.Why? The asset does not solve a problem worth an email address.
- It was written as marketing collateral.Why? It was produced by people selling the service rather than people delivering it.
- Delivery expertise never entered the document.Why? No practitioner time was budgeted for it.
- Content production is treated as a marketing cost.Why? Its value is measured in downloads rather than pipeline.
- The asset is measured on the wrong number.Root cause. Downloads are a vanity metric; qualified conversations are the output.
The diagnostic
Run this before planning any work. It tells you whether this is your constraint or whether something else is.
- Read your gated asset. Would you give a stranger your work email for it?
- Check whether it answers a question the reader has this week, or explains a category they already understand.
- Confirm the landing page does one thing. Navigation on a landing page is a leak.
- Check what happens in the seven days after a download. If the answer is nothing, fix that before the asset.
- Look at your consent language against the privacy rules in every market you collect from.
- Check whether downloads are segmented by asset in the CRM, or all dumped into one list.
The build sequence
| Stage | Work | Timing |
|---|---|---|
| Choose | Pick a high-intent operational problem your delivery team solves weekly. | Week 1 |
| Build | Write it with a practitioner. Diagnostic and checklist beat explanation. | Weeks 2–3 |
| Land | One focused page, one action, no navigation, consent captured properly. | Week 3 |
| Sequence | Four to six educational emails that assume the problem, not the category. | Week 4 |
| Route | Send qualified downloads to a human with a defined response expectation. | Week 4 |
| Review | Check lead quality monthly, not download volume. | Ongoing |
KPI watchlist
| Metric | Source | Read it as |
|---|---|---|
| Downloads per month | Form data | Reach, not success |
| Opt-in rate on the page | Landing page analytics | Whether the offer is compelling |
| Conversations from downloads | CRM source field | The actual output |
| Cost per qualified lead | Spend against CRM stage | Whether it pays |
Record a baseline and a date range for each before any work begins. Reconstructing a baseline afterwards is usually impossible.
Four ways this goes wrong
- Gating a brochure. It costs you the next offer too.
- Building the asset with no sequence behind it.
- Asking for phone number on a first download.
- Counting downloads as pipeline in a board report.
Build one asset properly rather than five badly
One gated asset with a real diagnostic outperforms a library of overviews.
