Skip to content
DEVOPSMULTICHANNELCTO & CISO

Cold email sequence for DevOps & cloud — 15% response rate

7 steps over 40 days. 5 emails, 1 phone call, 1 LinkedIn message. 369 prospects contacted.

Charles Perret, founder of devlo

Charles Perret

Founder of devlo.ch · March 2026

369
Prospects contacted
58%
Open rate
15%
Response rate
6
Interested prospects

The 7 keys in the sequence

5 emails, 1 phone call, 1 LinkedIn message — over 40 days.

LinkedInDay 1LinkedIn login
{% spin %}{% variation %}Hello{% variation %}Dear{% variation %}Hi{% endspin %} {{firstName}}, {{linkedinnote}}. The LinkedIn note begins as follows: “Your LinkedIn post regarding… Your LinkedIn profile states that… Your interview OR your article OR your blog post… My colleague Charles told me about… … I’m delighted to connect with you. [Client_Name]” If the LinkedIn connection request is accepted, the following message is sent 7 days later: Hello {{firstName}}, my colleague {{salesRep}} has sent you an email. Do you handle self-hosted [ProductName] solutions that might be of interest to {{companyName}}? [ClientCustomer] and several Fortune 500 companies use our solution, as do companies such as {{company name}}. They are accelerating the integration of their on-site, nearshore or offshore software development teams. And they are turning to our solution because it is the first CDE platform to offer both productivity and data security. If the LinkedIn connection request is accepted, the following message is sent 21 days later: Hello {{firstName}}, would it be best to contact {{colleaguename1}} or {{colleaguename2}} to discuss the developer experience, productivity, laptop management and compliance costs, etc.?
EmailDay 1Email #2
Subject: our call {{firstName}}
{% assign ampm = "now" | date: "%P" %}{% if ampm contains "am" %}Good morning{% else %}Good morning{% endif %} {{firstName}}, A] {{icebreaker}}. My research shows that you lead [ProductName]. B] My research indicates that you, {{colleaguename1}} and {{colleaguename2}}, lead [ProductName]. Our clients, companies such as [ClientCustomer], rely on our solution to improve their developers’ productivity and coding experience. Internal and external teams work on self-hosted cloud development environments (CDEs). Unlike DaaS or VDI, CDEs are pre-configured Linux development environments that include all the tools, libraries, dependencies and security features. [ClientCompanyName]’s CDEs are the first secure, standardised, ready-to-use development environments. Among other things: Developer onboarding time has been reduced from several days to just a few minutes Laptop management and compliance costs have been reduced by 50% The entire development environment is now secure Does the idea of having a bit more context during a call appeal to you, or am I way off the mark? PS – Version A{{firstName}}, does that ring a bell? {{signature}}
Email7 days laterEmail #3
{% assign ampm = "now" | date: "%P" %}{% if ampm contains "am" %}Good morning{% else %}Good morning{% endif %} {{firstName}}, What do you think of my latest suggestion, which is to explore how our clients balance developer productivity with security? The idea is to meet for an initial, no-obligation discussion. What’s more, the {year} special offer allows [ProductName] to see for themselves, in their own environment, that there’s no need to sacrifice efficiency for the sake of security. This 45-day pilot project helps: DevOps teams to ensure their developers’ productivity and comfort CIOs to reduce risks associated with software development ({{colleaguename3}}?) CIOs to reduce costs whilst ensuring compliance ({{colleaguename4}}?) PS: One of the benefits our clients appreciate most is access to real-time information. They have an overview of all aspects of their [ProductName], as shown in the dashboard I created for {{companyname}} below: {{signature}}
Email5 days laterEmail #4
Subject: Talk to {{colleaguename1}} or {{colleaguename2}}
{% spin %}{% variation %}Hello{% variation %}Dear{% variation %}Hi{% endspin %} {{firstName}}, Would it be best to contact your colleague {{colleaguename1}} or {{colleaguename2}} to discuss the DevOps infrastructure, code development efficiency and data resource security? Or perhaps someone else? I understand you’re busy, but it would be a shame not to explore whether there are opportunities for improvement at {{companyName}} through the use of cloud-based development environments. Thanks PS: My to-do list below reminded me to write to you 😉 {{signature}}
Call3 days laterPhone call
Cold call no. 1 Date sent: 3 days after the last message If the prospect answers: “John Doe speaking” Hello John, I’m {{salesRep}} from {clientCompanyName}. How are you? “I’m fine” I contacted you by email regarding (If the market were a little more mature) online containers for code development activities to ensure developers’ productivity and comfort pre-configured, self-hosted Linux development environments We improve the efficiency, security and governance of your entire application development process whilst reducing management costs. This is recognised in this year’s {clientRecognition} report. Do you have a minute to discuss this? “Yes” “I don’t have time right now, I’m about to go into a meeting” See below ↘ Oh, right, could I ring you back tomorrow morning around 10 am? “Yes, that suits me” Right, thank you. You’ll receive an invitation. Have a good meeting and see you tomorrow. [END] To give you a bit of context, (If not already mentioned: to be confirmed Are you interested? “Yes” See below ↘ “No, I’m not the right person” to be confirmed ↙ ↓ “Yes” See below ↘ to be confirmed Would it be a good idea to organise an initial meeting for all of us to discuss and share best practices, with no obligation, of course? [Get contact details] And for now, what projects are you overseeing to help your colleagues with their work? [...] (full content available on request)
Email0 days laterEmail #6
Subject: Our telephone conversation
{% spin %}{% variation %}Hello{% variation %}Dear{% variation %}Hi{% endspin %} {{firstName}}, I tried to call you today on [PhoneNumber]. You’re probably familiar with GitHub Codespaces, so you might be interested to find out how [ClientCompanyName] is the most secure self-hosted alternative for managing development environments. Would you like to have a virtual coffee to discuss this in more detail? {{signature}}
Email4 days laterEmail #7
{% assign ampm = "now" | date: "%P" %}{% if ampm contains "am" %}Good morning{% else %}Good morning{% endif %} {{firstName}}, Would it be a good idea to contact {{colleaguename3}} or {{colleaguename4}}, given that our cloud development environment is the first infrastructure-as-a-service solution focused on security? Our {clientRole} {clientName} and I have tried to contact you several times. We thought you might be interested to know how our clients: improve their developers’ experience (it now takes just one minute to onboard them) thanks to ready-to-use Linux development environments that work in any browser control the risks of data exfiltration and access to resources achieve savings of 30–50% by switching to CDE If this doesn’t interest you, please let me know – I completely understand. Or should I get back to you early next year? Kind regards, {{signature}}

Why this sequence works

369 prospects were contacted, with a 15% response rate in the DevOps sector. The 58% open rate is typical for this technical segment, where decision-makers are approached on a daily basis. The sequence of seven follow-ups over 40 days allows technical managers time to consult their teams before replying.

The technical positioning is precise: the distinction between CDEs, DaaS and VDIs in the first email immediately demonstrates technical expertise. For a DevOps leader, this familiarity with the terminology is a sign of credibility that sets the message apart from the hundreds of emails sent by generalist salespeople.

Customising the dashboard with the prospect’s company name (Touch #3) is a remarkably effective ‘show, don’t tell’ technique. Rather than having the benefits described to them, the prospect can immediately visualise how the solution would work in their specific context.

What you can learn from this campaign

  • Establish your technical stance right from the first email. Distinguishing between CDEs, DaaS and VDIs demonstrates a level of expertise that DevOps decision-makers respect.
  • Customise the dashboard with the prospect's name. "Show, don’t tell" is more powerful than a list of features.
  • Propose a 45-day trial period. For a DevOps leader, testing in their own environment is the only valid argument.
  • Target multiple decision-makers (DevOps, CISO and CIO). Mentioning four different colleagues increases the chances of reaching the right person.

When to use this sequence

DevOps and Cloud Development Solutions

Does your product focus on development environments, code security or development infrastructure?

Targeting CTOs, VPs of Engineering and CISOs

The session is aimed at DevOps, security and infrastructure managers alike.

Companies with nearshore/offshore teams

If your solution addresses the productivity and security challenges faced by remote teams.

Sale with test drive

The 45-day pilot is a model that can be applied to any DevOps or infrastructure solution.

Who can use this sequence?

DevOps and cloud publishers

Whether your solution covers development environments, security or infrastructure.

SDRs targeting engineering teams

The technical terminology and call scripts are tailored for leading DevOps professionals.

Developer experience startups

Adapt the workflow to your own developer productivity metrics.

Cloud integrators and security

If your offering combines cloud infrastructure with data protection for development.

Frequently Asked Questions

How can you capture the attention of a DevOps decision-maker?

Precise technical terminology is essential. Distinguishing between CDEs, DaaS and VDIs in the first email demonstrates a level of expertise that DevOps leaders respect. Mentioning specific technologies (GitHub Codespaces at Touch #6) and well-known clients such as Fortune 500 companies establishes credibility.

Why a 45-day pilot scheme?

DevOps decision-makers want to test the solution in their own environment before committing. A 45-day trial allows them to assess the impact on developer onboarding, reduced maintenance costs and security. It is long enough to yield meaningful results, yet short enough to maintain a sense of urgency.

How can I customise the dashboard for each prospect?

Create a dashboard template featuring the prospect’s company logo and name. It takes five minutes per prospect but triples the response rate. The prospect can immediately visualise how the solution would look in their own context, which is more effective than a generic demo.

Want a customised sequence for your industry?

devlo designs and executes bespoke B2B cold email campaigns. ICP, buying signals, multi-channel sequences — we take care of everything.

View all 25 sequences

Last updated: March 2026