Clay

Signal-Based Account Scoring Without Runaway Enrichment Costs

Enrichment is priced per row, so the cost scales with your list rather than with your results. How to order the steps so you pay for signal instead of for volume.

Mauricio Esparza By ·Published ·2 min read
mithub.club
Short answer

Order the steps from cheapest to most expensive and let each one reduce the list. Free filters first, then one cheap enrichment that disqualifies, then the expensive waterfall only on what survives, then the model column last on the shortlist. Most teams run it in the opposite order, which is why the bill tracks the list size instead of the number of qualified accounts.

Enrichment is priced per row. That single fact means the order of your steps is your budget.

The order most teams use

Enrich everything, then score, then filter.

This pays full price for every row, including the ones a free condition would have removed in the first second. It is also the intuitive order, which is why it is so common.

The order that costs a fraction

1. Free filters first. Geography, company size, obvious disqualifiers, anything already a customer, anything already in your CRM. Costs nothing and usually removes a large share of the list.

2. One cheap enrichment whose job is to disqualify. Not to enrich. To remove. A single inexpensive signal that eliminates a meaningful percentage pays for itself many times over before anything expensive runs.

3. The expensive waterfall on what survives. Waterfall logic already helps here: ask one source, and only pay the next one if it fails. Coverage goes up and cost goes down.

4. The model column last, on the shortlist. It is the most expensive per row and it produces better answers when the other data is already there.

Same table, same outcome, a fraction of the spend.

Two rules that keep the columns honest

One column, one question. A column that answers three things cannot be verified, and unverifiable enrichment is money spent on something you cannot use.

Mark unknown as unknown. Anything the source does not say should be recorded as missing rather than guessed. An invented value costs more than a blank one, because it gets said out loud to a prospect.

The controls that prevent a bad month

  • A cap per run. A hard limit on rows processed.
  • An alert on daily spend, not monthly. The expensive incidents are loops and accidental re-runs, and both are visible within a day.
  • A test on fifty rows before any full run. Always. It catches the column that is wrong before it is wrong five thousand times.

The number to watch

Not credits used. Cost per qualified account.

Credits used falls when you optimise and also falls when you enrich less and qualify nothing. Only the second number tells you whether the table is worth running.

Track it monthly against the alternative: what the same qualified account costs through any other channel. That comparison is the one that survives a budget conversation.

When enrichment is the wrong answer entirely

When the data you need is already in your CRM and merely dirty. That is cleaning, not enrichment, and normalising what you own is far cheaper than buying it again.

Frequently asked questions

What is the single biggest lever on cost?

Filtering before enriching. Every row removed with a free condition is full price saved with no loss of outcome, and most lists can be cut substantially on geography, size and obvious disqualifiers alone.

Why run a cheap enrichment before the expensive one?

Because its job is to disqualify rather than to enrich. One inexpensive signal that removes a large share of the list pays for itself many times over before the waterfall runs.

When should the AI column run?

Last, on the shortlist. It is the most expensive per row and it produces better answers when the other data is already present, so running it early costs more and returns less.

How do we avoid a surprise bill?

A cap per run, an alert on daily spend, and a test on fifty rows before any full run. Runaway loops and accidental double runs are the usual cause, and all three controls are cheap.

Sources

  1. Building effective agents · Anthropic (accessed 2026-09-22)
  2. Why evaluate AI workflows · n8n Docs (accessed 2026-09-22)
  3. Handle errors gracefully · n8n Docs (accessed 2026-09-22)
ClayRevenue EngineeringData
Mauricio Esparza
Mauricio EsparzaGTM Systems Lead · Revenue Engineer · Founder of MitHub. Designs and runs revenue systems for multi-location businesses: AI voice campaigns, enrichment, CRM automation and attribution. Founded MitHub to teach the method in the open.

Part of Clay on MitHub.

Keep going