LeadGen OS — Outbound That Replaces Your First SDR Hires
This proposal deploys the outbound engine you walked through on the call, tuned for the ICPs you ghostwrite for, sending from infrastructure that protects your real domain, at a fraction of the per-lead cost of the platforms an SDR hire would otherwise drive. The pitch is simple: the first SDR you'd hire to grow the practice can be a system instead, running the same loop more consistently than a person would and feeding the rest of your stack while it works.
The flow we walked through on the call
Six moving parts. The engine runs all of them.
- 1. Source — configurable research per ICP, the system reverse-engineers where to find each prospect
- 2. Enrich — multi-source signal pulled per lead at a fraction of per-lead-priced platforms
- 3. Personalize — openers grounded in real research, reviewable in batch before send
- 4. Send — multi-channel sequencing across email and LinkedIn, isolated from your real domain
- 5. Detect — replies caught automatically, sequences paused, real conversations routed within hours
- 6. Sync — replies become deals in your pipeline, signed prospects become clients in delivery
The engine is already in production. We use it ourselves to run Node's outbound. Plug-and-play means we deploy it under your accounts, calibrate it for the ICPs you actually want to write for, and hand you the keys. Same engine we run on our own pipeline, calibrated for yours.
You've built a credible ghostwriting practice on top of a content output that earns warm inbound on its own. The brand works. What's missing is a second engine running in the background, one that doesn't depend on the next piece performing, doesn't cost a full SDR salary, and doesn't put your primary domain at risk every time it goes wide.
Strengths
- AI-native already. You run your day through Claude and a sharpened toolkit. The engine is built to plug into that workflow rather than displace it. You're already operating at the abstraction level it expects.
- Sharp ICP intuition. You know which founders, operators, and brands you want to write for and which you don't. That intuition is the most important input the engine takes; everything downstream depends on it being right.
- Content output that already produces warm inbound. The brand is doing real work. Outbound doesn't replace warm inbound, it sits beside it, picking up the prospects who would have been a fit but were never going to find you on their own.
But four limits cap the next stage of the practice.
Limitations
- New-client acquisition is manual or absent. Inbound is unpredictable by design. Every quarter without a second acquisition channel is a quarter where pipeline depends on whoever happened to land on a post that week.
- An SDR hire is the obvious next move, and the wrong one to make first. Salary, ramp, management, the cost of training someone into your taste and your ICPs. The first hire that earns out is rarely the first hire you have to make. The engine takes the first 1-2 SDR jobs off the table entirely.
- Per-lead enrichment costs eat the budget on the obvious platforms. At the volumes you'd actually need to fill the calendar, the per-lead pricing on the standard tools turns outbound into an expense line that fights against itself. The engine consolidates the same upstream signal at a fraction of the cost.
- Your primary domain is the wrong place to send cold. Outbound from the inbox you use for clients, partners, and warm conversations ties brand reputation directly to deliverability. One bad week and the domain you use to talk to existing clients pays the price for months.
Opportunities
- Sustained volume at the same reply rate. Reply rate is set by the offer and the ICP, not the tool. What changes is how much volume you can put through that reply rate without burning your domain or your hours.
- Per-lead costs collapse. The same upstream signal the expensive platforms charge per-lead premiums for, run through infrastructure under your own accounts. The longer the engine runs, the wider the gap.
- One engine, every campaign cycle. Today's ICPs. Next quarter's new offer. The agencies and founders you want to land six months from now. Build the outreach engine once, recalibrate it as the practice evolves.
The outbound engine you saw demoed, deployed under your accounts and calibrated for the ICPs you actually want to write for. Three layers. One workspace. Bidirectional sync into the rest of the stack.
The Engine
Layer 1 · Sourcing & Research
Find the right people, with the right context
- Decision-maker identification tied to the role you actually need to reach (founders, marketing leads, heads of content, ops partners), not blasted into a generic database. The engine reverse-engineers where each ICP lives.
- Configurable research profiles per ICP. Different sources for different segments: social posture for one ICP, website signal for another, third-party data for a third, search-grounded research for the fourth. Each profile is a setting, not a custom build; you reconfigure it as your practice evolves.
- Plug-and-play scraping. Point the engine at a new competitor, account, or source URL and it backfills the last three months automatically, then keeps a refresh cadence you set. New sources stop being projects.
- Cost economics that compound. The same upstream data the expensive platforms charge per-lead premium for, run through infrastructure under your accounts. The longer the engine runs, the wider the gap between what you spend and what a per-lead-priced setup would cost.
Layer 2 · Personalization & Sending
Reach them at volume without burning the brand
- AI-grounded openers built from real research, not template variables. The opener references something specific that was actually surfaced (a recent campaign, a post, a hire, a funding event), not a Mustache slot. Reviewable in batch before send.
- Batch review surface. You approve openers a screen at a time, not one email at a time. Tone shifts, framing nudges, the occasional rewrite, all in one pass, then the whole cohort sends.
- Multi-channel sequencing across email and LinkedIn with reply detection and automatic sequence-pause the moment someone responds. Follow-up cadence built for B2B partnership cycles, not generic SaaS sales sequences.
- Brand-domain protection. Outreach sends from isolated infrastructure: warmed-up secondary sending domains and dedicated accounts. Your primary domain stays untouchable. If a campaign ever spikes complaints, it spikes on infrastructure built to absorb that risk, not on the domain you use to talk to your clients.
Layer 3 · Reply Intelligence & Pipeline Sync
Conversations land where you can act on them
- Auto-pause on response. The moment a prospect replies, the sequence stops. No follow-up four lands the day after they said yes. No reply gets lost in a queue.
- Real conversations routed within hours. Auto-replies screened out; positive intent surfaced and pushed to wherever you actually work (inbox, pipeline, dashboard). The latency on a hot lead is the difference between booked and ghosted.
- Bidirectional sync into the rest of your stack. A reply becomes a deal in your pipeline tool. A signed deal becomes a client in delivery. The handoff between outbound, sales, and client-ops stops being three separate copy-paste jobs.
- Performance loop. The openers and angles that land get weighted higher; the ones that don't get retired. The engine sharpens the longer it runs, against your actual reply data and your actual ICPs.
The Outcome
The first SDR you'd hire becomes a system. The reply rate doesn't change — that's set by your offer and your ICP, not the tool. What changes is the volume you can sustain at that rate without burning your domain or your hours, the per-lead cost of getting there, and the speed at which a replied lead becomes a booked call and then a signed retainer. The engine is reusable for every campaign cycle after the first: new ICPs, new offers, new angles as the practice evolves.
End-to-end outbound pipeline, all configurable, all yours after handover. Four stages, each surfaces in the workspace you saw demoed.
Source
Pre-built sourcing layer · the same upstream signal the expensive platforms use
B2B contact data, executive-tier prospecting, role-based filtering, and warm-signal targeting from public activity. Configurable per ICP: the engine knows that a founder ICP gets sourced differently from an in-house marketing lead, and runs the right profile for each. New source URLs backfill the last three months automatically and refresh on a cadence you set.
Research & enrich
Configurable research profiles per ICP
For each lead, the engine runs the research profile tied to that ICP: their recent posts and signals if the angle is social, their site and funding history if the angle is operational, their last hires or campaigns if the angle is commercial. The profiles are reconfigurable per campaign; the output feeds the personalization layer directly.
Per-lead enrichment runs at a fraction of the cost of the per-lead-priced platforms. With Claude integration enabled, enrichment can route through your existing membership tokens at near-zero marginal cost at scale.
Personalize
Openers grounded in real research, reviewable in batch
Each prospect gets a personalized opener built from the enrichment output: a specific observation tied to a real signal, not a template variable swapped into a generic line. For your ICPs: the post that's already getting traction, the hire that signals the next quarter's content need, the campaign their last quarter ran that connects to the work you ghost.
Openers surface in a batch review screen before anything sends. You approve the framing once; the engine applies it across the cohort. Per-lead labor drops from manual research and writing to under a minute of review.
Send & sequence
Multi-channel, isolated infrastructure, replies caught and routed
Email and LinkedIn outbound from dedicated sending infrastructure: warmed-up secondary domains for email, dedicated accounts for LinkedIn. Multi-step sequences with reply detection, automatic sequence-pause on response, follow-up cadence built around B2B partnership-cycle norms.
Your primary domain stays clean. Outreach runs through Node-managed sending infrastructure isolated from your real mailboxes. Replies are screened, routed to you within hours, and synced into your pipeline so the conversation lives where you can act on it.
Three things change when you move from "the obvious stack plus a future SDR" to this engine:
- Per-lead enrichment platforms → integrated source layer. The expensive platforms charge per email looked up. The new setup pulls the same upstream signal without the per-lead premium. At the volume you'd actually need to fill the calendar, the savings are measured in months of subscription cost, not pennies.
- Manual personalization → AI research-grounded openers. You stop writing each opener by hand or, worse, sending a templated one that lands like every other agency. The engine does the research pass, drafts the opener, you approve the cohort in batch. Per-lead labor drops from ten-plus minutes to under a minute of review.
- Employee mailboxes → isolated sending infrastructure. Outreach stops running from your primary inbox. It moves to warmed-up secondary domains and dedicated accounts. Reply rate stays the same; deliverability stays clean across volume; your real domain stays untouchable.
What doesn't change: your taste in ICPs, your judgment on which conversations are worth taking, your voice when the conversation gets interesting. The engine runs the boring 95% so that the 5% where it matters, the actual conversations, gets your attention.
The Claude integration advantage
You already pay for Claude. The engine plugs in natively — enrichment runs on your existing tokens.
The integration layer lets enrichment route through Claude membership tokens you already pay for, rather than a per-call platform fee. The practical effect at scale: instead of paying per-lead enrichment costs that compound with volume, marginal enrichment cost approaches zero. For an engine that's meant to run continuously across multiple ICPs and campaign cycles, that math reshapes what's affordable. We're running this on our own outbound; happy to demo on the kickoff call.
4-6 weeks from kickoff to live outreach. Each phase ends with something concrete: the engine in your hands at the end of phase 2, doing real work by phase 3.
Engine calibrated to your ICPs
Week 1 · all tiers
What you have at the end of this week: the engine deployed under your accounts, research profiles configured per ICP, opener framework tuned to your voice, and a starter list of named contacts ready to enrich across your priority segments.
Sending infrastructure warmed
Weeks 1-2 · all tiers
What you have at the end of this phase: warmup complete on dedicated sending infrastructure, your primary domain protected, sending capacity ready for real volume without deliverability risk. The Claude integration is live in your workspace.
First campaign live
Weeks 3-4 · all tiers
What you have at the end of this phase: outreach in market, replies routed within hours, the first conversations on the calendar. Pipeline sync is bidirectional: a reply becomes a deal, a deal becomes a client downstream.
Tuned to what's replying
Weeks 5-6+ · all tiers
What you have at the end of this phase: openers refreshed based on what's actually replying, target list expanded into adjacent ICPs, the engine running on its own cadence, ready for the next campaign cycle without rebuilding.
One engine, three operating models. The choice is how much of the campaign work you own versus hand to us. Pricing in EUR.
The plug-and-play option. We deploy the engine under your accounts, calibrate it for your ICPs, warm the sending infrastructure, and hand you the keys. Right if you want to drive the engine yourself, learn it from the inside, and decide later whether to extend.
- Engine deployed under your accounts. You own the deployment forever
- Calibrated to your priority ICPs (research profiles, opener framework, source mix)
- Sending infrastructure provisioned and warmed
- Starter list of named contacts across your priority ICPs
- Pipeline sync configured into the rest of the stack
- Claude integration deployed in your workspace
- Live training call + recorded walkthrough of every screen
- 30 days of post-launch async support
Recommended
Same build, plus a light monthly retainer for ongoing campaign support. We handle the campaign brief, the opener refresh, and the deliverability monitoring. You handle execution: reviewing the cohorts, taking the conversations, closing the deals. Right if you'd rather have us tuning the engine alongside you than scope each campaign cycle as a separate project.
- Everything in Tier 1 setup, plus ongoing campaign support
- Monthly campaign brief: segments to push, fresh angles, refreshed target lists
- Opener framework refresh based on what's actually replying
- Deliverability monitoring across the month, with warnings flagged before they hit volume
- Additional ICPs and research profiles configured as your practice evolves
- Bi-weekly strategic call: what's working, what's not, what to adjust next
- Async support, prioritized response
An embedded outbound team. Node runs the engine end-to-end: sourcing, research, personalization, sending, follow-up, reply triage. You receive weekly written summaries of conversations to handle and meetings to take. The engine runs in the background while you focus on the writing, the existing clients, and the conversations we surface.
- Campaign strategy and ICP prioritization: what to push, when, in what sequence
- Target list curation and refresh, per cycle
- Personalization across the full target list, reviewed and tuned by us
- Multi-channel sequencing with reply detection and auto-pause
- Reply triage, auto-replies screened, real responses routed to you within hours
- Weekly written summary: meetings booked, hot leads, what shifted in the campaign
- Monthly strategic working session: reviewing the funnel, planning next month's push
Operating cost (pass-through, paid by you)
The engine runs on infrastructure billed directly to your accounts, no markup. Everything under your ownership.
Cold-email platform — the sending and inbox-rotation layer
€47–97/mo
Sending infrastructure — secondary domains and dedicated accounts that keep your real domain clean
€10–30/mo
Per-prospect enrichment — research per lead (or near-zero with Claude integration enabled)
~€0.01–0.05/lead
AI generation — usage-based, runs on your existing provider tokens
variable
We build it right, or we fix it.
30 days of post-launch support at no cost. If anything we built breaks, we fix it. No exceptions.
You approve every milestone.
Nothing moves forward without your written sign-off. If a deliverable doesn't match what we promised, we revise it until it does.
No surprises.
2 revision rounds per deliverable included. Timeline and scope locked once we start.
What we guarantee — and what we don't.
We guarantee the work: deliverability hygiene, personalization quality, and the engine running cleanly under your accounts with pipeline sync live. We don't guarantee signed retainers. That depends on the offer, the ICPs, and the conversation work that happens in the meeting itself. The engine books the conversations; closing them stays with you.
Each quarter without the engine is a quarter of paying per-lead premiums on the obvious platforms, of considering a hire whose loaded cost dwarfs the build, and of running cold outreach (if you run it at all) from the same domain you use to talk to existing clients. The first SDR hire only gets more expensive. The engine is the version of the next move where the cost stays flat as the practice scales.
Ready to move forward? Here's how we get going.
01
Review & reply
Read through the proposal. Reply with your tier preference. If anything in scope, timeline, or pricing feels off, push back. We'd rather adjust now than ship the wrong shape of engagement.
02
Deposit invoice
50% deposit on Tier 1. First month + setup on Tiers 2 and 3. Payment confirms the start date and locks in the timeline.
03
Account provisioning
We send a checklist for the accounts the engine runs against: sending domains, enrichment, AI tokens, pipeline sync targets. All under your ownership, billed direct, you own everything.
04
Kickoff call
60 minutes within 48 hours of deposit. We walk through your priority ICPs, the offer you want the engine to pitch, the existing pipeline you want it to feed, and the angles you want pulled into the opener framework. We come with a pre-built starter; you sharpen it.
05
Build & handover
Setup runs week 1; sending infrastructure warms weeks 1-2; first campaign goes live weeks 3-4; tuning runs weeks 5-6+. Weekly written updates Monday mornings. Recorded walkthrough plus live training before handover. From handover, the engine is yours to run.