← All blogs

How to build an ICP scorecard template from your closed-won deals

Most ICP scorecards are built in a room that has no data in it. Here is how to build one from your closed-won deals instead, using the CRM you already own.

Most ICP scorecards are built in a room that has no data in it. A founder, a head of sales and a marketing lead sit down for a Tuesday afternoon workshop, argue for two hours, and come out with a slide called "Our Ideal Customer" that lists three industries, a headcount band and a couple of pain points. It looks defensible. It is not.

The failure is in the source, not the format. A scorecard built from opinion tells you who your team hopes will buy; a scorecard built from closed-won deals tells you who actually does. Those two lists overlap less than most revenue leaders assume, and the gap between them is where quota goes to die.

Here is how to build the second version, without a data team, using the CRM you already own.

Your scorecard is only worth what your closed-won data says it is

I have audited more than a dozen midsize B2B revenue orgs in the last year, and every single one had an ICP document. Fewer than half of them had ever compared that document to their own closed-won list. When we ran the check, roughly three quarters of the "ideal" attributes were not predictive at all. A few were actively negative signals.

Workshop scorecards capture what your team hopes about the market. Closed-won scorecards capture what the market has already paid for. That gap is why the rebuilt version usually looks nothing like the one on the wiki.

Scope matters here. Real-time buyer intent scoring is a different job, covered in the buyer intent signals guide. That system asks whether an account is showing behaviour worth acting on this week. An ICP scorecard sits underneath it and asks the slower question: if this account did show intent, would you actually close them, and would they stick around long enough to renew. Skip the ICP work and your intent scoring amplifies the wrong noise, and your reps get faster at chasing deals they were always going to lose.

What actually goes on the scorecard

An ICP scorecard is a short list of attributes with weights attached, scored against every open account, producing a single number that ranks fit. The mechanics are not the interesting part. The interesting part is which attributes you include and how you decide the weight.

Start with your closed-won list from the last 18 months. Not 12: 18 gives you enough deals to see a pattern without pulling in stale ones from an old positioning. Rank them by lifetime value, not annual contract value. LTV filters out the deals that closed loud and churned quiet, which are the deals most likely to distort the scorecard if you weight by revenue alone.

Now list every attribute you could plausibly know about a customer before the deal opens. Group them into four families:

Attribute family Examples How to weight
Firmographic Industry, headcount, revenue band, geography By win-rate lift vs your baseline. If deals in the 200–500 headcount band close at 22% and your baseline is 12%, that band earns a strong positive weight.
Technographic Core systems in the stack (HubSpot, Salesforce, Snowflake), category tools that imply readiness By presence-plus-conversion. Track which stack combinations recur in your top-quartile deals.
Behavioural Inbound trigger type, event attendance, referral source, buying-committee size at first meeting By deal-quality correlation, not deal count. A trigger that produces many small deals is not the trigger you want to weight.
Deal-shape Cycle length under 60 days, discount under 10%, multi-year contract at first purchase These are outcomes as much as inputs, but they belong on the scorecard as post-hoc validators of the fit call you made at entry.

Weight the attributes in each family by how strongly they correlate with the outcome you actually want, which is usually renewed revenue two years out. Then hard-cap the total: no more than seven attributes across all four families. The tenth attribute you add is almost always noise a spreadsheet cannot hear over.

The rubric produces one number per account. Above 70, prioritise. Between 40 and 70, work but not first. Below 40, disqualify or park. Those thresholds are yours to set against your own win rates, not defaults to copy from a template.

Three plays for building the scorecard from real deals

The deliverable isn't the scorecard itself; it's what the scorecard changes about next quarter's targeting, routing and outbound. Three specific plays get you there.

The first play is the top-quartile diff. Pull your top 25% of closed-won accounts by LTV, then your bottom 25%. Line up every attribute side by side and mark the ones that differ meaningfully. In one midsize RevOps audit I ran last year, the top-quartile accounts were 4x more likely to have implemented a data warehouse before the first sales call. That attribute did not appear in the client's stated ICP at all. It became the third-highest weighted attribute in the rebuilt scorecard, and it changed the account selection for the next outbound cohort.

The second play is loss-adjacent analysis. Pair the scorecard with your closed-lost data. If an attribute scores high on your closed-won list but also shows up on a lot of your losses, that attribute is a fit signal masking a timing or capability problem. It stays on the scorecard, but it earns a note next to it: "high fit, needs multi-thread from week one." A scorecard without a loss overlay will confidently point your SDRs at the same graveyard your AEs just walked out of.

The third play is stack-fit weighting. Technographic fit predicts conversion more reliably than most firmographic attributes at midsize and up. A prospect with three of your five ideal stack components is meaningfully more likely to close than a headcount match with none of them. Public case studies from category leaders like Gong and Datadog show stack signals drove some of their earliest ICP refinements. Weight it once you have measured the lift, not because the vendor selling you the stack-detection tool said so.

If your team is working from a persona doc that does not include stack fit or a warehouse-readiness signal, the scorecard rebuild will change your target list within the first hour. That is the point.

Join the MeetIQ waitlist →

What to do this week

You do not need a data team to run the first version of this. You need three hours and a CSV export.

  1. Pull the export. Every closed-won deal from the last 18 months. Include ACV, cycle length, source, industry, headcount band, primary contact role and any technographic data your CRM captures. If your CRM does not capture stack data yet, add it to a five-minute AE update on the next handful of deals so the next audit has it.
  2. Rank and diff. Sort by LTV. Compare the top quartile against the bottom quartile on every column. Ignore any attribute that does not show at least a 1.5x lift. You are looking for signal, not decoration.
  3. Score ten open accounts by hand. Take the weighted attribute list, apply it to ten accounts your team is already working, and see whether the ranking matches your reps' instincts. Where the scorecard and the reps disagree, that is the conversation you want to have on Friday. One of them is wrong and the answer is usually informative either way.

The point of the first pass is not to build the perfect model. It is to prove to yourself that a rules-based scorecard, run on data you already own, will produce a different account priority than the one your team is running today. It will.

The scorecard is only worth what it changes

A scorecard earns its place by changing what your team does next: which accounts get worked, which get parked, and which get routed to the AE who closes that pattern most often. Building it from closed-won data means the fit call is anchored in something the market has already paid for, not something five people in a room agreed to on a Tuesday.

Bain & Company's classic loyalty work, Prescription for Cutting Costs, put the value of a marginal retained customer at roughly five to twenty five times the value of a marginal new one. Your scorecard is the mechanism that keeps you spending sales cycles on the accounts most likely to renew.

Turn closed-won patterns into live routing

MeetIQ is being built to compress the loop from "we built the scorecard" to "the next outbound cohort reflects it," so the fit call happens before the SDR touches the account. Waitlist members lock in founding pricing.