pain-identifier

Identify and prioritize B2B pain points from hiring, funding, and tech stack signals.

277|88|Updated Jan 4, 2026
One-click install
npx skills add https://github.com/Othmane-Khadri/YALC-the-GTM-operating-system --skill pain-identifier
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pain-identifier
Source: https://github.com/Othmane-Khadri/YALC-the-GTM-operating-system/tree/main/.claude/skills/lemlist/pain-identifier
Command: npx skills add https://github.com/Othmane-Khadri/YALC-the-GTM-operating-system --skill pain-identifier

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you identify and prioritize likely B2B pain points for a specific target company using observable growth and operational signals, so your outreach and lead qualification are relevant rather than generic.

Core Features & Use Cases

  • Company profiling from signals: Builds an industry, size, stage, and messaging context from sources like LinkedIn, the website, and commonly referenced business data.
  • Signal-to-pain mapping: Translates hiring patterns, funding timing, tech stack indicators, and expansion/product milestones into concrete, role-relevant pain hypotheses.
  • Prioritized pain ranking: Scores each inferred pain using severity, evidence strength, solution fit, and urgency, then outputs a clear outreach strategy tied to the top pain.

Quick Start

Use pain-identifier for a specific company URL by asking it to “identify and prioritize [Company]’s evidence-based pain points for [your solution].”

Frequently Asked Questions about pain-identifier

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I identify B2B pain points from hiring signals and tech stack data?

B2B pain point identification analyzes observable signals like hiring patterns, funding timing, and tech stack indicators to infer role-relevant pain hypotheses for a target company. It translates these growth and operational signals into concrete business problems.

What is signal-to-pain mapping for lead qualification?

Signal-to-pain mapping translates observable company events, hiring trends, and tech stack indicators into prioritized, role-relevant pain hypotheses. It scores inferred pains using severity, evidence strength, solution fit, and urgency to improve lead qualification relevance.

How do I personalize B2B outreach using evidence-based account research?

Personalizing B2B outreach requires prioritizing evidence-based pain points from account research to frame your messaging. It uses a scoring model driven by hiring, funding, and tech stack signals to generate targeted discovery questions and outreach strategies.

Can I use observable company signals to generate discovery questions for sales outreach?

Observable company signals like expansion milestones, hiring patterns, and tech stack indicators can be mapped to specific B2B pain points. This mapping generates relevant discovery questions and outreach personalization tied to the target's highest-priority pain.

What B2B data do I need to prioritize evidence-based pain points for a target account?

Prioritizing evidence-based pain points requires structured input including the target company URL, your proposed solution, and known observable signals. These inputs feed a signal-to-pain scoring model driven by hiring, funding, tech stack, and company events.

When should I use signal-driven pain point analysis instead of generic account research?

Signal-driven pain point analysis is used when lead qualification needs evidence-based relevance rather than generic outreach. It applies specifically to B2B scenarios requiring prioritized pain hypotheses generated from observable hiring, funding, and tech stack indicators.