The irritation
RevOps teams need geographic ownership rules, but changing a territory can silently reassign companies, disrupt routing, and leave no trustworthy way to explain or undo the result.
ProductBuildingLive early access
TerritoryLogic
A live early-access HubSpot app for assigning U.S. ZIP codes to company sales territories and simulating ownership changes before any approved owner writes.
- Current state
- Building — Live early access
- Jack’s role
- Product architecture, Geospatial engineering, Cloud systems, HubSpot integration
- Find it in the workshop
- Systems & Maps Lab · Illuminated map table
Built because…
The real build story.
What I built
I built a ZIP-first HubSpot Marketplace app where teams assign whole U.S. ZIP5 codes to hierarchical company territories, combine them with CRM criteria, save revisions, simulate the exact record impact, and prepare guarded publication and rollback.
The hard part
The system has to preserve tenant isolation and immutable evidence while it re-reads HubSpot before every write, handles drift and retries, and refuses to publish when the saved simulation is no longer safe.
Under the casing
Proof, not decoration.
Build evidence03 items
- Exact U.S. ZIP5 membership with CRM criteria, overrides, locks, and owner pools
- Revision-bound simulation, guarded publication, write evidence, and rollback
- A live Cloudflare, PostgreSQL/PostGIS, and HubSpot early-access implementation
- MapLibre
- PostGIS
- Hono
- Cloudflare Workers
- Queues
- Workflows
- R2
- Hyperdrive
Scope of work
What I owned.
- Product architecture
- Geospatial engineering
- Cloud systems
- HubSpot integration
No victory-lap math
Outcome and lesson.
Where it landed
TerritoryLogic is live in public early access with self-service read-scope installation, a hosted console, company and ZIP sync, drafts, and read-only simulation. General live owner writes remain restricted to separately approved and reauthorized portals; paid billing and several release gates are unfinished.
What stayed
Operational software should make consequences visible before it changes a CRM. Simulation, final re-reads, recovery, and rollback are core product behavior, not back-office details.
This project has a physical address.
In the playable workshop, TerritoryLogic lives in the Systems & Maps Lab as a illuminated map table. You can inspect it without unlocking anything.