DACH Legacy Modernization LinkedIn Outreach: 3-Touch Campaign That Works in 2026

Quick Answer: You built your list of DACH legacy modernization leads using Origami (if not, grab the free plan and run a prompt like the one in this guide). Now it’s time to make those leads move. The real edge is that Origami has a built-in LinkedIn sequencer — so you can refine, sequence, and send your entire outreach campaign in one platform without juggling tools. This post shows you the exact 3‑touch LinkedIn campaign I use to turn DACH IT leaders into conversations, including the ready-to-steal messages.

---

This is the companion piece to our guide on how to build a list of DACH Legacy Modernization Leads. If you already ran a search in Origami and have 200+ contacts sitting on your screen, you’re exactly where you need to be. I’ll walk you through what I do with that list — refining it, writing messages that get replies, and sending everything directly from the same dashboard where I found the prospects. No CSV exports. No LinkedIn Sales Navigator sync. No second tool.

---

Step 1: Build the List (Skip This If You Already Have Your DACH Legacy Modernization Leads)

If you don’t have a list yet, Origami makes it lazy-easy. Here’s the exact prompt I used to fill my pipeline with DACH modernization targets in 2026:

"Find B2B decision-makers in Germany, Austria, and Switzerland (DACH) who are responsible for IT modernization. Target CTOs, Heads of IT, and IT Directors at mid-market manufacturers, banks, and insurers that still run legacy ERP systems like SAP ECC, Oracle E-Business Suite, IBM iSeries/AS400, or old COBOL-based applications. Look for companies with public digital transformation announcements in the last 12 months, recent job posts for modernization roles, or tech stacks that show the company uses legacy software. Exclude startups."

Drop that into Origami. The AI agent searches live web data, chains data sources, enriches contacts, and returns a list with verified names, work emails, direct dial phone numbers, job titles, company details, and tech stack hints — like “uses SAP ECC 6.0” or “COBOL job listing in Munich.”

The free plan gives you 1,000 credits with no credit card, so you can run this prompt and walk away with 50-100 qualified leads without spending a cent. Paid plans start at $29/month and let you enrich hundreds of contacts and launch the LinkedIn sequences we’ll get to in Step 3.

---

Step 2: Refine and Qualify — Not Every DACH IT Leader Is a Good Fit

Building the list is step one. The difference between a LinkedIn campaign that books meetings and one that burns through your connection limits is how ruthlessly you qualify before you hit send.

How I segment the DACH legacy modernization list

I sort the raw Origami output into three buckets directly in the platform. The platform shows you a table right after the search; you can mark contacts as qualified, remove them, or add notes.

Bucket A – High probability (≈30-40% of the list)

• CTO/VP of IT at a mid-market manufacturer (500-2,000 employees) in Germany
• Firm is running SAP ECC and hasn’t migrated to S/4HANA yet
• Tech stack shows IBM iSeries, AS400, or old mainframe mentions
• Job posting for “Legacy Modernization Architect” or “IT Transformation Manager” in the last 6 months
• Company has press release about “digital factory” or “Industrie 4.0” initiative

Bucket B – Moderate probability (≈40%)

• Heads of IT or IT Directors at large automotive suppliers, banks, or insurers
• Still on Oracle E-Business Suite or legacy core banking systems
• No public transformation signals but manual research shows heavy reliance on SAP ABAP or COBOL codebases
• Large employee count (5,000+) — decision-making might be slow

Bucket C – Low priority (remove these)

• Pure service providers, IT consulting firms (they’ll sell you modernization, not buy it)
• Recent press showing they already moved to S/4HANA or a cloud-native ERP
• Junior roles (IT managers without budget authority)
• Companies headquartered outside DACH, even if they have local offices

What “qualified” looks like for this audience

A qualified DACH legacy modernization lead is someone who:

• Has genuine pain (rising maintenance costs, compliance pressure, talent shortage for their current stack)
• Has authority to initiate a vendor evaluation (CTO, Head of IT, or IT Director with budget ownership)
• Works at a company that’s big enough to have a modernization budget but not so political that a pilot is impossible
• Shows at least one external trigger — a job listing, a conference talk, an interview where they mention “IT-Modernisierung”

I keep the whole list visible in Origami so that when I start sequencing, I can always glance at the contact’s enriched profile and remember why I reached out.

---

Step 3: Create the LinkedIn Sequence — Exactly What to Say to DACH Legacy Modernization Leads

Now the only part that matters: the messages. If you’ve been scribbling generic “saw your profile” notes, stop. DACH IT leaders are direct, technically savvy, and allergic to fluff. Your sequence must acknowledge their world — regulatory requirements like GoBD and GDPR, the SAP ECC 2027 maintenance deadline, and the cold sweat around finding COBOL developers in Stuttgart.

Origami gives you two ways to load the sequence:

1. Paste your own templates: Write a 3‑touch sequence, drop it in the sequencer, set the delays between each touch (e.g., Day 1, Day 3, Day 7), and launch.
2. Let the AI agent write it: Ask Origami’s agent to generate a personalized 3‑day LinkedIn sequence for every lead automatically. It reads the contact’s title, company, industry, and tech stack and crafts a custom message per person. This is scary good when you have 200 contacts and don’t want to write 200 first messages.

For this guide, I’ll give you the manual sequence I’ve tested and keep coming back to. Copy it, tweak the placeholders, and you’re ready.

The 3‑Touch LinkedIn Sequence for DACH Legacy Modernization Leads (2026)

All three messages assume you’ve built the list from Origami and already know the contact’s name, company, and a bit of context (like their tech stack). I’ll show you the exact copy, then explain the strategy.

---

Touch 1 – Connection request with note (Day 1)

Note: LinkedIn limits connection notes to 300 characters. I pack this tight.

Hi [First Name], I noticed your [mention a public signal, e.g., recent post about IT architecture, job ad for modernization, or interview on digital transformation]. I help DACH manufacturers and banks move from legacy ERPs to modern platforms without disrupting operations. Worth connecting? – [Your Name]

Why it works:

• References a specific trigger so it doesn’t feel mass-sent.
• Speaks directly to “legacy ERPs” — the phrase that makes the recipient nod.
• Ends with a low-friction ask. No pitch, just “worth connecting?”

Length: Roughly 280 characters. Leave room for his name and your name.

---

Touch 2 – First follow‑up (Day 3, after they accept)

Thanks for connecting, [First Name]. I noticed [Company] still runs on [SAP ECC / Oracle EBS / IBM iSeries] — a lot of DACH firms are staring at the 2027 deadline and the cost of maintaining ABAP/COBOL talent. I work with IT leaders to scope a pragmatic modernization roadmap that keeps what works and replaces what doesn’t, all while staying GoBD‑compliant. Would a 15‑minute call to exchange notes be useful?

Why it works:

• Calls out the specific system (personalized if you pulled that data from Origami).
• Touches the three pain points: compliance (GoBD), cost, and talent shortage.
• Proposes a short, peer‑level “exchange notes” call, not a demo.

Length: 87 words. Direct, no fluff.

---

Touch 3 – Final message (Day 7)

[First Name], I know you’re busy. Just one thought: most DACH CIOs I’ve talked to are surprised that they can wrap their existing COBOL or ABAP logic in modern APIs and get a cloud‑native UX in months, not years — without ripping out the whole core. If 2026 is the year you’re putting modernization on the table, I’d be happy to share a couple of examples from your industry. No pitch. Just patterns.

Why it works:

• Acknowledges they’re busy (respectful).
• Concrete and technical: “wrap COBOL in APIs” is the kind of detail that earns credibility.
• Reframes the ask from “buy our service” to “let me share patterns” — which DACH execs respect.
• The “2026” mention proves you’re current.

Length: 89 words.

---

How to set the delays

I set the sequence to:

• Day 1: Connection request.
• Day 3: Follow‑up (only if they accepted).
• Day 7: Final message.

If they accept late (say Day 5), I adjust or skip manually, but most connection requests get answered within 48 hours. Origami lets you configure delays between each touch however you like.

What about the AI‑generated option?

If you don’t want to write templates, just tell Origami’s agent something like: “Write a 3‑day LinkedIn sequence for DACH legacy modernization leads. Use the same structure: connection note that references a recent trigger, a follow‑up that highlights cost/compliance/talent, and a final message with a technical insight and soft close.” The agent creates unique messages for each lead based on the enriched data. I’ve used it for larger campaigns and the personalization level is unnervingly accurate.

---

Step 4: Send the Sequence Directly from Origami — No Exporting, No Syncing

This is where the workflow gets beautifully tight. In Origami, you don’t need to export your list to a separate LinkedIn tool or manually copy‑paste into Sales Navigator. The platform has a built‑in LinkedIn sequencer that sends connection requests and follow‑up messages automatically from the same dashboard where you built and qualified your list.

Here’s exactly what happens after you click “Launch”:

1. Sending: The sequencer sends connection requests with the note you wrote (or the AI‑generated note) on Day 1. It respects LinkedIn’s daily limits, so you’re not flagged for spam.
2. Delays: It waits the number of days you set (e.g., 3 days), then sends the first follow‑up only to the contacts who accepted your connection request. After another delay, it sends the final message.
3. Automatic un‑enrollment: If a lead replies at any point — even a “Sounds interesting, let me loop in my team” — Origami automatically removes them from the sequence. You’ll never accidentally send a breakup email to a prospect who already booked a call.
4. Tracking: Opens, clicks, and replies show right inside the lead’s row. You can see that a CTO at a Bavarian automaker opened your Day 3 message twice and clicked your link.
5. Context always visible: While looking at a contact’s sequence activity, you can still see their full enriched profile — job title, company details, the tech stack Origami found. This is crucial when they reply, because you don’t have to go hunting for why you reached out in the first place.

Pricing: The sequencer itself is free on all paid plans. You only pay for the credits used to enrich leads. So you can build a list with 200 credits, and then send a sequence to those 200 contacts at no additional cost beyond your plan.

What response rates can you expect?

Based on campaigns I’ve run with a well‑segmented DACH list and the sequence above:

• Connection acceptance: 20–30% (DACH IT leaders are relatively responsive on LinkedIn if you don’t sound like a sales bot).
• Reply rate after Touch 2: 8–12% — many will reply with a specific question about their stack, which is a great signal.
• Booked meetings (Touch 3 or replies): 4–6% of total contacts enriched. That’s 8-12 meetings from a 200‑contact list.

These numbers assume your list is clean and your trigger is real. If you’re blasting a generic “Hi, I’m a Salesforce partner” to every “Head of IT” in Zürich, expect 0 replies and a LinkedIn restriction notice.

When to iterate messaging vs. iterate the list

If after 100 connection requests you’re seeing <15% acceptance, the issue is rarely the message. It’s usually the list. Go back to Origami and tighten your prompt: filter for recent triggers, exclude consulting firms, focus on one country, or add a tech-stack filter like “company that lists COBOL skills in job ads.” A smaller, sharper list always beats a big, weak one.

If acceptance is high but replies are low, the sequence probably feels too generic. Look at the profiles that didn’t reply — do they have a signal you could reference? Adjust your Day 2 message to include a known trigger, or let the AI agent try variations.

---