leedab · idea · 2026-05-03 · half-baked, sharing for reaction
Auto-generate per-prospect pitch pages, on a pipeline.
We just hand-built three of these for Rome, Pillarix, and the lead-gen idea itself. The pattern is repeatable. The marginal cost per prospect is tiny if we automate it. Here's the shape — partnership outbound first, customer outbound second.
The pipeline.
Five steps · same loop for both tracks · changes per track are scraper inputs and generator prompt.
step · 01
Find
Scrape candidates by ICP filter — adjacent agent cos, vertical SaaS, SMB tooling cos for partnerships; vertical-shaped SMBs for customers.
tools · Apify · Sales Nav · Apollo
step · 02
Enrich
Pull public context — what they do, who's there, what they've shipped, which gaps they hint at on their site / blog / hiring page.
tools · Claude web search · Clearbit · LinkedIn
step · 03
Generate
Render a personalised one-pager from the LeedAB template — their name, their pain, their fit shape, our matching offering.
tools · Claude API · the existing HTML template
step · 04
Deliver
Send via the right channel for the prospect — LinkedIn DM, email, WhatsApp. Format depends on warmth (see next section).
tools · n8n · Gmail · LinkedIn API · iMessage
step · 05
Track
Per-prospect URL · open / time / scroll · feeds back into scoring · next-best-action recommendation.
Same generator. Different scraper input, different prompt, different artifact tone.
primary
track · 01 · partnership outbound
Find adjacent companies. Pitch the trade lane.
Adjacent agent companies, vertical SaaS, SMB tooling, infra companies for AI agents — anyone where LeedAB is a substrate, complement, or distribution surface. The artifact is what we sent Rome and Pillarix: market map + 3 trade shapes + what we'd want to learn.
think · Rome AI · Pillarix · vertical AI cos by category · agent-infra cos
artifact: trade-lane one-pager · 3 partnership/license shapes · discovery questions · "we'd love a 30-min call"
secondary
track · 02 · customer outbound
Find SMBs in pain. Pitch the offering.
SMBs in target verticals showing ops drift signals — multiple manual handoffs, growing headcount without ops infrastructure, complaints in reviews about delivery / billing / scheduling. The artifact is pain-shaped, not partnership-shaped.
think · 30–150 person services / trades / agencies · firms naming ops pain in hiring posts or job ads
artifact: "what LeedAB would do for you" · their named pain · their stack · our agent set · "demo your business in 7 days"
The "scary link" problem.
Cold recipients won't click an unfamiliar URL. The artifact format has to match the warmth of the channel.
format · 01
Image card.
One PNG/JPG that summarises the pitch. Renders inline in WhatsApp / iMessage / LinkedIn. No click required.
trust
friction
use · cold first contact
format · 02
PDF attachment.
Same content, downloadable. Email-native. Feels like a normal business document, scannable on phone.
trust
friction
use · email outreach
format · 03
Hosted on owned domain.
Branded URL — leedab.com/p/<slug>. Looks legit. Use after first reply or when sender is known.
trust
friction
use · warm follow-up
format · 04
Pages.dev random URL.
What we used for Rome and Pillarix. Fine when there's existing context (Muiez forwards). Cold-spam from unknown sender = ignored or flagged.
trust
friction
use · internal · forward-warm only
trigger conditions
When this gets built.
wait
Manifest reorg + COO MVP ship first. We don't have spare cycles for a new build until those land. Mid-late May 2026.
wait
ICP signal sharpens. We need 2–3 more paying customers to know what "looks like a LeedAB customer" means in scrape-able terms. Pattern-matching, not guessing.
go
Solutions agent (prospect-builder) is functional — this idea is its natural extension. Same code path, different entry point. Build it as a feature of Solutions agent, not a separate system.
don't
Don't ship slop. Templated personalisation reads worse than generic copy. Bar is genuine-feeling per-prospect, or don't send it.
questions for muiez
What I'd love your read on.
Do we agree partnership-outbound first, customer-outbound second?
What's the ICP signal you'd trust for SMB customers — review sentiment, hiring posts, tech stack, all three?
Do we host the artifacts on leedab.com (warmer) or accept the pages.dev for v1 and migrate later?
Should this slot under the Solutions agent or be its own pipeline / repo?
What channel do we trust most for cold outreach — LinkedIn / email / WhatsApp / mix?