CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

synter/outbound-research

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.

Quality

98%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Overview
Quality
Evals
Security
Files
name:
outbound-research
description:
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.

Synter Outbound Research & Prospect Qualification

Find a checkable fact about the person, or do not mail them.

0. Finding & Enriching Prospects in Synter

Use Synter's native discovery and signal tools to find the right person and verified contact channels:

  1. Find Decision-Makers (company_intel_search_people / outbound_search_prospects):
    • Search by company domain, job function, seniority level (c_suite, vp, director), technology stack, or keyword query.
    • Returns matching people with their LinkedIn URLs, titles, companies, and enriched contact data.
  2. Enrich Emails, Phones & LinkedIn (enrich_contacts):
    • Pass any combination of LinkedIn URLs, work emails, or phone numbers to enrich_contacts to resolve verified work_email, personal emails, direct phone / phones, linkedin_url, job_title, and company.
  3. Check Company Signals (company_intel_get_signals / company_intel_get_profile):
    • Pull hiring velocity, open roles, tech stack changes, and firmographics to ground outreach in a verifiable fact.

The test

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.

1. Disqualifiers first — they veto, they do not score

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.

CheckBlocks because
In the CRM alreadyknown contact or open deal
We have already metcold copy insults someone whose call you attended
Current paying customerthey already buy from us
Contacted before, any channeldouble-touch reads as spam
Suppressed, bounced, unsubscribedlegal 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.

2. Positive signals — use the strongest you can actually fetch

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 send

Ranking rules:

  1. Recency beats strength within a tier. A reaction from yesterday beats an ad click from four weeks ago.
  2. Honour the decay windows. Opening with "I saw you engaged with my post" about something from March is worse than no personalization.
  3. Person-level beats company-level. "You clicked" is a fact. "Someone at your company visited" is an inference and must be written as one.

3. Land it without the AI tell

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:

  • "I hope this email finds you well"
  • "I noticed that..." / "I saw that you..." / "I came across your profile"
  • "As a {TITLE} at {COMPANY}, you probably..."
  • Em-dashes anywhere
  • The word "click" — Synter is prompt-driven; say "one prompt"

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 specifically

Keep 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.

4. Timing anchors

Send dayUseAvoid
Mon"kicking off the week""Happy Monday!" — the most-used cold-email opener there is; it signals bulk mail instantly
Tue-Wednothing, these are the best daysforcing an anchor
Thu"before this week gets away"
Fri"Before the weekend,"asking for a call today
Sat-Sundo 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.

5. Seasonal and fiscal

Read from their calendar, not ours. For a DTC brand in October the anchor is peak retail season, not our quarter.

  • Jan new budget, planning reopens · Feb-Mar Q1 under pressure
  • Apr-Jun mid-year reforecast · Jul-Aug thin teams, keep asks small
  • Sep everyone back, strongest window of the year
  • Oct-Nov Q4 planning, next-year budget locking, retail peak
  • Dec do not start sequences after the second week

6. Life events — the strongest human hook

EventWindowAngle
New rolefirst 90 days, the best window there ischoosing a stack, wants early wins
Promotion60 daysscope grew, budget grew
Funding90 dayspressure to deploy into growth
Team growth60 dayshiring 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..."
Workspace
synter
Visibility
Public
Created
Last updated
Source
CLI
Repository
No repository linked. Set repository in the plugin manifest, or publish from a GitHub Action to verify it.
Badge
synter/outbound-research badge