Lead Magnet Lab
Every lead-magnet idea our strategy swarm produced for LinkBuildingService.ae, scored, red-teamed and mapped to the visitors it serves. Open the prototypes, read the trade-offs, and pick the ones you want built.
- Add magnets or a whole bundle to My picks
- Copy my picks as plain text
- Paste the list into the chat to commission the build
- Visitor scenarios
- 25visitor scenarios mapped
- Concepts
- 58concepts scored and red-teamed
- Prototypes
- 10working prototypes to try
- Bundles
- 3build bundles, from lean to full
The final pass that merged, ranked and routed everything below.
Ten prototypes forming one system, not ten pop-ups. A Capture Conductor (your-ledger-workspace) owns every ask: one interruptive ask per visit, suppression after capture, one profiling question per return, and the WhatsApp Bridge that makes giving a number one tap. Magnets map to buying moments: price, comparison, WhatsApp-first founders and Arabic visitors, AI anxiety, not-now visitors, abandoners and non-buyers. Lean launch ships five in about 10 weeks; Growth adds comparison, AI and alerts; Full machine adds groups, compliance, pilots and partners.
How the swarm worked
Five stages, run in order. Each one fed the next.
-
Stage 1
Scenario mapping
Mapped who visits, where they land, what they want right now and the channel they prefer.
25 scenarios -
Stage 2
5 ideation lenses + market research
Five lenses generated concepts in parallel, alongside research on what agencies and tools already offer.
5 lenses in parallel -
Stage 3
3 gap-hunt rounds
Critics looked for visitors nothing served yet, and the swarm filled each gap.
24 gaps · 21 new concepts -
Stage 4
3 two-lens judges + red team
Each judge scored two of six criteria. The red team wrote a flaw and a fix for every concept.
58 scored · 3 fatal flaws -
Stage 5
Architect
Merged overlaps, shortlisted ten for prototyping, routed every scenario and wrote the rules and bundles.
10 shortlisted · 19 cut
One conductor decides which magnet a visitor meets
The ten prototypes run as one system. The Capture Conductor owns every ask, so a visitor sees one interruptive ask per visit at most, and none once we can reach them.
-
Step 1 Visit A visitor arrives from search, ads, an AI answer, a partner or a WhatsApp share.
-
Step 2 Page and trigger Page, referrer and behaviour match a routing row: scroll depth, idle time, a tool result or exit intent.
-
Step 3 · Capture Conductor Picks one magnet
- One interruptive ask per visit, never in the first 30 seconds
- Suppressed for 30 days once we hold a channel
- Priority: resume what they started, deliver what was generated, then the routed primary, then the fallback
-
Step 4 Capture One field, in the channel the visitor prefers. EmailWhatsApp
-
Step 5 Delivery The file, verdict or voice note lands where they asked for it.
-
Step 6 Nurture Only what they opted into, plus one profiling question per return visit.
-
Step 7 Strategist hand‑off A Hot lead (score 70+) gets a named strategist within 2 business hours, with the session timeline attached.
- Interruptive asks per visit
- 1
interruptive ask per visit, at most
- Quiet period after capture
- 30days
without interruptive asks after a capture
- Lead score bands
- 0–100
lead score from fit and intent; Hot is 70+
- Reply time
- 2hours
for a strategist reply to a Hot lead, in business hours
Three ways to stage the build
Each bundle includes everything in the one before it. Picking a bundle adds all of its magnets to My picks, and you can remove any of them afterwards.
The three bundles load from the portfolio data on this page.
Ten prototypes, in the architect's order
Each one is a clickable page with simulated data, so you can try the flow before anything is built. Open full detail for the brief, the routing and the red-team fixes.
Weighted total out of 10: capture rate 25%, lead quality 25%, differentiation 18%, feasibility 12%, brand fit 12%, safety 8%.
The ten prototypes load from the portfolio data on this page.
Which magnet each visitor meets
Every scenario has a primary magnet, a fallback, the trigger that fires it and the channel it captures on. Open a row to read its trigger.
Swipe the table sideways for magnets and channels. The scenario stays pinned.
| Scenario | Stage | Traffic share | Primary magnet | Fallback | Channel | Trigger |
|---|---|---|---|---|---|---|
| The 25 routing rows load from the portfolio data on this page. | ||||||
All 58 concepts, scored and red-teamed
Every concept the judges scored, including the ones that missed the shortlist. Open a row for the mechanic, the red-team flaw and fix, and the judges' notes.
Showing 58 of 58 concepts
- The catalogue loads from the portfolio data on this page.
No concepts match these filters.
The 23 rules the conductor runs on
These apply to every magnet you pick. They cap asks, govern consent and decide when a strategist steps in.
The rules load from the portfolio data on this page.
What the critics found, and what we cut
The gaps drove the three gap-hunt rounds. The dropped list shows what was merged away or ruled out, and why.
Gaps the critics found24
The gaps load from the portfolio data on this page.
Ideas dropped or merged, with reasons19
The dropped ideas load from the portfolio data on this page.
Ready to commission the build?
Add magnets or a bundle, then copy your picks and paste the list into the chat. We scope and build from that list.
My picks (0)
Paste the copied list into the chat to commission the build.