Why this matters
Ask five people to define the ideal customer profile and you get five sentences that all sound right. "Mid-market operations-heavy businesses with a growing hourly workforce." Nobody disagrees, because nobody can.
Then somebody builds a target list from it, sales says the list is bad, marketing says it is fine, and the argument runs for a quarter, because there is nothing either side can point at.
What you will be able to do
- Turn an adjectival ICP into weighted rules on fields that exist in your data.
- Require a reason string on every score, and say why a score without one cannot be improved.
- Spot a rule that fires on almost everything, and delete it.
Rules on fields that exist
"Growing sales team" is not a rule: there is no column called growing. Write conditions on fields
you have. Here, accounts.csv (from the data/ folder of your practice pack, copied into
10-data/ in L7.1) gives you segment, employee_count, industry, country,
region, lifecycle_status and primary_lead_source; opportunities.csv gives you history;
product_usage.csv and support_tickets.csv give you behaviour on accounts you already serve.
One warning first. accounts.region was derived from country at creation and never dirtied: the
reliable geography field. accounts.country and accounts.industry are not clean everywhere
(data/DATA-DICTIONARY.md in your practice pack): the file holds united states, DE, netherlands, The Netherlands,
Retail, logistics and Hospitality & Leisure. Match industry = 'Retail' exactly and you
silently drop ACC-02948, recorded as ' Retail' with a leading space.
So the rule file has a normalisation section before it has rules, and the brief applies it. Same discipline as the match rules in Module 5: a comparison is only as good as the strings going in.
Weights, tiers, and the reason string
Give each rule a weight, sum to a score, and cut the score into named tiers. Then the requirement that makes it auditable:
Every scored record carries a reason string listing which rules fired and what each contributed.
ACC-02831, score 90, Tier A
reason: I1 segment Mid-Market +30 | I2 region EMEA +15 |
I3 industry Logistics +20 | I4 employees 617 +15 |
I5 prior closed-lost +10
A score with no reason string cannot be argued with, so it cannot be improved. When somebody says Tier A is wrong for an account, the reason string makes it a conversation about a weight, ending in a rule change. Without it, it ends in "the scoring is broken" and you learn nothing. The reason string is also how you find the rule that does nothing. That is next.
The rule that fires on everything is not a rule
Score the shipped prospect pool with the exercise rules below and one thing stands out. Of 163
prospect accounts with no open opportunity, 154 have a prior closed-lost opportunity. The "they
have evaluated us before" rule, worth +10, fires on 94% of the population, adds ten points to nearly
everything, and separates nothing. The score looks richer; the ranking is identical. Delete it, or
sharpen it: closed-lost in the last 12 months, or closed-lost with loss_reason = Price when
your packaging has since changed.
So the last step of writing an ICP is not writing it. It is running each rule against the population and printing the fire rate:
For each rule, report: rule id, records matched, percentage of the population.
Any rule above about 80% or below about 5% deserves a second look. The first is a constant, the second a special case you will forget you wrote.
The scoring brief, run for real
OUTCOME
Score every account in the export against the ICP rules and output one row per
account with the score, the tier and the reason string.
INPUTS
10-data/accounts.csv, 10-data/opportunities.csv
Rules: 40-reference/icp-rules.md, sections N (normalisation) and I1 to I5,
tier bands in section T.
OUTPUT SHAPE
30-output/demand/icp-scores.csv, columns exactly:
account_id, account_name, score, tier, reason, suppressed, suppression_reason
reason is a single string of the form "I1 <condition> +<n> | I2 ... ".
Every scored row has a non-empty reason.
Then, printed in the chat, not written to file: the rule fire-rate table.
Columns: rule_id, records_matched, pct_of_population.
CONSTRAINTS
Apply the normalisation in section N before any string comparison.
Scoring and suppression are separate steps: score every account, then set
suppressed = TRUE with a reason where a suppression rule applies. Do not remove
suppressed rows from the file.
Do not invent a rule that is not in icp-rules.md. If a record cannot be scored
against a rule, write it to exceptions.csv rather than scoring it as zero.
DEFINITION OF DONE
Every account in the input appears exactly once in the output.
Row count in equals row count out.
Two lines in that brief do real work. "Scoring and suppression are separate steps": filter suppressed accounts out during scoring and you can no longer answer "how much of our best-fit universe is already in play", one of the more useful numbers a marketer can produce. "Row count in equals row count out": the reconciliation. It catches the run that silently drops the two accounts with a dirty industry string, without you having to notice which two.
Try this now: score four accounts by hand, then check the rules
About seven minutes. Do the arithmetic yourself. It is the last time you will, and it is why you will trust the output afterwards.
You are settling the ICP argument before territory planning, with accounts.csv and
opportunities.csv. Sales says logistics and hospitality in EMEA. Marketing says anything
mid-market.
Create
40-reference/icp-rules.mdfromtemplates/M7/icp-rules.mdin your practice pack.Write these five rules with these weights, so your numbers match the answer below:
I1 segment Mid-Market +30, Enterprise +25, SMB +5 I2 region EMEA +15, NA +5 I3 industry Retail, Hospitality, Logistics or Healthcare +20 Facilities Services +10, Manufacturing +0 (after normalisation: trim, title case) I4 employees 200 to 1500 +15, above 1500 +10, below 200 +0 I5 history any prior Closed Lost opportunity +10 Tiers A at 70 and above, B 50 to 69, C below 50Write one suppression rule: an account with an open opportunity is suppressed, with the reason recorded. It is still scored.
Score these four accounts by hand, with a reason string for each:
ACC-02831,ACC-02885,ACC-03112,ACC-02995.Run the fire-rate check on rule I5 across all prospect accounts with no open opportunity, and decide what to do about it.
Starter brief (fill the gaps marked <<...>>):
OUTCOME
Score the four named accounts and print score, tier, reason, suppressed.
INPUTS
10-data/accounts.csv, 10-data/opportunities.csv
Rules: 40-reference/icp-rules.md
OUTPUT SHAPE
A table in the chat. Columns: account_id, account_name, score, tier, reason,
suppressed, suppression_reason.
The reason string format is <<write the exact format you want, with an example>>.
CONSTRAINTS
Normalise industry before comparing by <<which operations, in which order?>>.
An account is suppressed when <<state the condition, and say which file tells you>>.
<<does suppression change the score? say so explicitly>>
DEFINITION OF DONE
Four rows. Every row has a non-empty reason naming every rule that fired.
EXCEPTIONS RULE
<<what happens to an account whose industry value is not in your list at all?>>
If you get stuck
Hint 1: the idea
Two of the four accounts will surprise you, and both times the rules are working correctly. Before you call a score wrong, decide whether you disagree with the score or with the weights. Only one of those has a fix.
Hint 2: the move
Suppression is not in accounts.csv. Look in opportunities.csv for a row on that account whose
stage is not Closed Won or Closed Lost. Do the same lookup for I5, with the opposite test.
One of the four scores well and is suppressed. That combination is the most useful row in the output, not an error.
Hint 3: the shape
A correct answer spreads the four across all three tiers, and exactly one carries
suppressed = TRUE while still holding a score. Two are dragged down by the same rule: that is the
weight doing most of the work.
The fire-rate check on I5 should come back high enough that the rule separates almost nothing. When it does, change the rule. Do not be pleased about the coverage.
Check your answer
| account_id | account_name | score | tier | reason | suppressed |
|---|---|---|---|---|---|
| ACC-02831 | Westmoor Logistics GmbH | 90 | A | I1 Mid-Market +30 | I2 EMEA +15 | I3 Logistics +20 | I4 617 employees +15 | I5 prior Closed Lost OPP-007384 +10 | FALSE |
| ACC-02885 | Ardleigh Works BV | 70 | A | I1 Mid-Market +30 | I2 EMEA +15 | I3 Manufacturing +0 | I4 1,385 employees +15 | I5 prior Closed Lost OPP-007295 +10 | FALSE |
| ACC-03112 | Ardleigh Industries Inc | 20 | C | I1 SMB +5 | I2 NA +5 | I3 Manufacturing +0 | I4 138 employees +0 | I5 prior Closed Lost OPP-007338 +10 | FALSE |
| ACC-02995 | Selby Supply Chain BV | 80 | A | I1 Mid-Market +30 | I2 EMEA +15 | I3 Logistics +20 | I4 1,154 employees +15 | I5 no prior loss +0 | TRUE, open opportunity OPP-006969 |
Fire-rate check, rule I5: 154 of 163 prospect accounts with no open opportunity have a prior Closed Lost opportunity. 94.5%.
Your answer may legitimately differ: different weights give different totals, and the exercise only
asks that your arithmetic matches your own rules. What must match is the structure: four rows, every
reason string naming every rule including the +0 ones, and ACC-02995 scored and suppressed rather
than dropped. Omit the +0 rules and you cannot see which rule does nothing. If ACC-02995 is
missing entirely, your brief conflated scoring with filtering.
If ACC-02885 came out at 90 rather than 70, check whether you gave Manufacturing an industry
weight. That is a genuine choice, and it decides whether Ardleigh Works BV is on next quarter's
list.
Worth knowing: the rule that felt most insightful when you wrote it, "they have evaluated us before", fires on 94% of the population and changes nothing about the ranking. The rule doing the real work took ten seconds to write.
What you keep
40-reference/icp-rules.md: normalisation, five rules with weights, tier bands, the reason-string requirement, the suppression rule, and a fire-rate line per rule with the date it was last checked.
Check yourself
- Which of these is usable as an ICP rule, and rewrite the other: (a) "operations-led businesses
with complex scheduling needs"; (b)
employee_countbetween 200 and 1500 ANDregion = EMEA. - Your scoring output has a
score, atierand noreason. Sales says Tier A is wrong. What can you do, and what can you not do? - A rule fires on 3% of your population and contributes 25 points when it does. Problem? Say what you would check before answering.
Where this goes next
L7.3 writes the account research brief, then breaks it on the way research actually fails: a number that was true, from a source that said it was unverified, restated as a fact.