How to Run a Cold Email Campaign for ESP-IDF Student Founders (2026)

Quick Answer: You already used Origami to find a list of ESP‑IDF student founders building IoT products. Now you run the entire outreach on the same platform—because Origami has a built‑in email sequencer that lets you refine the list, write hyper‑personalised messages, and send multi‑touch campaigns without ever exporting a CSV.

---

You’ve built your list of ESP‑IDF student founders using Origami (if you haven’t yet, jump back to the guide on how to find them). Now comes the part most people get wrong: turning that list into conversations. Student founders who are deep in firmware, wireless stacks, and hardware prototypes aren’t going to reply to generic “growth hacking” emails. They need something that shows you understand their world.

This post walks through exactly how to run that campaign—from refining your Origami list to writing and sending a 3‑touch sequence that gets replies. You’ll find real message copy you can steal, subject lines that work, and the mechanics of sending everything from inside Origami. No separate sequencer, no syncing tools.

---

Step 1: Recap—Your list lives in Origami

Before you email anyone, you need the list. If you followed the parent guide, you already typed a prompt like this into Origami:

“Student founders actively building IoT products with ESP‑IDF. Include email, LinkedIn, company name, and GitHub profile. Exclude pure hobbyists—focus on those with commercial intent.”

Origami then scours the live web, chains data sources, enriches contacts, and qualifies leads—all from that single prompt. What you get back is a clean table with verified names, email addresses, job titles, company details, GitHub handles, and sometimes even links to Hackaday or Hackster projects. You don’t need to go hunting for contact info elsewhere.

If you’re just starting out, the free plan gives you 1,000 credits (no credit card required), which is enough to build a decent starter list and send your first sequence.

Now, from inside Origami, you can start segmenting that list for email.

---

Step 2: Refine and qualify the list for email

A raw list of ESP‑IDF student founders is noisy. Some are taking a university elective; others are shipping beta units to customers. Quality email outreach only works when you’re writing to the right people. In Origami’s lead view, you can filter, sort, and remove contacts. Do this now.

What to look for

• Project stage: Filter by signals of commercial intent—links to product pages, Kickstarter mentions, App Store or Google Play companion apps, or a “buy now” page on a simple website. If the GitHub profile only has a course assignment repo and no public device firmware, skip it.
• Team size: Solo founders or very small teams (2‑5 people) are the sweet spot. Larger student clubs often don’t have the urgency to change tools or adopt new hardware.
• Activity freshness: Prioritise founders who have committed to an ESP‑IDF repo or posted about their device in the last 3 months. Origami’s enrichment pulls the last‑active timestamp from GitHub, so you can filter by recency.
• Location & language: If you’re selling tools or components that only make sense in certain regions, add a location filter. For English‑language outreach, ensure the founder’s LinkedIn or GitHub bio is in English.

What “qualified” looks like for this audience

A qualified lead is a person who:

• Has a public ESP‑IDF repository that is clearly beyond a tutorial—custom board support, OTA updates, or BLE Mesh, for instance.
• Has a product page or a “coming soon” landing page, even if it’s just a Notion doc.
• Is a founder, CTO, or “electronics lead” (not just a team member).
• Optionally, has posted on Hackaday, Hackster, Reddit’s r/esp32, or Twitter about their build.

Once you’ve cut your list to a few dozen highly‑relevant founders, you’re ready to write the sequence. Keep the rest of the list for later campaigns once you’ve proved the messaging.

---

Step 3: Create the email sequence

In Origami, the sequence builder lives right next to your lead list. No uploads, no exports. You build the flow of touches directly on the same screen. You have two options:

1. Paste your own templates – Write your own 3‑touch copy (subject lines, body, preview text) and paste them into Origami’s sequence editor. Set the delays between touches—Day 1, Day 3, Day 7, or whatever cadence you like—and hit “Launch.”
2. Let the AI agent write it – Alternatively, ask Origami’s AI to generate a personalised 3‑day email sequence for all your leads automatically. The agent crafts messages based on each lead’s profile data—title, company, industry, GitHub project—so every message feels custom. It’s a fast way to get a first draft that you can then tweak.

Below is a ready‑to‑steal 3‑touch sequence written specifically for ESP‑IDF student founders. It’s direct, never over 100 words, and references real pain points like hard faults, memory optimisation, and BLE power consumption. Use it as your starting point.

Example 3‑Touch Sequence for ESP‑IDF Student Founders

Touch 1 – Day 1: The reference hook

Subject: Quick fix for your [project_name] firmware?
Preview text: (One config change that might save you a week of debugging)

Hi [First Name],

I noticed your work on [project_name] in ESP‑IDF. Most student founders I talk to hit a wall with memory management and BLE power when they move from breadboard to a real case. I’ve got a short guide that shows how to cut BLE current consumption by ~40% with two config tweaks—no heavy refactoring.

Want me to send it over?

– [Your Name]

Why it works: It proves you’ve looked at their actual project, names a concrete technical problem, and offers something immediately useful without asking for anything in return.

Touch 2 – Day 3: The overlooked pitfall

Subject: The 3 ESP‑IDF settings most student teams overlook
Preview text: (And why they cause random resets)

Hey [First Name],

Last time I mentioned the power optimisation trick. Another common trap I see in student‑built IoT devices is poorly configured task stack sizes and FreeRTOS priorities—leads to random crashes right when you’re demoing.

I’ve put together a checklist of 5 ESP‑IDF configs that prevent those issues. Happy to share if you’re still fine‑tuning [project_name].

– [Your Name]

Why it works: The second touch opens a different angle (stability vs. power) and reminds them of their own project’s name. It also implies you have deep knowledge of the ESP‑IDF ecosystem.

Touch 3 – Day 7: The respectful break‑up

Subject: Closing the loop on [project_name]
Preview text: (No worries if you’re heads‑down, just wanted to say good luck)

Hi [First Name],

I know you’re likely deep in bring‑up. If my earlier notes didn’t resonate, that’s totally fine. But if you’re still wrestling with ESP‑IDF stability or connectivity, I’m just one reply away. Otherwise, I’ll quit bothering you. Good luck with [project_name]—the device you’re building looks really cool.

– [Your Name]

Why it works: The break‑up email acknowledges their reality, removes pressure, and leaves a positive final impression. Many founders respond at this stage because they realise you’re not another blast tool.

---

Step 4: Send the sequence directly from Origami

This is where Origami differs from old‑school workflows. You don’t export your curated list, upload it to a separate sequencer, and pray the sync works. You launch the entire campaign from the same dashboard where you built and refined the list.

1. With your sequence ready, you set the delays between touches (defaults to Day 1, Day 3, Day 7, but you can adjust to 1‑3‑5 or 1‑2‑4—whatever fits your audience’s rhythm).
2. You review that the automatic personalisation tokens ([First Name], [project_name]) draw from the enriched fields Origami already has.
3. Hit Launch Sequence. Origami starts sending according to that schedule—no manual follow‑ups, no forgetting to send the third email.

Tracking and reply management

While the campaign is running, all tracking data flows back into the same lead view:

• Opens and clicks – See who engaged with your emails, including device and location.
• Replies – Incoming replies appear alongside the contact’s enriched profile (title, company, GitHub, tools used), so you instantly recall why you reached out and what angle you took.
• Prospect context – While you’re reading a reply, you still see all the enrichment data that prompted the outreach. No switching tabs.

Crucially, Origami’s sequencer includes automatic un‑enrollment: if someone replies, they’re taken out of the sequence immediately. No risk of sending the breakup email after they’ve already booked a meeting.

The cost

The built‑in email sequencer is included on all paid plans. You only pay for credits to enrich your leads. The actual sending is free. The free plan (1,000 credits, no credit card) lets you test the entire workflow—find a few contacts, write a small sequence, and send it—without spending anything.

What response rates to expect

When you email ESP‑IDF student founders with a list that’s been qualified as described, and you use a sequence that references their actual project, a reply rate of 8–15% is realistic. I’ve seen campaigns hit 18% when the message mentions a specific commit or a hardware BOM from the founder’s own repository. Open rates are less meaningful because Apple Mail Privacy hides many opens, but tracked opens in this audience often run 40–60%.

These numbers aren’t magic; they’re a function of highly relevant targeting and messaging that sounds like it came from a peer, not a marketer.

When to iterate on messaging vs. iterate on the list

If you’re not getting the replies you want after two cycles, here’s how to diagnose:

• Low opens across the board? Check your subject lines, sender name, and deliverability (SPF, DKIM, DMARC). Origami supports custom SMTP so you maintain your own sending reputation.
• Opens but few replies? The body copy or CTA isn’t landing. Try a shorter, more direct ask—offer a resource rather than a call. Test one small variable at a time, like replacing “guide” with “checklist.”
• Near‑zero engagement after two campaigns? The list may be too broad. Go back to Origami’s search and add tighter filters—for example, founders with a commit in the last 30 days to a specific ESP‑IDF component. Then re‑run the enricher to refresh data.

---

Next steps

You now have a repeatable, closed‑loop workflow that lives entirely in Origami:

1. Find your audience using plain‑English prompts.
2. Qualify and segment right inside the leads table.
3. Write (or let the AI write) sequences that speak the language of ESP‑IDF founders.
4. Send, track, and manage replies—all from one screen.

No other platform lets you go from “describe my ideal customer” to “send email number three” without touching a CSV or syncing a CRM. That matters when you’re targeting an audience as technical and niche as student founders building with ESP‑IDF—every minute you save on tool‑hopping is a minute you can spend understanding their projects better.

If you haven’t built your list yet, head over to the full guide on how to find and prospect ESP‑IDF student founders. Then come back here and launch your first campaign.