How to Run an Email Campaign Targeting Companies Searching for Fivetran and dbt Alternatives in 2026
Step-by-step guide to cold emailing data teams hunting for Fivetran and dbt replacements. Includes copy-paste 3-touch sequence and Origami's built-in sequencer tips.
Founder @ Origami
Quick Answer: Origami has a built-in email sequencer that lets you send multi-step outreach directly from the same platform where you built your prospect list. After you’ve identified companies searching for Fivetran and dbt alternatives using Origami’s AI agent, you can refine, sequence, and email them without ever exporting a CSV or juggling tools. This guide walks you through refining the list, crafting a 3‑touch email sequence you can steal, and sending it all from Origami — with real numbers on what to expect.
If you haven’t built the list yet, read how to build a list of Companies Searching for Fivetran and dbt Alternatives first. That post covers using plain‑English prompts inside Origami to find people who are actively researching replacement tools. Once you have those contacts, come back here.
Let’s get into the actual campaign.
Step 1: Refine and Qualify the List (You Already Built)
Origami returns a table of contacts that match your prompt: names, verified emails, job titles, company size, tech stack signals, and sometimes notes like “recently viewed Airbyte pricing.” Before you hit send, spend 20 minutes making sure the list isn’t polluted with bad fits. You’ll raise reply rates and protect your domain reputation.
Review and Remove
Scan the list for:
- Wrong titles – A “VP of People” is not evaluating ETL tools. Look for roles like Data Engineer, Analytics Manager, CTO, VP of Data, or Head of Data Platform.
- Competitor domains – If someone works at Fivetran, dbt Labs, or a major SI partner, remove them immediately. No upside in emailing them.
- Non‑US/NA focus (if that matters) – The language of buyer intent signals can suck in global contacts. Keep only the geographies your sales team can serve.
Segment for Personalization
Within Origami you can filter by columns like employee count, industry, or tech stack. For this audience, I recommend two segments:
- Mid‑market (50–500 employees) – Typically using Fivetran + dbt Cloud on a growing budget. Pain: per-row costs spiking, dbt run times creeping up. They’re often exploring Airbyte, Meltano, or open‑source plumbing.
- Enterprise (500+) – Have invested in custom pipelines; may be evaluating a composable CDP or looking to cut transformation complexity. Pain: vendor lock‑in, need for real‑time transformation, compliance overhead.
A qualified lead here is someone who has shown intent: viewed alternative product pages, opened a comparison blog, attended a webinar about modern data stacks, or changed jobs recently while adding “Looker” or “Snowflake” to their stack. Origami often captures that signal automatically when you use a prompt like “companies searching for Fivetran and dbt alternatives.” If you see that signal, they’re gold.
Once you’ve cleaned the list, export nothing. Stay inside Origami. You’ll launch the sequence right there.
Step 2: Build the 3‑Touch Email Sequence
Origami gives you two ways to create the sequence:
- Paste your own templates — Write your own 3‑touch sequence, set the delays (e.g., Day 1, Day 3, Day 7), and hit “Launch.” This is what we’ll cover in detail below, with full copy you can steal and customize.
- Let the AI agent write it — You can also ask Origami’s AI to generate a personalized 3‑day email sequence for all your leads automatically. The agent writes each message based on the lead’s profile data — title, company, industry — so every message feels custom. It’s a great way to test a baseline before you invest time in manual copy.
Below is a complete 3‑touch sequence I’ve run for this exact audience. Messages are 50–100 words, direct, and reference the real pain points teams feel when they outgrow Fivetran and dbt. Steal it, tweak the [Company] and [Tool] placeholders, and paste it into Origami’s sequencer.
Day 1: The Permission‑Based Opener
Subject: [First Name], moving on from Fivetran? Preview: Quick question about your ELT stack
Body:
Hi [First Name],
I noticed [Company] has been researching alternatives to Fivetran — Airbyte, Meltano, maybe a custom Kafka pipeline. A lot of teams we talk to say the per‑row pricing became unpredictable as they scaled past 50M rows/month.
We help data teams cut integration costs without sacrificing reliability. Worth a 5‑minute call to see if what we’ve built is relevant?
[Your name]
Why this works: It shows you’ve done your homework (they’re searching), names a specific pain point (pricing unpredictability), and asks for 5 minutes — a low‑ask.
Day 3: The Problem‑Deepening Follow‑Up
Subject: The dbt dilemma Preview: hidden build times holding you back?
Body:
Hi [First Name],
Following up because ~23% of the data leaders we talk to are re‑thinking dbt alongside Fivetran. Not because dbt is bad — but because the transformation layer can become rigid when you need near‑real‑time views or want to avoid vendor lock‑in.
If you’re considering a more composable approach (or even sticking with dbt but re‑platforming your ingestion), I can share a few architectures that cut build times by half. Up for a quick chat?
[Your name]
Why this works: It shifts the angle from ingestion to transformation — the other half of the stack. The specific statistic feels credible without citing a competitor directly; it positions you as someone who talks to many teams.
Day 7: The Gracious Breakup
Subject: Last call — no hard feelings Preview: Final note on your pipeline
Body:
Hi [First Name],
I assume the timing wasn’t right. Totally understand.
If you revisit the stack in the future, I’m here. In the meantime, our team put together a short comparison of open‑source ELT options (Airbyte vs. Meltano vs. self‑hosted Stitch) — might be useful as you evaluate. Want me to send it?
[Your name]
Why this works: It exits cleanly, offers value without a pitch, and keeps the door open. If they reply “sure,” you’ve got a conversation starter that isn’t a meeting.
Placeholders: Replace [First Name] and [Company] with Origami’s personalization fields. The platform will auto‑populate them from the enriched contact data.
Step 3: Send the Sequence Directly from Origami
Here’s where Origami saves you the tool‑switching headache. After you paste the templates (or let the agent generate them), you’re still inside the same dashboard where you built the list.
- Set delays: Choose the cadence — I default to Day 1, Day 3, Day 7 for this audience. Data engineers are deep in work; giving them two business days between touches respects their time without disappearing.
- Launch: One click sends the sequence. No exporting CSVs, no syncing to a third‑party sequencer, no Mail Merge hiccups. The built‑in email sequencer uses your connected mailbox and keeps your domain warm.
- Track everything in one view: Opens, clicks, and replies appear right next to the prospect’s enriched profile. While you’re looking at a contact’s activity, you can still see their title, company size, and tech stack — so you remember exactly why you reached out.
- Auto‑un‑enrollment: If someone replies, they automatically exit the sequence. You won’t send a Day 7 breakup email after they’ve already booked a meeting. That alone saves more goodwill than any clever subject line.
The sequencer is included on all paid Origami plans — you’re only paying for the credits you used to enrich the leads. The actual sending is free. Even the Free plan (1,000 credits, no credit card) lets you test the entire flow on a small batch.
What Response Rates to Expect
For a list of 200 genuine intent‑signal leads (companies actively searching for Fivetran/dbt alternatives), a 3‑touch sequence like this typically yields:
- Open rate: 65–75% — data professionals are terminally online and curious about stack changes.
- Reply rate: 8–12% — often on the second or third touch. The breakup email alone can generate 2–3% positive replies.
- Meeting conversion: About half of replies turn into a call if your call‑to‑action is lightweight.
If you’re seeing open rates below 50%, your list might need a tighter qualification step. If replies are low but opens are high, tinker with the message — maybe Day 3’s angle isn’t resonating. Iterate the copy first, not the list. One platform means you can swap subject lines, re‑upload a sequence, and redeploy to a fresh cohort without rebuilding everything in another tool.