The Repeatable Playbook: Why Most Sales Processes Don't Survive Headcount Growth
The companies that got this right did one thing differently: they built the process before they hired the people.
Most PE-backed companies say they have a sales process. Most of them have a sales playbook. Those are not the same thing.
A playbook is documentation. It tells you what happened. It captures what your top performers do, what the pitch looks like, what the stages are called. A process is infrastructure. It shapes what happens next. It makes new reps productive without depending on anyone specific to show them how.
Think of it as a foundation. Build it on concrete and it holds when you put pressure on it. Build it on gravel and sand, and the moment you add headcount, it shifts. The stages still exist in the playbook. The process that should have absorbed those new reps does not.
That is when companies call us. Not because the reps failed, and not because the managers were wrong. Because the infrastructure was never there.
What a real process actually does
A real process has four properties that a playbook does not. Most portcos already have two of them, and they have the easier two. Here is what all four look like:
- ObservableThe process lives in the CRM, not in a rep's head or a manager's memory. A new manager on day one can see what is happening in every deal without asking anyone.
- TeachableA new rep can learn the sales motion from the system, not from shadowing the top performer. The process carries the knowledge. The person does not have to.
- Data-generatingEvery stage produces something measurable: not a forecast category, but a specific, observable criterion that creates a data trail a manager can actually coach to.
- ScalableWhen you add reps, the process absorbs them. The quality of execution does not degrade when the team doubles.
The test that cuts through all four at once: if your frontline manager left tomorrow, would new reps know the sales motion from the CRM without asking anyone? The test is not about product knowledge. It is about whether the process itself carries the motion.
If the answer is yes, you have a process. If the answer is no, you have a playbook.
Why adding headcount is not always the solution
Companies that added headcount before having an established process often do not see the uplift they expected.
When a process cannot absorb a new rep, the new rep absorbs the manager.
The manager spends time onboarding and holding deals instead of coaching the team.
This is how a portfolio company hires ten reps and produces the revenue of four. The reps are not the problem. The system that should have made them ramp quickly is not there.
Before the next hiring plan
The setup that produces the miss is always the same: the board wants headcount, the CEO wants revenue, and the VP of Sales wants to hire. That alignment of intentions is exactly where this mistake repeats.
Before the next hiring plan, run the four-property test on your current process:
-
Can a new manager navigate every deal in your pipeline from the CRM on their first day?
-
Can a new rep learn the sales motion without a senior rep shadow?
-
Does every stage generate at least one piece of data a manager can coach to?
-
Did your quota attainment hold, or improve, the last time you added headcount?
If any answer is no, the process is not ready. Hiring before it is ready produces another cohort that takes nine months to ramp instead of three.
For the operating partner: this is a structure problem. Every time it gets treated as a talent problem, the org runs another hiring cycle to fix what the last one did not.
For the VP of Sales: the most useful argument you can make to a board pushing headcount is a ramp-time number from the last cohort.
The foundation does not earn a slide in the quarterly deck. It is not visible until it is missing. The companies that got this right did one thing differently: they built the process before they hired the people. That sequence is what separates the teams that compound from the ones that keep starting over.