3. Market Map
(the transcript is below)
Action Step
Complete this before moving on.
Watch the full overview video above and read through the transcript below. As you go through, pay attention to the difference between having an ICP and having an operationalized ICP, and how tiering and valuation change the way reps prioritize accounts.
Part 1: Hook / Open
A CRO sits down with a new sales rep on their first day and says "here's your territory, go find deals."
The rep opens the CRM and sees 1.3 million accounts. No tiering, no prioritization, no signal on who to call first.
So they do what every rep does in that situation — they cherry pick. They Google around. They ask the rep next to them "who are the good accounts?"
That's what the CRM looks like at a lot of the companies we work with — a million accounts and no way to tell who matters — and the project that solves it is what we call the Market Map.
Market Map is the infrastructure that takes a company's ICP from a Google Doc sitting somewhere into the CRM and turns it into every account tiered, valued, and enriched so sales actually knows where to focus.
My name is Yasin from LeanScale, and in this video I'm going to break down for you our entire Market Map Playbook... what it is, the core concepts, how it gets built, and what changes once it's in place.
Part 2: What Market Map Is
So when we talk about the Market Map project, what we're actually building under the hood is a scored, tiered, and valued account universe inside the CRM, powered by an enrichment engine in Clay.
On the input side of this project there's the company's existing CRM data, their closed won and closed lost history, firmographic data, technographic data, and whatever ICP definition the team has — even if it's informal or tribal knowledge.
On the output side, once the project is complete, every account in the total addressable market has been pulled, enriched, scored against the ICP, assigned a tier — T1, T2, T3 — and given a dollar valuation. And every target persona at those accounts has been identified and loaded with contact data.
Now here's what changes once it's built: every new account gets scored the same way. Every account that enters the CRM gets run through the same enrichment and scoring logic — no one is manually tagging accounts, no one is eyeballing fit.
The way we describe it to clients is that Market Map is like surveying a mountain range before sending your miners in.
Without it, you're sending reps out to dig in random mountains. One rep comes back with a wheelbarrow of gold, another comes back empty handed, and the third finds a train-load — but nobody figured out where the gold actually was before they started digging.
Market Map surveys every mountain first — how much gold is in each one, which ones are worth sending your best people to, and which ones to skip entirely. Then you assign territories based on actual value, not guesswork.
Part 3: Market Map Pro Tips
Now the Playbooks Library below this video goes deep on the full methodology behind the Market Map project — but before we get into how it gets built, here are a couple things you really don't want to get wrong when implementing this into a startup.
First — having an ICP is not the same as having an operationalized ICP. Almost every company we work with says "we already have our ICP." And they probably do have pieces of it. But the question is whether every criterion in that ICP is enrichable through a data provider and scoreable by automation. If a machine can't look at an account and grade it against the ICP, it's not operationalized — it's tribal knowledge.
Second — do not skip straight to Clay enrichment without defining the ICP matrix first. The sequence matters. If you start enriching accounts before you've locked the scoring rubric, you're burning credits on accounts that don't matter and your reps still won't know who to call. ICP matrix first, valuation second, fit score third, then enrichment.
Third — TAM does not equal target list. A lot of companies confuse their total addressable market with a usable account list. If a rep has 10,000 accounts assigned to them, those aren't "best fit" accounts, those are just "accounts." The sweet spot we see across implementations is 50 to 2,000 accounts per rep for T1. Anything above that and the criteria are too loose.
Part 4: The Problem in Context
And this isn't just theory, we actually have data on this.
Earlier this year we helped Fullcast publish a 2025 report on exactly this problem. The report analyzed 440,000 opportunities worth 43 billion dollars.
Here's what the report found: only 23% of pipeline actually fits ICP — meaning 77% of the deals sitting in pipeline right now are wrong fit.
That same research found that wrong-fit deals are 8x harder to close. Longer sales cycles, lower win rates, more resources burned on deals that were never going to happen.
And 77% of sellers missed quota in 2025, even after companies cut quotas by 13%.
Meanwhile, 63% of CROs admit they have little or no confidence in their own ICP definition.
So it's not that companies don't have an ICP — it's that the ICP isn't in the systems. Sales can't filter for it, marketing can't segment on it, leadership can't validate territory assignments against it, and finance can't tie quota targets to actual TAM data when the board asks whether the plan is realistic.
Part 5: How It Gets Built
So how does a Market Map project actually get implemented?
At LeanScale, for all of our projects, we follow a four-phase approach — Strategy, Engineering, Enablement, and Handoff.
Strategy
In the Market Map project, like in most of our projects, strategy is the phase that matters most.
This is where we work with the stakeholders — the CRO, VP of Sales, RevOps manager, sometimes marketing leadership — step back and define what we call the ICP vectors. These are the 5 to 10 criteria that define an ideal customer — geography, firmographics, technographics, company size, industry, custom signals like number of locations or funding stage — every criterion that matters for this specific company.
The reason this is critical is that every criterion must be enrichable. It's not enough to say "we sell to mid-market companies" — the system needs to be able to look at an account and score it. If a data provider can't return that data point, it can't be part of the scoring rubric.
From there, we define the valuation methodology — how much is each account actually worth to the business. This could be based on employee headcount for per-seat products, revenue coefficient for usage-based pricing, or product-specific signals. And we lock the fit score rubric — a point-based system where each criterion gets weighted, and tier thresholds get set so T1 means 75 to 100 points, T2 is 50 to 74, T3 is below that.
Before the project even kicks off, our team scrapes the company's existing CRM data — closed won history, closed lost patterns, current account universe — and assembles a V1 of what the ICP matrix and valuation model should look like, based off best practices from having built this project for dozens of startups, combined with the unique data from the team we're working with.
We also lean heavily on AI agents throughout this process — agents trained on our playbooks that know how to pull CRM exports, run correlation analysis on win rates by segment, and draft a V1 ICP matrix with scoring rubrics. We go deeper into how we use AI in the implementation of this project in the full playbooks in the library.
From there, we iterate on that V1 with the stakeholders and at the end of that process, four things are locked in: the ICP matrix with tier definitions, the valuation methodology, the fit score rubric, and the list scope — whether we're pulling full TAM, tiered accounts, or T1 only.
Engineering
Phase two is the technical build.
This is where the Clay tables, the enrichment workflows, the CRM fields, and the scoring logic actually get created inside the systems.
We built a 6-part build sequence that covers everything from setting up the master Clay account table with all criteria columns, to pulling accounts through Clay Searcher and CRM imports, to enriching firmographic and technographic data through waterfall providers like Apollo, Clearbit, and vertical-specific sources, to calculating fit scores and valuations, all the way through to pushing tiered and valued accounts into the CRM with full field mapping.
Then comes persona enrichment — identifying the actual people at those accounts that reps need to contact. We build a persona scoring rubric that mirrors the account scoring, pull contacts using Clay's People Search, enrich contact data, and load personas into the CRM linked to their tiered accounts.
So what's changed in the agentic AI era for engineering implementation on this project?
We've built a Market Map Agent that uses JSON files in a database with all of the ICP scoring rubrics, tiering logic, and territory segmentation rules codified. Using APIs and MCPs, that agent connects directly to the CRM — whether that's Salesforce or HubSpot — and enrichment platforms like Clay and ZoomInfo, and starts building out the account scoring fields, tier assignments, and territory views from the strategic output.
What used to be a 40 to 80 hour manual engineering effort now gets delivered in a fraction of the time because the agents handle the repetitive table setup, field creation, and enrichment orchestration while our human engineers focus on quality assurance, orchestration, and the custom criteria enrichment.
The full details of the AI agents we use and the 6-part build process are broken down inside the playbook library if you're curious.
Enablement
Phase three is enablement, because the system is useless if the team doesn't know how to use it.
For Market Map specifically:
We train RevOps on how to maintain the Clay tables — running incremental enrichment, adding new accounts, updating ICP criteria, monitoring credit usage, and troubleshooting sync issues.
We train sales leadership on how to use the CRM reports — filtering by tier, building outbound lists, assigning territories based on valuation, and tracking closed won and lost by tier over time.
And we train marketing on segmenting audiences by tier for campaigns, building targeted lists, and tracking conversion rates by tier so they can see which segments are actually responding.
Handoff
From there, phase four is the handoff, and this is where maintenance expectations get set.
Now one thing worth knowing — Market Map is not a one-time project.
It requires monthly maintenance to keep the data accurate — incremental enrichment for new accounts entering the CRM, credit monitoring in Clay, data quality checks for duplicates and missing fields, and quarterly persona coverage refreshes to catch new contacts who've joined T1 accounts.
And here's why that matters: every time a rep closes or loses a deal, every time the product pricing changes, every time the team hires new reps and territories need rebalancing — someone needs to update the model.
If nobody owns that, what happens is the tiering drifts. New accounts come in unscored. Reps start ignoring the tiers because they stopped matching reality three months ago. Marketing segments off stale data. And leadership is setting quotas against a TAM model that hasn't been validated since it was built.
After one full sales cycle — typically 30 to 90 days — we recommend pulling a report on closed won and lost by tier. If the team is closing more T3 accounts than T1, that's a signal the ICP criteria need adjustment. And at minimum, the ICP should be validated twice a year — at the halfway point and during planning season.
So the handoff isn't just about transferring ownership — it's about making sure after we've finished the build... someone on the team understands the system deeply enough to keep it accurate.
Part 6: What It Unlocks + Close
So let's bring this all together to where we started. Once the Market Map project is in place, what actually changes?
Reps open the CRM and instead of 1.3 million accounts with no direction, they see a prioritized universe — T1 accounts with Tier 1 personas loaded, fit scores visible, valuations assigned. They filter, they sequence, they work.
Territory design goes from arbitrary to equitable. Every rep gets a territory valued based on actual account potential, not geography or gut feel. Leadership can prove territories are fair by showing the valuation distribution.
And marketing stops enriching everything and starts enriching only ICP-qualified accounts — focused targeting, smarter credit spend, higher conversion rates because campaigns are segmented by tier instead of blasted at the whole database.
And the biggest thing that changes after this project is knowing exactly where to point the team.
That CRO who got asked "what's our ICP?" now has a data-backed answer sitting in the CRM. Not a Google Doc, not a slide from last year's offsite — actual infrastructure powering the systems. The board asks whether quotas are realistic, and there's TAM data to back it up. Reps stop cherry picking and start working a system.
Everything covered in this video about this project — the concepts, the methodology, the full implementation process — all of it is broken down in detail in our Playbooks Library for each project. Our Advisory Overview Playbook covers the problem, approaches, and strategic understanding behind this project. The Methodology Playbook goes deep on every concept we talked about for this project. And the Implementation walks through the step-by-step build process.
And if you're a revenue leader at a fast growing startup who's feeling good about the targeting side after watching this — but you're thinking, okay, now how do I turn that into real quota targets and a pipeline plan that actually holds up — we have a whole playbook on exactly that called the Growth Model. It's broken down the same way in our Playbook Library. And while you're there, you'll see we have playbooks on every major GTM project — from Automated Inbound and Attribution to Quote to Cash and more. Feel free to check those out next.
Again, this is Yasin from LeanScale, and I'll see you in the next one!
Comment in Slack
Post your answer in your onboarding channel.
What did you learn? What clicked?
Any questions — or will you have more questions once you actually get into the hands-on trainings? Either is fine. Just capture where you are right now.