Why the map is built on counties. The map answers a question about market,
not delivery. AEs sell CTV, streaming audio, digital display, social and search across
the entire DMA regardless of cable-wire coverage, and linear reaches non-wired ground through
the interconnect — so drawing the sellable world as a wire map would understate the
addressable market.
The base geography is the 17 counties of the Cleveland–Akron (Canton)
Nielsen DMA: Ashland, Ashtabula, Carroll, Cuyahoga, Erie, Geauga, Holmes, Huron,
Lake, Lorain, Medina, Portage, Richland, Stark, Summit, Tuscarawas, Wayne. Counties are
non-overlapping, they cover the market completely, they are the unit every syndicated
source (Scarborough, BIA, Vivvix, IBISWorld, CBP) already cuts by, and they are a unit
an AE can actually be assigned.
Strategy scoring sits on the accounts, not the county. Client-level Keep/Grow
and prospect-level Get are more actionable than a single blended county score, and they
don’t average opposite situations into a middling number. This is documented in full
under Get / Keep / Grow — how & why above.
Geography. County boundaries are the Census 2023 cartographic boundary file
(cb_2023_us_county_500k, NAD83), simplified to roughly 80m and rounded to 5 decimal
places — visually identical at DMA zoom, and the whole 17-county layer costs 21 KB.
Nothing is drawn by hand.
Demographics — read this before quoting a number in the room. All
demographics are ACS 2020–2024 5-year, computed at county level.
They will not tie to the Market Map 2026 deck. The deck’s
figures are TruAudience, published per zone only; re-cutting them to counties would mean
inventing a weighted average, which is exactly the fabrication this tool has refused
throughout. Census is the only source that reports natively at county geography, so it is
the only internally consistent choice once zones are gone. The visible difference is
median age: the deck reads ~56 per zone, Census reads ~41 DMA-wide, because the deck’s
figure is on a different base (adult or head-of-household, not whole population). Income,
education and homeownership track much more closely. If someone has the deck open next to
this tool, that is the discrepancy they will find.
• Population growth is Census PEP 2020→2024 — annual estimates,
clean non-overlapping endpoints.
• Income growth compares ACS 2017–21 to ACS 2020–24 medians.
The vintages overlap by two years, so it is directional only, not a clean delta.
• Business density, business base growth and vertical variety are County
Business Patterns 2023 and 2019, restricted to the 11 locally-advertising sectors.
• Hispanic population index is county Hispanic share indexed to the
17-county DMA aggregate = 100, so 138 means Cuyahoga is 38% above the DMA rate —
not a national index.
• Unemployment is ACS (unemployed / civilian labor force), so that every
demographic on the map comes from one source at one geography.
Sample data. Every client, prospect, revenue and budget
figure in this tool is fictional and flagged SAMPLE DATA wherever it appears. The 211
sample clients and 261 sample prospects were redistributed from the old zones to counties
by seeded draw from each zone’s real ZIP→county distribution, so an Akron book
lands in Summit rather than at random. The prospect universe contains the client
book — clients appear with status “Client” and their SR revenue —
so captured + whitespace = addressable and the two panel modes reconcile county by
county. County budgets were split from the old zone targets in proportion to where each
zone’s book landed. A real build replaces all of it with CRM and Sales Ops extracts
joined to a competitive-spend source (Vivvix/Kantar) and a business file (D&B, Data
Axle). What is real: all geography, all demographics, and the entire county
tailwind that drives half of every Get score.
Panel modes. The AE Interface is the inward view — the existing book
in a county, budget attainment, wallet share, and each client’s Keep/Grow posture.
The Prospecting Tool is the outward view — the county tailwind, every tracked
business whether or not it is a client, addressable spend, whitespace, and ranked Get
targets. Toggling modes never changes the map: identical counties, colors, filters and
selection; only the right-hand panel re-renders.
Budget & sales plan. Each county carries an annual revenue target. The AE panel
shows budget vs. booked, an attainment bar and the variance —
green over plan, red under —
measured on the full book, so it does not move when filters change. Any county under plan
gets a Sales plan: its open accounts in Get-priority order, each sized at
open whitespace × the county’s own share of wallet × close probability
(10–45%, from the fit score), stacked until weighted pipeline reaches 2.5× the
gap — a coverage ratio, because most opportunities don’t close. Where a
county’s whole prospect file can’t carry that, the panel says so rather than
inventing a plan. The close-rate curve and the 2.5× coverage
ratio are assumptions pending calibration against real win rates.
Color scale. Green = favorable, red = unfavorable, and each metric declares a
direction so “good” is always green (low unemployment maps to green). Purely
descriptive demographics — median age, households with children, homeownership,
race/ethnicity, build year — use a neutral light-to-dark blue ramp instead: painting
population attributes as good or bad would be misleading, and a bad look in an SLT room.
Nothing on the map is a strategy score.
Basemap © OpenStreetMap contributors © CARTO.
This visualizer was created by George Lee.