I built a cold email AI agent for freelance devs in 8 hours — here's what I learned

I spent the last decade watching cold email tools get worse. Apollo. Lemlist. Instantly. Smartlead. Every one of them now ships "AI personalization" that pastes a first name into a template and calls it intelligence. Reply rates have collapsed to 0.7-1.5% on most B2B campaigns (Saleshandy 2025 benchmark).This week I sat down and built what I actually wanted: an n8n workflow targeting one narrow ICP (freelance devs), referencing one verifiable fact per email (their GitHub bio), and shipping in 8 hours. Here's the build log + what surprised me.## The hypothesisEvery "AI cold email" tool I've used has the same structural flaw: the AI doesn't know anything specific about the recipient. It sees a name, a title, maybe a company. So it writes a generic email. The recipient pattern-matches it as AI in 200ms and deletes it.The fix is structural, not prompt-engineering: give the AI a real, verifiable fact before it starts writing. For freelance devs, that fact is sitting in plain sight on every prospect's GitHub profile.## The buildThe workflow has 21 nodes, but the actual logic is six steps:1. Webhook or scheduled trigger — runs Tue/Thu 9am or fires on demand.2. Apollo lead scrape via Apify Actor — pulls 20 freelance dev profiles per run, filtered by title + location.3. Dedup against Google Sheets — never email the same person twice.4. Validate email with mails.so — drop bounce risks before they hurt domain reputation.5. Enrich with GitHub bio — best-effort GitHub API call using the prospect's LinkedIn slug as a username guess.6. GPT-4o-mini personalization — strict-JSON output, system prompt forbids three specific clichés.7. Gmail send + Sheet log + 45-second rate limit.The whole flow runs in ~30 minutes for 20 emails, costs about $0.04 in API fees, and stays well under Gmail's send-rate thresholds.## What surprised me #1: the prompt does 80% of the workI started with a "write a friendly cold email" system prompt. The output was unreadable AI slop. Then I added one line: "NEVER use the phrases 'I hope this finds you well', 'I came across your profile', or 'I'd love to connect'." The output quality jumped immediately.Then I added: "ALWAYS reference one specific, verifiable fact about the recipient — their GitHub bio, a repo they maintain, or a blog post they wrote." Quality jumped again.Then I added: "Subject ≤ 50 chars. Body ≤ 90 words. No signature." Quality jumped a third time, because the model couldn't pad with fluff.Most cold-email AI tools are running 5-line system prompts. This one runs 12 lines. The difference is night and day.## What surprised me #2: GitHub enrichment is best-effort, and that's fineI assumed I'd need to perfectly map every LinkedIn URL to a GitHub username. Turned out, ~40% of freelance devs have the same handle on both platforms. For the remaining 60%, the GPT prompt falls back gracefully to "reference their stated location or services" — and the email still feels personalized because the system prompt is doing the heavy lifting, not the data.Lesson: don't over-engineer enrichment. Get one decent fact, and let a good prompt make it sing.## What surprised me #3: the rate limit IS the productI almost didn't add the 45-second wait between sends. It feels redundant — Gmail handles rate limiting itself. But after talking to two friends who do agency cold email, I added it. Reason: a fresh mailbox sending 100 emails in 5 minutes triggers Gmail's spam filter. A mailbox sending 100 emails over 75 minutes does not. (Indie Hackers thread on warmup pacing confirms similar pacing math.)The wait node isn't friction. It's protection. The product is "you won't get banned" as much as it is "you'll get replies."## What I'd do differently1. Add reply detection from day 1. Right now if a prospect replies "STOP," the next batch still sends. I'll add an IMAP poll to flag opt-outs in v1.1.2. Build the Looker Studio dashboard upfront. Buyers want to see their reply rate trend without manually computing it from the Sheet. v1.1 ships a one-click template.3. Stop building "general purpose" tools. Picking ONE ICP (freelance devs) made every decision easier — the prompt, the personalization, the search URL, the pricing. Generic = unsold.## Why this isn't a SaaSI keep getting asked: "Why isn't this a $29/month SaaS?"Two reasons:1. Cold email tools have terrible margins. You pay sender infra, validation API, lead scraping, AI tokens, support. After that, $29/month per user is barely breakeven.2. Every dev I talked to wants to OWN their workflow, not rent it. They want to fork it, swap GPT for Claude, change the rate limit, run it on their own n8n. A $39 one-time template gives them that. A SaaS doesn't.The repeat-purchase upsell isn't a subscription — it's the next ICP pack. Same buyer, new audience.## The full workflow + 50 LinkedIn ICP queriesI packaged the whole thing — workflow JSON, README with SPF/DKIM/warmup guide, 6-min video walkthrough, and 50 proven LinkedIn search queries for finding freelance devs — for $39 one-time on Gumroad. 30 days of Discord support included. 7-day refund if it doesn't run on your n8n.Get it here →If you'd rather build your own, the n8n.io community templates are open-source and a great starting point — workflow #6098 and #11037 have the bones — but you'll be writing your own personalization prompt and ICP discovery from scratch. That's the 8 hours.Either way: stop sending generic AI cold email. Pick one ICP. Reference one fact. Send fewer, send better.## Appendix: The exact GPT-4o-mini system prompt I'm using

You are a senior cold-email copywriter who writes for indie devs selling tools to other freelance devs.You ALWAYS reference one specific, verifiable fact about the recipient (their GitHub repo, blog post, or portfolio project).You NEVER use AI clichés like "I hope this finds you well" or "I came across your profile" or "I'd love to connect".You write friend-to-friend, never salesy. You assume the recipient is busy and skeptical.Output strict JSON: { "subject": "...", "body": "..." }- Subject ≤ 50 chars- Body ≤ 90 words- No signature (n8n adds it later)- No emoji- No bold or markdown- Plain text only

Appendix: Why I picked freelance devs as ICP #1Three reasons:1. Verifiable presence. Every freelance dev has a GitHub. Most have a personal site. ~70% have a Twitter. The data exists publicly and is high-signal.2. Predictable buying budget. A freelance dev billing $80/hr makes $13K/month. They'll spend $39 on a tool that saves them 1 hour. The math is obvious.3. Self-serve adoption. Devs hate sales calls. They want to read the README, run the demo, decide. This product format matches the buying behavior — no demo required.For comparison: SaaS founders also have predictable budgets, but they're harder to reach (most are solo + email-overwhelmed). SEO agencies have predictable budgets but they buy services, not tools. Freelance devs are the only ICP I tested where ICP economics + buyer behavior + data-availability all aligned.If you're picking an ICP for your own cold-email tool: optimize for public-data availability first. Without verifiable facts, every email turns into AI slop, and reply rates collapse no matter how good the rest of your pipeline is.> Built this in a week. Selling it for $39 to make back the build time. If it helps you — Gumroad link. If it doesn't — at least the system prompt above is yours to copy.