Outbound Account Prioritizer

Adam's take

SDRs lose their mornings to deciding who to call. Hand them a ranked list and watch activity quality change within a week.

Required tools

Optional tools

Expected value

SDRs start each day with a ranked list; less time deciding, more time executing

Deployable workflow pack

The full pack includes the agent spec, deployment guide, architecture diagrams, n8n workflow skeleton, Clay template, HubSpot properties, JSON schemas, OpenAPI spec, cost and ROI calculators, demo data, QA checklist, and governance notes.

How to deploy this agent

SDRs lose the first 20 minutes of every shift deciding who to call. The inputs to make that decision well already exist — fit tier, buying-committee coverage, intent recency — scattered across other agents’ output fields. This agent does the arithmetic every morning so a rep opens one ranked list instead of assembling one from four dashboards.

Core signals

Input schema

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://deploytheagent.com/schemas/agent-004-input.schema.json",
  "title": "Agent #004 Outbound Account Prioritizer Input",
  "type": "object",
  "required": [
    "record_id"
  ],
  "properties": {
    "record_id": {
      "type": "string",
      "description": "CRM record ID (company/contact/deal depending on agent)."
    },
    "domain": {
      "type": "string"
    },
    "config_version": {
      "type": "string",
      "description": "Versioned config used for this run."
    }
  },
  "additionalProperties": true
}

Output schema

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://deploytheagent.com/schemas/agent-004-output.schema.json",
  "title": "Agent #004 Outbound Account Prioritizer Output",
  "type": "object",
  "required": [
    "record_id",
    "outbound_priority_rank",
    "outbound_priority_reason",
    "outbound_list_date"
  ],
  "properties": {
    "record_id": {
      "type": "string"
    },
    "outbound_priority_rank": {
      "type": "string",
      "description": "Agent #004 output field."
    },
    "outbound_priority_reason": {
      "type": "string",
      "description": "Agent #004 output field."
    },
    "outbound_list_date": {
      "type": "string",
      "description": "Agent #004 output field."
    }
  },
  "additionalProperties": false
}

Scoring / classification logic

Ties within a tier break by freshness — the least-recently-touched account first. Every ranked account carries a short, generated reason string (e.g. "Tier 1, intent signal 2 days ago, not touched in 6 days") so a rep sees why an account is ranked where it is, not just a bare number.

HubSpot CRM properties

n8n workflow skeleton

The Outbound Account Prioritizer turns the account priority score, tier, intent signals, and contact/committee coverage into a single ranked daily outbound list. SDRs open one list instead of assembling their own from four dashboards. Configure every node marked CONFIGURE before enabling the trigger.

1. Trigger
   CONFIGURE: set cadence per agent-spec.md's What It Does section. Leave disabled until Step 6 of deployment-guide.md.
2. Load versioned config
   CONFIGURE: replace with your versioned config built from real data (see deployment-guide.md Step 1).
3. Fetch source data
   CONFIGURE: {{HUBSPOT_CREDENTIAL}}. Pull the fields listed in agent-spec.md's Inputs table.
4. Validate + gate records
   Drops records missing required inputs or failing suppression/gate checks defined in agent-spec.md. Logs every drop.
5. Apply workflow logic
   Implements the Workflow Logic table from agent-spec.md. Writes model/config version alongside every derived value for auditability.
6. Write agent-owned CRM fields
   CONFIGURE: {{HUBSPOT_CREDENTIAL}}. Writes only: outbound_priority_rank, outbound_priority_reason, outbound_list_date. Never writes sales-owned fields.
7. Route to human review / alert
   CONFIGURE: {{SLACK_CHANNEL}}. Fires for records requiring human review per agent-spec.md's Governance section.

Cost calculator

ROI calculator

Governance notes

• This is a ranked suggestion list, not an assignment lock — reps can skip or reorder without any workflow override.
• Suppressed and unsubscribed accounts are filtered out before ranking even runs, not after — they never appear on the list at all.
• The agent never writes to deal-stage or lifecycle fields; its only outputs are the rank, the reason, and the list date.
• Every day’s list is dated and logged, so a rep’s "why was I working this account" question always has a documented answer.

Failure modes

• Same accounts rank #1 every day: usually means the freshness penalty isn’t actually being applied — caught by a QA test that confirms recently-touched accounts drop in rank.
• Suppressed accounts sneak onto the list: the suppression filter has to run before ranking, not after, or a suppressed account can slip through on a technicality.
• A generic, non-specific reason string: if the "why ranked here" text is the same boilerplate for every account, it isn’t doing its job of building rep trust in the list.

QA checklist

FAQ

Related agents