246 coaching conversations in eight weeks.
Scored on GitLab's own rubricGitLab™ coached every rep. 8.2x more coaching, on their own method.
GitLab had already bought a serious sales method. The harness took GitLab's buyers, that method and its scoring rubric, and gave every rep a coach that read their calls against them. 246 coaching conversations in the first eight weeks, against 30 to 40 a quarter before.
- 8.2xmore methodology coaching deliveredGitLab · customer-reported
- 246coaching conversations in the first eight weeksGitLab · customer-reported
- Up to 60%stronger methodology execution, first attempt to bestGitLab · customer-reported
A method paid for. Forty sessions a quarter to coach it.
GitLab sells across regions, product lines and buying committees, and its enablement team had already built the frameworks. What ran out was the hours to coach them.
- 01The method was never the problem.
The frameworks and the rubric existed. The reps who ran them well were the reps who could get a manager's time.
Adoption depended on the calendar. - 02Coaching scaled with manager hours.
The traditional model needed significant coordination to deliver 30 to 40 sessions a quarter across a global organisation.
A lean enablement team runs out of hours fast. - 03Practice was rationed.
Reps with strong foundations needed repetition to make them stick, and top performers wanted more than the model could give.
The limit was the volume of good coaching one team could deliver.
Coaching stopped being rationed. Every rep, from the first week.
A coach for every rep changed the arithmetic. In the first eight weeks, reps had 246 coaching conversations, against 30 to 40 sessions a quarter before. Reach is what moved: the method GitLab had invested in finally met the whole team.
Any call, live or practice. A real prospect call or a rehearsal, read against GitLab's method and rubric.- Scored on GitLab's standard. Which step was skipped, and what a stronger version of that moment sounds like.
Back in to try again. The next practice round or the next live call, coached too.
Their buyers, their method, their rubric. Then every call read the way GitLab sells.
Ask a general model to coach a rep and it works from nothing: it has never met GitLab's buyers, it blends every method it has read, and with no rubric it has nothing to score against. With all three installed, a coaching loop is possible.
- Bring the call.
Every conversation a rep has, live or practice, goes to the coach, which reads it against GitLab's methodology and rubric.
- Talk it through.
The rep hears where they got stuck, which part of the method they skipped, and what the stronger version of that moment sounds like. A conversation, held to GitLab's framework.
- Go back in.
The coach puts the rep straight into the next situation to apply it, then coaches that one too. Diagnose, coach, try again. That loop is what turns a method on a slide into a habit on live deals.
Coach · GitLab methodologyIllustrativeRapport built. Impact never quantified.
The opening was strong, then the pitch arrived before the buyer had put a number on the problem. Run the same opening and make the cost land before you talk product.
The point was adoption. Reported by GitLab.
The numbers are GitLab's. 8.2 times more coaching, 246 coaching conversations in the first eight weeks, and reps who lifted their methodology execution by up to 60% from first attempt to best. The team ran the method GitLab had invested in. Coaching no longer depended on a manager's diary.
A method earns its keep when reps run it, and adoption is what shows up where leaders look: win rates, cycle length, deal size. That holds for any serious method, MEDDPICC, Command of the Message or the ValueSelling Framework®. GitLab built the coaching engine that drives the adoption those outcomes depend on.
"With Replicate Labs, we scaled our coaching mechanism across GitLab's entire sales organization. The combination of a platform and deep enablement expertise from their leadership made all the difference."
Reps who engaged improved their methodology execution scores by up to 60%. The direction is the signal: reps across the team got measurably better at running the method, session after session.
What was the challenge GitLab set out to solve?
Adoption at scale. GitLab had invested in a strong sales methodology, but a methodology only pays off when every rep runs it on live deals. The traditional coaching model carried heavy coordination overhead and reached only a fraction of the team, so adoption depended on who could get a manager’s time.
What did Replicate Labs install?
GitLab’s buyers, GitLab’s own methodology and the scoring rubric that judges it. Replicate Labs is the GTM harness: a general model has never seen a team’s buyers, mixes every methodology it has read, and has no scorecard to judge a call against. With all three in place, every call could be read the way GitLab sells.
What does "8.2x more coaching" mean in practice?
The traditional model delivered 30 to 40 coaching sessions a quarter. With Replicate Labs, reps had 246 coaching conversations in the first eight weeks, an 8.2x increase in coaching delivered. The shift that mattered is the reach: every rep got coached, so methodology adoption stopped being rationed to a few.
Is this about volume, or about results?
Results. The volume is what it takes to get there. A methodology earns its keep when reps run it, and adoption is what shows up where leaders look: win rates, cycle length, deal size. GitLab built the coaching engine that drives it.
Where does the "up to 60% improvement" come from?
Reps who engaged improved their methodology execution scores by up to 60% from first attempt to best. The signal that matters is the direction: reps across the team were measurably getting better at running the methodology, session after session, long after a one-off training would have worn off.
Does this replace GitLab’s sales managers?
No. The coach handles the high-frequency work a human manager cannot do at scale, the call-by-call feedback and the practice rounds, which frees leaders for strategy and deal support. As John Blevins put it, the combination of the platform and deep enablement expertise is what made the difference.
Bring the method you already run. Watch it reach a live deal.
Most teams have a method and no way to coach it onto every call until it holds. Bring one deal and the playbook. We run the session on your pipeline and you see the read before anything is signed.
GITLAB is a trademark of GitLab Inc. in the United States and other countries and regions. This case study describes a past engagement and is published by Replicate Labs. It does not imply any ongoing relationship, affiliation, sponsorship, or endorsement by GitLab Inc. Figures and quotes are used with permission.