Agent skill
pain-qualified-segment
Build segments based on tension heuristics that indicate active pain points, not just firmographics
Filed under Prospecting and list building.
From jurjen-gtm-engineer/gtmskills · 55 skill entries · 0 · pushed 2026-10-04
What it does when it runs
Build segments based on tension heuristics that indicate active pain points, not just firmographics
Automated analysis of the skill and the 0 files bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.
- Keys and connectors you must supply
- None found.
- Hosts it reaches
- blueprintgtm.com
- Tool permissions it declares
- No
allowed-toolsin the frontmatter. It only issues instructions, so there is nothing to bound. - Actions present in the files
- None. Instructions only.
Install it
View source on GitHub ↗git clone --depth 1 --filter=blob:none --sparse https://github.com/jurjen-gtm-engineer/gtmskills.git /tmp/gtmskills git -C /tmp/gtmskills sparse-checkout set "skills/pain-qualified-segment" mkdir -p ~/.claude/skills/pain-qualified-segment cp -R "/tmp/gtmskills/skills/pain-qualified-segment/." ~/.claude/skills/pain-qualified-segment/
Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗
The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.
The skill
Source on GitHub ↗Reproduced in full from jurjen-gtm-engineer/gtmskills/blob/77dc0b3112dbf6cf906dfc3d526b6f7031bf964c/skills/pain-qualified-segment/SKILL.md, which is licensed MIT (repository). 786 words, 13 headings.
Pain Qualified Segment
You are building segments based on "tension heuristics" - data points that indicate a prospect is experiencing active pain, not just matching firmographic criteria.
Core Concept
Identify your best performing segment, not just by revenue bracket, but by nuanced, calculated data (e.g., specific tech usage, personnel ratios, unique business pain-points).
Traditional ICP: "Companies with 500+ employees in Finance" Pain Qualified: "Companies with 500+ employees in Finance that just lost their CISO and have 3+ compliance job postings"
Input
User provides:
- Target ICP or segment criteria
- Pain points your solution addresses
- Optionally: customer data to analyze
Process
-
Identify Tension Indicators
Prompt Pattern:
For this ICP: [DESCRIPTION] And this pain point: [PAIN] What 2-5 measurable or inferable signals would indicate this pain is ACTIVE right now? Consider: - Personnel ratios (e.g., sales engineers vs total staff) - Recent changes (funding + hiring freeze, leadership departure) - External pressures (regulatory deadline, competitive threat) - Capability gaps (job postings for roles they lack, tech stack gaps) - Timing factors (end of quarter, budget cycle, contract renewal) -
Define the Segment
Structure:
Segment Name: [Descriptive name] Base ICP: - [Firmographic criteria] Tension Heuristics (2-5): 1. [Signal] - indicates [pain] 2. [Signal] - indicates [pain] 3. [Signal] - indicates [pain] Data Sources to Detect: - [Signal 1]: [How to find/measure] - [Signal 2]: [How to find/measure] -
Output Format
## Pain Qualified Segment: [Name] ### Why This Segment The combination of [base criteria] + [tension signals] indicates: - The problem is acute right now - External pressure is forcing change - Timing is favorable for a solution ### Definition **Base Criteria:** - [Firmographic 1] - [Firmographic 2] **Tension Heuristics:** | Signal | What It Indicates | How to Detect | |--------|-------------------|---------------| | [Signal 1] | [Pain indicator] | [Data source] | | [Signal 2] | [Pain indicator] | [Data source] | ### The List Is the Message (Jordan Crawford's phrase) Because you know WHY they're on this list: - Messaging writes itself - Personalization is substantive, not cosmetic - "Why you, why now" is obvious **Outreach Angle:** "[We noticed/Given that] [tension signal], [companies like yours/you might be] [experiencing pain]. [Value prop]..." ### Detection Workflow 1. Start with [base criteria] filter 2. Enrich with [data needed for tension signals] 3. Score/flag where [X of Y tension signals] present 4. Route high-tension accounts to immediate outreach
Examples
Input: "We sell security compliance software. ICP is mid-market SaaS companies."
Output:
## Pain Qualified Segment: Compliance-Pressured SaaS
### Why This Segment
Companies facing compliance pressure with capability gaps:
- Regulatory or customer pressure is forcing action
- They lack internal expertise to handle it
- Timing is urgent (audits, renewals, enterprise deals)
### Definition
**Base Criteria:**
- SaaS company
- 100-1000 employees
- B2B (enterprise customers likely)
**Tension Heuristics:**
| Signal | What It Indicates | How to Detect |
|--------|-------------------|---------------|
| No CISO or security leader | Capability gap | LinkedIn search, org chart |
| "SOC 2" in job postings | Active compliance initiative | Job board scraping |
| Enterprise customer logos | Compliance requirements from customers | Website analysis |
| Recent Series B+ | Pressure to professionalize | Funding data |
| Security vendor on their stack | Already investing, may need more | Technographic data |
### The List Is the Message (Jordan Crawford's phrase)
**Outreach Angle:**
"I noticed you're hiring for security roles and have enterprise customers like [Customer], compliance requirements can be overwhelming when you're scaling. We help SaaS companies get SOC 2 ready without hiring a full security team..."
### Detection Workflow
1. Filter: SaaS, 100-1000 employees, B2B
2. Enrich: Job postings, customer logos, funding, tech stack
3. Score: 3+ tension signals = high priority
4. Route: High-tension to AE, others to nurture
Key Principles
-
Tension > Firmographics: A small company with acute pain beats a perfect-fit company with no urgency
-
Measurable Signals: If you can't detect it, you can't target it
-
The "Why" Drives Messaging: Knowing why they're on the list makes personalization substantive
-
Dynamic, Not Static: Tension changes, signals should trigger re-evaluation
Related Skills
/data-point-research- Find the data to detect tension/company-goals- Job postings reveal priorities/recent-news- Events that create tension/role-focus- Who feels the pain
Credits
Pain-qualified segments, tension heuristics and "the list is the message" are Jordan Crawford (Blueprint GTM)'s concepts. The prompts and wording here are ours.
Examples are illustrative. Company names, prices and numbers in them are placeholders or may be out of date, so check the live source before you rely on any detail.
Other skills for the same job
Different authors, same problem. Matched on the words in the skill name, across every library in the catalogue except this one.
- linkedin-job-post-to-buyer-pain-map by Varnan-Tech · 672
- pain-identifier by Othmane-Khadri · 317
- find-qualified-titles by getaero-io · 64
- pain-finder by zime-ai · 17
- gtm-segment by getbeton · 6
- pain-language-engagers by edupegoretti · 0
- get-qualified-leads-from-luma by edupegoretti · 0
- beachhead-segment by drevon-dev · 0
Need help setting it up?
This page tells you what pain-qualified-segment does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.
Book a call →The directory stays free. There is nothing gated behind this.