Discover and qualify prospects in Synter before writing cold outreach — find people and verified contact info (emails, phone numbers, LinkedIn URLs), verify a checkable fact from first-party signals, rank competing signals, and land it in the email without sounding AI-generated. Use when finding prospects or leads, building or topping up an outbound list or lead list, writing a first-touch cold email to a researched prospect, or deciding whether someone should be contacted at all.
98%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Find a checkable fact about the person, or do not mail them.
Use Synter's native discovery and signal tools to find the right person and verified contact channels:
company_intel_search_people / outbound_search_prospects):
c_suite, vp, director), technology stack, or keyword query.enrich_contacts):
enrich_contacts to resolve verified work_email, personal emails, direct phone / phones, linkedin_url, job_title, and company.company_intel_get_signals / company_intel_get_profile):
For one real lead on the list, ask: if they replied "where did you get my information?", what would I say?
If the honest answer is "you match an industry and a job title," the research is not done. Cut the cohort rather than send it. That question is not hypothetical — it is a verbatim reply from a real campaign that mailed 750 people a character-identical email.
Check these before any positive research (query_crm_pipeline, query_attio, get_crm_contacts). One hit stops the send, no matter how strong the positives.
| Check | Blocks because |
|---|---|
| In the CRM already | known contact or open deal |
| We have already met | cold copy insults someone whose call you attended |
| Current paying customer | they already buy from us |
| Contacted before, any channel | double-touch reads as spam |
| Suppressed, bounced, unsubscribed | legal and deliverability |
A lapsed customer is the deliberate exception: a win-back target, and a strong one. Say so plainly rather than pretending it is a cold approach.
One fact per email. Never stack them.
they clicked our ad ............... strongest 30 day window
they used the product ............ very strong 45 day window
they engaged our social post ..... strong 60 day window (comment > reaction)
someone at their company visited . moderate 30 day window (company-level only)
new role, promotion, funding ..... strong 90 day window
role + industry only ............. NOT A SIGNAL — do not sendRanking rules:
Never name the surveillance. The fact goes in, the mechanism stays out.
BAD "I noticed you visited our pricing page on Tuesday."
BAD "Our system flagged that you clicked one of our ads."
GOOD "Your take on the PMax thread stuck with me."
GOOD "You were looking at programmatic pricing recently, so this may be timely."The test: would the sentence be creepy said aloud at a conference? If yes, reference the topic, not the event.
Banned openers — the tells that read as generated:
Shape of the opening:
line 1 timing or season anchor, short and human
line 2 the fact, stated as theirs not ours
line 3 why it matters to them specificallyKeep the fact out of line 1. Leading with it is what makes it feel like a merge field. A human beat first, then specificity, is what makes it feel written. Body under 90 words.
| Send day | Use | Avoid |
|---|---|---|
| Mon | "kicking off the week" | "Happy Monday!" — the most-used cold-email opener there is; it signals bulk mail instantly |
| Tue-Wed | nothing, these are the best days | forcing an anchor |
| Thu | "before this week gets away" | |
| Fri | "Before the weekend," | asking for a call today |
| Sat-Sun | do not send cold |
Rotate anchors across a cohort — the same one on every email is its own tell. And only use a day anchor if the schedule actually matches it; "before the weekend" landing on Tuesday is worse than nothing.
Read from their calendar, not ours. For a DTC brand in October the anchor is peak retail season, not our quarter.
| Event | Window | Angle |
|---|---|---|
| New role | first 90 days, the best window there is | choosing a stack, wants early wins |
| Promotion | 60 days | scope grew, budget grew |
| Funding | 90 days | pressure to deploy into growth |
| Team growth | 60 days | hiring paid roles means scaling spend |
Congratulate in one clause, then get to the substance. A paragraph about their promotion is transparently a device.
GOOD "Three weeks into the growth seat - you're probably still
picking what the paid stack looks like."
BAD "Congratulations on your well-deserved promotion! It's always
exciting to see talented leaders like yourself step into..."