Hello there, welcome! At Reo.Dev, around 25-30% of the accounts we reach out to end up converting into meetings. Here’s the exact playbook we follow to make that happen.
Pre-Requisites
We follow certain email authentication protocols to maintain high deliverability.
We used to track open rates, but they can be misleading. That makes writing genuinely interesting emails that people care about even more important.
First Email
We’re very bullish about keeping the first email succinct - we try to stay under a 150 words.
Subject Line
Comapanies & Developers Evaluating [X]
Whether someone opens an email depends entirely on the subject line. This can’t be compromised.
Our subject lines spark intrigue. Because our product is open source, prospects are naturally curious about which companies and developers evaluate their product, making it hard to ignore.
Introduction / Credibility Statement
I'm one of the CoFounders of Reo.Dev, an intent tool for DevTool companies.
We are big fans of contextualization over personalization.
- Personalization focuses on who the person is, like “I saw your talk at DevOpsDays.” It flatters but doesn’t always connect to the problem.
- Contextualization focuses on what’s happening around them, like “I noticed you just added a Terraform provider—bet infra visibility’s top of mind.” It creates instant relevance, urgency, and product fit.
The intro establishes two things: credibility and premise. It clarifies that the cofounder of Reo is writing about an intent tool for DevTool companies, hinting at value already in the subject line. This grabs attention immediately.
Hook / Problem Statement
Would it help if you knew who's installing your packages or running commands like 'npm install -S @[X]hq/sdk' on CLI?
This is the hook - often where emails lose readers.
From experience, sales calls, and positioning, we know this intel truly matters. For example: knowing who runs key commands like npm install for their product. The command varies by company, and we research it carefully.
Nothing here is automated. SDRs use Reo’s data, tag intelligently, and write manually - making every line relevant. That’s what grabs attention.
In 9 out of 10 cases, companies don’t track this signal. This unique edge consistently gets prospects to read further and discover how else they could benefit from Reo.
Value Proposition
Along with this, Reo can also identify signals like which companies/developers are evaluating competitor/complementary solutions in incognito, and having conversations about headless browser solutions on Reddit, StackOverflow, GitHub and more
We don’t want them to think this is all we do. Reo also identifies signals like companies evaluating competitor or complementary solutions incognito, and tracks conversations about headless browser solutions on Reddit, StackOverflow, GitHub, and more.
Social Proof / Building Trust
Many of our customers have switched from other intent tools to Reo.Dev because it’s a comprehensive, all-in-one solution for their GTM needs.
This is highly contextual. We research which competitor or similar tools companies use and what those tools cover. While they may use an overlapping tool, it’s not comprehensive.
We address this gap without naming competitors. Many customers switch to Reo.Dev because we offer a complete, all-in-one GTM solution. This social proof shows we understand their setup and deliver more value.
Call to Action
Would you be interested to know more?
We don’t ask for meetings in the first or second email - only from the third onward.
Instead, we use a low-barrier prompt like, “Would you be interested to know more?” It makes it easy for people to respond positively by clicking one of the default reply options. We’ve tested this a lot, and it works well on LinkedIn and email.
Getting an early positive reply lets you share more info later while protecting deliverability. The first email’s goal is simply to get a positive response.
TLDR
- Context & Background: Keep first emails under 150 words, focused on engagement and protecting deliverability.
- Subject Line: Make it highly intriguing and relevant to boost open rates.
- Introduction / Credibility: Use contextualization, not generic personalization; establish credibility quickly.
- Hook / Problem Statement: Craft a researched, relevant hook that shows unique value; avoid automation.
- Value Proposition: Highlight broader product value beyond the initial insight.
- Social Proof: Show understanding of their current tools and gaps without naming competitors; prove why others switch.
- Call to Action: Don’t ask for meetings early; use low-barrier CTAs to get positive responses first.
Second Email
Once someone replies positively, you’re clear to share case studies, videos, or personalized landing pages without deliverability concerns.
These are some of the templates we follow:
- We created a custom landing page & then hyperlink it to an image in the email. It’s better to prefer the image over a link because it grabs attention and makes people curious to click. When they do, it opens a customized webpage with all the details about what we offer and how we can help.
- Sometimes, we create a custom demo video using HeyGen & plug it in.
Third Email
We include screenshots showing which developers or companies might be evaluating them. Sharing this sample data helps people see real value and works really well.
Fourth Email
The fourth email is generally followed up with information like how other people are using it / case studies.
Conclusion
Beyond emails, we use a multichannel approach - including LinkedIn DMs and targeted ads—to stay top of mind and increase engagement.
We leverage Reo.Dev’s intent signals to identify and prioritize the right accounts, which significantly boosts meeting success. If you’d like guidance on selecting the best accounts and people to reach out to, you can schedule a free consultation with one of our in-house experts.
For any questions or support, feel free to reach out to us at support@reo.dev.
