# Score Accounts

> Score and tier a list of accounts by ICP fit, intent, and trigger signals. Returns a composite 0–100 with explainable component breakdown, a specific "why now" per account, and the working weight set as a saveable filter.

**Source:** https://gtm.ai/marketplace/gtm-skills/zoominfo-score-accounts

---

## Overview

Score Accounts ranks a list of accounts (ZoomInfo IDs, names, or domains, mixed freely) by ICP fit, buying intent, and recent triggers. Every score is shown with its component breakdown, so the composite is never an opaque number. Sellers reject black-box scoring, and transparency is what makes the output trusted.

The skill scores on four axes: Fit (versus your ICP), Intent (active topic research), Trigger (fresh events in the last 90 days), and Engagement (CRM-style narrative for known accounts, with the weight redistributed when absent). Composite is a weighted sum with defaults exposed on every run. Sellers can adjust weights and re-tier from cached axis scores without re-fetching data.

Resolution is deliberately conservative. Numeric IDs auto-resolve, domains usually auto-resolve, and names with multiple plausible matches surface for confirmation rather than getting silently picked. Duplicate records sharing the same domain root get flagged and unioned, since tech and intent signals are often split between them.

## What It Does

- **Four-axis scoring**: Fit, Intent, Trigger, and Engagement each scored 0–100 with banded sub-dimensions (industry, employee band, revenue band, geography, business model).
- **"Why now" per account**: One sentence anchored on the strongest signal, citing event type and recency, never restating the composite.
- **A/B/C tiering with action**: Tier A accounts get auto-pulled CRM-style narrative for deal stage, champion, and last activity, attached inline below the why-now.
- **Relationship pre-flight**: Tags each account as competitor, customer, partner, or prospect against your GTM context, with visual flags before the tier letter.
- **Saveable filter set**: On accept, returns a JSON filter set that other skills (Build List, Find Similar, TAM Sizer) can consume.

## Use Cases

### Prioritizing an Inbound Account List

When a sourced list comes in (event scans, demo requests, SDR research), run Score Accounts to tier them A, B, or C with a specific reason per row. Tier A accounts get routed to AEs within 24 hours with the why-now and engagement context already attached, so the outreach call lands on a concrete signal.

### Building a Tiered ABM List

For an ABM program, swap the default weights to favor fit and intent over triggers, then tighten the A threshold to 80 and the B threshold to 55. The skill re-tiers from cached axis scores without re-fetching, and the resulting filter set drops into Build List or Find Similar for cohort expansion.

### Territory Planning

When a rep inherits a new territory, pass the full account list and use territory-planning weights. The tier distribution shows where the real opportunity sits, the why-now per row tells the rep where to start, and the saved filter set becomes the basis for ongoing list refresh.