MapKraken
Territory Mapper
Territory management, simple. Territory Mapper builds Salesforce territories from census block groups, nests them to any depth, and assigns geocoded accounts to the territory that contains them.
The problem
A territory is a shape on a map and a row in your CRM. They drift.
Territory boundaries get drawn in a mapping tool, typed into a spreadsheet, approved in a slide, and then hand-maintained in Salesforce by whoever inherited the job. The map and the CRM agree on the day they are built and never again.
When a rep moves, the map is right and Salesforce is wrong for a quarter. Nobody finds the gap between two territories until an account in it goes unworked.
Coverage gaps nobody can see
The area no territory covers is invisible on a spreadsheet and obvious on a map.
Boundaries that only one person understands
Hand-drawn shapes have no definition anyone else can reproduce.
Assignments that fail quietly
A record that cannot be placed should land in a queue, not in nothing.
How it works
How it works
Select the geography
Click states, counties, tracts or block groups on the map. Box-select or lasso a region.
Make it a territory
The selection becomes one dissolved polygon with a name, inside a named territory model — "Sales", "Service", "FY27 Plan".
Nest it
Territories nest to whatever depth your organisation actually has. A branch can be built from counties while its sibling is built from block groups.
Let it assign
A geocoded account resolves to the territory that contains it, and the association is written back into Salesforce. Failures land in a queue you can work.
Differentiation
What is actually different, with the way to check it.
Territories built from census block groups, not ZIP codes
The smallest unit you can put in a territory is a US census block group — roughly 600 to 3,000 people. Every territory tool we have checked stops at the ZIP code, which is a mail-delivery route with no legal boundary and around nine thousand people in it. And one branch of a model can be counties while its sibling is block groups.
How to check this: eSpatial publishes ZIP as "the most granular boundary dataset available" (espatial.com, ZIP code mapping software). Salesforce Maps Territory Planning publishes Postal Code, 3-Digit Postal Code, State and County as its US container sets (Salesforce Help 000388999). Fullcast builds "from the country, state, and zip code levels" (fullcast.com). AlignStar could not be verified — see 26-F3. Verified 2026-08-09.
We publish what we do not have
Our security page carries a fifteen-row list of the controls we do not yet have — encryption at rest, HTTPS-only, SOC 2, a DPA — because a security page that lists only controls is a marketing page. Read it before you talk to us, not after.
How to check this: docs/security/trust-page.md §12, derived claim-by-claim from posture.md. Verified 2026-08-09.
Architecture
Where it runs, and what that means for your security team
In your org
A managed package holds the territory model, the assignment logic and the administrative setup.
In a Canvas frame
The map runs inside Salesforce. Writes to your data run as the signed-in user, with field-level security and sharing rules enforced by the platform.
On our infrastructure
A geospatial service on AWS does the spatial work. It holds census geography and the identifiers it needs to name a polygon. It holds no CRM records and no addresses.
Specification
Every row here is something you can test in a demo.
| Geographic units | State, county, census tract, census block group |
|---|---|
| Finest unit | Census block group (~600–3,000 people) |
| Territory depth | Unlimited nesting |
| Mixed resolution in one model | Yes — per branch |
| Territory geometry | Dissolved polygon, computed server-side |
| Assignment source object | Account |
| Assignment trigger | On geocode — when latitude and longitude first populate |
| Failure handling | Every failure is recorded in an exception queue in your org |
| Salesforce integration | Managed package + Canvas application |
| Geographic coverage | United States (US Census TIGER/Line) |
| Hosting | Amazon Web Services, us-east-1 |
And what it does not do yet
- Assignment runs on Accounts. Any Salesforce object that carries an address is on the roadmap.
- Geography is United States census boundaries. There is no international boundary set today.
- Territory Mapper is pre-release and has no production subscribers.
Talk to us
Tell us what you are trying to cover.
How many people work an area, how many records need assigning, and what breaks today. We will tell you whether Territory Mapper is the right shape for it.