MapKraken
Geospatial workflows and data that deliver the value of your location.
We build the software that turns where your customers are into who is responsible for them. Territory Mapper is the first of them.
Release the power of location.
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
Four steps, in the order you actually do them.
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.
Why this and not the others
Two things that are true of us and checkable.
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.
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.
Validated against Salesforce Maps, eSpatial, AlignStar and Fullcast on 2026-08-09. Two claims we started with did not survive that check and are not on this page.
Products
One product today. The shelf is built for more.
What’s next
Roadmap, not product. Neither of these exists yet and neither has a date.
- Optimization Engine Balance territories by revenue, workload and travel time.
- Planning Copilot Describe the outcome you want; get scenarios with the tradeoffs explained.
Security and trust
We publish what we do not have.
Our security page describes the architecture, names every third party in the path, lists exactly what the geospatial service stores — and carries a fifteen-row register of the controls we do not have yet. If one of them is a blocker for you, we would rather you find it in the first conversation than the fourth.
Pricing
Licensed to the organisation, not to the map.
Tell us your seat count, your object volume, and how many people actually edit boundaries, and we will quote it.
- Your organisationOne Salesforce org, one territory estate.
- Who editsThe people who build and change territory models.
- Who looksEveryone who needs to see a territory on a map.
Pricing is not published while Territory Mapper is pre-release.
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.