Score Every Account, Contact Only a Beachhead

Scoring a company from a domain cost 1.99 records in a 200-company test. That makes scoring a whole market cheap enough to test. The limit moves to review, sending and the employment check.

Anshul
Anshul Bhatia
Founder
November 9, 2026 · 9 min read

Scoring one company from a domain cost 1.99 records. That's the average over 200 random domains in a test on 27 October 2026: 398 billed records, two calls a company, and 199 of the 200 came back with a headcount and a size band.

And that's small enough to change an argument GTM people keep having.

This piece prices scoring a whole market and shows where the limit moves next. We have no evidence that wider scoring improves results, so the claim stays at cheap enough to test.

Two newsletters, two answers, no price

Two GTM newsletters in August gave opposite advice. One said to kill the segment and score every person. The other said to pick one beachhead and stay on it until you hold most of that market. I only saw the headlines and short summaries, so this describes the positions and not the reasoning behind them.

Neither answer, as far as I could see, puts a price on the scoring it depends on. That premise has a number now, and it's small.

My answer borrows from both. Score every account, then contact only a beachhead. (A company becomes an account once it sits on your target account list.)

What it costs to score a company

From a domain, scoring takes two calls. The first turns the domain into a LinkedIn company page, and the second pulls the company record. BlitzAPI bills one record for each call that finds something. A call that finds nothing bills nothing. The test drew 200 domains at random from 4,789 in the enrichment archives, on the BlitzAPI plan Lead Line Partners holds today, which is a different plan from Start. (Notes on the data API sit on the BlitzAPI tool page.)

Table A. Records billed in the 27 October 2026 test
StepCallsRecords billedResult
Domain to LinkedIn URL200199199 matched; the one miss billed 0
Company enrichment199199199 returned
Both, per company200398 (1.99 each)199 of 200 scored
One page of ten people20191 (9.55 each)Default employee finder page

The two calls averaged about 0.56 seconds a company in latency. The whole run took about 3.6 minutes, with a 0.25 second pause between calls. The fields came back full: size band and headcount for 199 companies, industry for 198, revenue range for 192 (96%). Of the 199, 187 are headquartered in the US.

As of October 2026, the BlitzAPI pricing page lists Start at $99 a month with a fair use policy of 200,000 records, and Scale at $499 with 5,000,000. Divide by 1.99 and Start covers about 100,000 companies a month from a domain list, and the $99 Start plan looks very interesting to us and is under consideration. Already hold the LinkedIn URLs? Only the second call applies, so you get 200,000 a month instead. Scale reaches about 2.5 million.

The vendor docs I read list one record on success for both calls, on every plan. But the test measured that on the current plan only, and Start billing hasn't been observed. At the 10 requests a second Start allows on each endpoint, you'd spend about three hours of calls per endpoint on 100,000 lookups. That figure is calculated from the published limit, not measured.

The limit I'd put first: you can't tell from this test how often a domain lands on the right company. A crude name check flagged 8 of the 199 matches. One is clearly wrong. The other seven are unchecked. And scoring the wrong company is worse than skipping it, because the rank looks just as confident either way.

What it costs to meet the people

The people cost more. One default page of ten people from the employee finder averaged 9.55 records across 20 of those companies, 191 in all. That's 4.8 times the 1.99 for the company score. It's only page one.

And full rosters are the real bill. Logged pulls in the archives averaged about 1,590 records an account (23,853 records over 15 accounts), a floor taken from an inventory log and not re-derived. At that rate, a Start month covers only about 125 full rosters.

Try an illustrative split: score 20,000 companies (39,800 records), then pull one roster page for your top 1,000 (9,550 records). That's 49,350 records, about a quarter of the month, and you'd still have the other three quarters. The gap between the two costs is why the answer has two halves.

The decision layer costs cents

A record alone doesn't rank anything: something has to read the fields and say how well the company fits. Jev, a decision model priced at $0.042 per million input tokens with output free, shows what a simple yes/no gate costs. The workloads below come from the Jev write-up.

Table B. Modeled from published rates, September 2026. The Jev price is vendor-claimed, for a simple yes/no gate.
WorkloadJevgpt-5-nanoClaude Haiku 4.5Claude Sonnet 5
ICP-fit gate, 10,000 leads at about 1,500 tokens$0.63$0.83$16.00$32.00
Reply triage, 50,000 replies at about 600 tokens$1.26$1.90$35.00$70.00
Enrichment gate, 200,000 rows at about 300 tokens$2.52$4.60$80.00$160.00
Scaled from the table: 100,000 companies at about 1,500 tokens$6.30$8.30$160.00$320.00

And the last row is the ICP-fit row times ten, since 100,000 companies is ten times 10,000 leads. Even at the Haiku price, ranking 100,000 companies runs $160. Cost isn't the blocker.

But Jev has been in early access since 15 September 2026, with no published SLA that I could find, and its confidence runs above its accuracy: 80.1% right against 90.1% stated, in the independent test our write-up cites. The maker's own price page wasn't reachable, so the rate comes from a third-party guide that restates it, and a second doc confirms output is free, both as of 27 October.

If you test a model like this, have it rank accounts and keep a person on every send. The write-up on this site says to wait before letting it gate anything live, and that advice stands.

The fit and signal axes in the account scoring template still apply, only now you can run them on the whole market. The logic should stay readable enough to open when a ranking looks wrong, the point of scoring buying intent without a black box. And a person decides who gets contacted.

What one killed segment taught us about screening

A data-infrastructure client's team proposed a segment of young companies, and we tested it in one run instead of debating it. The run enumerated 467 companies across several programs. About 237 stayed eligible after a recency cutoff, and we gated a sample of 60 of them. Of the 60, 38 had a findable company record and 22 did not (21 invisible to the data tool, 1 acquired). Eight of the 38 sat in the client's employee band, and 30 sat under it. Four of the eight cleared funding. One had an open relevant role, and that one failed a deeper check. All 60 failed.

This is one run for one client, so read it as an example. The sample of 60 isn't verifiably random. The funding and open-role counts come from the run notes and weren't recounted. A follow-up piece covers the case in full.

A headcount screen of all 467 would have cost about 930 records at 1.99 each, 0.5% of a Start month. That is a calculation; nobody ran it. And I'm saying headcount on purpose, because funding wasn't a field the company test returned, so I can't price that gate.

In that run, 21 of the 60 were invisible to the data tool used, and the 200-domain test drew from established target lists. But whether 1.99 holds for very young companies is untested.

Where the limit moves

Once scoring is cheap, three things set how many accounts you contact. A person has to review them. Your mailboxes and domains have to carry the sends, and your sellers have to answer what comes back. And someone has to confirm that each person still works where the data says, because data decay tends to hit people-level records first, though we haven't measured it.

But we haven't measured how long a person takes to review an account or how many sends a setup carries, so I won't print a number. Yours is whatever your team can read and send before quality slips. Find it before you size the beachhead.

In Trellis, the workspace a client works from, each account we propose arrives on Radar with the reason it was picked, the tier it earned and the dated signals behind both. You approve, hold or decline. And nothing arrives pre-approved, while a decline carries a reason that goes into our next search. Before anyone on an approved account is written to, we check on our side that they still work there. The AI in Trellis can't send, approve or dial.

What we would do with it

Score every company you could plausibly sell to. And sort the strong ones into tiers on fit and signals, the way ABM tiers behave once strategist hours stop being the limit. Lead Line Partners coined depth at width for that state, where every fit account gets research depth that used to go to a few dozen. Then contact the top of one tier, a beachhead sized to what your reviewers can read and your mailboxes can send. And widen it as that capacity allows.

Three results would change my mind. If the seven unchecked matches turn out wrong, the cheap score is cheap noise. If young companies keep coming back empty, as 21 of the 60 did in that run, the score has a hole where early-stage accounts live. And if Start bills a lookup differently than the docs say, every count above moves.

If you want this run on your own domain list, we start with a 200-company sample and show you the records billed and the matches we couldn't confirm before you decide anything.

Frequently asked questions

What is a target account list, and how long should it be?

A target account list is the named set of companies you've chosen to sell to, usually with a tier and a reason beside each. Its length depends on what you can review and contact, not on what you can find. Scoring a whole market is cheap enough to test, so the list can run long while the beachhead stays small.

How many tiers should an account list have, and can they run together?

There's no right count. Tiers decide how much work an account gets, and they run side by side because each account sits in one tier while you work every tier at once. And cheap scoring lets you assign tiers on fit and signals instead of on strategist hours, which is what changes if strategist hours stop being the limit.

How do you set up an account scoring model?

Split it into two axes. Fit covers the structural traits that change slowly, and signals are the dated events that decay. And fit gates the universe while signals order it. Keep the logic readable, so you can see why an account ranked where it did and change a weight when the ranking looks wrong.

How do you decide which scored accounts get contacted?

A person decides. Scoring ranks the accounts, and your beachhead is the top of one tier, sized to what your reviewers can read and your mailboxes can send. Before anyone is written to, check that they still work there. And keep the reason for each pick visible, so a decline can teach the next search.

How fast does company data go stale?

Headcount and size band drift as companies hire and merge, and roles change faster than company fields, so people-level records tend to go stale first. We haven't measured a decay rate. Re-score on a schedule, and re-check employment shortly before you send.

What does it cost to score 100,000 companies?

In the 27 October 2026 test, a company scored from a domain used 1.99 BlitzAPI records, so 100,000 companies is about 199,000 records, inside the 200,000 a month that Start lists as of October 2026. A yes/no fit gate over 100,000 companies is modeled at about $6.30 at a vendor-claimed rate, and about $160 at Claude Haiku 4.5 rates. Billing was measured on one plan only, the current one.

Supporting

  1. BlitzAPI, pricing page, plans and fair use policy, accessed 27 October 2026
  2. BlitzAPI, domain to LinkedIn URL documentation, billing per call, accessed 27 October 2026
  3. BlitzAPI, company enrichment documentation (docs.blitz-api.ai, API reference), billing per call, accessed 27 October 2026
  4. Lead Line Partners, Jev in GTM engineering, modeled rates as of September 2026
  5. Treg, How to use Jev, restates the $0.042 per million input token rate, accessed 27 October 2026
  6. OpenRouter, Jev documentation, output tokens free, accessed 27 October 2026
  7. Lead Line Partners newsletter audit, August 2026 issues (internal records, not published)
  8. Lead Line Partners test log and archive spend logs, 27 October 2026 (internal records, not published)
  9. Lead Line Partners client segment test run notes, September 2026 (internal records, not published)
Written by
Anshul

Anshul Bhatia

Founder
IIT Kharagpur. Builds GTM systems for B2B SaaS.

Anshul builds the outbound systems behind Lead Line Partners. Clay workflows, AI enrichment, and research-first sequencing for teams that want more with less.

More posts
GTM EngineeringThought leadership · 6 min read

What You Should Be Able to Open When You Hire an ABM Agency

An ABM agency writes to your buyers under your name. Seven things you should be able to open while the work can still change, from the account list to the bill.

By Anshul Bhatia
GTM EngineeringGuide · 6 min read

What Should a Reply Stop? A Decision Table for Outbound From Several Sellers

When several sellers write to one account, a reply has to stop the person, not one sequence. Eight events, with who stops, for how long, who restarts, and where each rule comes from.

By Anshul Bhatia
GTM EngineeringThought leadership · 9 min read

Room for Judgement: How Trellis Keeps Every Send Human

Where a person decides in Trellis: which accounts we work, what each email says, and whether a campaign launches, with do-not-contact above every approval.

By Anshul Bhatia

Ready to engineer your GTM motion?

Tell us how your motion runs today. We'll show you what we'd engineer.

Contact us