# Output 1 ## Mode 6 — Subject Line Lab **Inputs used:** Offer = fixed-fee Salesforce pipeline cleanup, 21 days. ICP = VP Sales, 50–200 person B2B SaaS. Trigger = company just hired its first RevOps leader. No proof/cases available, so nothing implying results or social proof is included. ### 20 Subject Lines **A. Lowercase internal (reads like an internal note)** 1. quick q re: pipeline data 2. salesforce cleanup timing 3. new revops hire + pipeline 4. pipeline hygiene before next qbr **B. Specific noun (concrete, no hype)** 5. Salesforce pipeline audit 6. 21-day pipeline cleanup 7. stale opportunity records 8. pipeline data hygiene **C. Question** 9. Is your Salesforce data RevOps-ready? 10. How clean is your pipeline data right now? 11. Who owns pipeline hygiene now that RevOps is in place? 12. Worth a look at stale opportunities? **D. Trigger reference (new RevOps hire)** 13. Saw you brought on a RevOps lead 14. Congrats on the new RevOps hire 15. New RevOps leader, messy pipeline? 16. RevOps onboarding and CRM data **E. Curiosity gap (honest, not clickbait)** 17. one thing new RevOps leaders always ask for 18. the pipeline problem most VPs inherit 19. what your RevOps hire will find first 20. before your RevOps lead runs their first report ### Top 5 Ranked by Expected Reply Quality | Rank | Subject Line | Category | Why | |---|---|---|---| | 1 | Saw you brought on a RevOps lead | Trigger | Specific, timely, clearly relevant to the recipient — reads like it was written for them, not blasted | | 2 | what your RevOps hire will find first | Curiosity | Names a real, near-term concern (new hire auditing the CRM) without overpromising | | 3 | Who owns pipeline hygiene now that RevOps is in place? | Question | Surfaces a real organizational ambiguity a VP Sales would want to answer | | 4 | 21-day pipeline cleanup | Specific noun | Plainly states the offer and timeframe — low risk, sets accurate expectations | | 5 | new revops hire + pipeline | Lowercase internal | Low-key, non-salesy tone tends to get opened by senior recipients | Lines 2, 17, and 19 lean closest to "curiosity" — kept deliberately mild (no withheld shocking claim, no fake personalization) so they stay in the honest/non-clickbait zone requested. --- **Assumptions made:** - "First RevOps hire" is treated as a title/role change trigger, not tied to a named individual (no fabricated personalization). - No case studies or metrics were referenced anywhere, since none were provided. - Ranking is a directional estimate based on copywriting principles (relevance, specificity, low pressure) — not backed by this account's actual open/reply data, since none was supplied. **Verification / compliance checks before sending:** - Confirm the RevOps-hire trigger data for each recipient is accurate and recently verified (avoid stale trigger data — nothing kills credibility faster than referencing a hire that left or a role that changed). - Confirm domain authentication (SPF/DKIM/DMARC) and sending reputation are in good standing before testing subject lines at volume. - Confirm applicable outreach/opt-out laws (e.g., CAN-SPAM, CASL, UK PECR, GDPR depending on recipient jurisdiction) and that a working opt-out path is included in the email body. **Single best next action:** A/B test subject line #13 ("Saw you brought on a RevOps lead") against #17 ("what your RevOps hire will find first") on a small, verified segment (Mode 12 — A/B Test Designer) before scaling to the full list, since these represent the two strongest distinct hypotheses — direct/trigger vs. curiosity/pain — for reply quality.