| #1 | "Acme + RevOps benchmarking — quick ask" | Names the prospect's company and a specific angle. |
| #1 | "{Mutual contact} suggested I reach out" | Mutual-contact subjects routinely double open rates. |
| #1 | "Question on your Q4 RevOps stack" | Question subjects out-open statement subjects. |
| #2 | "Re: Acme + RevOps benchmarking" | Re: prefix mirrors a real thread — opens get a 2-3× lift. |
| #2 | "Floating this back up" | Honest, low-pressure, doesn't pretend to be a new message. |
| #3 | "Acme + the RevOps tool-stack benchmark" | Subject promises a deliverable, not a meeting. |
| #3 | "One-page teardown for the Q4 review" | Names a deliverable the reader can use right now. |
| #4 | "How {peer} cut RevOps tooling 40%" | Named peer + a hard number = a clickable promise. |
| #4 | "{Peer company}'s 14-tool to 1-tool migration" | Peer-company specificity beats generic case-study framing. |
| #5 | "Different angle — quick research question" | Pattern interrupt signal — readers open out of curiosity. |
| #5 | "Three questions for a RevOps benchmark" | Names a finite ask the reader can satisfy in minutes. |
| #6 | "Closing your file — Acme" | Loss-aversion + honourable framing — the highest-reply subject. |
| #6 | "Should I stop emailing?" | Direct breakup — bluntness signals respect for the reader's time. |
| #6 | "Quick yes or no" | Pre-grants the easy-out in the subject line itself. |
| #7 | "Saw the Series-D — back in touch" | Trigger-based re-opener. No ask, just signal. |
| #7 | "Three months later — quick update" | Honest about the gap, respects the reader's memory. |
| #all | "{Specific question they would enjoy answering}" | When in doubt, ask a question the reader genuinely cares about. |
| #all | "Idea for {their specific project}" | Names a project the reader is publicly working on. |
| #all | "Two minutes — {specific benefit}" | Names the time cost and the payoff in the subject itself. |
| #all | "Worth a reply?" | Pre-grants the no — counter-intuitively raises yes-rate. |