Why the territory plan you write in April is the one that lands in July
Every field sales team inherits a territory plan in January that was agreed in December and built in October. By April the plan has drifted. Two reps have left. Three hires have joined. A cluster of accounts the January plan treated as a single patch has split into two buying profiles. A postcode that carried a quarter of the region's pipeline last year carries a tenth of it now. The plan is still on the deck. The deck is no longer the map.
May and June are when a field sales leader either fixes that drift or accepts it until next January. A proper territory re-plan for Q3 has to land before the 1 July start date. Working backwards, the decisions need to reach procurement by mid-June. The decisions themselves need two solid weeks of work. That puts the real kick-off somewhere in the last days of April or the first days of May. Later than that and you are shipping the new territory cold to reps in the field on a Monday morning in July. Which tends not to end well.
The exercise is not a spreadsheet exercise. It was treated as one for a decade. The symptoms of that are visible in every territory meeting that runs over by an hour. The exercise is a geographic exercise. Accounts sit somewhere. Routes run between those places. Rep capacity is bounded by drive time. A map is the only honest canvas for the conversation. A spreadsheet gives the illusion of control. It then breaks the moment a stakeholder asks what the change looks like on the ground.
This piece is the playbook Pin Drop has seen work across hundreds of field sales teams moving their territory plan onto a map ahead of Q3. Who runs it. What to write down first. How to sequence the conversations so the plan reaches procurement in time. How to avoid the two or three small mistakes that cost teams a month of pipeline in August every year.
If you run revenue operations, the Q3 territory plan is your deliverable whether it says so on your job description or not. You are the one who owns the data. You are the one who knows that the January plan assumed 18 reps and is being run by 14. Four of the accounts on last year's top-quartile list are in administration. The plan on the deck does not reflect any of this.
Pull three things before the re-plan kicks off. A clean account master with last-year revenue, pipeline stage and last-contact date. A live rep capacity model: how many working days each rep has between 1 July and 30 September, not how many days the HR system says they have. A current route density read for each patch. The Pin Drop post on route planning for sales teams sets out the route-to-target maths in detail. Read it before the kick-off meeting.
If you manage the field sales team day to day, you are the one who has to defend the re-plan in front of reps who have been working the current patch for two years. You know which accounts are worked because they are easy. You know which accounts are worked because the rep actually believes in the product. The difference matters. A territory redrawn only on past revenue misses the second group entirely.
Spend the first two days of the exercise riding with one experienced rep and one new rep. Do not open the map while you are with them. Watch how they decide where to go next. When you get back to your desk, read the Pin Drop guide on moving from spreadsheets to maps. Most of the friction the experienced rep has worked around is the friction the map is about to remove.
If you sit in finance, the territory re-plan is where half of next year's commission envelope gets decided, even though the conversation usually feels like an operations one. The number that matters is not the headline quota. The number that matters is route density. A patch that a rep can cover in two days costs the business half the drive time of a patch that needs four days. Multiplied across 14 reps across 13 weeks, that gap is rarely small. The annual effect of a good re-plan is usually several multiples of the mapping software budget that unlocks it.
Q2 is also the quiet budget window. The back-half freeze lands in September for most organisations. A tool switch decided in May reaches live status in June with a fortnight of margin. A tool switch decided in July does not land until January. Pin Drop's Salesforce Maps alternative comparison sets out the cost-to-switch conversation in full. The Google My Maps alternative piece covers the same ground for teams moving off a free tool. Both are worth a read before you price the re-plan.
The two-week Q3 territory re-plan, day by day
The exercise fits into ten working days. Seven of those days are actual work. The other three are the buffer everyone always needs for the conversations that run long. Here is the shape Pin Drop has seen land cleanly across field sales teams of roughly 10 to 150 reps. Scale it up if you are larger. For a team below 10 the plan finishes on day six.
Days 1 to 2: baseline the map
Do not open a spreadsheet on day one. Open a live map. Import the account master as pins, coloured by last-year revenue band. Import the current territory polygons so every pin sits inside whichever rep's patch it currently belongs to. Add last-quarter activity as a second layer: visits logged, meetings booked, opportunities opened.
Three things jump out within the first hour of looking at the map. The first is account density. You will see a cluster of pins in one postcode area that is carrying twice the revenue of the rep whose patch contains it. The second is route waste. You will see reps whose January polygon stretches 70 miles across two motorway junctions for a handful of accounts that could sit in the neighbour's patch with no loss. The third is coverage gaps. Postcodes that the January plan included in a patch but where nothing has happened since March.
Write each of these down on a specific pin. Not as a memo. As a note on the map. Day one ends with a map that tells the truth about the current territory, rather than a plan that no longer matches it.
Days 3 to 4: shadow and listen
Get out of the office. Ride with one experienced rep for a day. Ride with one rep who joined since January for a day. Do not open the map while you are with them. Take paper notes. Watch the three moments that matter.
The first moment is the pre-work scan. The five minutes before the rep leaves the first site of the day. What are they looking at? What are they deciding? Where does the decision live?
The second moment is the recovery moment. A meeting collapses. The next two hours are cold. Watch what the rep does. A good rep has a mental model of which neighbouring accounts are worth a cold stop. A great rep has that model written down somewhere the team can see. Most reps have it nowhere at all.
The third moment is the end-of-day write-up. Watch what gets logged in the CRM. Watch what gets kept in a notebook. Watch what goes nowhere. The gap between the three is where the next territory plan needs to get smarter.
At the end of day four you should have a short list of six to eight specific moments where the current plan was the friction. Keep the list specific. "The rep runs a Notes app list of the three nearest accounts to every scheduled meeting because the tool does not show proximity" is useful. "The tool is bad" is not.
Days 5 to 6: redraw the patches
Now sit with the map and the friction list. Redraw the polygons. Three rules keep the re-plan honest.
- Patch by drive time, not distance. A patch that reads as 40 miles across on a map might take a rep 45 minutes or two hours depending on motorway access. Drive time is the real bound. If the mapping tool cannot give you drive-time isochrones, the tool is in the way of the plan.
- Density before equity. A patch that carries four times the revenue of its neighbour but half the accounts is a good patch. The temptation to flatten account counts across reps is strong. Resist it. Pipeline follows density rather than equity.
- Keep the trust relationships intact. Every experienced rep has three or four account relationships that took eighteen months to build. Those relationships do not transfer well on 1 July. Protect them in the re-plan even at the cost of clean polygon lines. The revenue loss from breaking a long trust relationship is rarely recovered in the same financial year.
By the end of day six the new polygons should be on the map. Each polygon carries four attributes:
- A named rep
- A drive-time estimate for the full patch
- A revenue expectation for the quarter
- A written note of the three trust relationships that stay with that rep regardless of polygon geometry
Days 7 to 8: stress-test the plan against the field
Bring two or three reps back in. Not in a boardroom. In front of the live map. Walk them through the new polygon that affects their patch. Let them redline it in real time on the shared map.
Every territory plan survives the stress test with two or three adjustments. That is the point of the stress test. The adjustments are not a failure of the plan. They are the working knowledge of the field reaching the plan before it goes live rather than afterwards. A plan that reaches reps on 1 July with no redlining has not been stress-tested. It has been published.
The shared map is doing the work in this meeting. A plan that lives in a slide deck cannot be redlined by the rep who knows the patch. A plan that lives in a CSV cannot be redlined by the manager who owns the team. A plan on a live map can be redlined by both in the same room within the same half hour. The Pin Drop guide on sharing a map with your team covers the permissioning setup this meeting needs.
Days 9 to 10: lock, communicate, document
Day nine is lock-down. Freeze the polygons. Freeze the rep assignments. Freeze the drive-time estimates. Anything still open at the end of day nine becomes a day-one-of-Q3 conversation. It does not belong in the re-plan.
Day ten is communication. Each rep gets a personal walkthrough of their new patch, their new accounts, the trust relationships that move with them, the trust relationships that stay behind. Send the walkthrough as a shared map link rather than a PDF. A rep reading a PDF of a new territory has to rebuild the geography in their head. A rep opening a shared map sees it.
On day ten the mapping tool you are using becomes visible for what it is. A tool that does the Q3 re-plan cleanly stays in the budget. A tool that fights the re-plan at every step is the quiet reason most field sales leaders look at alternatives in April. If you are in that position this year, the Pin Drop posts on the Badger Maps alternative and the Salesforce Maps alternative cover the moment each current tool tends to tip over.
How Pin Drop fits the Q3 re-plan
The way Pin Drop is built maps neatly to the work the re-plan keeps running into. Field sales leaders do not move to Pin Drop because a feature is missing from the current tool. They move because the current tool does not hold the way the team actually works when the territory is being redrawn in anger. Five places where Pin Drop tends to score differently in a re-plan exercise.
Polygon truth. Territory polygons in Pin Drop are collaborative. A manager redraws a polygon. The change is visible to every rep the instant their next pin loads. There is no version. The map is the plan. The first time a team runs a stress-test meeting on a live shared map rather than a PDF, the time saved is measured in hours rather than minutes.
Drive-time first. Pin Drop's route planning is built around real drive-time isochrones rather than straight-line distance. Patches are sized in hours of working day rather than miles of polygon. A useful companion read on this is the Pin Drop piece on route planning for sales teams, which sets out the maths behind patch sizing in full.
Pin persistence. The re-plan is not the first time a patch has been drawn. It is the fourth or fifth. Every pin the team has dropped since 2011 is still there. Pin Drop has held places for accounts since the year the iPhone 4 launched. That is the point of pin persistence. The history of a territory survives every re-plan, every CRM migration, every rep change.
Shared link, zero training. The new territory reaches each rep as a shared map link. A rep opening a shared Pin Drop link sees the patch in full within two taps. No login gate. No onboarding flow. No manual. This is Pin Drop's design principle of zero-training interfaces at work. A plan is only as good as the moment the rep sees it. The faster they see it, the faster they trust it.
Private by default. A territory map contains client names. It contains pipeline values. It contains rep-level performance notes. None of that should be accessible to anyone outside the circle the manager has drawn. Pin Drop's privacy model defaults to private. The Pin Drop piece on private maps covers the permissioning in full.
The two-week test
The honest way to evaluate Pin Drop against the Q3 re-plan is to run the first two days of the playbook above on a Pin Drop free account. Export the last quarter of pins from your current tool. Import them into Pin Drop. Drop in last quarter's visits as a second layer. Look at the map.
If the map shows you something the current tool was hiding, the re-plan has already made the case for the switch. If it shows you nothing new, the experiment has cost you ninety minutes. You have your answer either way. You have also spent less time on the evaluation than you would spend in one coordination meeting trying to reconcile a territory spreadsheet with the reality on the ground.
The Q3 window is short. Seven working weeks from the start of May to the day the new patches go live. The plan is easier to run on the map that will hold it afterwards. Open a Pin Drop account, import a territory, run the first two days. The map will tell you whether the rest of the fortnight is worth scheduling.
