How to set up an outbound motion for under €300 a month
A solo founder's automated outreach blueprint, end to end.
The headcount math for outbound used to look something like this. Three SDRs writing sequences, two EAs cleaning lists and routing replies. Five people, fifty thousand a month all-in once you add tools. A real team for a real budget.
I run the same motion as one person for €300 a month.
This isn’t a productivity hack. It’s a stack. Six tools, one operator, and a clear separation of what humans do versus what software does. Below is the full blueprint. The process, the systems, the costs, where it breaks.
If you’re a founder who needs to do outbound but can’t justify a team yet, this is the playbook I use.
The stack
The full stack costs around €60 a month for the bare minimum and €300 if you add enrichment.
Instantly.ai for sequencing, sending, and reply routing. €37/month.
A cold-sending domain separate from your main domain, so deliverability stays clean. €15/year, call it €1.25/month.
Three Google Workspace mailboxes on the cold domain to spread sending volume. €18/month total.
Claude (Pro or API) for drafting variants, scoring segments, and configuring campaigns. €20-200/month depending on usage.
Cal.com or similar for the meeting link. Free tier works.
Clay (optional) for enrichment if you want fancier targeting. €149/month.
The core minimum without Clay lands around €60-100 a month for technology. The rest is your time.
The blueishprint
This is a seven-step B2B outbound email campaign motion:
ICP definition — who exactly you’re targeting.
General pain mapping — what hurts enough to make them open a cold email.
Segment scoring — which slices of the ICP are worth a lane.
Lane and lead selection — the two or three segments you’ll actually run, and the leads in each.
Message variants — the angles you’ll test per lane.
Segment-specific personalization — how each variant lands for its specific audience.
Set up and run the campaign — the operational engine that turns all of the above into sent email and booked meetings.
Steps 1 through 6 are strategy and content design. The output is a plan: a scored segment list, two chosen lanes, message variants ready to ship.
Step 7 is execution, and it’s where this post lives. The next section provides the detailed walkthrough, from locking in your lanes (which is where the strategic prep crystallizes into an actual campaign), through setting up sending infrastructure, configuring cadences, building lists, sending, and routing replies. After the campaign starts, every reply routes into one of six buckets that determine the follow-up path.
Three recommendations to make this work as a single-operator motion.
Commit to lanes. Two or three segments at a time, never more. Each lane gets its own campaign, leadlist, and message variants.
Run experiments inside experiments. The lane tests whether the segment is right. The variants inside the lane test which message resonates. One variant tells you whether the lane works. Three variants tell you why.
Let Claude do the assembly work. Drafting, scoring, formatting, configuring. You stay in the loop on judgment calls — does this segment have the pain we think it has, does this list look real, is this subject line saying anything new. The typing is automated.
Sub-steps 2 through 4 of the walkthrough run in parallel during the two-week domain warmup, so calendar time is about three weeks before your first real email goes out.
The campaign setup
Step 1: Score segments and pick two lanes
This is the only purely strategic step. Skip it and you’ll burn the rest of the stack on the wrong audience.
I keep a scoring sheet with around 45 segments scored across ten weighted dimensions: pain, PII handling, volume, reachability, ability to pay, ACV potential, K-factor, regulatory pressure, segment homogeneity, and competitive density. Weights are tuneable, formulas update live. The output is a top-10 with a tie-breaker.
Pick two or three lanes from the top, never more. Three is the upper bound for a solo operator. Above three, you lose the thread on what’s working.
For each lane, write the ICP in one sentence. Something like “independent professional services firm, one to five operators, regulated by the relevant authority, member of the trade body.” That sentence becomes your filter for everything downstream.
Step 2: Set up the cold domain (start warming immediately)
This is the part most people get wrong, and it’s the slowest piece, so start it on day one.
Sending cold email from your main domain risks torching its reputation. Bounces, spam complaints, and unusual sending patterns will tank deliverability across all your real correspondence too. Your investor updates start landing in spam folders.
The fix is a separate cold-sending domain. Volume only ever leaves the secondary, the main domain stays reserved for real correspondence.
On the cold domain you set up:
DKIM, SPF, DMARC authentication. Without these your mail goes straight to spam. Instantly walks you through this in setup.
Three mailboxes minimum on Google Workspace. Sending volume should never exceed about 30 emails per mailbox per day in warmup, scaling to 50 once warm. Three mailboxes give you 90-150/day capacity.
Two weeks of warmup before any real sending. Instantly has a built-in warmup tool that simulates real conversation across a network of mailboxes. Skip this and your first real campaign will land in spam universally.
While the warmup runs in the background, do Steps 3 and 4 in parallel.
Step 3: Configure cadences (let Claude drive)
This is the step where the time math actually changes.
Setting up an Instantly campaign by hand takes about two hours of clicks. Four sequences, four steps each, sixteen email bodies, sixteen subject lines, plus delays and sender mailboxes. For a real campaign with proper variants, multiply that by three: six hours of clicking, copying, pasting, double-checking.
I let Claude drive the browser. End to end the same campaign takes about an hour, most of which is me writing the cadence in a spreadsheet and watching Claude work.
The workflow
I write the cadence in a single sheet, one row per email step. Columns:
sequence_name — e.g. “Lane A — Problem-first”
step — 1 through 4
subject — the subject line
body — the email body, with {{first_name}} and other variables inline
wait_days — days to wait before this step fires (0 for the first email)
For a three-variant lane that’s 12 rows. For two lanes running three variants each, 24 rows. The sheet is the source of truth. If you want to change a subject, you change the cell, not the campaign.
Then I open Instantly in Chrome, share the sheet with Claude, and give it a one-paragraph prompt: “Create a new campaign called X, add three sequences named per the sequence_name column, and for each sequence add the four steps from the sheet with their subjects, bodies, and wait days.” Claude navigates Instantly’s UI, creates the campaign, and configures every step from the sheet.
The {{ trick
The non-obvious part is how Claude actually gets the email body into the editor.
Instantly’s body editor — like most rich-text editors built for outreach tools — intercepts {{ as a variable trigger and pops a dropdown. If Claude tries to type the body in naturally, every variable opens the picker and the text gets mangled. Paste doesn’t work either; the editor reformats on paste.
The workaround: switch the editor to HTML / code view. That view is a plain textarea, no interception. Claude uses its JavaScript tool to set the textarea’s value directly, then flips back to rich-text view. Instantly re-parses the body, variables render as proper merge fields, and the test send works exactly as expected.
This pattern works in most of the outbound and CRM tools I’ve tried. Wherever the rich editor blocks you, the code view is the escape hatch.
Where the human stays
I watch Claude work, not the whole hour, but enough to catch the failure modes. Sometimes Claude clicks the wrong “create” button if there are two on the page. If a sequence_name in the sheet has a typo, Claude creates a typo’d sequence. And test sends are mandatory before you go live: five minutes per sequence catches variable mismatches, escaped HTML, and the occasional case where Claude pasted the wrong cell.
Per lane I run three message types in parallel: a problem-first variant, a founder-voice variant, and a price-or-time variant. Each runs as its own four-step sequence with the same day cadence, day 0, day 3, day 7, day 12. The variants compete head-to-head inside the lane. By the end of week two you know which voice is landing.
Step 4: Build the lead list
Lead sourcing can go fully automated (Clay, Apollo, Lusha, and similar) or fully manual. I recommend starting manual. You’ll learn what a good lead actually looks like in your segment, and that knowledge is what makes the automation work later. A follow-up post will cover the manual sourcing playbook in detail.
Either way, this is the step where you have to think.
Tools won’t do this for you, and shouldn’t. The lead list is your judgment about who you actually want to reach. If you outsource it to a generic enrichment platform or a cold AI agent, you’ll get a list that looks plausible and contains nobody who matters.
The pattern I use:
Find a primary list from public registers and trade association directories. LinkedIn Sales Navigator works if you have it. The cheapest leads are usually the cleanest.
Manually scrub. Open the list, read the names, drop anyone obviously wrong. This takes an hour for 100 leads. It’s the most valuable hour in the whole process.
Enrich what’s missing. First name, company name, role title, email. If your source already has it all, skip enrichment.
Upload as CSV to Instantly. Map columns to email, first_name, company_name. Set custom fields if you want segment-specific personalization later.
Don’t skip the manual scrub. Any list of more than 200 leads gets sampled before it ships. If 5% of the sample looks wrong, the list goes back for review.
Step 5: Send slow, measure, iterate
When you launch, send slowly. Twenty leads a day, not two hundred. You’re not optimizing for volume yet. You’re optimizing for whether the message lands at all.
Two lanes I ran recently make the case. The first lane: around 60 sends, roughly 7% reply rate. A clean signal that the lane works. The second lane: around 80 sends, just over 1%. Same stack, same operator, same week. The lane just didn’t connect.
That gap is exactly why you run two or three lanes in parallel. Until you have real reply data, you don’t know which segment your message will land in. If you’d bet everything on the second lane, you’d have spent weeks chasing a signal that wasn’t there.
Within each lane I A/B test subject lines and bodies. The winners are rarely the ones I expected. In one sequence, the breakup email — subject “Are you OK?” — pulled more replies than two carefully polished subjects earlier in the sequence combined. Some subject lines just punch above their weight. Body copy is the same story: the price-first variant beat the founder-voice variant in one lane, then lost in another. The only way to find the winner is to ship three variants and let the data choose.
Three numbers matter:
Reply rate. Below 1%, something is wrong with the list, the message, or deliverability. 5 to 15% is good for a tight lane.
Meeting rate. Of replies, how many turn into a 20-30 minute call. 30 to 40% is normal.
Bounce rate. Below 2% is healthy. Above 5% means your list is dirty.
Don’t track open rate as a primary metric. Apple Mail and Gmail iOS preload images, marking emails as opened whether the recipient actually looked or not. It’s noise.
After a week of data, kill the worst variant. Double the volume on the winner. After two weeks, if the numbers hold, expand the leadlist. After a month, you have enough signal to either scale or pivot the lane.
Most people skip the patience and dump 500 leads on day one. They get bad data, can’t tell which variant won, and conclude the channel doesn’t work. The channel works. Patience is the part most people miss.
Step 6: Route the replies
This is what separates outbound that scales from outbound that vacuums up your time. Every reply lands in one of six buckets, each with its own follow-up path.
Interested — connect on LinkedIn, ask for the call directly, follow up after 1, 3, and 7 days if no scheduling response. After three follow-ups without a calendar invite, mark as dead.
More info — connect on LinkedIn, send content (case study, one-pager) on the same 1/3/7-day cadence.
Wrong person — custom response asking for the right contact. Same 1/3/7-day follow-up if no name comes back.
Contact later — custom response acknowledging the timing, then drop the lead back into the sequence after a 3-6 month cooldown.
Not interested / auto-reply / do-not-contact — dead immediately. Don’t argue.
No response after the full 4-email sequence — one final 1-week follow-up, then a 2-week follow-up, then dead.
Tag every incoming email with the right inbox label as you read it. Instantly automates the rest from there: the follow-up sequences, the LinkedIn handoff, the cooldown timer for “contact later” leads. Without routing, every reply becomes a 5-minute decision. With routing, it’s 30 seconds. At scale that’s the difference between half an hour a day on outbound and three hours.
Where this breaks
Three honest limits.
It doesn’t work if your ICP is too narrow. If you’re targeting fifty companies in the world, automated outreach is the wrong tool. Hand-write those fifty.
It doesn’t work without a clear hook per segment. Generic value props get generic responses, which is to say, none. The lane-and-variant structure exists because each segment needs its own pain and language.
It doesn’t replace a real SDR for complex multi-stakeholder enterprise sales. For a six-figure ACV deal with five stakeholders across procurement, security, and the buying team, you still want a human running the play. This stack is for the segment of business where one cold email leads to one demo and one deal in three weeks.
What it costs in time
Around 2 days of active work the first time you set this up end to end. Domain config, lead sourcing, cadence build, mailbox warmup setup, the manual scrub on your first lead list. The 2-week domain warmup runs in the background, so calendar-time it’s about three weeks before you send your first email. After your first campaign is live, count on 6-8 hours per new campaign. The heavy first-time setup amortizes across every lane after.
Once it’s running, ongoing time is maybe 30 minutes a day. Read the replies, route them with inbox labels, drop the polite-nos, mark wrong-people for cleanup. The whole motion fits between morning coffee and the first standup.
For €60 to €300 a month plus a part-time hour a day, you’re running an outbound function that produces real meetings. That’s what makes it work as a solo founder motion.
If your business has a repeatable wedge that works for a defined segment, this stack will produce results that justify the cost within sixty days. If your wedge isn’t clear yet, this stack will surface that for you fast, and that’s worth the cost too.
References
Outbound Engine board on Figma — full process map including reply-routing
Originally posted to Third Vector’s The Blueishprint. If you build outbound and want to compare notes, hit reply.
Image credits: Kindel Media via Pexels