Territory changes happen once, on a map, and propagate everywhere. The CRM, the warehouse, and the AI agents all agree on which franchise serves which ZIP — and anyone can check in seconds, with a log to prove it.
Our Work Home-services franchise network
Franchise territories, synced from the CRM to a map
An internal platform that keeps franchise locations in sync with GoHighLevel, assigns ZIP codes to territories on an interactive map, and answers 'which franchise serves this address?' for every other system.
17 tools
Exposed to the network's AI agents
01 · THE PROBLEM
Which franchise serves this ZIP code?
Locations lived in GoHighLevel, territories in spreadsheets, calendars were edited one at a time — and every application in the network had its own answer.
Source of truth
Where is the territory map?
ZIP assignments needed one authoritative home that every other system could read from.
Sync
Do the CRM and the warehouse agree?
Locations, calendars, and territories had to flow both ways without anyone re-typing them.
Speed
How long does a territory change take?
Selling a territory or moving a ZIP meant touching several systems by hand.
02 · THE APPROACH
Change it once. Everywhere agrees.
- i.
Sync locations from the CRM.
Franchise sub-locations pull from GoHighLevel automatically, and booking hours are edited across many calendars at once.
- ii.
Draw territories on a real map.
Census ZIP boundaries, color-coded by status, with click, polygon, and bulk assignment — and conflict detection so two franchises can't claim the same ZIP.
- iii.
Publish one answer.
A lookup API resolves any ZIP to its franchise, falls back to the nearest one, and syncs both ways with the central warehouse.
03 · SYSTEM ARCHITECTURE
GoHighLevel
Franchise sub-locations · booking calendars
Franchise operations platform
Territory map · booking groups · lookup API · audit
Central data warehouse
Bidirectional sync · shared by every application
Also connected
Public ZIP lookup APIMCP server · 17 toolsScheduling systemGoogle sign-in (invite-only)
04 · CORE CAPABILITIES
What the system does.
CAP 01 · Territory map
ZIPs on real boundaries
Census ZCTA polygons color-coded by status — sold, temporary, unassigned — with search by ZIP, city, or state and multi-select bulk reassignment.
CAP 02 · GHL sync
Locations and calendars
Automated sub-location sync and a visual weekly calendar editor with click-and-drag selection across multiple calendars.
CAP 03 · Lookup API
One answer for every system
ZIP → franchise, territory, and booking group. Nearest-franchise fallback by distance, full request logging, and a stats dashboard.
CAP 04 · Warehouse sync
Two-way, chunked, tracked
Auto and bulk sync with dirty-record tracking and chunked processing, so every application sees the same data.
CAP 05 · AI-ready
17 MCP tools
Franchises, territories, booking groups, lookups, sync status, and audit logs exposed to the network's AI agent hub.
CAP 06 · Governance
Auditable by default
Invite-only Google sign-in with admin and viewer roles, and a full audit trail of every create, update, delete, import, and sync.
Change it once. Everywhere agrees.
Assign
Every ZIP has exactly one franchise.
Sync
CRM, warehouse, and AI agents stay in step.
Prove
A log behind every lookup and every change.
05 · THE RESULT
What changed.
06 · TECHNOLOGY FOUNDATION
Built on.
Frontend
React 18TypeScriptWouterTanStack Queryshadcn/uiTailwind CSSLeafletTurf
Backend
Node.jsExpressTypeScriptPassport.jsGoogle OAuth 2.0MulterPapaParseZod
Data & connections
PostgreSQLDrizzle ORMGoHighLevel APIData warehouse syncMCP SDK
Have a process like this one?
Book a free discovery call. We'll map it, tell you what to automate first, and what it's worth to your business.
Book a Free Discovery Call