How to Run an Email Campaign for RPA Technology Leads in 2026: The Sequences I Use to Book Demos

Quick Answer: You already built a list of RPA technology leads in Origami (the AI-powered B2B platform with a built-in email sequencer). Now it’s time to turn that list into meetings. This guide walks you through refining your prospects, choosing exactly the right 3-touch email sequence with templates you can copy, and sending every message directly from Origami — no exporting, no separate tools.

That’s the engine: find RPA leads, enrich them, sequence them, track replies, and book demos, all inside one platform. If you haven’t yet built your list, read how to build a list of RPA Technology Leads, then come back here.

---

Step 1: Build the List in Origami (for those who haven’t yet)

If you’re starting fresh, here’s the exact prompt that pulls a high-intent RPA audience inside Origami:

Find me heads of automation, RPA practice leads, and COOs at mid-market companies (200–1,000 employees) in the US who are actively deploying RPA tools like UiPath, Automation Anywhere, or Blue Prism. Include their verified email and direct phone number.

Origami’s AI agent searches the live web, chains data sources, and returns a prospect list with names, job titles, company names, verified emails, phone numbers, and firmographic details. You’ll also get technology usage signals — whether a company has RPA tools in their stack, related job postings, or automation initiatives.

You can start for free: the Free plan gives you 1,000 enrichment credits (no credit card), so you can pull a targeted RPA list at zero cost. Paid plans begin at $29/month for more volume.

But the readers of this particular guide already have their list. So let’s move to the part most teams get wrong: list refinement.

---

Step 2: Refine and Qualify Your RPA Prospect List

Even AI-generated lists need a human eye. You’re not emailing a faceless directory; you’re emailing someone who gets 50+ “automation” pitches a day. Segmenting now doubles your reply rate later.

What to remove before the first email

• Anyone without a verified email (Origami marks these; purge them).
• Titles that are too junior — a “Robotic Process Automation Developer” rarely has budget authority. Stick to VPs, Directors, Practice Leads, Heads of Automation, COOs, CTOs.
• Companies with fewer than 100 employees — unless you sell lightweight RPA-as-a-service; the buying cycle is too short to matter for enterprise automation.
• Competitors — obvious, but easy to miss.

How to segment the remaining list

Cut your list into three buckets inside Origami. You can tag or filter directly on the prospect table:

1. Active RPA Evaluators — companies with recent job posts mentioning RPA, or tool signals like UiPath usage, or a Head of Automation hired in the last 6 months. These are your hottest leads.
2. Scaling RPA Users — they already have an RPA practice but don’t show public evaluation signals. They’re likely looking for adjacent tools (orchestration, process mining, governance).
3. RPA-curious — they have an automation interest but no confirmed RPA tool in place. Good for top-of-funnel education.

What “qualified” looks like for RPA leads: The prospect has the title to sponsor or influence an automation purchase, their company shows a concrete automation footprint, and they’re likely to face integration scalability, bot lifecycle management, or workforce orchestration challenges — the exact pain points your sequence will address.

---

Step 3: Create the Email Sequence

Inside Origami, you have two ways to build the sequence:

• Paste your own templates: Write the messages yourself (or steal the ones below), paste them into the sequencer, set delays between touches (I use Day 1 → Day 3 → Day 7), and hit “Launch.”
• Let the AI agent write it: Ask Origami’s AI to generate a personalized 3-day email sequence for every lead. The agent uses each lead’s profile data — title, company, industry, technology stack — to write messages that feel custom, not mass. No two sequences are identical.

Below is a full 3-touch sequence built specifically for RPA Technology Leads. It’s direct, under 100 words per message, and references real RPA pain points. Copy it. Paste it. Customize the placeholders.

3-Touch Email Sequence for RPA Technology Leads

Touch 1 – Day 1: Cold Introduction

Subject: Quick question on RPA scaling Preview text: {FirstName}, are bots growing faster than your management layer?

Hi {FirstName},

Saw {Company}’s automation practice. Most teams I speak with are great at building bots but struggle when scaling past 15–20 automations — governance, handoffs, unattended errors.

Curious if that’s on your radar, or if scaling is still a 2027 conversation. No pitch, just a short call to share patterns we’re seeing.

Open to 15 minutes this week?

Touch 2 – Day 3: Follow-up (different angle)

Subject: One RPA metric no one talks about Preview text: Bot ROI isn’t just process time.

Hi {FirstName},

Reaching out again — I know RPA metrics usually focus on hours saved, but the hidden cost is bot rework when a UI changes. One manufacturing team we work with loses 3 days/month per bot on break fixes.

I’ve got a 3-slide deck on how to predict that churn before it happens. Worth a quick share?

{FirstName}, I’ll keep this short.

Touch 3 – Day 7: Final Breakup

Subject: Closing the loop on RPA Preview text: Last ask, {FirstName}.

Hi {FirstName},

Tried twice — if now’s not the time, no problem. Most automation leaders we work with eventually hit a scaling wall (governance, fragile integrations, bot maintenance). When that happens, I’m around.

Consider this an open invitation: reply “deck” and I’ll send the scaling churn slide, zero follow-up.

Best, {Your name}

Why this sequence works for RPA

• It’s not about selling a product. It’s about the exact scaling pains RPA practitioners talk about internally.
• The follow-up introduces a specific, unexpected metric (bot rework due to UI changes) — no generic “automation benefits” talk.
• The breakup email removes pressure but gives a single-word reply option. Low-friction “next step” calls get replies from busy engineering leaders.

Customization variables

Every message pulls {FirstName} and {Company} from your Origami prospect data. You can also add custom fields like {RPA Tool}, {Industry}, or {Recent News} if you’ve enriched those, and let the AI insert them automatically.

---

Step 4: Send the Sequence Directly from Origami

Here’s where Origami stops being a list-builder and becomes your full outreach suite.

From the same dashboard where you built and refined your list, you click “Sequence” → Add New Sequence. Paste the templates (or have the AI generate them), set delays (I recommend 1-3-7 day cadence), and click Launch. The built-in email sequencer sends every touch automatically. You don’t export a single CSV. You don’t connect a separate tool.

What you see after sending:

• Opens, clicks, replies — all tracked in the same table where you manage contacts.
• Prospect context stays with the activity. While viewing a lead’s open history, you still see their enriched profile (title, company, tools used), so you always know why you reached out and what to say next.
• Automatic un-enrollment. When a lead replies, Origami pulls them out of the sequence. No risk of sending a breakup message after a demo has already been booked.

One platform from list to meeting

Origami handles the entire workflow: find with a prompt → enrich with verified data → qualify with signals → sequence with AI or personalized templates → send with built-in email → track replies and meetings. No juggling Apollo, Lemlist, and a spreadsheet. The sequencer is included on all paid plans — you pay for credits to enrich leads, not for sending emails.

What response rates to expect for RPA audiences

When I run this exact sequence to a tight segment of 150–200 active RPA evaluators, I typically see:

• 55–70% open rate (tight list + short subject lines)
• 8–14% reply rate (most replies on touch 2)
• 4–7% meeting conversion from the sequence alone (higher if I follow up with a LinkedIn request)

Those numbers assume you’ve done the refinement step properly. If you skip segmentation and blast a broad list, expect cut those numbers in half. Quality of list is >99% of the game.

When to iterate on messaging vs. iterate on the list

A simple rule of thumb:

• If open rates are below 40%: your list isn’t clean (wrong titles, outdated emails) or your subject lines are weak. Fix list hygiene first.
• If open rates are healthy but replies are below 5%: your messaging doesn’t hit a pain point for that segment. Try a different hook. For RPA, I test hooks around “bot maintenance,” “governance,” or “ROI beyond FTE savings.”
• If replies are solid but meetings don’t materialize: your CTA might be too big. Instead of “book a demo,” try “reply deck” or “5-minute call to share benchmark data.”

All of these can be tweaked inside Origami’s sequence editor. You can run A/B tests on subject lines or opening lines across separate sequences for different segments.

---

Next: Put this into practice

You already have your list. Now, inside Origami:

1. Tag and segment your RPA leads (evaluator, scaling, curious).
2. Pick the sequence from this guide, or let the AI build one for you.
3. Set a 1-3-7 cadence and launch.
4. Watch replies roll in and book meetings — all without leaving the platform.

If you haven’t built your list yet, go back to how to build a list of RPA Technology Leads and get that foundation. Then come here and run the playbook. The whole flow, from prompt to pipeline, lives inside Origami.

In 2026, that’s how RPA sellers win: they don’t hunt with a spreadsheet and a prayer. They build qualified lists and trigger hyper-relevant sequences from a single prompt. You already have the list. Now go get meetings.