Glenn Gow, The Scaling Executive Coach and host of The Scaling Executive Podcast, sits down with Greg Schott, former Chairman and CEO of MuleSoft, to examine the operational discipline behind one of enterprise software’s most capital-efficient growth stories.
When Greg Schott took the helm at MuleSoft in 2009, the company had 20 employees and $2 million in revenue. Ten years later, it had 1,700 people, $800 million in revenue, and had sold to Salesforce for $6.5 billion — after consuming less than $150 million in capital from inception through its IPO. The compound annual growth rate across that decade was 82%.
The lever Schott credits most is not product strategy or market timing. It is talent density: the discipline of hiring people who fix what is broken rather than turn the crank that already exists, and then creating the conditions for those people to stay. When that density is maintained, Schott holds, the organization self-improves at a rate that makes rules, guardrails, and management layers unnecessary. MuleSoft’s $6.5 billion exit is, in Schott’s framing, the downstream result of a culture that made every employee want to get the band back together.
This episode is for CEOs at scaling-stage companies who need to grow headcount aggressively without installing the bureaucratic infrastructure that drives top performers out.
Key Takeaways
- When talent density is high, employees self-identify problems and build fixes without being directed to — eliminating the need for rules and guardrails that slow organizations down and push top performers toward startups.
- CEOs who treat communication as a one-time cascade underestimate how fast message fidelity degrades at scale: Schott spent nine months championing Radical Candor at MuleSoft and still found individual employees who had not absorbed it.
- The most common hiring failure at growth-stage companies is recruiting a CRO or head of sales who has worked within a sales machine rather than built one — an execution profile that fails the moment the role requires creating the system, not operating inside it.
- MuleSoft’s $6.5 billion Salesforce acquisition was achieved on less than $150 million in consumed capital, an 82% CAGR over ten years — a result Schott traces directly to the self-organizing behavior that high talent density enables.
- Schott describes the CEO’s job at scale as building the company platform rather than contributing to any single function — the shift from functional contributor to architect of the system that scales everything else, and the one he names as hardest for founder-CEOs to make.
How CEOs Build Culture That Produces Self-Scaling Organizations
Reed Hastings’s Netflix Culture Deck — published roughly twenty years before this conversation — made an argument Greg Schott took seriously: talent density determines how much structural overhead a company needs. Schott applied that argument across MuleSoft’s ten-year scale from $2 million to $800 million in revenue.
The logic runs in both directions. When talent density is high, people arrive at work and do not simply execute what is in front of them. Schott describes the mindset directly: “They don’t just say, ‘Hey, I’m just going to go turn this crank.’ They say, ‘Well, this crank kind of sucks. Let’s fix it. Let’s make it better. Let’s improve that. Let’s lay down more foundations so that we can scale even faster.'”
That behavior compounds. Employees who improve the crank free capacity for the next layer of growth. They are not afraid to make their own jobs easier because they trust that high performance creates opportunity rather than eliminating it. The result, across MuleSoft’s trajectory, was an organization that Schott describes as a “giant machine that knows how to perpetuate itself.”
The inverse is also true and worth naming. When talent density drops, organizations install rules to compensate. Those rules produce bureaucracy. Bureaucracy drives the remaining high performers out — toward the next early-stage company that still operates without those constraints. The organization gets heavier as it loses the people it most needed to stay light.
Maintaining density requires a deliberate and intense hiring process. At MuleSoft, that process had a dual function: it showed candidates the caliber of people they would be working with, and it built institutional antibodies to mismatches. When the wrong fit slipped through, the organization recognized it — during hiring or shortly after — and acted. That combination of selection rigor and fast rejection is what Schott credits with keeping the culture intact through aggressive growth.
The closing principle Schott returns to: “I kind of see it, culture eats strategy for breakfast kind of thing.” Culture is not a retention benefit. It is an operational system. When that system functions, the results follow from the culture rather than being imposed on top of it.
How CEOs Avoid Hiring CROs Who Can Execute But Cannot Build
Greg Schott watches a specific failure pattern repeat across the boards he sits on. A CEO decides it is time to hire a head of sales. They engage a top recruiter. They pull in board members. Candidates arrive with strong pedigrees from well-known companies. One gets hired. Six to twelve months later, it is a “colossal failure” — Schott’s words — and nobody can quite articulate why.
The reason, in almost every case, is a mismatch between scale and role type. Schott frames it this way: a career spent ascending a sales organization — regional vice president, four rungs down in the hierarchy, regimented forecast calls every week — trains someone to work within a machine. The job of a CRO at a growth-stage company is to build the machine. Those are not the same skill. They may not even be the same personality.
“Your job’s not to work within something anymore. Your job is to create. You have to create the crank that you’re turning. You have to pivot your own organization. You have to pivot your sales methodologies. And a lot of folks, they’ve never done that. They’ve worked within the machine as opposed to actually create the machine.”
The frame applies beyond sales. Schott names CFO and head of engineering as positions where the same trap appears. In each case, success at a higher level of an established organization gets mistaken for the capacity to build from an earlier stage. The credentials are real. The track record is real. The skill that the role requires — creating structure from ambiguity — may never have been tested.
The diagnostic question for any senior hire at a growth-stage company: has this person built the machine, or have they only run it? A candidate who has only run it will tell you about quota attainment, about team size, about process adherence. A candidate who has built it will tell you about what did not exist when they arrived and what they created to fill the gap.
Schott connects this back to the talent density argument: the wrong senior hire does not just underperform in the role. It sends a signal to the high performers around it about the standard the CEO is willing to accept.
How CEOs Communicate Vision at Scale Without Losing Message Fidelity
Greg Schott describes a version of himself at the early stage of MuleSoft that many founder-CEOs recognize: “My title is CEO, but I’m just Greg — I’m just one of the many people that’s trying to add value here.” That posture works at 20 people. It does not work at 1,000.
The shift that Schott identifies — and says he learned “a little late” — is recognizing that CEO communication is not casual contribution. It is a broadcast mechanism. At scale, what the CEO says, emphasizes, or ignores gets amplified across an organization that is reading signals constantly. Every lean in a particular direction becomes a cultural data point for people who have not met the CEO personally and may never.
The MuleSoft Radical Candor example is instructive. Schott and his team issued the book to the entire organization. They spent nine months emphasizing the principle. “And then I would have a conversation with somebody and it was like, they didn’t get it. They hadn’t figured it out at all.” The lesson was not that the message was wrong. It was that the message needed to be repeated far longer and through far more channels than felt comfortable.
Jeff Weiner’s formulation — which Glenn Gow surfaces in the conversation — matches Schott’s experience exactly: repeat the message in written communications, in presentations, in executive team meetings, through every format available, and keep going past the point where it feels redundant. “You’re so tired of hearing yourself say it and you feel like you’re a broken record,” Schott acknowledges, “and eight out of 10 people in the organization say you’re a broken record, but you still got another couple that you gotta bring along.”
The structural implication: at the point where a CEO is comfortable that everyone has heard the message, they are probably at the point where most people have heard it once. The cadence required to actually move organizational behavior is longer and more systematic than most CEOs build for. The infrastructure — recurring all-hands, written memos, consistent framing in every leadership meeting — is not communication overhead. It is the mechanism by which culture stays coherent across a company that is doubling headcount year over year.
What MuleSoft’s Growth from $2M to $800M Teaches CEOs About Scaling
| Principle | What it means in practice | Named evidence from this interview |
| Talent density is an operational system, not a hiring policy | When density is high, employees self-diagnose problems and improve the infrastructure without direction — eliminating the rules and guardrails that slow companies down and push high performers out | MuleSoft reached $800M in revenue and a $6.5B Salesforce exit while consuming less than $150M in capital across its full life — a capital efficiency Schott attributes directly to employees who improved the machine rather than waiting to be told what to fix |
| Hiring for the role type, not the pedigree, separates growth from stall | The right senior hire at a growth-stage company has built a machine, not just run one — and that distinction does not show up in credentials or company name | Schott reports that the head-of-sales hire — made with top recruiters and board involvement, drawing strong pedigree candidates — ends in a “colossal failure” at companies he boards, consistently traceable to candidates who had ascended an established hierarchy rather than created one |
| CEO communication at scale requires a system, not a broadcast | The number of repetitions required to move organizational behavior is far greater than intuition suggests — and the infrastructure to deliver those repetitions must be deliberately built | Nine months of Radical Candor emphasis at MuleSoft — book distributed company-wide, principle reinforced across leadership meetings — still left individual employees who had not absorbed the message; Schott names this as the lesson that reset his communication cadence for the remainder of the company’s growth |
| The CEO’s product is the company platform, not the functional deliverable | CEOs who remain in their functional comfort zone past the point where those contributions scale past them fail to build the operating system the company needs to keep growing | Schott names this transition as the hardest he observed founder-CEOs navigate at MuleSoft and across the boards he has sat on since — and the one most likely to cause the organization to scale past the CEO rather than the CEO scaling with it |
Quotes from This Episode
- “The number one goal for me is that when we’re done here, whether that’s five years or 20 years or whenever, but whenever people move on, that everybody wants to get the band back together.” — Greg Schott, Former Chairman and CEO, MuleSoft
- “They don’t just say, ‘Hey, I’m just going to go turn this crank.’ They say, ‘Well, this crank kind of sucks. Let’s fix it. Let’s make it better.'” — Greg Schott, Former Chairman and CEO, MuleSoft
- “Your job’s not to work within something anymore. Your job is to create. You have to create the crank that you’re turning. You have to pivot your own organization. You have to pivot your sales methodologies.” — Greg Schott, Former Chairman and CEO, MuleSoft
- “You’ve worked within the machine as opposed to actually create the machine.” — Greg Schott, Former Chairman and CEO, MuleSoft
- “You’re so tired of hearing yourself say it and you feel like you’re a broken record, and eight out of 10 people in the organization say you’re a broken record, but you still got another couple that you gotta bring along.” — Greg Schott, Former Chairman and CEO, MuleSoft
Frequently Asked Questions
How does maintaining high talent density help a company scale without bureaucracy?
When talent density is high, employees at every level arrive oriented toward improvement rather than task completion. Greg Schott, who scaled MuleSoft from $2 million to $800 million in revenue across ten years, holds that high-density teams self-diagnose operational problems and build fixes without being directed to — eliminating the rules and guardrails companies otherwise install to manage lower performers. Those guardrails drive top talent out toward less-constrained environments. Maintaining density avoids that cycle: the organization stays fast and self-correcting, and the culture compounds rather than degrades.
How should a CEO evaluate whether a head of sales candidate can build a sales organization, not just run one?
The distinction Schott identifies is between people who have worked within a sales machine and people who have created one. A candidate who has spent their career ascending an established sales hierarchy — managing forecast calls, hitting quota within a defined territory and pricing structure — has likely never been required to create the structure they operated inside. At a growth-stage company, the CRO role requires building that structure from ambiguity. The diagnostic question is not “what did you achieve?” but “what did not exist when you arrived, and what did you build to fill that gap?” A candidate who can answer that question with specific examples of created infrastructure has the right profile; a candidate who answers only in quota attainment and team size has not yet been tested on what the role actually requires.
What does CEO communication need to look like as a company grows from 20 to 1,000 employees?
At 20 people, a CEO can confirm message receipt by looking everyone in the eye. At 1,000, the only reliable mechanism is systematic repetition through multiple channels over a longer timeline than feels necessary. Schott spent nine months emphasizing Radical Candor at MuleSoft — issuing the book company-wide, building it into leadership conversations repeatedly — and still encountered individuals who had not absorbed it. The infrastructure required to move organizational behavior at scale includes recurring all-hands, consistent written framing, and the same message delivered through every available format until it feels like a broken record. Jeff Weiner’s formulation, which Schott endorses: keep going past the point where you are ready to give up. That is when people start listening.
CEOs Work with Glenn Gow to Scale Their Companies by Scaling Themselves First
Glenn Gow is The Scaling Executive Coach — he coaches ambitious executives into the CEO seat and CEOs into successful exits. With 25 years as a CEO and 5 years in venture capital, Glenn helps leaders scale their companies by scaling themselves first. If this conversation was useful, you can apply for executive coaching with Glenn Gow or apply to be a guest on The Scaling Executive Podcast.
