Review & send
One row per contact. Ready letters first — open a row to read, edit or approve.
- 1 · You approve
- 2 · Sent from your mailbox
- 3 · Replies land in your inbox (interested ones alert you)
- 4 · No reply → follow-up here for approval
- 5 · They start from the link
Maya Okonkwo Head of RevOps Cobalt Forge Ready Cutting RevOps tooling sprawl at Cobalt Forge ✓ clear
Maya, saw your post on Cobalt Forge's RevOps tooling audit last quarter — 14 vendors down to 6 is rare to see land cleanly...
Fits the campaign and makes no claim we couldn't back up — clear to send.
Skip
Edit
Jordan Reyes VP RevOps Helix Robotics Read first Pipeline coverage question — Helix Robotics ! glance
Jordan, caught the Helix engineering blog post about pulling deal-stage data into your Linear workflows...
Held back: Second paragraph hedges twice ('curious whether', 'happy to share') — reads tentative for a VP-level recipient. Tighten before sending.
Skip
Edit
Sam Liu Director RevOps Pelican Health Ready RevOps tooling at Pelican Health ✓ clear
Sam, noticed Pelican Health is hiring its second Senior RevOps Analyst this quarter...
Fits the campaign and makes no claim we couldn't back up — clear to send.
Skip
Edit
Priya Mehta Head of Revenue Operations Mailroom Cloud Held back The '9-day build queue' figure does not appear in Priya's public materials — the worker invented a specific number. Sending an unbacked claim damages credibility. Rewrite with a verified detail or skip.
Priya, I see Mailroom raised the Series B in March — congratulations. We're working with three teams at your stage on the 'my BI dashboards now have a 9-day build queue' problem...
Held back: The '9-day build queue' figure does not appear in Priya's public materials — the worker invented a specific number. Sending an unbacked claim damages credibility. Rewrite with a verified detail or skip.