Beyond Static Filters: Scoring Your ICP with Predictive Firmographic Signals

A static ICP filter tells you a company was a fit when someone last updated the field — industry, headcount, and location don't change often, so the filter goes stale without ever looking wrong. Predictive firmographic scoring replaces the snapshot with a trend: is this company growing, hiring into the function you sell to, or adopting adjacent tools right now. This piece covers what signals are worth scoring, how to weight them without overfitting a small dataset, and where predictive scoring breaks down.

Where Static ICP Filters Stop Being Useful

Static firmographic filters are good at exclusion and nearly useless at prioritization. 'SaaS company, 100-500 employees, US' tells you a company clears the bar for being theoretically reachable — it says nothing about whether now is a good time to reach them, or whether they're likelier to reply than the next 400 companies with the same profile. Once a list clears the static filter, everyone on it looks identical to the scoring model, which is exactly the problem: reps end up working the list in the order it was imported instead of the order that reflects actual likelihood to convert.

The filter also degrades quietly. Headcount and industry classification rarely change, so a company that was genuinely mid-market a year ago can still pass the filter after it's been acquired, downsized, or pivoted into a different market — the static fields don't flag any of that. A predictive layer is what catches the difference between still technically fitting the profile and actually behaving like your best customers did before they became customers.

The Signals Worth Feeding Into a Score

Not every available data point is worth scoring. The useful signals are the ones that moved before your best existing customers bought, which you can only know by looking at your own closed-won history rather than a generic vendor list of buying signals.

• Revenue and funding trajectory — a recent funding round, a revenue growth estimate, or a new investor on the cap table signals fresh budget, not just company size.
• Headcount velocity, overall and by department — a company growing headcount by 15% or more over two quarters is behaving differently than one flat at the same size for years, even if both show the same static headcount today.
• Hiring specifically into the function you sell to — open reqs for the role your product supports is one of the tightest available proxies for near-term budget in that function.
• Technology stack changes — new tool adoptions or removals in an adjacent category, visible via technology-footprint scanners, show active investment in a related problem.
• Leadership changes — a new VP or director in the relevant function within the last few months, since new leaders typically re-evaluate vendor and tooling decisions in their first two quarters.
• Public-facing activity — new office openings, press releases, product launches — lower-signal individually but useful as tie-breakers.

Weighting Signals Without Overfitting a Small Dataset

B2B cold outreach datasets are small compared to consumer scale, a few hundred closed-won accounts rather than millions of transactions, which means an elaborate multi-variable regression model will overfit before it generalizes. Start with a simple weighted checklist instead: list the four to six signals from your closed-won review, assign each a point value based on how often it was present in a won deal versus a lost or no-reply one, and sum them into a score band, for example 0-100.

Validate the weights against a holdout set of deals you haven't looked at yet, not the same deals you used to build the weights, or you're just confirming a pattern you already assumed. If the weighted score doesn't separate won from lost deals better than the static filter alone did, the weights are wrong or the signal isn't actually predictive for your business, and it's worth cutting rather than keeping for the sake of complexity.

Signals Expire — Build Decay Into the Score

A funding-round signal is informative for a defined window, not indefinitely. Budget from a raise typically gets allocated within two to three quarters; scoring a company as high-priority a year after its last funding event because the field is still populated produces a stale high score that sends reps chasing a signal that's no longer true. Set an explicit decay: full weight for 0-3 months, half weight for 3-6 months, zero weight after 6 months, adjusted per signal type.

Hiring signals decay faster than funding signals. An open req can close in weeks, and treating a three-month-old job posting as current is a common way predictive scores drift out of sync with reality. Re-pull hiring data on a cadence that matches how fast the signal actually changes, not on a fixed quarterly enrichment schedule that's convenient for the tooling but wrong for the signal.

Rescoring on a schedule matters more than the initial scoring pass. A list scored once at import and never refreshed converges back to a static filter within a couple of months — all the predictive value was in catching the signal near when it appeared, not in remembering that it existed at some point.

Where Predictive Scoring Goes Wrong

The same properties that make predictive scoring useful — it's dynamic, weighted, and specific — make it easy to misuse. Most failures trace back to one of a handful of habits.

• Buying a vendor's generic intent or scoring model and applying its default weights without checking them against your own closed-won data — the weights were built for someone else's product and buyer.
• Building a score with 15 or more variables on a dataset of a few hundred deals — the model fits noise, and nobody on the sales team can explain why a given company scored high.
• Never decaying event-based signals, so accounts that were hot two quarters ago still show up at the top of the queue.
• Treating the predictive score as a replacement for the static ICP gate instead of a layer on top of it — a high-growth company that's a bad fit on industry or geography is still a bad fit, no matter how fast it's hiring.
• Scoring more companies than the team has capacity to act on personally — a predictive score that surfaces 2,000 hot accounts a week just becomes a new version of the mass-blast problem, defeating the point of scoring in the first place.

How LDM Layers Predictive Signals on Static Filters

In LDM's model, the static ICP definition lives as company-level custom fields and list membership — industry, size band, geography — and acts as the gate a company has to clear before it's eligible for any campaign. Predictive signals sit on top as additional custom fields and tags that get refreshed on a schedule rather than set once, so a hiring or funding signal populates a field that campaigns and saved views can filter or sort on without redefining the underlying list.

Because campaigns pour from a defined company or contact list rather than an open-ended score threshold, a rising predictive score doesn't automatically enroll a company in outreach — it changes where that company sits in a prioritized queue that a rep or the sequence logic works through in order, which keeps the same discipline around personalization and volume that targeted B2B outreach depends on.

FAQ