By Township Canada
Launching Territory & Prospecting — Polygon Search + CSV Export for Ag Sales Teams
Draw a polygon, get every quarter section inside with crop history and soil productivity, export to CSV with Salesforce / HubSpot column mapping. Ag Investor only.
A territory manager at a crop input retailer covers 200 km by 150 km — six RMs around the dealership. The customer book lives in Salesforce with legal land descriptions in the address field. Without a map, the territory manager works from memory: which growers are clustered, which corridors are under-served, which parcels are growing the inputs the retailer sells.
The new Territory & Prospecting tool at /app/territory lets the territory manager draw a polygon over the territory, get every quarter section inside it with dominant crop and LSRS productivity, and export the list to CSV pre-mapped for Salesforce / HubSpot import. Five minutes of work; replaces an afternoon of standalone GIS.
What ships
A workspace at /app/territory with:
Polygon drawing. Click vertices, double-click to close. The drawn polygon snaps cleanly to the zoom level you're at — province scale or RM scale. Uses the same terra-draw library as the existing measurement tool, so the UX is consistent.
Saved territories sidebar. Name a drawn polygon (e.g., "Central Alberta — Lacombe corridor"), save it, come back to it. Each Investor account can save up to 25 named territories.
Parcel list with joined data. Clicking a saved territory runs the spatial query: every parcel centroid inside the polygon, joined to the LSRS productivity layer (AB) and the AAFC crop summary layer (AB + SK). Returns legal land description, coordinates, area in acres, LSRS score, dominant crop, plus summary stats: parcel count, total acres, dominant-crop breakdown by % area, weighted-average LSRS productivity.
CSV export with CRM column mapping. One click downloads a CSV with column headers pre-mapped for Salesforce Account / Lead import and HubSpot Lead / Contact / Custom Object import. RFC-4180 CRLF row separators, properly escaped commas / quotes / newlines. Drops in without remapping. See Import an Ag Territory into Salesforce or HubSpot.
Tier — Investor only
The Territory tool is the Ag Investor tier's primary differentiator. At $100 CAD/month it's the entry point to polygon-scale workflows; Ag Farmer at $50/mo gets all the parcel-report and overlay features but not the polygon tool.
Server-side gating: every endpoint goes through requireAgPlan(event, PLAN_AG_INVESTOR). Non-Investor users hit the page and see an upgrade gate that routes to /pricing.
Use cases
Crop input retailer territory mapping. Draw the dealership coverage area. Filter the parcel list to canola-dominant + LSRS class 1-2. That's the prospecting universe — already cropping the input you sell, on productive ground. Export to CSV, drop into Salesforce.
Grain company catchment. Draw a 50km radius around an elevator. Get every quarter section inside, ranked by total acres and dominant crop. Lower-LSRS rotation-cycling growers vs. higher-LSRS continuous-canola operators have different delivery profiles — useful for grower outreach prioritization.
Farmland investor portfolio screening. Draw the geographic area you're shopping. Summary stats give a productivity-distribution read; per-parcel detail feeds the individual diligence at /parcel/[lld].
Carbon project boundary scoping. Draw the candidate project boundary. The dominant_crop column tells you the existing rotation; the LSRS column tells you the productivity baseline. Both inputs to the TIER Conservation Cropping protocol.
What's not in the CSV (yet)
The account_name column is left blank by design. Operator-name inference from AAFC crop continuity and provincial registry data is pending legal sign-off on the inference methodology (OQ-6 in the Ag Bundle PRD). The column structure is ready for it; the data isn't surfaced until legal clears the methodology.
For now, the post-import workflow is: bulk-fill account_name with placeholder values, then cross-reference via ISC Map Search (Saskatchewan), SPIN (Alberta), or LTSA (British Columbia) for the actual owner / operator. The CSV gives you everything except the operator name; the operator-name diligence is one extra step.
Caps and limits
- Saved territories: 25 per Investor account
- Parcels per query: 5000. A multi-RM polygon that exceeds the cap returns
truncated: trueand the UI surfaces a "split the territory" suggestion.
Try it
Investors can open the workspace directly at /app/territory. Anyone else can see the feature page or read the retailer use case.