PILLAR THREE · THE PEOPLE · RAISE THE TEAM

You do not hire a great team. You RAISE one.

RAISE is the team-scaling system, the people domain of the Sales Operator: how a sales org gets recruited, anchored to a standard, inspected, coached, and held to a number it can defend. A hub is headcount. A bench is a system.

01 / THE PROBLEM

Every one of these is a roster problem pretending to be a people problem.

Hiring is the lever everyone brings, and it is the one that does not work on its own. Here is one team, the way it goes without a system, on both sides of the org chart.

01Day one
THE TEAM

A quota and a login. Ramp meant watching call recordings alone until the number started counting.

THE LEADER

Approved the headcount against a number, not a profile, and called the start date the ramp plan.

02Month three
THE TEAM

Still ramping, against a bar nobody wrote down. The norm says four to six months, so nobody asks why.

THE LEADER

Raised the activity target, because activity is the only thing on the dashboard.

03The forecast call
THE TEAM

Nine people running nine processes. Commit means five different things on the same call.

THE LEADER

Defended a number with a mood behind it, and the miss landed on their credibility.

04The rebuild
THE TEAM

The same seats, hired twice, a year apart. The people who stayed wait to see if this time is different.

THE LEADER

Approving more heads while revenue per head keeps falling, because hiring is the only lever anyone brings.

RAISE BUILDS THIS COLUMN.
HEADCOUNT ALONE BOUGHT THIS ONE.
02 / THE SYSTEM

You raise a team, you raise the bar, you raise leaders.

Five letters in causal order: recruit before you ramp, ramp before you inspect, inspect before you coach, coach before you call the number. Each letter below is one question, what lives underneath it, and how it ran on the team rebuild, the build where a smaller team outproduced the one it replaced.

R

Recruit the profile, don't profile the recruit

Who wins in this seat, defined before a single interview?

THE PROFILE

What does good look like here, not elsewhere?

A spec, not a vibe, written from the motion GIANT aimed and the deals PLAN read. Skip it and you judge whoever is in the chair against a bar you never wrote down.

THE LENS

How do you see it in an interview?

GRIP is the interview lens: recruit the profile, and GRIP is the profile. Run inside the teams that hire with it rather than published here.

THE TRAP

Why does the star from the last company struggle here?

Experience does not predict performance in a new environment. Hire for the thing that does, and when the profile is wrong no amount of coaching fixes the funnel.

On the team rebuild: the seat was redefined around who actually wins it, not who was available when the last rep left. Recruited to a profile, not a resume pile, and the bet behind the cut was on that profile, never on volume.

Weak sounds like: “Hire the one who crushed it at their last company.” Strong sounds like: “A spec written before the first interview, and every candidate scored against it.”

A

Anchor the standard

Is there one way the team works, and a bar for ready?

THE PLAYBOOK

What is the one way this team sells?

The playbook, the single source of truth, the motion everyone runs the same way. Anchor first, or there is nothing to inspect, coach, or forecast against. Most people problems are missing-anchor problems.

THE RAMP

When is a rep ready?

Ready is a decision, not a date. A certification bar a rep clears when they can run the motion, instead of a countdown that ends when the calendar says so.

THE OPERATING SYSTEM

How does the team run once it exists?

FORCE is how the team operates: the daily motion that turns a collection of individuals working in parallel into a team. Named here, run inside the teams that use it.

On the team rebuild: ramped against a bar, not a countdown. Ready was a certification. Elsewhere the same anchor produced 45-day ramps against a four-to-six-month industry norm.

Weak sounds like: “Ramp is a 90-day countdown and a folder of call recordings.” Strong sounds like: “A rep leaves ramp the week they can run the motion to the bar, and not before.”

I

Inspect the work

What gets looked at, how often, and to what end?

THE CADENCE

When does the work get inspected?

Deal and pipeline discipline on a named rhythm: the deal review, the pipeline review, the weekly one-to-one. What gets inspected gets done, and what gets inspected honestly gets better.

THE OBJECT

What are you inspecting?

The work, not the person. Look to coach, not to catch. Inspection surfaces that something is off; it does not yet say what.

THE FORK

Will, or capability?

Are they winning? If not, are the results of effort showing? If not, is the effort there at all? Effort missing is a will problem. Effort present without results is a capability problem. Two different conversations.

On the team rebuild: PLAN selling installed and inspected weekly, in a named cadence, every deal read the same way. That is what the survivors believed, not the speech.

Weak sounds like: “A pipeline call that asks how it is going and gets a mood back.” Strong sounds like: “Every deal scored on the same letters every week, and the fork named before the coaching starts.”

S

Sharpen the coaching

Where does the coaching land?

THE GAP

What did inspection surface?

Coaching lands on the real gap the work showed, every week, not on generalities. Run the fork out loud with the rep; they find the floor faster than the manager does, and then they own the gap instead of being handed one.

THE WEEK AND THE QUARTER

What runs the rhythm?

The weekly coaching rhythm runs the week. The development arc runs the quarter: explain the why, define what good looks like, show it, coach it, enable it, hold it accountable.

THE LEADERS

Where do managers come from?

Recruit through Sharpen is also how managers get made. Pointed at the people who will run the next team, it is the seller-to-leader track.

On the team rebuild: the coaching landed on what inspection surfaced, not on generalities. Elsewhere the same rhythm lifted closed-won productivity 300%+ across a region.

Weak sounds like: “A monthly training on discovery for everyone, whatever their gap.” Strong sounds like: “One gap per rep, named from the inspection, worked for a month, then the next one.”

E

Earn the forecast

Can you defend the number without the leader in the room?

THE COMMIT

What is behind every deal in the forecast?

A confidence and a reason on every commit. A deal with no reason is a hope with a close date.

BOTTOM-UP

Where does the number come from?

From the deals, read on the same letters, rolled up. Not from the top, and not from a pipeline multiplier applied to a feeling.

THE RECEIPT

Did it hold?

The forecast is the one letter that answers to a number every month. It is earned by the four letters before it, and it is what the board believes before it believes anything else.

On the team rebuild: forecast accuracy went from 65% to 90%+, and the smaller team outproduced the one it replaced. The first forecast that held is what earned belief in the week after the cut.

Weak sounds like: “Commit means five different things on the same call.” Strong sounds like: “A number the team could defend without the leader in the room, with a reason on every deal in it.”

Inspection feeds coaching, and coaching earns the forecast. Skip a step and scaling reads as activity instead of a system.

Across four companies, one system underneath: fifteen sellers promoted through a first seller-to-leader track, 45-day ramps against a four-to-six-month norm, a coaching rhythm that lifted closed-won productivity 300%+, and a forecast that went from 65% to 90%+ accurate.

THE SALES OPERATOR, IN THREE MOVES
03 / RUN IT

The system is open. Here is what to run it with.

Three places on the site, each one serving a letter: the rhythm that inspects, coaches and forecasts, the ramp against a bar, and where the machine takes the drag so the team keeps the conversations.

RAISE YOURS

The system is yours. The GRIP blueprint, the scorecards, and the enablement builders come with the subscribe.

One story a week on building teams that outproduce bigger ones, and what broke along the way. Plus the runnable tools behind RAISE, GRIP, and FORCE.