Building a PR Outreach Command Center with M365, SendGrid, and Resend
Summary
We rebuilt PR outreach around five pieces — tagged contacts and address lists, a template library, real connected mailboxes (Microsoft 365, SendGrid, Resend), a reply ledger with human approve/reject, and pending → sent → replied → followup tracking.
Quick answer
Classify contacts with type tags into reusable address lists, keep a template library, send through real connected mailboxes (Microsoft 365, SendGrid, Resend), scan every reply into a ledger for human approve/reject, and track status pending → sent → replied → followup. Never blind-send: pick a list and template, preview the real email, then confirm.
Our PR outreach used to live inside a personal mailbox. Contacts were a spreadsheet. Templates were copy-paste. Replies were something we checked by eye, when we remembered. One outreach round was enough to prove the setup did not scale — and that we were burning warm leads without knowing it.
Why personal-inbox outreach collapses
Running PR outreach from a personal mailbox has three structural problems. Contacts live in a static spreadsheet with no classification. Each email is hand-assembled, so quality and consistency drift. And replies arrive as unread-count noise — a warm reply from a journalist can sit buried under a newsletter for days. The pipeline leaks at every stage.
The command center: five pieces
We rebuilt outreach as a tracked operation. The core pieces:
- Contact classification. Every contact gets a type tag — media, PR vendor, startup media — and belongs to a reusable address list.
- A template library. Reusable subject and body templates: PR vendor inquiries, direct media pitches.
- Real connected mailboxes. Sending goes through Microsoft 365, SendGrid or Resend — real sender infrastructure, not a black-box relay.
- Reply scanning into a ledger. Every reply is captured with subject, preview and body, then reviewed one by one and approved or rejected.
- Status tracking. Contacts move pending → sent → replied → followup.
The rules that keep it safe
Three rules protect both reputation and results. First, never blind-send: pick an address list and a template, preview the actual email, then confirm before anything goes out. Second, every reply leaves a trace — warm leads do not die in a sent folder. Third, the sending infrastructure is real and auditable: it is our own mailbox and our own API keys, not an opaque relay we cannot inspect.
The reusable checklist
- Tag contacts and build address lists. Type tags make one list reusable across campaigns.
- Maintain a template library. Inquiry and pitch templates that stay consistent.
- Connect real mailboxes. M365, SendGrid or Resend — no black-box relays.
- Scan replies into a ledger. Subject, preview, body — each approved or rejected by a human.
- Track status and follow up. pending → sent → replied → followup, nothing left in the sent folder.
This command center is exactly what our email outreach automation module packages — contact lists, templates, connected mailboxes and a reply ledger with human review.
Frequently asked questions
Why is sending through connected mailboxes better than a relay?
A connected mailbox (M365, SendGrid, Resend) is real, identifiable sender infrastructure that you own and can audit. A black-box relay hides how and where mail is sent, which is risky for reputation and impossible to verify when deliverability drops.
What does the reply ledger actually do?
Replies are scanned from the mailbox with subject, preview and body, then each one moves through pending → approve or reject. Nothing sits unseen in an inbox, and a warm reply from a journalist surfaces in a workflow instead of being buried under newsletters.
When should a contact move to followup?
When a sent email goes unanswered for a reasonable window, or when a reply signals interest, the contact transitions to followup automatically. The rule is simple: a warm lead should never sit untouched in the sent folder.