with the skill
A 2% reported open rate is a reason to check deliverability before rewriting the subject line. Open tracking is unreliable, so it doesn’t prove your emails are landing in spam, but copy alone may not be the issue.
**Here’s a starting draft**, assuming your training is for developers:
**Subject:** developer security training
Hi [First name],
How does your team decide which secure-coding topics developers need most?
[Company] offers cybersecurity training focused on [specific development problem], so engineers can apply it to the code they’re shipping.
Would a sample lesson be useful?
[Your name]
[Company] · [Postal address]
If this isn’t relevant, reply “no” and I won’t follow up.
**What would make this stronger**
Show the rest (11 more lines)
- **A relevant trigger:** An actual engineering initiative, hiring push, or technology change connected to the training.
- **One credible proof point:** A customer result you can substantiate. Don’t invent a percentage.
- **A narrower audience:** For developer training, an AppSec or engineering leader may be closer to the need than the CTO. For employee awareness training, a CISO or security-awareness lead may be a better fit.
**Before sending another batch**
- Confirm SPF, DKIM, and DMARC are configured correctly.
- Test inbox placement and verify addresses; keep bounces below 2%.
- Turn off open and click tracking. Measure replies, positive replies, and meetings.
- Use an authenticated secondary sending domain clearly associated with your company, rather than risking your primary domain.
Paste your current email and subject line, and tell me **who the training is for** and **your strongest customer result**. I’ll turn this into a specific rewrite rather than a generic cybersecurity pitch.