The script that closes deals in the US does not translate to DACH. Not because DACH executives are harder to reach. Because the way they evaluate an outreach attempt is fundamentally different. They are reading for precision, not enthusiasm. They are checking whether you understand their role before they decide whether you are worth their time.
This guide covers how to write outreach scripts for every major executive role in the DACH market: CTO, CMO, CEO, CFO, VP Sales, Head of Marketing, Procurement, IT Director, HR Director, Operations Director, Product Manager, VP Engineering. Each role has different priorities, different trigger words, and a different tolerance for cold contact.
Why Role-Specific Scripts Matter More in DACH
A German CTO and a German CFO do not want to hear the same pitch. One cares about technical debt and implementation risk. The other cares about total cost of ownership and contract terms. Sending the same email to both is not outreach. It is a list blast.
DACH executives are used to vendor pitches. The ones that get through are the ones that demonstrate clear understanding of the recipient's actual job before making any ask. Role-specific scripting is how you demonstrate that understanding in the first two sentences.
The CTO and Technical Leadership
German CTOs are skeptical of vendor claims and allergic to buzzwords. They will read your email for technical accuracy before they read it for business value. Lead with the technical problem, not the product. Reference architecture decisions, integration complexity, or technical debt where relevant. Avoid "cutting-edge," "next-generation," and "AI-powered" without specifics. They have heard all of it.
What works: a specific technical observation about their stack, their infrastructure footprint, or a common problem in their industry. What does not work: a feature list and a calendar link.
The CFO and Finance Leadership
CFOs in DACH are cost-conscious and compliance-aware. They read for risk and total cost before they read for opportunity. Your script needs to address what the decision costs to avoid making, not just what it costs to implement. Quantify. Use Euro amounts, not percentages. Name the compliance framework if relevant (GDPR, HGB, Basel III for finance). Skip the ROI calculator link in email one.
The CMO and Marketing Leadership
Marketing leaders in DACH are suspicious of performance claims they cannot verify. Attribution is a known problem. "We generated 3x pipeline for a company like yours" requires a named reference or it lands as empty. Position around a specific marketing problem they are visibly dealing with: headcount, channel saturation, measurement gaps. Keep it specific to their visible situation, not the category they are in.
The CEO at Mittelstand and SME
At companies under 200 employees in DACH, the CEO is often still in the operations. They do not have a team to evaluate vendors. They are the evaluator, the budget holder, and the decision-maker. Your script needs to be short, direct, and operationally grounded. No corporate speak. One specific problem. One specific ask. That is it.
Procurement and Buying Committees
Reaching procurement directly skips the relationship-building that DACH buying typically requires. Procurement is a later-stage conversation. Going to procurement first signals that you do not understand how decisions get made in the company. Start with the business owner or the technical owner. Let procurement come to you when the decision is already moving forward.
VP Sales and Revenue Leadership
Sales leaders in DACH are measured on quota attainment and cycle length. They care about pipeline quality, not quantity. Scripts that reference pipeline velocity, deal stage conversion, or DACH-specific close rate benchmarks have a better chance than scripts about "boosting revenue." They have seen the revenue-boosting pitch before. Show them you understand what their pipeline actually looks like in this market.
What Every DACH Executive Script Needs
- A specific trigger. Something visible about their company, market, or role that explains why you are reaching out now, not three months ago.
- One problem, stated precisely. Not a category of problems. The specific one that is most likely costing them something they care about.
- No social proof in email one. The name-dropping comes in the follow-up, after they have shown interest. In email one it reads as defensive.
- A low-friction ask. Not a demo. Not a 30-minute call. A yes/no question or an offer to share a relevant document.