Back to the blog
Issue No. 03·Enablement

Onboarding Ends on Day 30. Ramping Doesn't.

And the gap between those two things is quietly wrecking your pipeline.

7 min read·May 20, 2026·Meghan Jennings
Cover art for Onboarding Ends on Day 30. Ramping Doesn't

Her name was Kayla.

She was sharp, coachable, came out of her final interview with the hiring panel practically buzzing. The kind of hire you call your manager about. The kind you tell the team is coming and watch them get excited.

She crushed onboarding. Product knowledge? Solid. Tools? Set up and running. Role-plays? She made the trainer laugh. By Day 14 she was asking questions the other new hires hadn't thought of yet.

Day 31, she went live.

And I watched her fall apart in slow motion.

Not dramatically. It wasn't a single bad call or one disastrous week. It was quieter than that. Calls that went nowhere. Emails that landed flat. A pipeline that looked like activity and felt like sand. She was working. God, she was working. And nothing was converting.

By month four she was questioning whether she was cut out for sales. By month five she was gone.

Here's what I know now that I didn't know then: I didn't lose Kayla on Day 31. I lost her on Day 1. The moment I confused onboarding with ramping and assumed they were the same thing.

They are not the same thing. And that confusion is costing you more than you think.

The Lie We All Agreed To Tell

Onboarding has a start date and an end date. It has a checklist and a completion percentage and an LMS dashboard that goes green when someone clicks through enough slides. It feels like progress because it looks like progress.

It is not ramping.

Ramping is messier. It doesn't have a clean end date. It doesn't go green on a dashboard. It's the slow, unglamorous process of turning a new hire into someone who can actually create pipeline. And it doesn't end when onboarding does. It ends when the rep is producing. Which for most BDR roles is somewhere between Day 90 and Day 120. Sometimes longer.

The gap between those two moments. Between "onboarding complete" and "actually ready". Is where your new hires are quietly drowning. Where your managers are defaulting to activity coaching because they don't have anything better. Where your pipeline looks busy and your progression numbers tell a completely different story.

Most orgs fill that gap with hope. A little extra Slack encouragement. A few more ride-alongs. A vague sense that things will click eventually.

Some of them do click. Those reps become your top performers and you credit your hiring instincts.

The ones that don't? You call it a bad hire. Move on. Start the process again.

I'm going to ask you to sit with something uncomfortable: what if it wasn't the hire?

The Numbers First

Before we get into the system, let's sit with the reality of what's happening out here.

4–6 mo
Average BDR ramp time at most orgs
36%
Faster ramp with structured badge-gated onboarding
Mo 4–8
When most struggling reps quietly exit

Sources: Klaviyo Global BDR Enablement Data · Bridge Group BDR Benchmarks 2025

Read that middle number again. Thirty-six percent faster ramp. That's not a good quarter. That's not a lucky cohort. That's what happens when you replace hope with a system.

"The gap between onboarding complete and actually ready is where your pipeline goes to die. And most managers fill it with vibes-based coaching and crossed fingers."

Ramp as a System

The model I've built and tested looks like this: three gates, three badges, one real activation point. And before you roll your eyes at the word "badges". Stay with me.

  1. 01

    Day 30. The Foundation Badge

    Before a rep sends a single cold email to a real prospect, they earn this. Not complete it. Not check the box. Earn it. A live cold call scored against a real rubric. A real sequence built and submitted. Core personas walked through without a safety net. And a manager sign-off that actually means something.

    This is the gate most orgs skip. They let reps go live because the calendar says it's time. Because it feels awkward to say "you're not ready" to someone who's been working hard for a month. So they send Kayla live. And then they wonder why Day 31 looks the way it does.

  2. 02

    Day 60. The Discovery Badge

    By now the rep has real data. The Day 60 gate is about what happens after the meeting gets booked. Can they map a buying group before the call? Can they articulate pain in the prospect's language? Is their handoff brief something an AE actually wants to receive. Or is it a calendar invite with a name and a prayer?

    Most orgs measure meetings booked. They do not measure whether those meetings go anywhere. The Discovery Badge forces that question at Day 60, when you can still do something about it.

  3. 03

    Day 90. Activated

    Full quota. AE pairing locked. Advanced path unlocked. And the piece nobody talks about: the data from this rep's ramp feeds directly into the onboarding design for the next cohort. What broke down in week three? Which certification did this cohort struggle with? That feedback loop is how the system gets smarter. I call it everboarding. And it's the difference between a program that works once and one that compounds.

The Badge Nobody Chases

Here's the thing about certification architecture: if a badge unlocks nothing, nobody chases it.

I've seen beautifully designed certification programs that everyone quietly agreed to stop caring about. Reps completed them because they had to. Managers tolerated them because leadership asked. And then the whole thing slowly deflated like a balloon three days after the party.

The reason is almost always the same: the certification wasn't connected to anything a rep actually wanted.

Foundation Badge unlocks live outbound. Advanced Badge at six months unlocks the SDR-2 title and the promotion conversation. Expert Badge is the AE readiness gate. You don't get to have that conversation without it. Every badge tied to a real career outcome. Not a certificate nobody prints. A door that only opens if you've earned the key.

Watch what happens to rep engagement when the badge means something. The vibe shifts entirely.

Who Actually Owns It

Enablement designs the system. Managers own it.

I'm deliberate about that distinction to the point of being annoying about it. When enablement owns ramp, it becomes a program. Something that lives in a drive and gets referenced occasionally. When managers own ramp, it becomes a behavior. It becomes the 1:1. It becomes the call review. It becomes the conversation that happens before the rep goes live and the one that happens when they're struggling on Day 47.

"Training fails where manager inspection stops. I have never found an exception."

The Ramp Swap Sheet

Print this. Put it in your next manager 1:1. Review it every time a new hire goes live.

Stop doing this

  • "They've been here 30 days, they're ready."
  • "You need to make more calls."
  • General vibes-based 1:1 check-in.
  • "They'll figure it out." (Month 2 edition.)
  • Ramp data goes into a folder nobody opens.

Do this instead

  • Have they passed the Foundation Badge? Manager sign-off should mean something. Make it mean something.
  • Pull the ramp rubric. "Your openers are landing. Your CTAs aren't. Here's what we fix this week."
  • Structured 1:1 anchored to where they are in the ramp system. Rubric in hand, every time.
  • Day 60 gate. Multi-thread mapping. Handoff brief review. "Figure it out" is not a coaching strategy.
  • Ramp data feeds the next cohort's onboarding design. The system learns. Everboarding.

Somewhere in your org right now there's a Kayla.

She's working hard. She's trying. She's starting to wonder if she's the problem.

She's not the problem.

Build the system.

Share this LinkedIn X

Outbound, But Smarter

The Modern BDR Operator

Get the next one in your inbox.

New frameworks, hot takes, and playbooks. Written for operators, not audiences.

Subscribe to Booked.