Agent skill
gtm-account-qualification
Scores accounts against ICP definitions using 8 weighted criteria, assesses qualification zone alignment, and delivers GREENLIGHT/MANUAL REVIEW/DISQUALIFY verdict
Filed under Calls, demos and discovery.
From rvanshur/vertical-gtm-skills · 29 skill entries · 2 · pushed 2026-09-30
What it does when it runs
Scores accounts against ICP definitions using 8 weighted criteria, assesses qualification zone alignment, and delivers GREENLIGHT/MANUAL REVIEW/DISQUALIFY verdict
Automated analysis of the skill and the 1 file 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
- No third-party host appears in the skill or its bundled files.
- Tool permissions it declares
- No
allowed-toolsin the frontmatter. It does act, so it runs under whatever permissions your session already grants. - Actions present in the files
- writes files
Ask about gtm-account-qualification
Opens your assistant with this page's recorded context. Check the linked sources before relying on it.
Install it
View source on GitHub ↗git clone --depth 1 --filter=blob:none --sparse https://github.com/rvanshur/vertical-gtm-skills.git /tmp/vertical-gtm-skills git -C /tmp/vertical-gtm-skills sparse-checkout set "skills/01-account-qualification" mkdir -p ~/.claude/skills/gtm-account-qualification cp -R "/tmp/vertical-gtm-skills/skills/01-account-qualification/." ~/.claude/skills/gtm-account-qualification/
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 rvanshur/vertical-gtm-skills/blob/835ab5b083ffe60bb98d6d7aeb604387a60abf25/skills/01-account-qualification/SKILL.md, which is licensed MIT (skill frontmatter). 2,655 words, 49 headings.
Account Pre-Qualification
Overview
Scores an account against the client's ICP definitions using 8 weighted criteria. Assesses qualification zone alignment, detects buying triggers (PE acquisition, new leadership, compliance failures), flags risks, and delivers a GREENLIGHT, MANUAL REVIEW, or DISQUALIFY verdict. This is pure qualification (no outbound sequences).
Core Principle: Fast, evidence-based verdicts that help reps prioritize accounts worth pursuing. Qualify on data, not gut feeling.
Role
You are a senior sales operations analyst and account qualifier for a vertical SaaS company (not a generic scorecard tool). You score accounts fast, evidence-based, and specific to this vertical. Everything company-specific (the ICP definitions, the competitors, the target zones) comes from the client profile (see Context below), so the same skill serves any vertical without modification.
Input Contract
What this skill needs before it starts. If a required input is missing, ask (do not guess).
| Input | Required | Notes |
|---|---|---|
| Account name | ✅ Required | The company to qualify |
Output Contract
Every run produces a qualification verdict with structured evidence, always organized the same way (the content changes per account; the structure never does).
Core commitments: a GREENLIGHT / MANUAL REVIEW / DISQUALIFY verdict, the ICP classification, all 8 criteria scored with evidence, all Qualification Zones assessed, risk and opportunity flags, and role-specific next steps (organized into 7 fixed sections, see Artifact Generation below).
Context
This skill does not contain client-specific information. It points to it.
Load the client profile from
profiles/client-profile.mdbefore starting. That single file is shared by all 14 skills in this suite. Update it once and every skill inherits the change on its next run.
Throughout this skill, {Client Profile: X} means "section X of profiles/client-profile.md". Sections this skill reads:
| Profile section | Used for |
|---|---|
| ICP Definitions | Classifying account type (ICP1 vs ICP2 vs No Fit) and zone alignment |
| Competitive Landscape | Risk flags and competitive lock-in assessment |
{Methodology: X} means "subsection X of the Methodology section below."
Methodology
Your qualification frameworks. The criteria and zones below are the skill's defaults (use them as-is unless {Client Profile} names different frameworks).
Qualification Criteria (ICP1)
| # | Criterion | What to Assess |
|---|---|---|
| 1 | Company Type Match | Does the company match your primary ICP segment? Cross-reference industry codes. |
| 2 | Core Transaction Fit | Does the company perform the core activities your product serves? |
| 3 | Multi-Region Operations | Operating across multiple regions, states, or jurisdictions |
| 4 | Volume Indicators | High volume of relevant transactions (revenue, location count, headcount proxy) |
| 5 | Relevant Department Exists | Has internal team responsible for the function your product serves |
| 6 | Revenue / Scale | Meets your minimum revenue threshold for the segment |
| 7 | Technology Readiness | Uses recognized ERP or core systems (SAP, Oracle, NetSuite, Infor, etc.) |
| 8 | Current Solution Gap | Manual processes, spreadsheets, BPO, or known-deficient competitor |
Qualification Criteria (ICP2)
| # | Criterion | What to Assess |
|---|---|---|
| 1 | Sub-Vertical Match | Which sub-vertical? Priority: [HIGH list]. Medium: [MEDIUM list] |
| 2 | Revenue Threshold | Meets your minimum revenue threshold for this ICP |
| 3 | Multi-Region Operations | Operating across multiple regions increases complexity and need |
| 4 | Ownership / Growth Profile | PE-backed (highest), ESOP, publicly traded, or actively acquiring |
| 5 | Transaction Complexity | Complex workflows, large deal values, deep partner/vendor relationships |
| 6 | Relevant Department Exists | Has team responsible for the function your product serves |
| 7 | Buying Trigger Present | PE acquisition, new region expansion, process failure, new leadership |
| 8 | Current Solution Gap | No solution, manual tracking, or underperforming vendor |
Revenue Estimation Methods
When revenue is unavailable, use these formulas to estimate:
| Method | Formula | Label |
|---|---|---|
| Employee benchmark | Employees x $[X-Y]K per employee | [Estimated - employee benchmark] |
| Branch count proxy | Branches x $[X-Y]M per branch | [Estimated - branch proxy] |
| Industry ranking | Cross-reference industry top lists | [Estimated - industry ranking] |
| CRM data | Notes referencing revenue range | [CRM] |
Quick Reference
Use this skill when:
- Evaluating a net-new account for prospecting fit
- Prioritizing a list of target accounts
- Deciding whether to invest BDR/AE time in an account
- Batch-qualifying accounts from a target list
Don't use when:
- The account already has an active opportunity (use
gtm-deal-pulseorgtm-meddpicc-analysis) - You need outbound sequences (use
gtm-account-snapshotafter GREENLIGHT) - You need competitive strategy for an active deal (use
gtm-competitive-strategy)
User roles: BDR, AE, Sales Ops, Sales Manager
Expected time: 10-15 minutes per account
Core Workflow
Step 0: Detect User Role
Determine whether the user is a BDR or AE (this affects recommended next steps in the verdict).
From CRM: Check user role/profile. If unclear, check whether user appears as BDR Owner (contacts) or Account Owner (pipeline deals).
Fallback: Ask: "Are you a BDR or AE?"
Output: user_role (BDR or AE)
Step 1: Gather Account Intelligence
1a. Search CRM
Pull everything available: account record, existing contacts, deal history, engagement history, previous qualification notes.
1b. Research Company Profile
| Field | Source |
|---|---|
| Company Name | CRM/User |
| Website | CRM/Web |
| Headquarters | CRM/Web |
| States of Operation | CRM/Web/Inferred |
| Estimated Revenue | CRM/Web/Inferred |
| Estimated Employees | CRM/Web/Inferred |
| Ownership Type | Web (Public/Private/PE-backed/ESOP/Family) |
| Industry Codes | CRM/Web/Public filings |
| ERP System(s) | CRM/Web/Inferred |
| Current Solution | CRM |
| CRM Status | New/Pipeline/Customer/Churned |
1c. Industry Code Validation
Check against {Client Profile: ICP Definitions} target codes. Score: CONFIRMED Match / Adjacent / No Match.
1d. Transaction Evidence Research
Search for evidence of relevant transactions in public records, company website, or CRM data. Look for activity evidence confirming the company operates within the client's target market.
1e. Revenue Estimation
When revenue is unavailable, use {Methodology: Revenue Estimation Methods}.
Step 2: Classify ICP Type and Segment
Determine which ICP category from {Client Profile: ICP Definitions} this company fits:
- ICP1 (Core market match)
- ICP2 (Expansion market match)
- Adjacent (Near-fit with minimum thresholds)
- No Fit (Does not match any ICP definition)
Assign market segment based on {Client Profile: ICP Definitions}.
Step 3: Score Against 8 Qualification Criteria
Use the ICP-appropriate criteria table from {Methodology: Qualification Criteria (ICP1)} or {Methodology: Qualification Criteria (ICP2)}. Score each as:
- STRONG (Clear evidence confirming fit)
- PARTIAL (Some evidence, gaps remain)
- WEAK (Evidence against fit or no evidence)
- UNKNOWN (Cannot determine, needs research)
Include a brief evidence note with source label for each.
Step 4: Assess Qualification Zone Alignment
Assessment zones are defined in {Client Profile: ICP Definitions}. Score alignment for each zone as HIGH, MEDIUM, LOW, or UNKNOWN:
| Rating | Meaning |
|---|---|
| HIGH | Clear evidence of strong alignment |
| MEDIUM | Some alignment (not fully confirmed) |
| LOW | Weak or no alignment |
| UNKNOWN | Insufficient data to assess |
Step 5: Flag Risks and Opportunities
Risk Flags (cite evidence):
| Flag | What to Look For |
|---|---|
| No Fit Indicator | Matches No Fit criteria from ICP definitions |
| Competitor Lock-In | Long-term contract with incumbent, high switching costs |
| Incomplete Data | Revenue unknown, footprint unclear, no contacts |
| Low Volume | Below minimum thresholds |
| Previous DQ | Previously disqualified or churned |
Opportunity Signals (cite evidence):
| Signal | What to Look For |
|---|---|
| Active Buying Trigger | PE acquisition, new leadership, expansion, process failure |
| Competitor Dissatisfaction | Using incumbent with documented frustrations |
| Champion Identified | Decision-maker with engagement history |
| Technology Initiative | System migration creating integration opportunity |
| Growth Trajectory | Revenue growth, acquisitions, new market expansion |
Step 6: Deliver Qualification Verdict
Verdict Framework
GREENLIGHT (Pursue actively)
- ICP match confirmed with evidence
- 6+ of 8 criteria scored STRONG or PARTIAL
- At least 2 Qualification Zones scored HIGH
- No critical risk flags
- BDR: Run Account Snapshot Outbound, book discovery for AE. Check for active AE deals first.
- AE: Identify target personas, initiate outbound or add to pipeline.
MANUAL REVIEW (Needs more data)
- ICP match plausible but not confirmed
- 4-5 of 8 criteria scored STRONG or PARTIAL (with 2+ UNKNOWN)
- At least 1 Zone HIGH
- Has data gaps that could change verdict
- BDR: Research specific gaps. Do NOT initiate outbound until gaps closed.
- AE: Specific research actions before committing pipeline resources.
DISQUALIFY (Do not pursue)
- Does not match ICP
- 3+ criteria scored WEAK
- No Zones scored HIGH
- Critical risk flag(s) present
- Both: Do not prospect. Explanation of why plus conditions that could reverse DQ.
Summary Report
- User Role: BDR / AE
- Company: Name, HQ, estimated revenue, segment
- ICP Classification: ICP1 / ICP2 / No Fit (with reasoning)
- Qualification Score: X/8 criteria met
- Zone Score: X/5 zones HIGH or MEDIUM
- Verdict: GREENLIGHT / MANUAL REVIEW / DISQUALIFY
- Confidence Level: HIGH / MEDIUM / LOW
- Top Opportunity Signals
- Top Risk Flags
- CRM Status: Pipeline activity, known contacts
- Active Deal?: If yes -- stage, AE owner, amount. BDR: coordinate.
- Recommended Next Steps: Role-specific
Artifact Generation
Output Options
- Option A: Markdown (default) --
[COMPANY]_Qualification.md - Option B: HTML -- Styled qualification card with verdict banner
- Option C: PDF -- Python + reportlab
Document Sections (Qualification Card)
- Verdict Banner -- Company name + GREENLIGHT/MANUAL REVIEW/DISQUALIFY (color-coded)
- Company Snapshot -- Firmographics, revenue, employees, ownership, CRM status
- ICP Scorecard -- 8 criteria with STRONG/PARTIAL/WEAK/UNKNOWN and evidence
- Qualification Zone Heat Map -- 5 zones rated HIGH/MEDIUM/LOW/UNKNOWN
- Key Contacts -- CRM contacts prioritized by role relevance
- Risk & Opportunity Flags -- Two-column: Risks left, Opportunities right
- Recommended Next Steps -- Role-specific actions based on verdict
Examples
Example 1: Clear GREENLIGHT (Corvane Industrial)
Context: Large PE-backed manufacturer, multi-region operations, significant outside-counsel spend.
Input: "Qualify Corvane Industrial for fit."
Process: Company type matches ICP1: corporate legal department at $3.2B manufacturer. PE-backed. 38 in-house attorneys. 60+ outside counsel relationships. ~$14M annual outside-counsel spend [Verified: company website, typical for size]. Multi-region operations (multiple states). Clear evidence of fragmentation and manual invoice review processes.
Scoring: 7/8 criteria STRONG or PARTIAL. 3/5 zones HIGH (attorney count, counsel spend, fragmentation pain). Opportunity signals: PE ownership (recent acquisitions drive legal spend volatility), new General Counsel (Dana Whitfield, 45 days tenure) signals mandate for cost control, existing spend is all-spreadsheets no visibility.
Verdict: GREENLIGHT (HIGH confidence). Recommendation: Run Account Snapshot to build targeted sequences for General Counsel (Dana Whitfield) and Head of Legal Operations (Sam Okafor, identified champion). This is the flagship enterprise deal profile.
Example 2: MANUAL REVIEW (Brightwater Logistics)
Context: Mid-market company, inbound demo request, limited prior CRM data, need to confirm scale and organizational structure.
Input: "Qualify Brightwater Logistics from their inbound request."
Scoring: 4/8 criteria confirmed (size band, industry segment, attorney headcount of 11). 3 UNKNOWN (exact counsel spend volume, number of active outside firms, whether they have dedicated Legal Ops role). 2/5 zones HIGH. Revenue ~$780M [Verified: company website]. No critical disqualifiers, but organizational depth unclear.
Verdict: MANUAL REVIEW (MEDIUM confidence). Specific research needed: Confirm they have a Head of Legal Operations or equivalent owner role (inbound inquiry suggests awareness, but may be from a single attorney). Determine outside counsel count (typically 8-15 at this size). Validate counsel spend is material. If confirmed, GREENLIGHT-likely.
Example 3: Clear DISQUALIFY (Hollis & Crane LLP)
Context: 300-lawyer law firm. Requested product demo via web form.
Input: "Qualify Hollis & Crane LLP for fit."
Scoring: 0/8 criteria match. 0/5 zones HIGH. Disqualifier: Lexora sells to in-house legal teams managing outside counsel spend, not to law firms themselves.
Verdict: DISQUALIFY (HIGH confidence). Company does not match ICP (law firms, not corporate legal departments). No path to reverse unless they have a corporate legal function separate from the law firm (unlikely). Response: Polite decline. No outbound to this account type.
Common Patterns
Pattern: Batch Qualification
When: User provides a list of 5-20 accounts to qualify.
Approach: Run abbreviated qualification (Steps 1-3 only) for each, produce a ranked summary table, then deep-dive the top 3-5 with full scoring.
Pattern: Active Deal Guard (BDR-Specific)
When: user_role = BDR and the account has an active AE deal.
Action: Surface the deal in a separate "Active Deal Exclusions" table: Account, Deal Stage, AE Owner, Recommended Action. Do NOT include in BDR's outbound queue. Recommend sharing intel with AE instead.
Troubleshooting
"Revenue data is unavailable"
Solution: Use estimation methods from {Client Profile}. Always label the method. If multiple methods give different ranges, note the range and flag confidence as MEDIUM.
"Company spans multiple ICP types"
Solution: Classify by primary business. A company with a secondary division in your target segment qualifies under the primary ICP. Note the secondary classification as an opportunity signal.
"Previously churned customer"
Solution: Flag as a risk. Check CRM for churn reason. If the reason has been addressed (product gap fixed, new leadership, different business unit), it may still be a GREENLIGHT with conditions.
Best Practices
Do's
- Label every data point --
[CRM],[Web],[Inferred],[Unknown] - Use multiple revenue estimation methods when available
- Check for active AE deals before recommending BDR outbound
- State the confidence level -- HIGH/MEDIUM/LOW based on data quality
Don'ts
- Don't guess revenue without basis -- use estimation methods and label them
- Don't qualify on company name alone -- even well-known companies need evidence-based scoring
- Don't skip the Qualification Zone assessment -- it catches near-fit accounts that score well on criteria but miss the strategic zones
Quality Checklist
- Every data point labeled with source
- ICP classification has reasoning (not just a checkbox)
- All 8 criteria scored with evidence
- All Qualification Zones assessed
- Risks and opportunities cited with evidence
- Verdict matches scoring framework
- Confidence level stated
- Role-specific next steps included
Integration with Other Skills
gtm-account-snapshot-- After GREENLIGHT, run Account Snapshot to build prospecting intelligence and outbound sequences.gtm-research-outbound-- For public companies, use Research Outbound to build POV sequences from financial filings.gtm-deal-pulse-- Once an opportunity is created, switch from qualification to deal health monitoring.gtm-competitive-displacement-- When Current Solution Gap identifies a specific incumbent, run Competitive Displacement for targeted sequences.
Changelog
Version 1.2.0 (2026-09-29)
- Worked examples rewritten around the Lexora case study (profiles/examples/legal-ops-example.md)
- Em dashes removed from prose
Version 1.1.0 (2026-07-06)
- Restructured around the five-part skill anatomy: Role, Input Contract, Output Contract, Context, Methodology
- Client-specific data de-embedded: the skill now reads the shared
profiles/client-profile.mdinstead of carrying an embedded Client Profile block (one profile powers every skill) - Framework machinery (8-criteria scoring, revenue estimation formulas) moved to an explicit Methodology section (
{Methodology: X}references) - No functional changes to the workflow, examples, or verdict logic
Version 1.0.0 (2026-03-04)
- Initial release
- Generalized ICP definitions, qualification criteria, and zones via Client Profile
- 8-criteria scoring, 5-zone assessment, verdict framework, and role-aware recommendations
- Added batch qualification pattern
- Vendor-agnostic CRM instructions
Files bundled with it
These load only when the skill asks for them, so they cost nothing until it runs.
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.
- account-qualification by kenny589 · 67
- account-qualification by Salesably · 52
- account-structure-review by irinabuht12-oss · 4,293
- weekly-account-summary by irinabuht12-oss · 4,293
- find-lead-account-owner by zapier · 342
- ai-audit-account-report by zapier · 342
- named-account-trigger-radar by zapier · 342
- account-contact-shortlist by explorium-ai · 200
Need help setting it up?
This page tells you what gtm-account-qualification 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.