Key Takeaways
- Business headcount naturally outgrows engineering in scaling companies unless founders impose an artificial constraint.
- During Cristina Cordova's seven and a half years at Stripe, founders Patrick and John Collison stopped commercial expansion when sales hiring outpaced engineering, product, and design.
- To solve this, Stripe mandated that at least 40% of all employees sit in technical roles: engineering, product, design, and data.
- If sales teams wanted more account executives, they had to source and recruit engineers first to keep the company above the 40% floor.
- This discipline survives in high-efficiency companies like Linear, which reached over $100M ARR with roughly half the headcount of typical SaaS peers by using Stripe's 40% Technical Headcount Ratio Rule.
The Stripe's 40% Technical Headcount Ratio Rule
Sales teams are easier to hire than engineers. Left unchecked, go-to-market teams balloon, the company's center of gravity shifts away from product, and engineers spend their days answering custom feature requests for sales reps. At Stripe, leadership countered this drift with a strict operational ceiling.
Here are the three components of that operating rule:
- 1. Establish a Technical Watermark: Determine the desired DNA of the organization and establish a non-negotiable headcount ratio floor (at Stripe, at least 40% of all employees had to belong to engineering, product, design, or data).
- 2. Categorize and Monitor Headcount by Function: Create a centralized headcount tracking spreadsheet, classify every team member by department, and continuously calculate the operational percentage across all business lines.
- 3. Tie Business Expansion to Technical Recruiting: Freeze commercial hiring if the ratio threatens to dip below the watermark, requiring sales and GTM leadership to actively source and hire technical talent before opening additional business roles.
At Linear, Cordova carried over the same vigilance: “I created a headcount spreadsheet. It was one of the first things I did: put everyone into their categories of what function they're in, calculated the percentage, and I watch it.” (play from 1:10:45) Combined with rigorous pre-hire work trials and a refusal to add SDRs, Linear reached $100M ARR with a lean staff. “If you look at most companies at our stage and revenue, they have teams that are almost double the size in terms of headcount. We can be a lot more nimble than other companies because you're not moving this gigantic ship whenever you need to change direction.” (play from 1:06:22)
When This Works (and When It Doesn't)
This rule works when scaling high-growth software companies to prevent sales and operational headcount from diluting an engineering- and product-driven culture. It forces sales leadership to understand that their ability to close deals depends directly on product quality, not just phone calls.
It fails when your product requires human-in-the-loop operations. If you run a fintech with manual compliance reviews, a logistics platform with field dispatch, or a marketplace needing round-the-clock trust and safety teams, a blanket 40% technical ratio will starve your actual operations. In those models, segment your operational staff separately before applying the technical floor to your corporate core.
What to Do With This
Open your company roster today and tag every employee as technical (engineering, product, design, data) or non-technical (sales, marketing, recruiting, legal, operations). Calculate your current ratio. If your technical percentage is below 40%, announce an immediate freeze on commercial requisitions. Inform your sales and marketing managers that no new business positions open until they submit five vetted engineering referrals who make it to on-site technical interviews.