Clay logo, go to homepage

Search Marketplace

Browse all Skills
Score & qualifySkill

Account Tiering Workflow

The Account Tiering Workflow automates the scoring and tiering of accounts as they enter a specified audience in Clay, enriching their data and writing the results back to the account record without human intervention.

Sung Jo
Sung Jo

SEO/AEO Lead at Clay

About this Skill

When to use it

This Skill is ideal when you need to automatically score and tier accounts based on their fit for your product as they enter a segment. It is particularly useful for organizations looking to differentiate between prospects and existing customers, scoring them on distinct rubrics. If you want to ensure that your sales team focuses on accounts that are not only a good fit but also have a reason to act now, this workflow is essential. Avoid using it for static lists or single company monitoring, as it is designed for dynamic account scoring.

What it delivers

The primary artifact produced is the Scored & tiered account record, which includes fields such as Account, Track, Fit score, Tier, Priority, Why now, and Rationale. This workflow unlocks the decision-making process by providing a clear tiering system that separates fit from timing, allowing for better prioritization of accounts. The boundaries of this Skill ensure that it does not contact anyone, delete fields, or operate on static lists, maintaining a focus on dynamic account engagement.

SKILL.md preview

Sign in to install and view the complete SKILL.md

Illustrative preview. Sign in for the actual file.

How someone would prompt this

Can you set up an account-tiering workflow for my target audience?

Inputs & outputs

What someone provides before the Skill runs, and the reviewable artifacts it returns.

Inputs

  • 01The trigger audience
    • the Clay audience/segment whose accounts should be scored as they enter it
    • if missing, there is nothing to trigger the workflow
  • 02Your product & ICP
    • one paragraph on what you sell and to whom, and what signals fit: the tooling, hiring, firmographics and usage that mean a good account for you
    • if missing, this is the whole scoring rubric and without it the score is generic and wrong
  • 03Account-record fields
    • which fields on the record hold: domain, company LinkedIn URL, company name, current plan/tier, acquisition type (prospect/customer/churned), a usage metric, open pipeline, open-opp count, engagement status & summary, last-signal date, employee count
    • if missing, each unmapped field drops out of scoring and is listed as unobserved, with domain being required
  • 04In-scope rule
    • which accounts should run at all
    • the default is prospects, plus existing customers on the plan you want to expand from
    • if missing, an empty rule scores your whole audience and spends on accounts you would never work
  • 05Expansion-from plan
    • the plan name that means 'existing customer worth an upgrade motion'
    • if absent, every in-scope account is scored on the New-Business rubric only
  • 06Usage-pressure thresholds
    • the usage-metric cut-offs that mean an account has outgrown its plan
    • if missing, defaults to the source values and says so
  • 07Tier cut-offs
    • the score cuts for the tiers
    • if missing, defaults to the source values and says so — they are editable
  • 08Tech-stack connected account
    • the connected account for the tech-stack lookup
    • if absent, either connect one or swap in a Clay-credit tech action, stating which
  • 09Write-target fields
    • the six account fields to write: fit score, tier, priority, rationale, why-now, track
    • if the installer does not want a write, this is not this skill

Outputs

  • 01Scored & tiered account recordcontains the fields Account, Track, Fit score, Tier, Priority, Why now, and Rationale, which provide a comprehensive view of each account's scoring and tiering status

Representative output

Scored & tiered account record

Six fields written per in-scope account — one deliverable, six fields. This is their shape (placeholder accounts, invented values); fabrikam.example is the insight on one row: a 77 clears the fit bar and still lands Tier 2, because Tier 1 requires a live signal.

AccountTrackFit scoreTierPriorityWhy nowRationale
northwind.exampleNew Business82Tier 1Yes3 RevOps roles posted in the last 60 daysFull outbound stack (CRM + sequencer + data provider), RevOps + GTM-engineering hiring, 22% headcount growth; engagement thin, scored conservatively there.
contoso.exampleExpansion88Tier 1Yessevere usage pressure on the current plan (24 workspaces)On the expansion plan with 24 workspaces — structurally past it; large, still-hiring GTM org; open opportunity already in flight.
fabrikam.exampleNew Business77Tier 2NoNo timing signalStrong stack and healthy growth, but no GTM roles posted, no recent funding, and last signal is stale — good fit, nothing making it live this week.

The ranking key the workflow computes (fit + a Tier-1 bonus + a Priority bonus) is what makes a downstream digest sortable; it is computed but not written to the record.

How the Skill runs

Follow the steps in order. Each row includes the full instruction.

01
State the posture, then confirm the platform

This step confirms that the workflow will read the account record and public enrichment, and write six scoring fields back onto each in-scope account. It ensures that Clay is functioning correctly before proceeding.

Step
02
Collect the definition (interview at build; do not guess)

In this step, you will collect the necessary inputs for the workflow, including the trigger audience and account fields. It is crucial to gather this information accurately to ensure the scoring is effective.

Step
03
Confirm node syntax on the installed version

This step involves confirming the syntax of the nodes based on the installed version of the workflow. It ensures that the correct commands are used for building the workflow.

Step
04
Build the workflow *(write-approval: creating nodes in the workspace)*

In this step, you will build the workflow by creating a trigger and nodes in the audience. It is important to get approval before creating anything and to build in the correct dependency order. The run stops and waits for approval before writing anything.

Action
05
Validate and dry-run a small sample

This step validates the workflow graph and runs a dry run against a small sample of in-scope accounts. It is essential to confirm that the enrichments return the expected values before the workflow goes live.

Step
06
First live batch, then go live *(spend-approval + write-approval, one gate)*

In the final step, you will run the first live batch of accounts and report the actual costs. This step requires approval before proceeding and ensures that the workflow is functioning as intended. The run stops and waits for spend approval before continuing.

Action

Connections required

BuiltWithRequired connection

Install Clay and run it

Sign in once, install the Skill, then run the prompt.

  1. 1Install ClayUse the connector or official plugin in your coding-agent environment.
  2. 2Sign up or log inAuthorize Clay access and return when the connection is ready.
  3. 3Install the SkillRun the one-line install command from the Add this Skill card.
  4. 4Run the SkillPaste the example prompt and review the result.

Version history

Version 2From submitted SKILL.mdCurrent

Related Skills

Icp Outbound CampaignTurns your ideal customer profile into a verified lead list saved in Clay Audiences and a drafted outbound email sequence, without sending or launching anything.View Skill →Clean Company Names For CopyCleans raw company-name strings into short, natural versions for outreach copy, running a free normalizer first and escalating to AI only when a 20-row review shows the normalizer falls short.View Skill →Clean First Names For GreetingsCleans the raw first_name_raw field into a proper greeting name in a new first_name_clean column, withholding rows that fail six guard checks instead of guessing.View Skill →

Related searches

Score & qualify skillsBuiltWith skills