When a rep leaves, most teams open a req. Someone updates the org chart. A slack message goes out. The book of accounts that rep was carrying sits exactly where it was.
That is where pipeline goes to die.
The book is wrong the moment headcount changes
A departure does not just create a vacancy. It creates a coverage gap that starts compounding on day one. The accounts that rep was working go cold. The ones they were ignoring stay ignored. And the remaining reps, already at capacity, are not absorbing the difference in any meaningful way.
The same problem runs in reverse when someone starts. A new rep gets a book assembled under time pressure, often inherited from whoever left, often not reviewed for fit or balance. They spend their first weeks sorting through accounts that were never right for them.
Neither scenario is an execution problem. Both are a planning problem that starts the moment the headcount change happens.
Why teams are always a step behind
Redistribution is manual and no one treats it as urgent. When a rep leaves, the instinct is backfill, not rebalance. The assumption is that the team absorbs the gap until the new hire ramps.
That assumption is expensive. Coverage does not hold itself. Accounts do not wait. And by the time the new rep is onboarded and their book is assembled, weeks have passed with no one working that territory.
The book was wrong and stayed wrong because fixing it felt like a project.
Headcount change is a book trigger, not an HR trigger
The day someone leaves is the day the book needs to change. Not the day the backfill starts. Not the day the new rep signs their offer. The day the headcount changes.
That means having a system that can redistribute accounts based on capacity, not just territory lines. It means knowing which accounts are unworked, which reps have room, and what a balanced book looks like at your current headcount before you make any moves.
Gradient Works' Bookbuilder automates this. When headcount shifts, it redistributes accounts dynamically based on rep capacity and ICP-fit scoring. No spreadsheets, no manual carve sessions. The book adjusts to reflect the team you actually have.
Carve gives you the planning layer. Before you commit to a redistribution, you can model what the books look like at different headcount scenarios, test scoring thresholds, and see coverage gaps before they become pipeline gaps.
You plan the change, then execute it. In one motion.
The window is shorter than it feels
Every day the book is wrong is a day of coverage lost. If a rep leaves in week two of the quarter and the book does not get redistributed until week five, that is three weeks of accounts sitting idle during a quarter where you cannot afford it.
Q1 headcount changes are not unusual. Attrition happens. Reps ramp slowly. Teams get restructured. The teams that treat each of those moments as a book trigger come out of the quarter with coverage intact.
