How to Run a LinkedIn Outreach Campaign for RevOps Leads in the UK and Netherlands (2026)

Quick Answer

If you've already built a list of RevOps leads in the UK and Netherlands using Origami, the next step is running a LinkedIn outreach campaign that actually converts. Origami has a built-in LinkedIn sequencer — so you can find leads, enrich them, and send personalized multi-touch sequences from one platform without exporting a single CSV. The sequencer is included on all paid plans. You only pay for the credits to enrich your leads. The sending is free.

Below, I'll walk you through the full campaign workflow: how to segment your list for LinkedIn specifically, the exact 3-touch sequence with copy you can steal, and how to send everything directly from Origami while tracking replies, opens, and clicks in the same dashboard.

If you haven't built your list yet, start here: how to build a list of RevOps Leads in the UK and Netherlands. That post covers finding and enriching these prospects using Origami's AI agent. This post picks up where that one ends — with a clean list of names, verified emails, LinkedIn profiles, and company details ready for outreach.

---

Step 1: Build Your List in Origami

You've already done this if you followed the parent guide. But for context, here's what the list-building step looks like inside Origami and why it matters for the outreach that follows.

You type a prompt like this into Origami:

"Find me RevOps leads in the UK and Netherlands. Directors, managers, and heads of revenue operations at B2B SaaS companies with 50–500 employees. Include verified emails and LinkedIn profiles. Exclude agencies and consultancies."

Origami's AI agent goes to work — searching the live web, chaining data sources, enriching contacts, and qualifying leads. What you get back isn't a raw scrape. It's a structured prospect list with:

• Full name
• Verified email address
• LinkedIn profile URL
• Job title and department
• Company name, size, and industry
• Location (city and country)
• Phone numbers where available

All from a single prompt. No manual list-building. No switching between tools.

If you're starting fresh, Origami gives you 1,000 free credits on the free plan — no credit card required. That's enough to build and enrich a solid initial list before you commit to a paid plan (which start at $29/month).

The key point: you're not just getting LinkedIn URLs. You're getting verified emails and company context alongside each profile. When you send a LinkedIn sequence later, you can see — in the same dashboard — that the person you're messaging is a RevOps Director at a 120-person SaaS company in Amsterdam using Salesforce and HubSpot. That context shapes how you message them.

---

Step 2: Refine and Segment for LinkedIn Outreach

A raw list is a starting point. Sending the same sequence to every contact without segmentation is how you burn a good list. RevOps leads in the UK and Netherlands aren't a monolith — and your messaging shouldn't treat them like one.

Here's how to segment your Origami list before you launch anything.

Cut the Obvious Bad Fits First

Flip through your list and remove anyone who clearly shouldn't be there. Things to look for:

• Wrong department: Someone with "RevOps" in their title but actually sits in IT or finance. Check their profile — if their actual remit is internal tooling or FP&A, pull them.
• Wrong company type: Agencies, consultancies, and managed service providers occasionally slip through. If your ICP is B2B SaaS companies, remove anything that looks like a services business.
• Too junior or too senior: A "RevOps Analyst" at a 400-person company probably isn't a decision-maker. A Chief Revenue Officer might be too high — they delegate RevOps tooling decisions. The sweet spot for this campaign: RevOps Manager, Head of RevOps, Director of Revenue Operations, VP of Revenue Operations.
• Mismatched location: Someone might list "London" on LinkedIn but actually be based in Dubai or Bangalore. Check their profile location, not just the search result.

Segment by Company Size

Company size changes the RevOps conversation entirely:

• 50–150 employees: These teams usually have one RevOps person (or a fractional one). They're drowning in manual work. Their pain point is bandwidth. Messaging should emphasize efficiency and automation.
• 150–350 employees: This is where RevOps becomes a small team — maybe 2–4 people. They're fighting tech stack sprawl and data inconsistency. Messaging should focus on unification and clean data.
• 350–500 employees: Multiple RevOps specialists. They're thinking about forecasting accuracy, pipeline analytics, and board-level reporting. Messaging should speak to strategic visibility.

Create three sub-lists in Origami by filtering on company size. You'll tailor your Day 3 and Day 7 messages to each segment.

Segment by Geography

The UK and Netherlands share a lot — both are mature B2B markets with strong SaaS ecosystems — but culturally, the outreach plays differently.

• UK (London, Manchester, Leeds, Bristol): British prospects tend to be polite but guarded on LinkedIn. They respond better to understated messaging and a light touch. Hard pitches on Day 1 get ignored. Lead with curiosity.
• Netherlands (Amsterdam, Rotterdam, Utrecht, Randstad): Dutch prospects are famously direct. They appreciate brevity and hate fluff. A message that's too soft or vague reads as insincere. Get to the point faster than you would with a UK prospect.

Create a UK segment and a Netherlands segment. You'll use slightly different tone and pacing for each.

What "Qualified" Looks Like for This Audience

Before you sequence anyone, ask yourself: if this person replied tomorrow and wanted a call, would I be excited? If the answer is no, cut them. A qualified RevOps lead in this campaign meets these criteria:

• They own or influence RevOps tooling decisions (not just end-users of the CRM)
• Their company is B2B SaaS (or adjacent tech) with 50–500 employees
• They're based in the UK or Netherlands (not just "Europe" broadly)
• Their LinkedIn profile shows activity — posts, comments, or a reasonably complete profile — indicating they're reachable
• There's a visible pain point: recent job change (new role = new stack decisions), company growth (hiring = scaling pains), or a profile that hints at manual processes

A list of 200 names might become 120 after refinement. That's good. You want quality over volume — especially on LinkedIn, where irrelevant outreach gets you blocked.

---

Step 3: Create Your LinkedIn Sequence

This is the core of the campaign. You have two options inside Origami.

Option 1: Paste Your Own Templates

Write your own 3-touch sequence, paste the templates into Origami's sequencer, set your delays between touches, and hit launch. This gives you full control over copy and cadence. Use the templates I've written below — they're built specifically for RevOps leads in the UK and Netherlands.

Option 2: Let the AI Agent Write It

Alternatively, you can ask Origami's AI agent to generate a personalized 3-day LinkedIn sequence for all your leads automatically. The agent pulls from each lead's enriched profile data — title, company, industry, tools used — and writes messages that feel custom per recipient. One RevOps Director at a Salesforce shop in London gets different messaging than a Head of RevOps at a HubSpot-native company in Amsterdam. Same campaign, different words per lead.

I've used both approaches. The agent-written sequences work surprisingly well when you have a large list and want to move fast. But for high-value accounts — say, your top 30 prospects — I still recommend writing your own templates or at least reviewing the agent's output before it goes out.

Below are full copy-paste templates you can use immediately. Each message is 50–100 words, written for this specific audience, and designed to feel like a human wrote it — because one did.

---

The 3-Touch LinkedIn Sequence (RevOps Leads — UK & Netherlands)

Cadence: Day 1 (connection request + note), Day 3 (follow-up message), Day 7 (final message with soft close). Adjust delays based on your audience segment — UK prospects can handle a slightly slower cadence (Day 1, Day 4, Day 8), while Dutch prospects respond fine to tighter pacing.

---

Day 1 — Connection Request + Note

LinkedIn limits connection notes to 300 characters, so this one stays tight. The goal isn't to sell anything. It's to give them a reason to accept.

For UK prospects:

Hi [First Name] — saw you lead RevOps at [Company]. Curious how you're handling pipeline visibility across the UK team. I work with RevOps leaders on unifying their data layer for cleaner forecasting. Thought it'd be worth connecting. —[My Name]

For Netherlands prospects:

Hi [First Name] — your RevOps setup at [Company] caught my eye. I work with teams across Amsterdam and the Randstad on fixing the data layer underneath their CRM. Cleaner pipeline, faster reporting. Would be good to connect. —[My Name]

Why this works: It references their specific role and location. It hints at a problem (pipeline visibility, CRM data quality) without diagnosing it prematurely. It ends with a low-pressure connection request. No pitch, no link, no "I'd love to show you."

---

Day 3 — Follow-Up Message

They accepted your connection. Now you have an open inbox. This message delivers value — a concrete observation from your experience with similar RevOps teams. No "checking in" or "just following up."

For UK prospects (150–500 employee companies):

Hi [First Name], thanks for connecting. I've been speaking with RevOps leads across London and Manchester lately, and one pattern keeps surfacing: CRM data quality is quietly destroying forecast accuracy. One team I worked with cut their weekly reporting cycle from 8 hours to 45 minutes — not by switching CRMs, but by fixing their enrichment and deduplication layer. Curious if that's something on your radar this quarter. —[My Name]

For Netherlands prospects (150–500 employee companies):

Hi [First Name], thanks for the connection. Spoke with a RevOps lead in Amsterdam last month — 300-person SaaS company, scaling fast. Their forecasting was off by 20%+ each quarter because sales, marketing, and CS all had different definitions of a qualified lead. Aligning the data model fixed it in three weeks. If you're dealing with similar cross-team data friction, happy to share what they did. —[My Name]

For smaller teams (50–150 employees) — either region:

Hi [First Name], thanks for connecting. Quick observation from RevOps teams your size: the biggest time-sink isn't strategy — it's manual data work. Spreadsheets, CSV imports, deduping by hand. One team I know freed up 10 hours a week just by automating their lead enrichment. If you're feeling that bandwidth pinch, I can share how they set it up. —[My Name]

Why this works: Each version is specific to company size and region. It names a real pain point (forecast accuracy, data misalignment, manual work). It offers social proof without name-dropping. And it ends with an open question — not a demand for a call.

---

Day 7 — Final Message (Soft Close)

This is your last touch. Be direct. Acknowledge it's the final message. Give them an easy off-ramp.

For UK prospects:

Hi [First Name], last message from me. If pipeline hygiene and forecasting accuracy are on your roadmap this quarter, I'm happy to share what's working for RevOps teams scaling across the UK right now. No pitch — just patterns from people in your seat. Open to a quick call if it's useful. If not, no worries at all. —[My Name]

For Netherlands prospects:

Hi [First Name], I'll leave it here. If your RevOps roadmap includes tighter forecasting or cleaner CRM data in 2026, I've got some patterns from teams across the Randstad that might be useful. Happy to jump on a 15-minute call — or if timing's off, I'll leave you to it. —[My Name]

Why this works: It's direct without being pushy. It respects their time by announcing itself as the final message. It references the year (2026) to signal relevance. And it gives them permission to say no — which, counterintuitively, increases reply rates because it removes pressure.

---

Customization Notes

Don't copy-paste these blindly. Make three small tweaks per recipient before you launch:

1. Reference their actual CRM or tech stack. If Origami enriched their profile and shows they're using Salesforce, mention it: "...fixing the data layer underneath Salesforce" instead of "...underneath their CRM." Specificity signals you did your homework.
2. Acknowledge a recent trigger event. If they posted about a CRM migration or a hiring push, reference it: "Saw your post about the HubSpot migration — curious how the data cleanup phase went."
3. Match the tone to the individual. Some RevOps leads write very formally on LinkedIn. Others are casual. Mirror their style. A Dutch RevOps Director who posts memes gets a different Day 3 than one who only shares Gartner reports.

Origami's sequencer lets you insert variables like [First Name], [Company], and [Tool] directly into templates, so you can customize at scale without manually editing every message.

---

Step 4: Send the Sequence Directly from Origami

This is where Origami saves you from the tool-switching nightmare that plagues most LinkedIn outreach workflows. You don't export your list to a CSV. You don't upload it to a separate sequencer. You don't manually track replies in a spreadsheet.

Here's how it works:

Launch the Sequence

Inside Origami, select your refined prospect list. Open the LinkedIn sequencer. Choose whether you're pasting your own templates or using the AI agent to generate messages. Set your delays:

• Day 1: Connection request + note (sent immediately or scheduled)
• Day 3: Follow-up message (48–72 hours after acceptance)
• Day 7: Final message (4 days after the follow-up)

Hit launch. Origami handles the rest — sending connection requests, waiting for acceptances, then sending follow-ups on schedule. No manual queuing.

Track Everything in One Dashboard

As your sequence runs, Origami tracks:

• Connection acceptance rate: How many sent vs. accepted
• Message opens: Who opened each touch
• Clicks: If you include a link (use sparingly on LinkedIn — links can hurt deliverability)
• Replies: Who responded and what they said

All of this lives in the same dashboard where you built the list. You can click into any contact and see their full enriched profile — title, company, tools used, location — alongside their sequence activity. That context is gold when someone replies. You're not scrambling to remember who they are or why you reached out.

Automatic Un-Enrollment

If someone replies to your Day 3 message, Origami automatically pulls them out of the sequence. They won't get the Day 7 "last message" follow-up. This sounds small. It's not. I've seen campaigns where a prospect replies positively — "Sounds interesting, let's chat" — and then gets a breakup email two days later because the sender's sequencer didn't detect the reply. It kills the conversation instantly. Origami prevents that.

One Platform, End to End

This is the part that matters: you find leads, enrich them, write (or generate) sequences, send them, and track responses — all from Origami. No exporting CSVs. No syncing between a list-building tool and a separate sequencer. No "did I import this list already?" confusion.

The sequencer itself is included on all paid plans. You're only paying for credits to enrich your leads. The sending is free.

What Response Rate to Expect

For RevOps leads in the UK and Netherlands, using the templates above (properly customized), here's what I've seen in 2026:

• Connection acceptance rate: 35–50%. RevOps professionals are reasonably active on LinkedIn and open to connecting with peers. They're not as inundated as sales leaders or C-suite.
• Reply rate to Day 3 follow-up: 12–20%. The specificity of the message — referencing their region, company size, and RevOps pain points — drives this higher than generic "checking in" messages.
• Meeting booked rate (overall): 5–8% of the original list. A list of 120 qualified prospects should yield 6–10 conversations.

If you're below these numbers after two weeks, the problem is usually the messaging, not the list. RevOps leads are reachable — but they ignore generic outreach.

When to Iterate on Messaging vs. Iterate on the List

• Low connection acceptance rate (under 25%): Your connection note isn't landing. RevOps leads don't know why you're reaching out, or your note reads like every other sales pitch they get. Rewrite the Day 1 note. Lead with something specific to their company or role.
• High acceptance rate, low reply rate (under 10%): Your follow-up message isn't resonating. It's either too generic, too long, or too salesy. Swap in a more specific pain point or a tighter social proof example.
• High acceptance rate, decent replies, no meetings: Your soft close on Day 7 is too soft — or too hard. If you're getting replies like "thanks but not right now," your ask is premature. If you're getting no replies at all to Day 7, your message might feel like a template. Test a shorter, more direct version.
• Low everything across the board: Go back to your list. You might be targeting the wrong companies, the wrong titles, or people who aren't actually in RevOps.

Iterate one variable at a time. Change the Day 3 message and let it run for a week before touching anything else. You can't debug a campaign if you change three things at once.

---

Putting It All Together

The full workflow looks like this:

1. Build your list in Origami using the prompt from the parent guide.
2. Refine and segment — cut bad fits, group by company size and geography.
3. Create your sequence — either paste the templates above or let Origami's AI agent generate personalized messages.
4. Launch from Origami — no exporting, no tool-switching, everything tracked in one dashboard.
5. Review results after 10–14 days — iterate on messaging or list quality based on what the data tells you.

RevOps leads in the UK and Netherlands are a strong audience for LinkedIn outreach in 2026. They're technical enough to appreciate specificity, senior enough to have budget influence, and reachable enough to respond — if your messaging earns it. The templates above are a starting point. Customize them, test them, and let the data guide your next move.

Ready to build your list first? Start here: how to build a list of RevOps Leads in the UK and Netherlands.