Account Intelligence Credit Usage

This document explains how credits work in Account Intelligence and how to estimate your annual credit usage.

Two Primary Usage Models:

• Static lists of accounts you intentionally research on a schedule • Dynamic triggers where accounts enter workflows automatically when they take an action


1. Key concepts

Workflow

A workflow is a set of steps that run on accounts. You can add one or more agents that research, summarize, score, or enrich those accounts or people. Workflows can also trigger actions like retargeting or creating an SDR task.

This guide focuses specifically on credit cost for the AI research steps inside workflows.

Agent An agent is an AI worker inside a workflow. Examples:

• Score this account from 1 to 100 based on buying intent • Summarize key initiatives and risks • Find leadership changes in target departments or titles

Each time an agent runs for an account, credits are consumed.

Agent complexity ranges from 1 to 4 credits, depending on the depth of research. Most customers use agents that cost 4 credits for richer intelligence.

Credit Credits measure how much AI work is performed. More accounts, more agents, deeper research, and more frequent runs all increase usage.

Static account list A fixed list of accounts that you choose in advance (for example: your Tier 1 ABM accounts). You schedule the workflow to run on that list on a regular cadence.

Dynamic account list / trigger Accounts automatically enter a workflow when they do something HockeyStack tracks. For example

  • Visiting key pages on your website

  • Clicking a paid ad and then requesting a demo

  • Becoming an MQL or having a new opportunity created

These actions trigger the workflow on demand.


2. Two ways to use Account Intelligence workflows

There are two common patterns for running workflows. Each consumes credits differently.

A. Static ABM workflows

What it is You define a static list of X target accounts and schedule a workflow to run at a fixed frequency such as monthly, weekly, or daily.

Typical use cases

  • Ongoing research on your top ABM accounts

  • Regular refresh of account summaries and scores

  • Pre-meeting prep packs for named accounts

  • Research on key accounts for upcoming events or tradeshows

How credits are consumed

Credits used annually ≈ number of accounts × number of agents × workflow run frequency per year × average credits per agent run (1–4)

Calculation assumption:

We recommend estimating 4 credits per agent run to give a conservative estimate and avoid undercounting.


B. Dynamic trigger-based workflows

What it is Accounts are automatically enrolled when they take an action HockeyStack tracks. These workflows are “always on” and focus on real-time signals.

Examples: • Visiting high-intent website pages • Clicking a paid ad and requesting a demo • Becoming an MQL or creating a new opportunity

Typical use cases

• Alert SDRs when accounts show new intent • Re-score accounts when something meaningful happens • Generate new summaries only when a strong signal appears

How credits are consumed

Dynamic workflows are event-driven, not scheduled. Usage depends on: • Estimate how many accounts trigger the workflow each month • Number of agents that run per trigger

Credits used annually ≈ number of accounts × percent of accounts enrolled per month based on actions × number of agents × average credits per agent run (1–4) × 12 months

Calculation assumption:

We recommend estimating 4 credits per agent run to give a conservative estimate and avoid undercounting.


3. Static vs dynamic models at a glance

Static ABM workflows

Dynamic trigger-based workflows

Best for

Planned ABM programs

Speed to lead and real-time intent

How accounts enter

Predefined list of target accounts

Auto-enrolled when they do something HockeyStack tracks

When agents run

On a set schedule (daily, weekly, monthly)

When a trigger fires (visit, click, MQL, new opportunity, etc.)

Credit pattern

Predictable and steady

Event-driven and varies with activity

Main value

Consistent coverage of strategic accounts

Focus on accounts that are active and likely to buy right now

Most customers use both

  • Static = coverage for important accounts

  • Dynamic = priority and speed for active accounts


4. Example scenarios

Example 1 – Static ABM program

• 500 Tier 1 accounts • Workflow runs monthly • 2 agents

500 × 2 × 12 months × 4 credits= 48,000 annual credits

Example 2 – Dynamic speed-to-lead

• Average 200 accounts per month hit high-intent signals • Always ON • 3 agents

200 × 3 × 12 months × 4 credits = 28,800 annual credits

Examples illustrate how account volume, agent count, and frequency translate into credit usage for planning.

Last updated