A deal-density heatmap is a layer you toggle on top of your CRM map showing where your pipeline actually lives. Red zones are deal clusters. Blue zones are empty ground. Built right, it answers three questions instantly: "Are deals evenly spread across our territory?", "Where are the geographic gaps?", and "Which postcode zones should we target next?". For most field-sales teams, a spreadsheet of deal counts per postcode does the same job. For teams with 50+ reps and $10M+ ARR in pipeline, a heatmap is the difference between a spreadsheet meeting and a sales-ops decision made in 30 seconds.
Why Visualisation Beats the Table
Tables are compressed. A list of 200 postcodes with deal counts is technically complete, but your brain doesn't see pattern. A heatmap makes pattern immediate. A sales manager glancing at the CRM map sees red clustering in the north-west, a blue void in the south-east, and the implication is clear: we've over-assigned to one region and under-served another. No calculation. No "let me sort by count and squint." Just red and blue telling you where to reallocate.
Velocity X's heatmap updates in Realtime. A new deal logs, Postgres aggregation fires, the heatmap cell flips from blue-grey to a deeper red. Territory reviews that used to run quarterly ("let me export the Q3 data and run the maths") now run monthly or on-demand. You catch imbalances before they become rep conflicts or territory churn.
How It Works: H3 Hex Binning
The architecture is straightforward. Velocity X geocodes every deal and lead. Postgres stores latitude + longitude. On heatmap render, the client sends a zoom level to the server. The server buckets every deal into Uber's H3 hexagon grid — each hex is a geographic cell sized to the zoom level. At country scale, hexes are 10+ km across. At city scale, 200m. For each hex, the server counts deals, sums pipeline value, and reports both. The client renders a Mapbox GL heatmap layer with opacity + hue driven by deal density.
Why hexagons instead of squares? Square grids have edge artifacts — boundaries between cells create visual noise. Hexes tile evenly and feel natural to the eye. H3 is mature (Uber's open-source standard), fast to query, and widely supported. Postgres ST_Contains + unroll loops through 50k deals in under 200ms per zoom level.
The Three Use Cases
Territory Rebalancing
Annual (or quarterly) territory reviews burn hours. Sales ops exports six months of deals, calculates deal density per polygon, compares against target splits, and proposes a redraw. Velocity X's Brain feature automates this. It runs the same aggregation nightly, detects imbalance (e.g. one rep sits on 2.5× the team's average deal count), and flags the sales ops person. A single approval redraws all territory boundaries using the same H3 hex data to ensure fairness. The downstream query (point-in-polygon for every customer) re-runs and updates ownership. One click instead of three days in Excel.
Gap Identification
Blue zones on the heatmap are white space. Zero deals, no prospect activity. Depending on your business model, blue might mean "untapped" or "genuinely uneconomical." A field-sales team for industrial equipment sees blue zones in rural areas with no manufacturing base — that's fine, expected. A B2B SaaS team targeting tech startups sees blue in areas where startups concentrate (SF, NYC, Austin, London). If their map shows blue in London, it signals: untapped market, rep capacity, or prospecting gap. The team can then decide: hire a London rep, run a targeted ad campaign, or decide London isn't worth the effort. The heatmap turns a vague "we should expand" into a data-backed decision.
Campaign Geo-Targeting
You're running a paid-ad campaign with a geo-targeting budget. Where do you allocate the spend? Velocity X's heatmap shows you which postcodes are high-pipeline, high-opportunity. Red zones are hot — existing pipeline density suggests prospect concentration. Ad spend in red zones reaches prospects who are already of interest to similar customers. Blue zones might be cheaper (lower ad competition), but your sales team has no infrastructure there. The heatmap makes the choice visible. Spend in red to compress sales cycles, or experiment in blue to test new regions.
The Data: Realtime + History
Velocity X's heatmap is dual-mode. Toggle "Realtime" and it shows live deals from the last 30 days — useful for daily standup and routing decisions. Toggle "Historical" and it shows 12 months of aggregated deals with a sliding-window view. This answers "where have we been winning" versus "where are we winning now." If your product portfolio shifts (adding an upmarket offering), the historical view shows where the old customers clustered and where the new product is gaining traction. Overlaying both reveals the geographic transition.
Frequently Asked Questions
Can I drill down into a hex to see the actual deals?
Yes. Click a hex, see a list of every deal in that cell. Useful for spot-checking territory boundaries or investigating why a particular postcode is hot.
What if our sales cycle is 12 months? Is the heatmap outdated?
Good question. Velocity X lets you define the cohort: "last 30 days", "last quarter", "last year", "deals closed in the last 90 days". The heatmap re-aggregates instantly. For long-cycle sales, you'll probably use 12-month windows. For SaaS, 30-day. It's flexible.
Does the heatmap include prospects or just deals?
Both, separately. Toggle "Deals" for live pipeline, "Prospects" for total addressable market in each region. Prospect density reveals white space; deal density reveals where you're actually winning. Compare the two, and you see conversion hotspots (regions where prospects → deals at high rate) and conversion deserts.
Can I export the heatmap data for board presentations?
Yes. CSV export of every hex with deal count, pipeline value, and postcode list. Also PNG of the visual — drops straight into slides.
What about teams that are fully remote or field-based with no fixed territory?
The heatmap still applies — it shows deal geography, not rep geography. Even remote teams benefit from seeing "70% of our deals cluster in three metro areas" because it informs hiring, campaign spend, and product focus.
How does this compare to Tableau or Looker dashboards?
Business-intelligence tools give you charts. Velocity X's heatmap is a layer on your working map — it's embedded in your daily tool, not a dashboard you alt-tab to. No data latency, no export/refresh cycle. Click the heatmap button, make a territory decision in seconds. BI tools are better for executive reporting; heatmaps are better for ops execution.
The Bottom Line
Deal-density heatmaps are a category that shouldn't require custom data engineering to build. Velocity X bundles H3 hexagon binning + Postgres aggregation + Mapbox GL rendering as a default layer on every CRM map. Toggle it on, see where your deals live, and make territory, hiring, and campaign decisions backed by instant geographic insight. For teams making territory calls on hunches or quarterly exports, a heatmap is a 30-second shift to data-driven. For teams already running geographic analysis, it's the tooling you've been building ad-hoc — now native to the platform.
If you're running Velocity X and your territory review is coming up, flip the heatmap on. You'll spot the imbalances before the meeting starts.