account-research-brief
Use when preparing to engage a target account, researching a company before outreach, or building pre-call intelligence. Triggers: 'research this company', 'account brief for [company]', 'company research', 'what do I need to know about [company]', 'pre-outreach research'.
git clone --depth 1 https://github.com/Othmane-Khadri/gtm-engineer-playbook /tmp/account-research-brief && cp -r /tmp/account-research-brief/.claude/skills/gtm-playbook/account-research-brief ~/.claude/skills/account-research-briefSKILL.md
# Account Research Brief
Produce a comprehensive 1-page company intelligence brief in 2-3 minutes using WebSearch. Everything a GTM engineer needs to engage a target account — from company overview to ready-to-use outreach angles.
## Steps
### 1. Collect Input
Ask the user for:
- **Company name** (required)
- **Your product/service** (optional) — if provided, engagement angles will be tailored to the user's offering. If omitted, angles stay generic but actionable.
- **Target persona title** (optional) — focuses the Decision Makers section on that role. Default to CRO / VP Sales / Head of Growth if not specified.
Do NOT proceed until you have at least the company name.
### 2. Company Overview
Run 1-2 WebSearch queries (e.g., `"{company} what does it do"`, `"{company} funding crunchbase"`).
Gather:
- What they do (one paragraph, plain language)
- Founded year and HQ location
- Company size — employee count, revenue range if public
- Funding stage and total raised (for startups / private companies)
- Key product(s) or service(s)
- Recent news from the last 90 days (1-3 headlines with URLs)
If any data point is not findable, write "Not found" — NEVER fabricate company data.
### 3. Decision Makers
Run 1-2 WebSearch queries (e.g., `"{company} CEO founder"`, `"{company} {target persona title}"`).
Gather:
- CEO / Founder — name, short background (prior companies, notable achievements)
- Target persona — name and title of the person matching the user's specified role (or CRO / VP Sales / Head of Growth by default)
- LinkedIn activity themes — what topics they post or comment about (if findable)
- Recent public content — podcast appearances, conference talks, blog posts, tweets
- Org structure clues — approximate size of their sales / marketing / growth team (from LinkedIn headcount or job postings)
### 4. Technology Stack
Run 1-2 WebSearch queries (e.g., `"{company} tech stack job postings"`, `"{company} integrations partners"`).
Gather:
- CRM platform (Salesforce, HubSpot, etc.)
- Marketing automation (Marketo, Pardot, HubSpot, etc.)
- Outreach / sales engagement tools (Outreach, Salesloft, Apollo, etc.)
- Other known tools from job postings, integrations pages, G2 profiles, case studies
- Stack gaps — if the user provided their product/service, note where their product could fit
### 5. Recent Signals
Run 1-2 WebSearch queries (e.g., `"{company} news 2026"`, `"{company} hiring jobs"`).
Gather and present as a table:
| Signal | Detail | Date | Source |
|--------|--------|------|--------|
Signal types to look for:
- Fundraise announcements
- Hiring patterns (what roles are they adding? volume?)
- Product launches or major feature releases
- Partnership announcements
- Press mentions or media coverage
- Leadership changes (new C-suite, VP hires)
**ICP cross-reference:** If `docs/icp.md` exists in the project, read it and cross-reference the signals above against the ICP's buying signal list. Flag any matches explicitly (e.g., "MATCH: ICP buying signal 'Series B+ fundraise' — Company raised Series C in Jan 2026").
### 6. Competitive Landscape
Run 1-2 WebSearch queries (e.g., `"{company} competitors"`, `"{company} vs alternatives"`).
Gather:
- 3-5 main competitors
- How the target company positions itself vs. competitors (messaging, pricing tier, feature differentiation)
- Recent competitive moves — pricing changes, feature launches, market entries
- Market dynamics that affect them (regulation, consolidation, shifts in buyer behavior)
### 7. Engagement Angles
Based on ALL findings from steps 2-6, generate 3-5 outreach angles.
Each angle must include:
1. **Angle name** — a short label (e.g., "Hiring Surge Play", "Stack Gap Angle")
2. **Finding** — the specific research finding that makes this angle relevant
3. **Value connection** — how this finding connects to a pain point or opportunity
4. **One-sentence opener** — a ready-to-send first line for email, LinkedIn, or cold call
Rules:
- If the user provided their product/service, make every angle specific to their offering.
- If they did not, keep angles generic but grounded in the research (never vague).
- Each angle must tie to a SPECIFIC finding, not a generic observation.
### 8. Write the Brief
Write the output file to `docs/accounts/{company-name-slug}.md`.
The slug is the company name lowercased with spaces replaced by hyphens and special characters removed (e.g., "HubSpot" becomes `hubspot`, "Scale AI" becomes `scale-ai`).
Create the `docs/accounts/` directory if it does not exist.
Use this structure for the output file:
```markdown
# {Company Name} — Account Research Brief
**Website:** {url}
**HQ:** {location}
**Researched:** {YYYY-MM-DD}
---
## Company Overview
{One paragraph on what they do, key products/services}
- **Founded:** {year}
- **Employees:** {count or range}
- **Revenue:** {range or "Private"}
- **Funding:** {stage, total raised, last round date}
### Recent News
- {headline} — {source} ({date})
- ...
---
## Decision Makers
**CEO / Founder:** {name}
- {background, 1-2 sentences}
**{Target Persona Title}:** {name, if found}
- {background, activity themes, recent content}
**Team Size Clues:** {what's known about sales/marketing/growth org size}
---
## Tech Stack
| Category | Tool(s) |
|----------|---------|
| CRM | {tool} |
| Marketing Automation | {tool} |
| Sales Engagement | {tool} |
| Other | {tools} |
{If user provided their product: "**Stack Gap:** {where your product fits}"}
---
## Recent Signals
| Signal | Detail | Date | Source |
|--------|--------|------|--------|
| {type} | {detail} | {date} | [{source}]({url}) |
| ... | ... | ... | ... |
{If ICP cross-reference was done: "**ICP Signal Matches:** {list matches}"}
---
## Competitive Landscape
**Main Competitors:** {list}
**Positioning:** {how they differentiate}
**Recent Competitive Moves:** {notable shifts}
**Market Context:** {dynamics affecting them}
---
## Engagement Angles
1. **{Angle Name}**
- *Use when designing an autonomous agent, planning agent architecture, building a scheduled automation, or creating a Claude Code agent workflow. Triggers: 'design an agent', 'build an automation', 'agent architecture', 'automate this workflow', 'create a scheduled agent', 'shell script agent'.
Use when analyzing competitors, creating sales battlecards, building competitive positioning, preparing for competitive deals, or updating competitive intelligence. Triggers: 'battlecard for [competitor]', 'competitive analysis of [competitor]', 'how do we beat [competitor]', 'compare us to [competitor]', 'competitive intel', 'win against [competitor]'.
Use when auditing CRM data quality, finding duplicate records, identifying stale leads, cleaning pipeline data, or improving data hygiene. Triggers: 'clean my CRM', 'audit CRM data', 'find duplicates', 'CRM hygiene', 'data quality check', 'stale leads', 'pipeline cleanup'.
Use when building or refining an Ideal Customer Profile (ICP), defining target personas, mapping buyer psychographics, or discovering where prospects gather online. Triggers: 'build my ICP', 'define target customer', 'who should I sell to', 'refine ICP', 'persona mapping'.
Use when preparing for a sales meeting, discovery call, demo, or customer check-in. Triggers: 'prep me for a meeting with [company]', 'meeting brief for [company]', 'pre-call prep', 'I have a call with [contact] at [company]', 'meeting prep', 'call prep'.
Use when creating outreach sequences, writing cold email campaigns, building multi-channel cadences, designing follow-up flows, or crafting signal-triggered messages. Triggers: 'build an outreach sequence', 'write a cold email sequence', 'create a cadence', 'outreach for [signal]', 'email sequence', 'follow-up sequence', 'multi-channel outreach'.
Use when scoring leads, qualifying prospects, prioritizing pipeline, deciding which accounts to pursue, or building a lead scoring model. Triggers: 'score this lead', 'qualify this prospect', 'is this a good lead', 'lead scoring', 'prioritize my pipeline', 'qualification framework'.
Use when searching for buying signals, detecting intent data, scoring prospect readiness, or monitoring accounts for trigger events. Triggers: 'scan for signals', 'find buying signals', 'who is ready to buy', 'intent signals', 'signal scoring', 'account signals'.