See every location on the map
Import coordinate-based data from the files your team already uses.
Build territory maps from your own data
Upload CSV, Excel, KML, or KMZ files. Draw and edit custom territories, then watch counts, category breakdowns, and overlaps update the moment your boundaries change.
No account required · Uploaded project data is processed in your browser
Zone analytics
Group by: Segment
North Ridge12
Metro District14
Harbor10
East Vale14
In overlapping zones2
EnterpriseMid-marketSMB
Your locations, territories, and analytics in one workspace — watch the counts update as the boundary moves.
CSV importExcel XLSX & XLSKML & KMZCustom polygonsCircle zonesLive analyticsCategory breakdownOverlap detectionMetrics CSVGeoJSON exportPortable project fileCSV importExcel XLSX & XLSKML & KMZCustom polygonsCircle zonesLive analyticsCategory breakdownOverlap detectionMetrics CSVGeoJSON exportPortable project file
The problem
Stop managing territories across disconnected tools
When your locations live in a spreadsheet and your boundaries live in a separate map, every change creates another round of manual checking. TerritoryKit keeps the data, zones, and results together.
Change a boundary without starting over
Reshape a territory and let the zone results recalculate around the new boundary.
Compare territories with real numbers
Review totals, category breakdowns, and overlapping assignments in one place.
How it works
From source file to territory map in three steps
01
Import your data
Add a CSV, Excel, KML, or KMZ file. For spreadsheets, choose the latitude and longitude columns that place each record.
02
Draw and refine
Create polygons or circles, then rename, recolor, reshape, duplicate, merge, or split them as the plan changes.
03
Analyze and export
Compare zone counts, group by a field, inspect overlaps, and export metrics, membership, or GeoJSON.
Live zone analytics
The numbers move with the boundaries
Select the point layer and territory layer you want to compare. When you edit a zone, TerritoryKit recalculates the records inside it so the map and the analysis stay aligned.
Total locations per zone
Category breakdowns by field
Records in overlapping zones
Boundary points counted consistently
North Ridge now12locations inside the boundary
In the overlap2counted in more than one zone
These numbers are live. Watch them change in the demo at the top of the page.
Features
Everything you need to create and understand custom territories
Import the data you already have
Start with CSV, XLSX, XLS, KML, or KMZ files instead of rebuilding your project in a new format.
Draw boundaries that fit reality
Create free-form polygons or circles rather than being limited to predefined administrative regions.
Revise plans quickly
Rename, recolor, reshape, duplicate, merge, split, or delete territories without rebuilding the map.
Measure every zone
See how many locations fall inside each territory and compare the results across the map.
Go beyond total counts
Group records by a chosen field to understand how categories are distributed within each territory.
Make overlaps visible
Identify records that fall inside more than one territory instead of leaving conflicts hidden.
Keep layers organized
Separate point data, analysis territories, and reference geography so complex projects stay manageable.
Save and continue later
Export a portable TerritoryKit project file and reopen it when you are ready to continue.
Take the results with you
Export territory metrics and point membership as CSV, or export zone geometry as GeoJSON or KML.
Use cases
One workflow for several planning needs
Use case
Sales territory planning
Map customers, prospects, accounts, or branches, draw sales regions, and compare how records are distributed between territories.
Build a sales territory mapLocal-first workflow
Work with project data in your browser
TerritoryKit processes uploaded project data locally in the browser. There is no account or cloud workspace required for the current product. Export a portable project file when you want to continue later or move the work to another computer.
No account required
Local browser processing
Portable project files
User-controlled exports
Formats
Bring in the source data. Take out the results.
Spreadsheet data
CSV, XLSX, and XLS files containing latitude and longitude columns.
Geographic data
KML and KMZ files for existing geographic information.
Save and resume
Portable TerritoryKit project file.
Export analysis
Territory metrics CSV and point-to-territory membership CSV.
Export geometry
Territory GeoJSON and KML.
The current version does not convert street addresses into coordinates or import shapefiles.
Frequently asked questions
Build your first territory map
Bring your coordinates, draw the zones you need, and see the results as the map changes.
Open Map BuilderNo account required