From 180 Days to 14: Inside One B2B Team's Ramp-Up Rebuild

We noticed something odd in the numbers a mid-market cybersecurity vendor shared with us last spring. Their quota attainment looked fine on the surface — 82% of reps hitting plan — but the distribution underneath was ugly. Two hires from the previous year were carrying nearly 40% of new-logo revenue, while three others were still stuck at half quota eleven months in. The VP of sales called it a "ramp problem." We called it a pattern problem, and we followed the project long enough to see whether it could be fixed.

The team sold a $48,000 average contract value product into IT security buyers, a market where discovery calls live or die on the rep's ability to sound like a practitioner. Their existing onboarding was a six-week bootcamp followed by shadowing. New reps listened to maybe a dozen recorded calls, mostly from whoever happened to be free that week. Nobody had ever systematically compared what their top 10% did differently from everyone else. That gap is where Genkatsu entered the picture.

The decision point: stop guessing, start mining

The sales ops lead — let's call her Dana — had a specific constraint. She didn't want another dashboard that reps would ignore. She wanted something that would sit inside the tools her team already used and surface coaching in the flow of work, not in a Friday review. The evaluation took three weeks. Two competitors demoed well but required reps to log into a separate portal. That was a dealbreaker for a team of 22 reps who were already drowning in tabs.

What tipped the decision was a simple test. Dana uploaded six months of call recordings, email threads, and closed-won/closed-lost deal data from their CRM. The system was asked to identify which behaviors correlated with deals that reached the proposal stage versus those that stalled after discovery. Within 48 hours, it surfaced three patterns. Top performers asked about the buyer's previous security incident within the first eight minutes. They named a specific competitor's weakness by minute twelve. They never pitched pricing before confirming the buyer's internal approval chain. None of this was in the onboarding doc.

Building the 14-day ramp

The implementation timeline was tight. Week one: connect the CRM, ingest 14 months of historical calls and emails, and tag the top-quartile reps. Week two: validate the patterns with the sales managers, who pushed back on two of the five initially flagged behaviors. Week three: build the coaching prompts. Week four: pilot with four new hires who were scheduled to start anyway.

The obstacles were predictable. Two senior reps resisted having their calls analyzed, worried it would become a surveillance tool. Dana addressed it by giving them first access to their own dashboards and letting them see what the system flagged before any manager did. One manager ignored the alerts for the first ten days. A quiet nudge — showing him that his team's discovery-to-proposal conversion was 9 points below the peer group — changed his behavior overnight.

• New reps received real-time prompts during live calls: "Ask about prior incident" or "Confirm approval chain before pricing."
• Managers got a weekly digest of which reps were executing the top-quartile patterns and which were drifting.
• The onboarding doc was rewritten to reflect what the data actually showed, not what the founders remembered doing in 2019.

What actually moved

Fourteen days after their start date, the first pilot cohort was running solo discovery calls. That's not the same as being fully ramped, but it's close: they were handling the first two stages of the funnel without a shadow. The previous cohort had taken 180 days to reach that same milestone. By day 90, the pilot group's discovery-to-proposal conversion was 34%, compared to 21% for the prior three cohorts at the same point.

The bigger surprise was on the existing team. Once the top-quartile patterns became visible, three mid-performers started self-correcting without any manager intervention. They could see their own call recordings scored against the patterns. One rep — a two-year veteran who had been stuck at 70% of quota — closed 118% the following quarter. She told Dana she'd never known what "good" actually sounded like until she heard her own calls side by side with the top group.

We asked Dana what she'd do differently. She said she'd have started with the managers earlier and spent less time on the technical integration. The tooling was the easy part. Genkatsu reports 14 days as the median ramp compression for teams that follow the full onboarding sequence, but Dana's team took 21 days for the second cohort because they added a weekly manager calibration session. The extra week was worth it: second-cohort conversion hit 38% by day 90.

The post-mortem

Three things made this work. First, the data was already there — calls, emails, CRM fields — nobody had to change their workflow to generate it. Second, the coaching was specific and behavioral, not motivational. "Ask about the prior incident in the first eight minutes" is actionable. "Be more consultative" is not. Third, the managers owned the rollout, not the ops team. When a manager pushed back on a pattern, the system adjusted. That built trust.

What didn't work: trying to coach on 11 patterns at once. The team narrowed to three for the first month, then added two more. Also, the initial alert frequency was too high. Reps tuned out after the third prompt in a single call. They settled on a maximum of two prompts per call, only for the first 90 days of a rep's tenure.

If you're running a B2B sales team and your ramp is measured in quarters rather than weeks, the lesson isn't that you need more training content. It's that you probably already have the answers sitting in your call recordings and CRM. You just haven't mined them. The teams that do are compressing months into days, and they're doing it without adding headcount.