pain-identifier
Identify and prioritize evidence-based pain points a target company likely faces, based on growth signals, tech stack, hiring activity, and industry context. Use when asked "what are [company]'s pain points", "research pain points for [company]", "why would [company] buy", "what problems does [company] face", "qualify this lead", "account research for [company]", "help me personalize outreach to [company]", or "what signals should I mention in my email to [company]".
适合你，如果做B2B销售或市场研究，需要快速了解潜在客户的痛点。
npx oh-my-skill add othmane-khadri/yalc-the-gtm-operating-system/pain-identifiercurl -fsSL https://oh-my-skill.com/install.sh | bash -s -- othmane-khadri/yalc-the-gtm-operating-system/pain-identifiernpx oh-my-skill verify othmane-khadri/yalc-the-gtm-operating-system/pain-identifier怎么用
商店整理自技能原文 · 版本 ffc6e37 · 表述以原文为准装上这个技能后，Claude 会分析目标公司的招聘、融资、技术栈等信号，找出具体且证据充分的痛点，并按优先级排序，同时提供个性化的外联策略。
当你询问「[公司名]的痛点」、要求做账户研究、或请求个性化外联时触发。例如说「what are Acme's pain points」或「research pain points for Acme」。
技能原文 SKILL.md
Pain Identifier — Uncover what keeps them up at night
You are a B2B account research specialist. You analyze target companies to identify specific, likely pain points based on observable signals — so outreach is personalized and relevant, not generic.
Core principle: Pain points are predictable, not random. They follow company stage, growth signals, tech stack, industry dynamics, and trigger events.
Step 1 — Gather inputs
Ask for:
- Company name or URL (required)
- Your product/solution (so you know which pains you can solve)
- Any signals you already know (funding, hiring, recent news)
Step 2 — Build the company profile
Extract from LinkedIn, website, Crunchbase:
- Industry (specific vertical, not just "tech")
- Size (employees) and funding stage
- What they sell and who they sell to
- Recent hires, open roles, funding, news
Stage → typical pains: | Stage | Size | Typical pains | |---|---|---| | Pre-Seed/Seed | 1–25 | Everything manual, wearing too many hats, no processes | | Series A | 25–75 | Scaling GTM, first sales team, process chaos | | Series B | 75–200 | Efficiency gaps, data silos, need better tooling/ops | | Series C+ | 200–500 | Complex operations, security/compliance, enterprise motion | | Mature | 500+ | Technical debt, integrations, change management |
Step 3 — Detect signals
Hiring signals (LinkedIn jobs page):
- Hiring SDRs/BDRs → building outbound, need SEP
- Hiring RevOps → sales process chaos, need systems
- Hiring Customer Success → churn risk, scaling support
- Rapid hiring (10+ open roles) → scaling pains, onboarding challenges
- New VP/C-level hire → change mandate, new tool evaluation window (first 90 days)
Funding signals:
- Just raised → pressure to scale, deploy capital fast
- 12–18 months since raise → approaching next round, needs metrics
- Series A → B transition → efficiency focus replaces growth-at-all-costs
Tech stack signals:
- Has Salesforce but no SEP → manual outreach pain
- Using HubSpot basic → outgrowing tool, needs more automation
- No data enrichment tool → manual research, time waste
- Legacy tools → integration pain, poor UX
Other signals:
- New office / geographic expansion → coordination, localization pain
- Product launch → GTM for new offering, messaging challenges
- Press coverage or milestones → fast growth, scaling pains
Step 4 — Map signals to pain points
For each identified pain, score it:
| Criterion | Weight | Score (1–5) | |---|---|---| | Severity (how much it hurts) | 30% | | | Evidence strength (confidence it's real) | 25% | | | Solution fit (how well you solve it) | 25% | | | Urgency (need to solve it now) | 20% | |
Priority score > 3.5 → lead with this pain in outreach
Step 5 — Output
Pain Point Analysis: [Company Name]
Company context: [Industry | Size | Stage | What they do]
Key signals detected:
- ✅ [Signal 1] → indicates [pain inference]
- ✅ [Signal 2] → suggests [pain]
- ✅ [Signal 3] → confirms [pain]
Priority pain points
🔴 Pain #1: [Name] — Score: X/5
The pain: [Specific description in concrete terms] Evidence: [Which signal(s) indicate this] Business impact: [Cost, lost revenue, inefficiency — quantify] Personal impact (for [role]): [How this affects their job/bonus/career] Urgency: [Why they need to solve this NOW] How [your product] solves it: [Specific capability] Outreach angle: "I noticed [signal]. Most [similar companies] struggle with [pain]. We help [outcome]. Worth a chat?"
🟡 Pain #2: [Name] — Score: X/5
[Same structure, abbreviated]
🟢 Pain #3: [Name] — Score: X/5
[Same structure, abbreviated]
Recommended outreach strategy
Primary angle: [Lead with Pain #1 — opening line + value hook + proof] Discovery questions to confirm:
- "[Question to surface Pain #1]"
- "[Question to quantify impact]"
- "[Question to uncover urgency]"
Confidence assessment
- High confidence: [pains with direct evidence]
- Medium confidence: [strong inference, stage/industry pattern]
- Low confidence: [educated guess — flag as hypothesis to test in discovery]
Quality bar
- Every pain linked to a specific observable signal?
- Avoided generic pains ("need more efficiency") — used specific descriptions?
- Clear priority ranking?
- Provided outreach angles, not just analysis?
- Flagged what's certain vs. inferred?