Lauren Hughes cut enablement from 16 people to 6, then put 300 new revenue hires through a program that took ramp from 18 months to 8. AE bookings grew 28% last year (44% over two). She later rolled SDRs under her, lost 4 heads to AE promotions, and the team still ran 2x pipeline in Q1. Smaller team, faster ramp, more output. I have watched a lot of leaders treat headcount as the growth lever. Her scoreboard moves the other way.
Lauren is Justworks' first VP of Revenue Effectiveness. John Belle created the seat, put RevOps and enablement under one roof, and hired her to run it. She now supports 600 customer-facing people across 20 roles with a lean team and a lot of systems. The theme of this episode is the GTM operating system: measurement on everything, traditional enablement jobs she stopped staffing, and growth coming from a tighter machine.
Five things from the conversation that I keep coming back to.
1. You needed 32 people to keep Confluence updated
Justworks had already cut enablement from 32 to 16 before Lauren started. After ride-alongs with the remaining 16, her read was that they were all working on the same thing. She said "not one person was working on something unique versus everybody else." She took the team from 16 to 6, dropped traditional seats (instructional designer, LMS admin), never hired the onboarding coordinator that was sitting on the plan, and parked the seats for RevOps and AI content creators.
The old job of that 32-person org was human refresh of the help center. Enablement used to be the only group allowed to touch Confluence. Someone would wonder if a page was still accurate, ask 15 people, then rewrite it. Product launches pulled the field off the floor for an hour of country training they would not sell for 6, 9, maybe 12 months. They were paying for an LMS they were not using as a real LMS.
Lauren flipped the ownership model. Product, product marketing, and customer education now update the source. Stale pages alert, and AI suggests a refresh. The field gets the same content through Slack and through Spekit inside Salesforce. Onboarding lives in Tangelo, and she does not run an LMS.
"That's why we had 32 enablement people. Yeah, we needed 32 people to keep Confluence updated."
I told her that was going to be the quote of the podcast. It is also a pretty cheap diagnostic you can run on your own org. Count how many people exist to keep the wiki honest. If that number looks like a team, it's worth asking whether you've built content ops inside enablement.
That's a useful check.
The McKinsey Global Institute put numbers on this tax in 2012 and they still hold. Interaction workers spend nearly 20% of the week looking for internal information or chasing colleagues who can help. A searchable record of knowledge can cut that search time by as much as 35%.
Forrester's Total Economic Impact of Confluence, commissioned by Atlassian, still budgets ongoing admin as a real FTE cost, not a license line. You still pay for the wiki. Either in people who keep it current, or in the work of instrumenting freshness and serving it where the work already happens.
If you are still staffing instructional designer, LMS admin, field enablement, and onboarding coordinator as default seats, sit with the 16-to-6 math. Lauren is back to 10 or 12 with a couple of open roles, and the work that used to justify 32 people now runs as a system. The new bar was systems thinking, and she hired for it.
2. If week 3 data says they are ready, do not hold them to week 4
When Lauren joined, average time to ramp for a new sales hire was 18 months. Justworks is compliance-heavy. You are hiring someone off the street into HR, health insurance, and PEO language they have never spoken.
Last year 300 revenue-facing people went through a rebuilt program. Ramp is now 8 months, with a pretty clear path under 6. She measures time to average cohort attainment.
The entire AE population grew bookings 28% last year and 44% over two years. Some of that is less friction in the operating system. A lot of it is the new-hire program.
They still keep a couple of weeks of classroom. Mission, product, how Justworks makes money, how they treat prospects and customers. Then people drop into specialized learning paths by role, with quizzes, checkpoints, and AI roleplay. The gain is what the data lets her do next.
"We're finding out by week 3 that they're like ready to hit the phones, then awesome. Like, why are we holding them in training till week 4?"
If 10 of 12 AEs pass and 2 do not, she does not hold the 10. She diagnoses the 2. Maybe they have never sold. Maybe they have no industry background. Then you can adjust the path or work the nesting process with the manager.
A calendar is a pretty blunt way to run onboarding. Measured paths give you more room to release people when they look ready, or spend extra time with the ones who do not.
CSO Insights' 2018 Sales Talent Study found open sales seats sit empty for nearly 4 months, then another 9 months pass before a new hire hits full productivity. That is more than a year of drag before the seat pays for itself.
The Bridge Group's 2025 SDR report, across 351 B2B companies, now puts average SDR ramp at 3.0 months, the lowest since 2010. Lauren's 18-month starting point was an outlier even for a messy product. Moving it to 8, with a path under 6, is the spreadsheet event. Drag 18 months of half-productivity to month 8 and the unit economics of the hiring engine change.
I'd pick one role. Write the week-3 and week-4 gates in actual skills, not "complete the LMS." If the data says they can hit the phones, I'd let them hit the phones, even if the calendar still says week 4.
3. Thirty minutes on one contact is the operating-system diagnosis
Lauren's first 60 days were ride-alongs plus data. The story that still sits with me is 30 minutes with one SDR.
The contact was a former Justworks customer who had moved to a CFO seat. They checked him in LinkedIn, then Salesforce, then 6sense. Disjointed systems, same question: is this person legit.
They manually wrote a note about the old relationship and the new role. Lauren had to run to her next meeting. She sat down, opened her laptop, and the rep had already emailed her.
The prospect wrote back, "no, thank you. I'm not interested at this time."
Thirty minutes to send one note that died on arrival. That's the kind of thing a 30-minute ride-along actually shows you.
She tried to stand up a signal system in the background, then took the SDR team about 4.5 months ago. First move was to inspect the stack they had already paid for and half-adopted. 50% of Gong calls were going unrecorded. A parallel dialer pilot had fallen flat because of overlapping features nobody had stood up. She had a dialer in a POC within 4 days of taking the team.
Q1 at Justworks starts in June. They ran 2x productivity on pipeline opportunities (logo count) and 2x pipeline ARR, down 4 in seat from people moving to AE roles. She will not give you a smoking gun. Comp and the job description had not been refreshed in 3 years.
She added a pipeline ARR component next to logo count. She unlocked Claude for list building. She rebuilt the AE readiness path so the job had somewhere to go. 6 SDRs promoted to AE, 2 to partnership acquisition, one manager, one into revenue effectiveness, all in the first stretch with her.
"I wish I could say some, like, big aha thing, but it was really just this team needed focus."
Salesforce's fifth State of Sales (7,775 sellers) found reps spend 28% of the week actually selling. Teams use an average of 10 tools to close deals, and 66% of reps say they are overwhelmed by the number of tools. Lauren's 30 minutes is that research in a single desk. Three systems to validate one former customer is a purchased stack that never quite became one motion.
If you want the same diagnosis, I'd skip the tooling RFP. Sit with one SDR for 30 minutes and time a single contact. Write down every tab. That list is your backlog.
The tools you already pay for and have not adopted are often the first unlock. In her case, a 4-day dialer POC moved volume before any new vendor cycle.
4. You can tell if they will make it in the first couple of days
Onboarding measurement at Justworks is quizzes, checkpoints, and AI roleplay, plus the unglamorous stuff: attendance and camera on. A lot of people onboard on Zoom now. Some do not show their cameras. That is a mandated requirement for her, and it is also a signal.
"We can tell if somebody's not going to make it just based on how they show up the first couple days."
Cameras are a pretty cheap sensor. The useful move is getting the manager conversation going before you burn months of an 18-month ramp. Tangelo runs the scheduling for the first 3 to 5 weeks off the Workday role, scores knowledge checks, and alerts the manager when someone is off-pace. That is the onboarding coordinator they never hired. Early alerts exist so you can act while the cost of being wrong is still small.
They also changed who they hire. Her read was that the best AEs and best managers come from the SDR org, so they doubled down on SDO quality and sped up AE readiness. They ran a profiling pass on prior PEO experience versus a rep off the street, and on adjacent backgrounds (she has seen rental-car sales work). Hiring and onboarding are the same system.
If week 1 looks off, that can be a signal. Waiting on a 90-day review while you ignore it is one way ramps stay long.
Talya Bauer, Berrin Erdogan, and colleagues tracked 985 new hires at a Fortune 500 technology company across the first year. Day-1 resources (a workstation ready, meeting the manager on day 1, personal resources like proactive personality and organizational knowledge) related to early adjustment on role clarity, task mastery, and acceptance. Manager ratings later in the year still tracked those early trajectories.
Bauer's earlier SHRM Foundation work on onboarding made the same claim in plainer language: the trajectory starts on day 1. Lauren operationalized it. Quizzes, cameras, and roleplay are just the sensors.
I'd put three sensors on the first week (knowledge check, observed skill, and how they show up). Make the miss a scheduled conversation. If your onboarding cannot tell a manager by day 3 whether someone might be in trouble, you are mostly running a content library with a start date.
5. The Human Element: fuel vs friction
Most revenue leaders I know, myself included, reach for fuel first. Comp, incentives, another enablement hire, a performance plan, encouragement, then pressure. Loran Nordgren and David Schonthal call that fuel in The Human Element. Fuel heightens the appeal of the thing you want people to do.
Friction is the quieter force: effort, inertia, emotion, reactance. We pour on fuel and skip the work of taking friction out of the day.
Lauren's scoreboard moved after she pulled Excel census work off the floor. To quote health insurance, reps had to process a census. If the prospect goes by Nick and the legal name is Nicholas, the quotes for the person and their dependents fail. That is a VLOOKUP problem sitting in the middle of a sales motion.
A lot of the reps did not even know Excel well. Intelligent document processing took the spreadsheet off the reps. RevOps stood it up fast. Product is now building it in for real. Phase 1 was going live the day after we recorded.
Same pattern as the SDR desk. Same pattern as Confluence. The 16-to-6 cut, the 18-to-8 ramp, the 28% AE bookings lift, and the 2x SDR pipeline all sit on the friction side of the ledger. She promised the field three things at kickoff: more time with prospects and customers, more capability personalized to the 20 roles, and more opportunity. There is no excuse, in her words, that they should not be able to give more pipeline with the tools they already have.
I used the organ-donation default on air and I was sloppy with the numbers. Eric Johnson and Daniel Goldstein's 2003 *Science* paper is the clean version: in opt-in countries, effective consent rates sat around 4% to 28%, and in opt-out countries they sat around 86% to 100%. The ask did not change. The friction of the default did.
Marking a lead DQ, toggling a Gong recording, putting Nick instead of Nicholas into a census, tabbing LinkedIn to Salesforce to 6sense: those are defaults you can redesign.
Nordgren's warning is that more fuel can amplify friction. A SPIFF on a broken census process can read as you think they are not trying hard enough. Taking the Excel file off the desk reads as you were paying attention.
Ride-alongs plus data is how she picks which one she is looking at. She tends not to green-light a CRO idea until she's looked at the data.
Hypotheses are cheap.
If your first move on a missed number is a contest, a training, or a PIP, I'd stop and look at what the rep has to do with their hands to produce the behavior you want. Then delete a step.
The through-line is boring on purpose. Lauren keeps calling it dotting i's and crossing t's. She cut the team that existed to refresh Confluence. She'll release people at week 3 if the data says they are ready. Sit for 30 minutes on one contact and you start to see why outbound was slow.
Read the first couple of days like an early-warning system. Take friction out before you add fuel. That is a tighter GTM operating system. Headcount is easier to add once the machine is working better.
If this conversation was useful, rate the podcast. Five stars on Apple or Spotify is the easiest way to get more of these in front of other revenue leaders. Lauren was generous with the actual numbers. The least we can do is get more people listening.