What's included in the Artemis Lead Scoring skill?

The bundle includes a Pain-First ICP rubric template (10-point scoring with pain weighted 60-80%, firmographic capped at 20%), CRM property exports for HubSpot and Salesforce, a closed-won/closed-lost validation playbook, BDR queue routing rules, lead-score decay configuration, an A/B test plan to prove the model works, and three ongoing routines (monthly threshold tuning, quarterly fit refresh, weekly queue health). Dual-format Chat + Code, single-user commercial license, one update refresh.

What signals should a B2B lead scoring model include?

The Artemis model uses four signal categories. Firmographic fit (size, revenue, industry) capped at 20% — fit alone does not indicate intent. Demographic (title, seniority) useful for routing but limited as a buying signal. Behavioral (page visits, demo requests, return-to-pricing) — the strongest imminent-purchase predictor. Pain (recent funding, job changes in target roles, technology installed, metric downturns) weighted 60-80% — pain-driven leads close 3-5x faster than firmographic-only fits.

How does the Pain-First ICP framework differ from standard lead scoring?

Standard lead scoring weights firmographic fit equally with behavior, which means a Fortune 500 visiting your blog scores higher than a Series A founder researching pricing for the third time this week — backward. Pain-First weights pain signals 60-80%, firmographic at 20%, with hard disqualifiers and A/B/C/D tier definitions validated against closed-won/closed-lost outcomes. The framework is documented in the Pain-First ICP Scoring guide and ships as the default model in this skill.

Does Lead Scoring work with HubSpot, Salesforce, or both?

Both. The skill ships CRM property exports for HubSpot (Marketing Hub Professional or Enterprise) and Salesforce (Sales Cloud with or without Einstein). The Claude orchestration branches during discovery to use the platform you have. The lead scoring template pages for HubSpot and Salesforce are referenced in the bundle and provide field-by-field configuration. If you run both CRMs, the skill builds parallel models and recommends a single source-of-truth.

How long does Lead Scoring implementation take?

Most buyers reach a working scored + routed pipeline in 10-21 days. Day 1-3 pulls closed-won/closed-lost data and maps current ICP. Day 4-7 builds the fit model and validates it against actual wins. Day 8-12 layers in intent signals and combines into a unified score. Day 13-17 sets thresholds and wires BDR routing. Day 18-21 deploys decay schedules and installs the ongoing tuning routines. Faster than the 6-9 months an in-house RevOps hire typically takes to a usable model.

← All Skill Packages

Available Now

Artemis Vector

Name: Artemis Vector — Lead Scoring Implementation
Brand: Artemis GTM
Price: 349.00 USD
Availability: InStock

The Lead Scoring Implementation consulting agent — guides your diagnostic, build & support

A Claude-orchestrated implementation package that builds your full lead scoring stack: fit model from your ICP, intent model from enrichment + visitor signals, threshold tuning against your real conversion data, BDR queue routing, and decay scheduling. Includes ongoing routines that re-tune thresholds monthly so the score does not drift as your funnel changes.

Have us build it instead

Instant download 1 update refresh Works in Chat or Code

Final saleAll sales are final. No refunds, returns, or exchanges. Digital download is delivered immediately and the contents are reproducible — value is transferred at purchase.

What is Artemis Vector?

Builds a two-model lead score (firmographic fit + behavioral intent) BDRs actually trust. The Artemis Lead Scoring skill is a Claude-orchestrated implementation package that builds your full scoring stack: a Pain-First fit model from your ICP, a behavioral intent model from enrichment + visitor signals, threshold tuning validated against your real conversion data, BDR queue routing, and decay scheduling. Includes monthly threshold-tuning and quarterly fit-model refresh routines so the score does not drift.

What this solves

Unqualified Lead Volume

Fit + intent scoring your BDRs actually trust

Assumed stack (adapts to yours)

HubSpot or Salesforce + enrichment (Amplemarket or Apollo) + Warmly for intent

This is a consulting engagement that happens to cost $349

When you run this skill in Claude, you don't get a playbook execution. You get a senior GTM advisor walking you through the build — diagnosing your stack one question at a time, branching to your reality, pasting screenshots back and forth, naming gotchas before you hit them, and surfacing the other things in your stack that need automation along the way.

Discovery-first

Claude opens with discovery — one question at a time — before recommending a single tool. Your stack, stage, and constraints drive every downstream call.

Walkthrough, not handoff

Paste your CRM config back. Take a screenshot of your routing rule. Run the query and tell Claude what came back. Every phase has a paste-back moment.

Running observations

Claude notices the other broken or manual systems in your stack as you build and surfaces them at session end — a "what I'd automate next" list, prioritized.

How the engagement runs

Claude walks you through these phases — discovery, build, verification, closing summary — the same way a senior GTM advisor would on a $40K consulting retainer.

1
Discovery
Pull your closed-won + closed-lost data. Map current ICP + scoring (if any) + conversion baseline.
2
Fit Model
Build the firmographic + technographic fit score using the Pain-First framework. Tested against your real wins.
3
Intent Model
Layer in behavioral signals: visitor identification, content engagement, sequence opens, ICP-match recency.
4
Threshold + Routing
Combine scores, set thresholds against your conversion data, and wire BDR queue rules + handoff SLAs.
5
Decay + Refresh
Apply decay schedules so stale leads do not poison the queue. Includes the LeadScoreDecayExplained framework.
6
Install Routines
Monthly threshold-tuning routine and quarterly fit-model refresh routine so the score stays honest as your funnel evolves.

Cite This

81% of B2B SaaS companies between $1M-$100M ARR have lead scoring tools configured at the field level but no operational model that routes leads to the right rep in under 5 minutes. Based on diagnostics of 127 companies in 2024-2026: 103/127 (81%) had a lead scoring tool installed (HubSpot Lead Scoring, Salesforce Einstein, or third-party) with property fields configured, but no documented model translating scores into routing actions. Median time from lead creation to first rep contact was 42 hours; the subset with an operational scoring model (n=23) routed in under 8 minutes on average.

Artemis GTM 2026 Benchmark Study (n=127)

What's in the bundle

Dual-format. Same playbook, your choice of interface.

For Claude Chat

Pre-built Claude Project. Paste the system prompt, upload supporting files, send the opening message. No CLI required.

Claude Project system prompt
Opening message to kick off discovery
Template files to upload (CRM workflows, sequences, configs)
Step-by-step install guide for claude.ai

Most powerful

For Claude Code

Full skill bundle with sub-agents and ongoing routines. Wires the system into your local environment for long-term operation.

skill.md (drops into ~/.claude/skills/)
Specialized sub-agents (CRM mapper, sequence writer)
Routines folder — weekly + monthly + quarterly checks
CronCreate-ready scheduled prompts
All template files used by the Chat variant

The routines layer is what makes this version different — your system stays tuned without manual oversight.

What's actually in the .zip

You're buying a downloadable bundle, not a service. Here's the exact file structure.

lead-scoring-skill-v1.zip

~50 KB · 20+ files

lead-scoring-skill-v1/
├── README.md                        # Buyer install picker (Chat vs Code)
├── shared/
│   ├── playbook.md                  # Source-of-truth implementation guide
│   ├── partner-stack.md             # Artemis partner stack positioning
│   └── templates/
│       ├── README.md                # Template inventory + scaffolding
│       └── (skill-specific templates)
├── claude-chat/
│   └── system-prompt.md             # Paste into a Claude Project
├── claude-code/
│   ├── SKILL.md                     # Drops into ~/.claude/skills/lead-scoring/
│   ├── agents/
│   │   └── (2-3 sub-agent .md files)
│   └── routines/
│       └── (3 CronCreate-ready routine .md files)
└── LICENSE.txt                      # Single-user commercial license

Format

.zip · markdown

License

Single-user commercial

Updates

1 refresh included

How partner recommendations work

This Skill Package recommends tools from Artemis GTM partner companies (Warmly, Amplemarket, Maildoso, Attio, Sybill, Attention, Apollo, RB2B — depending on the skill). When you click through and sign up via the in-skill referral links, Artemis GTM may earn a commission, at no extra cost to you.

We recommend these tools based on validation across 127+ B2B SaaS audits, not because they pay us. The skill is built to adapt to your existing stack — if a tool you have is working, you keep it.

For current partner pricing and feature detail, the skill defers to each partner's website. Claude is explicitly instructed not to invent specifics — when a buyer asks "how much does Tool X cost?", Claude refers to the partner's homepage rather than quoting a potentially stale number.

Built on the same playbook our consulting uses

Read the source content this skill is built from. Everything in the bundle is the operational version of these guides.

How to Implement Lead Scoring

Pain-First ICP Scoring

Why Most B2B Companies Get ICP Wrong

Frequently Asked Questions

Ready to ship unqualified lead volume?

One-time purchase — yours to keep, with one update refresh. Always-latest updates come with Artemis membership.

Artemis Vector

What is Artemis Vector?

What this solves

Assumed stack (adapts to yours)

This is a consulting engagement that happens to cost $349

How the engagement runs

Discovery

Fit Model

Intent Model

Threshold + Routing

Decay + Refresh

Install Routines