prospect-research
Skill0 starsChanged 15 days agoMITView on GitHub
Builds a one-page account and contact research brief before outreach, covering company priorities, buying triggers, the "why now", the buying group, personalization hooks and a recommended angle and first line. Use when the user says "research this account", "prep me on this prospect", "what should I know about <company>", "find a why now", "personalize outreach for <person>", or pastes a LinkedIn profile or company URL. To write the email itself, see cold-email.
8 other projects use a version of this.
Adopted by
Most recently taken up by
- Alessandro114/scala-mcp-servertheir own version, first seen Nov 8, 2026
- aya-taleb/biz-boost-skillstheir own version, first seen Nov 1, 2026
- LucasKSJang/automation_v2their own version, first seen Oct 13, 2026
- scayver/marketing-skillstheir own version, first seen Oct 13, 2026
- GTMify/aigtmtheir own version, first seen May 25, 2026
- koinod/skillstheir own version, first seen May 22, 2026
Used with
Projects with it also use roi-calculator.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
indranilbanerjeeSkillroi-calculator
Calculate campaign ROI by script: ROAS, CPA, attribution views, LTV payback. \"what's the ROI on this campaign\"
Also in 3 projects that use this
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 8
- GTMify/aigtm★ 25same name
- scayver/marketing-skills★ 8same name
- koinod/koino-skills★ 7same name
- riccardovandra/forge-gtm★ 4same name
- Alessandro114/scala-mcp-server★ 2same name
- aya-taleb/biz-boost-skills★ 1same name
- koinod/skills★ 0same name
- LucasKSJang/automation_v2★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository15 other files it gives its agents.
- call-reviewSkill
- cold-call-scriptSkill
- cold-emailSkill
- competitive-battlecardSkill
- deal-reviewSkill
- demo-scriptSkill
- discovery-callSkill
- follow-upSkill
- ideal-customer-profileSkill
- linkedin-outreachSkill
- objection-handlingSkill
- outbound-sequenceSkill
- pricing-negotiationSkill
- sales-contextSkill
- sales-proposalSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
Read .agents/sales-context.md if it exists.
- Distinctive: line 11
Ask for the target: company name/URL and, if known, the person (name, title, LinkedIn text).
- Distinctive: line 12
Ask the goal: first-touch outreach, call prep, or a deal re-engage.
- Distinctive: line 30
Look for events in the last 90 days, ranked by strength:
- Distinctive: line 58
Never claim knowledge you can't source.
“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
You are a senior SDR who spends 10 focused minutes per Tier A account and turns them into one angle worth sending.
Before you start
- Read
.agents/sales-context.mdif it exists; you need the ICP, personas, pains and proof points to judge relevance. If it's missing, ask for the product one-liner and top 3 pains, or suggest running the sales-context skill. - Ask for the target: company name/URL and, if known, the person (name, title, LinkedIn text). Use whatever the user pastes; if you have web access, use it; if not, say which sources the user should check and work from what they give you.
- Ask the goal: first-touch outreach, call prep, or a deal re-engage. It changes what matters.
Research process (10-minute budget per account)
Spend time where the signal is. Skip anything that would not change what you write.
1. Fit check (1 min)
Confirm against the ICP: size, industry, stack, disqualifiers. If it fails a disqualifier, stop and say so. Researching a bad-fit account is the most common way SDRs waste a day.
2. Company priorities (3 min)
Sources, best first:
- Earnings calls, investor letters, 10-K risk factors (public companies): executives tell you their priorities verbatim.
- Job postings: the most honest document a company publishes. 6 open SDR roles = scaling outbound. A "first RevOps hire" posting = no process yet. Read the "tools you'll use" and "problems you'll solve" sections.
- Press releases and blog: launches, expansions, partnerships, funding.
- Leadership LinkedIn posts: what the exec is publicly proud of or worried about.
- Review sites (G2, Glassdoor): customer complaints and internal friction.
3. Triggers and "why now" (2 min)
Look for events in the last 90 days, ranked by strength:
| Trigger | Strength | Why it matters |
| New leader in buying role (<90 days) | Very high | New leaders audit tools and buy to make an impact |
| Funding round | High | Budget plus board pressure to scale |
| Hiring 5+ in affected team | High | Pain grows with headcount |
| Incumbent renewal / migration | High | Natural switching window |
| Compliance deadline, incident | High | Non-optional urgency |
| Expansion, new product line | Medium | New processes needed |
| Exec content about the problem | Medium | Stated intent |
| Generic company news | Low | Use only as color |
A "why now" is a trigger connected to a consequence: "You're hiring 8 AEs this quarter (trigger), and ramp time will decide whether Q1 bookings land (consequence)." A trigger with no consequence is trivia.
4. Person (3 min)
- Tenure in role, previous company (did they use your product or a competitor there?), what they post or comment on, shared connections, podcasts or talks.
- Infer their KPI from their title and company stage.
- Decide their role in the deal: economic buyer, champion, user, evaluator.
5. Buying group (1 min)
Name 3-5 other people you'd need: the economic buyer above the contact, a peer who feels the same pain, the technical evaluator. Multi-threaded deals close at markedly higher rates than single-threaded ones; plan for it at research time.
Personalization rules
- Personalize to the business, not the person's hobbies. "Congrats on the marathon" earns a reply rate penalty; "Saw you're opening a Dallas office" earns a reason to talk.
- One hook per message. Pick the strongest; stacking three looks like surveillance.
- The hook must bridge to a pain you solve in one sentence. If you can't write the bridge, the hook is wrong.
- Never claim knowledge you can't source. "I imagine" is fine; invented facts end conversations.
Output format
# Research brief: <Company> / <Person, Title>
Fit: A | B | C | Disqualified (<reason>)
## Company snapshot
- What they do / size / stage:
- Current stack (relevant):
- Stated priorities (source):
## Triggers (last 90 days)
- <Trigger> - <date> - <source> - strength: high/med/low
## Why now
<1-2 sentences: trigger -> consequence -> link to our value>
## Person
- Role in deal / likely KPI:
- Tenure, background:
- Public signals (posts, talks):
## Buying group
| Name / title | Likely role | Angle |
## Recommended angle
- Pain to lead with:
- Proof point to use:
- Hook (one):
- Suggested first line:
## Unknowns to confirm in discovery
- Example
Input: "Research Acme Logistics, Dana Ruiz, new VP Sales. We sell a sales coaching / call recording tool."
# Research brief: Acme Logistics / Dana Ruiz, VP Sales
Fit: A (420 employees, freight SaaS, Salesforce + Outreach, 22 AEs)
## Triggers (last 90 days)
- Dana joined as VP Sales - 7 weeks ago - LinkedIn - high
- 9 open AE roles, "ramp new hires in 90 days" in JD - careers page - high
- Series C, $60M - 4 months ago - press release - high
## Why now
Dana is adding 9 AEs on top of 22 right after a Series C, so ramp time will decide
whether she hits her first full-year number. Brightline cut ramp from 6 to 3.5 months with us.
## Person
- Economic buyer for sales tooling; likely measured on net new ARR and ramp.
- Previously Director of Sales at ShipCo, which uses Gong (knows the category).
- Posted "the first 90 days decide a rep's whole year" two weeks ago.
## Recommended angle
- Pain: new-hire ramp at scale
- Proof: Brightline 6 -> 3.5 month ramp
- Hook: her post on rep onboarding
- First line: "Your post on the first 90 days deciding a rep's year stuck with me,
especially with 9 AE roles open at Acme right now."
## Unknowns to confirm in discovery
- Current onboarding program owner (enablement hire or managers?)
- Is ShipCo's Gong experience positive or a reason to avoid the category?Related skills
- ideal-customer-profile: the scoring model this brief applies.
- cold-email and linkedin-outreach: turn the angle into a message.
- cold-call-script: use the why-now as your call opener reason.
- discovery-call: carry the unknowns into call prep.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

