Person → skill → execution: the onboarding order that sticks
Marc Snegg · September 18, 2026 · 10 min read
Outbound breaks people who only got “product training.” Here’s the exact development order we use to build confidence, then skill, then real execution—without a 3-month ramp.
Outbound has a way of exposing what you didn’t build.
You can give a new SDR a clean script, a shiny dialer, and “best practices” from the internet.
Then they get punched in the face on a cold call.
A hard objection. A dead line. A bad list. A no-show meeting. A week where the activity dashboard looks fine and pipeline doesn’t move.
If you skipped the person part, they fold.
That’s why we’re stubborn about development order.
Not because it sounds good on a poster.
Because outbound sales is mentally demanding, and performance is a system.
And systems only work when they’re built in the right sequence.
The failure pattern: “product training” without a person
Most onboarding programs are basically:
1) Here’s the product. 2) Here’s the deck. 3) Here’s the CRM. 4) Good luck.
And then leadership acts surprised when the rep’s confidence evaporates the first week.
We see this all the time, and it shows up in a few predictable ways:
- Reps hesitate to dial because they don’t feel ready.
- They over-explain because they’re trying to “prove” they know the product.
- They default to robotic outreach because it feels safer than being human.
- They get one bad day and treat it like a verdict on their ability.
It’s the same trap, just in different outfits.
Outbound doesn’t reward brilliance. It rewards repetition.
And repetition is hard when the person inside the role doesn’t have internal stability yet.
So the order matters.
Person → skill → execution.
Step 1: Develop the person (confidence, desire, persistence)
We start onboarding with mindset training based on *Think and Grow Rich*.
Not because we’re trying to be cute.
Because outbound is a game of rejection, ambiguity, and delayed gratification. If you don’t build the internal engine first, you’re asking a rep to operate with no fuel.
Here’s the language we use, verbatim:
- “Desire. Faith. Persistence. Affirmation.”
- “We teach Positive Mental Attitude.”
- “It starts with a definite desire: What do you want? How much money? By when? What will you give in return? What’s your plan? Now start. Whether you’re ready or not.”
That’s not motivational fluff. It’s operational.
A rep who has a “definite desire” doesn’t need a manager to beg them to show up. They show up because they’re building something.
And when a call goes sideways, they don’t interpret it as personal failure. They interpret it as reps.
That’s the entire point.
The mechanics (what this looks like in practice)
We do this in a structured 3-day ramp. The first block is the person block.
The rep gets specific about the goal. Not vague “I want to be successful.”
Specific.
- What do you want?
- How much money?
- By when?
- What will you give in return?
- What’s your plan?
Then we build practices:
- Faith
- Affirmation
- Visualization
- Imagination
- Persistence
- Organized planning
And we reinforce it. This isn’t a one-time hype talk.
In our internal rhythm, we reinforce mindset every two weeks in all-hands: writing, reflection, sharing.
That’s the development loop. It’s not separate from performance.
Because consistency beats talent.
One of the best SDRs we’ve ever fielded wouldn’t have impressed you in an interview. Quiet. No slick answers. You’d have passed.
What she had was consistency:
Same call blocks. Same follow-up discipline. Same notes, logged the same way. Months of it.
The flashy rep has a great Tuesday. The consistent rep has a great quarter.
That’s a person thing before it’s a skill thing.
Step 2: Develop the skill (scripts, role-play, workflows)
Once the person is anchored, then we go tactical.
This is where most companies *start*. We treat it as the second domino.
Because skills stick better when someone believes they can actually use them.
Here’s one of the clearest lines we have on this:
“We spend significant time on the script because that’s what gives SDRs confidence early on.”
It’s not about turning people into robots.
It’s about lowering cognitive load so they can be human.
A new SDR doesn’t need to become a product expert on day one.
They need to know how to open conversations and create opportunities.
That’s it.
What we teach in the skill block
In the same 3-day ramp, we go tactical on:
- Company overview and culture
- ICP and customer profiles
- Product deep dives
- Messaging and positioning
- SDR scripts and objection handling
- Role-playing
We build the baseline. The rep learns how to say the first 20 seconds.
Because if the first 20 seconds are shaky, everything downstream is shaky.
We also coach a mindset that protects them from “interrogation selling.”
Two phrases we use internally:
- “conversating”
- “stop the interrogation”
Framework plus judgment beats robotic selling.
Reps need structure, but the goal is a real conversation.
The script creates confidence. The conversation creates meetings.
A concrete example: the voicemail skill (20 seconds, three parts)
Here’s a tactical skill we train early because it’s simple and it works:
Most SDR voicemails are 60-second commercials. Nobody calls those back.
We train under 20 seconds, three parts:
- Who you are, in one line.
- One reason to care — a number, a question, something useful.
- Your phone number, said twice, slowly.
No pitch.
“The voicemail’s job isn’t to sell — it’s to make the follow-up email familiar. Send that email two minutes later with a subject line that references the voicemail. Recognition compounds.”
That’s not “talent.” That’s a skill. A repeatable mechanic.
Have your team try it on ten dials this week and watch the second-attempt connect rate.
Step 3: Develop execution (live dials + systems tested)
Then we execute.
And we don’t call onboarding “done” until execution is real.
“By the end of onboarding, reps are live, systems are tested, and the team is actively making dials.”
That line matters because it’s where most teams lie to themselves.
They confuse:
- *orientation* with onboarding
- *training* with readiness
- *activity* with execution
Execution requires the boring operational stuff to be done.
So during onboarding we coordinate with the client team and IT to provision:
- CRM access
- dialers
- Teams/Zoom
- ZoomInfo
- licensing
- hardware and login setup
If those things aren’t ready, reps don’t execute. They stall.
And when reps stall early, confidence dies. It becomes “maybe I’m not cut out for this.”
No. The system wasn’t ready.
Outbound sales is really an operational discipline.
Without the systems:
- Reps run out of leads
- Follow-ups fall through the cracks
- Activities aren’t tracked correctly
- AEs don’t know how to handle SDR-generated opportunities
- Messaging becomes inconsistent
- Coaching becomes reactive instead of proactive
So we treat execution readiness as part of development.
Not a separate department’s problem.
The hidden accelerant: speed + ramp economics
Development order isn’t just a philosophical preference.
It has direct economic impact.
Hiring an SDR and having a productive SDR are two different things. Ramp time matters.
That’s why we obsess over shortening ramp while building confidence and consistency from the very beginning.
We’ve seen teams treat “ramp” like a 3-month waiting room.
Our model is built to move faster because we’re not starting from scratch every time.
From kickoff to live outbound, we often aim for ~3 weeks. (That’s from our launch language, and it matches the operational focus: systems provisioned, reps live, dials happening.)
This is also why “outsourcing vs. building” is the wrong first argument.
Building in-house gets you control — and a 3–6 month ramp, recruiting risk, and a manager problem nobody budgets for.
Outsourcing gets you speed — and, if you buy on price, everything that made you swear off outsourcing last time.
The variable that actually decides it isn’t cost. It’s system ownership — who owns the playbook, the data, the coaching, the accountability.
Get that right and either path works. Get it wrong and neither does.
How we keep it from decaying: coaching rhythm + the learning loop
Development order gets someone launched.
But what keeps performance improving is the operating rhythm.
A lot of what we do differently is boring — which is the point.
Here’s the weekly operating rhythm we run:
- **Daily:** 15-minute standup — yesterday’s numbers, today’s blocks, one blocker.
- **Midweek:** call reviews — two calls per rep, scored, coached.
- **Pipeline review:** what’s real, what’s stalled, what needs a push.
- **Friday:** the week’s data — connects, conversions, what the messaging is telling us.
No genius in it.
But run that rhythm for a quarter and you have an engine: predictable activity, visible problems, compounding improvement.
Skip it and you have a group of people making phone calls.
This is also why “managers create performance more than reps do.”
Everyone benchmarks dials, connects, meetings.
Almost nobody benchmarks the input that drives all three: coaching hours per rep per week.
In the teams we run, the correlation is blunt. Reps getting regular call reviews and real 1-on-1s outperform un-coached reps by a wide margin — regardless of raw talent.
And the most common number we see inside companies that call us?
Zero.
The “manager” is a player-coach with a quota of their own, and coaching is what gets skipped.
So if you’re serious about development, it’s not “hire better reps.”
It’s build a coaching system that makes the average rep dangerous.
And then keep iterating.
Identify → plan → execute → inspect → re-plan.
That’s the loop.
Where teams break the order (and how to self-diagnose)
Most orgs don’t consciously reject the person → skill → execution order.
They just accidentally skip steps because everyone’s in a hurry.
Here are the three most common breaks we see:
1) Skill without person (script-first, confidence-last)
You teach the script. You do a product deep dive. You hand them the talk track.
But you don’t build the internal foundation: desire, persistence, faith, affirmation.
Then the rep sounds good in training and collapses in live fire.
2) Execution without skill (throw them on the phones)
Some teams go “trial by fire.”
They think pressure creates performance.
What it usually creates is avoidance.
Reps avoid dialing because they don’t know what to say, and they don’t want to feel stupid.
The script exists to give them early confidence. It’s not optional.
3) Person + skill, but fake execution (systems not ready)
This one is sneaky.
The rep is motivated. The script is solid.
But the CRM access isn’t provisioned, the dialer isn’t configured, lists are stale, and handoffs are unclear.
So execution becomes chaos, and the rep feels the chaos as “I’m failing.”
This is why we don’t call onboarding done until reps are live, systems are tested, and the team is actively making dials.
A simple question to bring it back to reality
Ask your team:
“How long does it normally take a new SDR to become productive?”
If you don’t know, you don’t have an onboarding system. You have onboarding vibes.
And if the answer is “it depends,” it usually means your process isn’t defined enough to be repeatable.
One next step: run a 3-day “order audit” on your onboarding
Here’s the next step I’d take if you’re reading this and thinking, “We’re skipping parts of the order.”
For the next three days, audit your onboarding like an operator.
Day 1 (Person): - Are we building confidence, structure, and momentum from day one? - Do reps get specific about goals? (“What do you want? How much money? By when?”) - Are we training persistence as a professional skill?
Day 2 (Skill): - Are we spending significant time on the script? - Are we role-playing objections? - Do reps know how to open conversations and create opportunities?
Day 3 (Execution): - Are reps live? - Are systems tested (CRM, dialer, data, licenses, logins)? - Are we actually making dials?
If you want a second set of eyes after you run that audit, the clean next step is a 20-minute working session. No deck required. We’ll pressure-test what you’re doing and tell you straight what we’d fix first.