Overview
Prospect outreach enrichment helps marketing and sales teams turn a raw account list into a weekly outreach table that is actually usable. This playbook checks contact routes, adds company context, and creates draft-ready email cues so the team can personalize faster without pretending every row is send-ready.
The output is a prospect outreach enrichment table with one row per account-contact pair. Each row can include the account, domain, contact, title, contact route, email status, evidence URL, company context, fit rationale, personalization cue, subject idea, opening line, recommended ask, priority, status, and next action.
Use it before a weekly outbound review, sales-assisted campaign, partner push, account-based experiment, or any moment when the team has a list but not enough confidence to write good emails. Juno separates ready prospects from missing contacts, weak fits, duplicates, and rows that need human review.
Why you should enrich outreach before drafting
Personalized outreach breaks when the research is fuzzy. A guessed email, vague company note, or copy-pasted opening line can make a decent prospect feel like spreadsheet confetti with a subject line attached.
This playbook puts the quality gate before the writing pass. Juno checks whether the account fits, whether the contact route is credible, whether the company context supports a reason to write, and whether the draft cue can be used without another research lap.
That discipline matters for both effectiveness and compliance. Google’s email sender guidelines emphasize respecting recipients’ inboxes and avoiding unwanted mail, while the FTC’s CAN-SPAM guide explains core rules for commercial email and opt-outs.
The practical win is a smaller, cleaner queue. Your outreach owner can see who is ready, what evidence supports the angle, which contacts need review, and where the list should be trimmed instead of padded.
Step-by-step
- 1Confirm the brand, offer, campaign goal, ideal customer profile, target buyer roles, exclusions, desired weekly queue size, and whether an existing outreach tracker should be updated.
- 2Normalize the supplied prospect list by reviewing account names, domains, contacts, roles, segments, source notes, prior status, and obvious duplicates.
- 3Set a practical acceptance bar covering account fit, truthful contact route, useful company context, and whether the row can support a draft-ready outreach cue.
- 4Enrich qualified prospects with the best available business contact route, preferring a named work email tied to the right person and company when that evidence exists.
- 5Capture company context that supports personalization, such as the relevant segment, trigger, likely business problem, and source-backed reason to write.
- 6Turn ready rows into concise outreach cues, including a subject idea, opening line, personalization note, and recommended ask, with placeholders where the sender must confirm a claim.
- 7Prioritize the weekly send queue by ICP fit, contact confidence, role relevance, personalization evidence, and urgency, then produce the table with a short summary of assumptions, reviewed rows, ready rows, rejection reasons, and gaps.
Frequently asked questions
What inputs do I need before running it?
Bring the prospect list, brand, offer, campaign goal, ideal customer profile, target buyer roles, exclusions, and any existing tracker. If the list is missing, Juno should ask for it before enrichment.
Does this write complete cold emails?
Not by default. The playbook creates draft-ready cues such as subject ideas, opening lines, personalization notes, and recommended asks. A marketer or sales owner still reviews the evidence and turns approved rows into final email copy.
What happens when contact data is weak?
Weak rows stay visible instead of being smuggled into the ready queue. Juno should label missing contacts, uncertain emails, weak-fit accounts, duplicates, rejected rows, and anything that needs review.
How often should we run it?
Weekly is the default, ideally before the team reviews the next outbound queue or prepares email drafts. On repeat runs, Juno updates the existing tracker, preserves prior statuses, refreshes near-term send candidates, and keeps old rejects from reappearing.
