Why a new field rep's first week is a geography problem, not a product problem
Every field sales leader has lived this Monday. A new rep starts. The laptop is set up. The CRM login works. The product training is booked for Thursday. The rep is keen, capable, hired for good reasons. By Wednesday they are parked in a lay-by near a ring road they have never driven, looking at a list of forty account names that mean nothing to them yet, choosing which one to visit next on instinct alone. The product knowledge will come. The geography is the thing nobody handed them.
Ramp time across the field sales sector now sits at close to six months on average. That figure has climbed by roughly a third since 2020. Most of the delay is not the rep learning the catalogue. It is the rep slowly rebuilding, account by account and mile by mile, the working map of the patch that the previous rep carried entirely in their head. Two in five organisations report that fully onboarding a field rep takes three months or longer. The cost of that gap is rarely a line on any budget. It shows up as a quarter of soft pipeline while the new rep learns where everything is.
There is a tidy seasonal reason this matters in July. The third quarter starts on the first of the month. Summer is when most teams run their graduate intakes, take on seasonal cover, or backfill the reps who resigned in the spring. The patch does not wait for the new starter to settle in. Customers still expect their visits. Targets still land on the first Monday. The week that decides whether a rep ramps in weeks or months is the first one, before a single bad habit has set.
This piece is the week-one plan Pin Drop has watched work across field teams handing a patch to someone new. Who owns the handover. What to put on a shared map before the rep's first drive. How to sequence the first five days so the geography arrives in days rather than the slow drip of a full quarter. It assumes you would rather the new rep spent week one selling than rebuilding a map that already exists.
If you manage the field sales team, the new rep's first week is your deliverable even when the calendar says you are busy with everything else. You are the one holding the knowledge that is about to walk a new patch blind. Which accounts convert on the first visit. Which gatekeeper responds to which approach. Which postcode looks busy on paper but eats a full afternoon for one meeting. None of that sits in the CRM. It sits with you and with the rep who left.
Before the new starter's first drive, get that knowledge onto a shared map rather than into a two-hour briefing they will half remember. Drop the patch as pins. Colour them by priority. Write the one line of context on each that you would have said out loud in the van. The Pin Drop playbook on Q3 territory planning covers how to draw the patch itself. This is the layer that goes on top.
If you are the new rep, the instinct in week one is to prove yourself by booking meetings fast. Resist it for the first two days. A meeting booked in the wrong corner of the patch costs you ninety minutes of driving you will never get back. The reps who ramp quickest spend their first days reading the map their manager built, asking why a pin is red, learning the shape of the patch before they commit to a route.
Open the shared map on your phone the night before your first field day. Filter to the accounts marked as priority. Look at how they cluster. The good clusters are the ones you can work in a morning without crossing a motorway twice. The Pin Drop guide on route planning for sales teams sets out how to build a day that respects drive time rather than account count.
If you own sales operations or enablement, every new starter is a test of whether the patch knowledge survives a person leaving. When a rep resigns, the question is not only who replaces them. It is how much of what they knew is written down anywhere the next person can reach. For most teams the honest answer is very little. The map walks out of the door with the rep.
Make the shared map the place that knowledge lives, so the next handover starts from something rather than nothing. A patch held on a live map persists through every resignation, every restructure, every intake. The Pin Drop piece on moving from spreadsheets to maps covers why a list cannot hold this kind of working knowledge for long.
The week-one onboarding plan, day by day
The plan below fits a standard working week. Five days. It assumes the patch already exists as a defined territory and that the new rep has the basics of the product. If the patch itself needs redrawing first, run the territory exercise before the rep starts rather than during their first week. The two jobs do not mix well.
Day one: build the map before the rep drives
The new rep does not get in a car on day one. Day one is a desk day, spent with the manager and a shared map. Import the patch as pins from the CRM or the last rep's list. Colour them by priority band. Add a second layer for the accounts visited in the last quarter, so the rep can see what is warm and what has gone quiet.
Then do the part that matters most. Walk the map together and add the context that was never written down. One line per account is enough. 'Reception will not let you past without an appointment.' 'Best caught before 9am.' 'Decision maker moved to the Leeds site in March.' This is the knowledge that usually takes a new rep two months to rebuild by trial and error. Written onto the map in an afternoon, it arrives on day one instead.
Day two: shadow a full day in the field
On day two the new rep rides with the manager or with an experienced rep from a neighbouring patch. The shared map is open on the phone for the whole day. Every time the experienced rep makes a decision, the new rep watches it happen against the map. Why this account before that one. Why the detour. Why the cold call into the industrial estate on the way back rather than a straight drive home.
The new rep's job on day two is to annotate. Each time they learn something the map did not already say, they add it as a note on the pin there and then. By the end of the day the patch has gained a dozen small truths it did not hold that morning. The rep has started to build the mental model that usually takes a quarter to form.
Day three: plan a route and walk it on the map first
Day three is the first solo planning day. The new rep builds tomorrow's route themselves, from the map, with the manager watching rather than directing. They pick a cluster of priority accounts that sit within sensible drive time of each other. They sequence the visits. They build in the two or three cold stops that turn a half-empty day into a full one.
Then they walk the route on the map before they ever drive it. The manager redlines it live on the same shared map. A stop in the wrong order. A motorway junction that adds twenty minutes. A priority account that has been left out. The corrections happen on the screen on day three rather than on the road in week three. The Pin Drop guide on sharing a map with your team covers the permissioning that lets a manager redline a rep's plan without taking it over.
Day four: drive the patch solo
Day four is the first real solo day in the field. The rep drives the route they planned and the manager approved. The part that matters is logging as they go. A visit done becomes a note on the pin while they sit in the car park afterwards, not a report written from memory at 6pm. A gatekeeper's name. A follow-up date. A reason the meeting did not happen. Each one lands on the map in the moment.
The manager does not need to call to ask how the day went. The map tells them in real time. Pins turning over through the afternoon. Notes appearing. A cluster in the north of the patch still untouched by three o'clock, worth a quick message before the rep heads home. This is the visibility a spreadsheet updated at the end of the week can never give.
Day five: review the week on the map
Day five ends with a review, held in front of the map rather than a spreadsheet of activity. Look at the week as geography. Which clusters got worked. Which corners stayed cold. Where the drive time ran longer than the plan assumed. The new rep can see their own first week laid out as a shape, which is a far better teacher than a list of numbers.
Set the second week from the same map. The priorities for the days ahead. The accounts that slipped. The clusters worth a full day each. By Friday afternoon of week one the new rep is not staring at a list of strangers any more. They are reading a patch they have started to know, on a map that will hold everything they learn from here. That is the difference between a rep who ramps in weeks and one who is still cold in October.
How Pin Drop fits the week-one handover
The reason a shared map shortens ramp time is not a single feature. It is that the patch knowledge stops living in one person's head and starts living somewhere the next person can reach. A few of the places Pin Drop tends to earn its keep in an onboarding week.
Context that persists. Every note a rep adds to a pin stays on that pin through every handover that follows. Pin Drop has held places for teams since 2011. When a rep leaves, the map they built does not leave with them. The next new starter inherits the working knowledge rather than rebuilding it from nothing.
Zero training to read it. A new rep opens a shared map link and sees the patch within two taps. No login gate on the first view. No course to finish before the map makes sense. This is Pin Drop's design principle of zero-training interfaces doing the quiet work. The faster the rep can read the patch, the faster they trust it.
Drive time, not distance. Routes are built around real drive time, so a new rep sizes a day in hours rather than guessing from how far apart the pins look. The patch that reads as compact on the map but takes all day to cover stops being a week-three surprise.
Live for the manager. The manager watches the rep's first solo days unfold on the same map in real time. Coaching happens in the moment rather than at a Friday debrief. The handover stays a shared job rather than a rep left to sink or swim.
Private by default. A patch map carries client names, pipeline values, rep-level notes. Pin Drop keeps all of it private by default, visible only to the circle the manager has drawn. The Pin Drop piece on private maps sets out the permissioning in full.
The week-one checklist
If you have a new field rep starting this summer, the shape of their first week is simple enough to write on one card:
- Day one. Build the patch on a shared map. Add the context that was never written down.
- Day two. Shadow an experienced rep with the map open. Annotate as you learn.
- Day three. Plan a route from the map. Redline it together before driving.
- Day four. Drive solo. Log every visit to the pin in the moment.
- Day five. Review the week as geography. Set week two from the same map.
Most teams that run this version of week one tell us the same thing. The new rep is not measurably faster at selling on day five. They are faster at knowing where to be, which is the part that usually takes a quarter. Get the geography in early and the selling follows on its own schedule.
The simplest way to test it is to run day one on a free account before your next starter arrives. Export the patch from your current tool. Import it into Pin Drop. Spend half an hour adding the context you would otherwise have delivered as a briefing nobody remembers. Then look at the map the way a new rep would on their first morning. If it tells them more than your current list does, the case for the switch has already made itself. Open a Pin Drop account, build a patch, hand it to the next person who joins.
