While not a traditional B2B company, Valve Corporation has transformed its gaming platform, Steam, into an epic marketplace with almost unprecedented unit economics. Its success offers profound lessons for any business, especially those in the B2B SaaS sector, on building efficient, capital-light operations.
By 2025, Valve is projected to generate over $17 billion in total gross revenue, with Steam commissions alone accounting for $4 billion at a remarkable 90%+ gross margin. What makes these figures truly astonishing is that they are achieved with an estimated 330-360 employees. This translates to over $12 million in revenue per employee. Focusing solely on the approximately 79-person Steam team managing these commissions, that figure skyrockets to over $50 million per employee. These numbers surpass even the most efficient hedge funds, making Valve a unique case study in the tech industry.
The best private tech company of all is Valve
— Bootstrapped
— $17B gross revenue
— $4B commissions
— $3B profit
— 336 employeesHFS
This is the dream pic.twitter.com/VeIPTjAsz5
— Jason SaaStr.Ai Lemkin (@jasonlk) November 18, 2025
Having spent over 15 years in B2B software and invested in more than 80 companies, I've never witnessed anything comparable. Let's delve into Valve's operational model and extract key insights for building highly efficient, capital-light businesses.
Valve Corporation, founded in 1996 by former Microsoft employees Gabe Newell and Mike Harrington, is renowned for iconic games like Half-Life, Counter-Strike, Portal, and Dota 2. However, its primary revenue driver is Steam, the dominant PC gaming platform controlling approximately 70% of digital PC game distribution worldwide.
Think of Steam as the “AWS of gaming”—it functions as a digital storefront, distribution platform, community hub, and payment processor. Developers upload their games, and Steam handles everything else: downloads, updates, multiplayer infrastructure, anti-cheat measures, payment processing, and discovery for over 130 million monthly active users.
What makes Valve truly remarkable is its ability to build one of tech's most profitable businesses with an exceptionally small team. Operating without VC funding, a board, or traditional managers, its approximately 360 employees generate over $6.5 billion in annual revenue. It represents perhaps the closest example of a “perfect” platform business model.
2025 Key Metrics:
- $16.2B+ in total Steam game sales (through mid-November, with 44 days remaining)
- $4B+ in Valve commission revenue
- 330-360 total employees (essentially unchanged since 2012)
- ~79 employees running the entire Steam platform
- $50M+ revenue per Steam employee
- 130M+ monthly active users
- 39.3M peak concurrent players (2024 record)
- 13,000+ games released annually
Learning #1: The 30% Rule — Platform Tax vs. Platform Value
The Metric That Matters: Valve charges a 30% commission on game sales up to $10 million, 25% from $10-50 million, and 20% above $50 million. Steam generated over $4 billion in commissions through November 2025, a significant increase from $3.2 billion in 2024 and approximately $100 million in 2009—a 40x growth in 16 years. Total game sales on Steam exceeded $16.2 billion in 2025.
The fascinating aspect is the ongoing debate about whether a 30% cut is “fair.” Competitors like Epic Games launched with a 12% rate, developers often complain, and regulators investigate. However, the crucial factor isn't the percentage itself, but the value created per dollar of commission.
Steam offers far more than just distribution. It includes:
- A powerful discovery engine (with over 13,000 games released annually)
- Automatic updates and cloud saves
- Robust community features and a workshop
- Anti-cheat and matchmaking infrastructure
- Integrated payment processing for over 130 million monthly active users
The harsh reality is that many platforms charging 30% don't deliver 30% of value. Valve, however, does. This is why, despite Epic's aggressive 12% offer and years of competition, Steam maintains approximately 70% of PC game downloads.
The SaaStr Parallel:
In B2B SaaS, we often scrutinize take rates in marketplaces, typically aiming for 10-25%. Valve demonstrates that if you genuinely provide immense value—real distribution, discovery, and infrastructure—customers will pay premium rates. The key is to make the platform so indispensable that opting out becomes more costly than opting in.
Tactical Takeaway:
Avoid competing solely on price. Instead, strive to embed your product so deeply into your customers' workflows that the cost of switching outweighs your commission. Valve achieved this by building tools, community features, and player accounts that are so integral that games essentially require Steam for PC success.
Learning #2: The 79-Person Platform — Team Size as Strategy
The Brutal Metric: In 2025, approximately 79 employees manage the entire Steam platform, handling over 13,000 game releases annually and serving more than 130 million monthly active users. This equates to over 1.6 million users per employee. Meanwhile, Valve's total headcount has remained remarkably stable at 330-360 employees (virtually unchanged since 2021), including about 180 in game development and 40 in hardware.
This isn't merely lean; it represents a fundamentally different operating model. Compared to similar-scale platforms:
- PlayStation: ~$2M revenue per employee
- Nintendo: ~$1.5M revenue per employee
- Xbox: ~$1.1M revenue per employee
Valve's 45-50x advantage (over $50 million per Steam employee in 2025) is not just about efficiency; it's architectural. Valve designed Steam from its inception to be maximally automated and self-service. Publishers upload games, algorithms manage discovery, the community self-moderates, updates push automatically, and payment infrastructure scales infinitely.
This approach contrasts sharply with how most B2B companies scale, which often involves adding Customer Success Managers, building implementation teams, and creating support tiers—typically 3-5 new hires for every $1 million in new Annual Recurring Revenue (ARR).
The SaaStr Parallel:
The most successful B2B companies I've invested in achieve Net Dollar Retention (NDR) of 120-130% with minimal human intervention. Less efficient ones require armies of CSMs to reach 110%. The difference lies in product-led growth engines that automate onboarding, expansion, and retention.
Companies like Owner.com (a portfolio company with 10.63x MOIC) exemplify this by building AI-powered tools that automate 80% of tasks previously requiring sales calls. RevenueCat (6.44x MOIC) developed such an effective self-service product that developers integrate it without needing to speak to anyone.
Tactical Takeaway:
Before hiring, always ask: “Could we build a feature to address this need instead?” Valve's competitive moat stems from building systems where competitors hired people. Systems scale; people don't.
Learning #3: Gross Margins Above 95% — The Ultimate Unit Economics
The Numbers That Matter: Steam's operating margins are projected to remain near 60% by 2025, with an estimated operating profit approaching $2.4 billion on over $4 billion in commissions. Crucially, the gross margins on digital distribution are effectively 95%+.
Why such high margins? There's zero cost of goods sold, no inventory, no manufacturing, no fulfillment centers, and no returns. Selling one copy of a game costs Valve the same as selling 10 million copies; the incremental cost approaches zero.
This translates to extraordinary capital efficiency:
- Valve is bootstrapped (never raised VC funding).
- Estimated annual revenue of over $6.5 billion by 2025.
- Approximately 40-50% net profit margin (over $2.5 billion in profit).
- 330-360 employees.
- Average salary of over $1.3 million per employee (2021 data, likely higher now).
This is the ideal scenario, but it's important to recognize that this level of efficiency cannot be retrofitted. Valve built for it from the very beginning through critical early decisions:
- Digital-only when physical retail dominated (2003).
- Platform-first instead of focusing solely on game sales.
- Developer tools that fostered publisher self-sufficiency.
- Community-driven discovery over editorial curation.
Each decision initially prioritized margin over market share. Over two decades, these margins compounded, leading to the most profitable business model in gaming.
The SaaStr Parallel:
The difference between 70% and 85% gross margins can define whether a SaaS business is merely decent or truly generational. Those 15 percentage points impact:
- How much you can spend on Customer Acquisition Cost (CAC).
- How rapidly you can grow without dilution.
- Whether you need Series C, D, or E funding to scale.
- Exit multiples (e.g., 10x vs. 20x revenue).
Many founders accept 60-70% gross margins as "good enough," but it's not. Gorgias (8.35x MOIC in my portfolio) meticulously pursued 85%+ margins before aggressive scaling. This discipline creates future options.
Tactical Takeaway:
Every 5 percentage points of gross margin matter exponentially at scale. Fight for them early, even when it seems insignificant. At $100 million in revenue, 5 points translate to $5 million more profit, which could fund 10-15 additional employees or increase go-to-market spend by 30-40% without requiring dilutive capital.
Learning #4: Flat Structure Enables Speed at Scale — Organization as Product
The Organizational Metric: Valve operates with zero managers, no hierarchy, and employees literally move their desks to work on projects they choose. With 330-360 people generating over $6.5 billion in revenue, this represents a 0% management overhead model. Remarkably, this headcount has remained virtually unchanged since 2012 (when they had around 250 people), even as revenue has grown 3-4x.
Many dismiss this model as unworkable for their own organizations. However, they miss the point: Valve's structure isn't merely about being employee-friendly; it's designed to maximize decision velocity.
Consider typical B2B software companies with $50-500 million in revenue:
- They often have 5-8 layers of management.
- Decisions require a minimum of 3-4 meetings.
- Feature prioritization can take weeks of debate.
- Resource allocation is often political rather than optimal.
Now, compare this to Valve's model:
- Engineers identify an opportunity within the Steam economy.
- A team self-assembles around the project.
- The feature ships to over 40 million daily users (2024: 39.3 million peak concurrent players).
- Iterations occur based on direct feedback.
This results in a minimum 10x difference in speed. However, this model only works if:
- Hiring is perfect (Valve's hiring bar is famously high).
- Compensation is transparent (everyone understands the stack ranking).
- Product is the organizing principle (not titles or territory).
- Non-performers are fired instantly (there's no room to hide).
Yanis Varoufakis, the economist, joined Valve in 2012 and wrote about their structure. His key insight was that "Traditional firms exist to solve coordination problems. Valve eliminated those problems through product design."
The SaaStr Parallel:
The fastest-moving companies I know don't have fewer meetings due to strict discipline; they have fewer meetings because they built systems that eliminate the need for them.
At SaaStr Fund I, my most successful deals came from founders who outpaced the market. Pipedrive, Algolia, Talkdesk—all demonstrated perfect records. Speed was the common thread, not recklessness, but rather systematic velocity.
My portfolio companies with 5-10x MOICs maintain "small company speed" even at scale. Those struggling at 2-3x often suffer from too many managers and committees.
Tactical Takeaway:
Count your management layers. If you're at $10 million ARR with more than 3 layers, you're building bureaucracy, not a business. At $50 million ARR with more than 4 layers, you're already too slow. Every additional layer halves your decision speed.
Learning #5: Network Effects at the Asset Layer — Building Moats Where Others See Features
The Data Point: The Steam Community Market processes millions of monthly transactions for in-game items (skins, weapons, etc.) in games like CS2 and Dota 2. Valve takes a small cut from each transaction. This isn't just revenue; it's a moat.
Here's the genius: Most platforms conceptualize network effects at the user layer. Valve built them at the asset layer.
Every CS2 skin, Dota 2 item, and trading card exists exclusively within Steam. Players invest thousands of hours and real money accumulating these digital assets. Convincing them to leave Steam would mean abandoning their valuable inventory.
The numbers illustrate this:
- The CS2 skin market alone exceeds $1 billion in annual transactions.
- Some rare items sell for over $100,000.
- Players often have "Steam accounts" with assets valued between $5,000 and $50,000.
This creates what I call “economic gravity”—the more you use the platform, the more expensive it becomes to leave. This isn't due to contracts or lock-in, but because of the accumulated value within the ecosystem.
The Numbers Behind the Moat:
- Over 1 billion registered Steam accounts (lifetime).
- Over 130 million monthly active users (2025).
- 39.3 million peak concurrent users (2024 record).
- Average user has over 100 hours invested in their game library.
- Plus digital assets worth real money.
Compare this to the Epic Games Store, which launched with a 12% commission (versus Steam's 30%). Despite over six years of aggressive subsidies and exclusives, Epic has captured perhaps only 10-15% market share. Why? Because Epic offers merely distribution, while Steam provides economic infrastructure.
The SaaStr Parallel:
The best B2B companies don't just have high switching costs; they possess accumulating value that makes switching economically irrational.
Salesforce doesn't just store your CRM data. It encompasses:
- A decade of historical records.
- Custom workflows that power your business.
- Integrations with over 100 other tools.
- Reports executives rely on daily.
- Extensive user training and muscle memory.
Extracting this system doesn't just incur monetary costs; it risks the entire go-to-market engine.
In my portfolio, RevenueCat perfectly embodies this. They don't just process app subscriptions; they become the source of truth for subscription data, analytics, and experimentation. After 6-12 months, customers have built dashboards, attribution models, and pricing experiments all dependent on RevenueCat's data. Moving to a competitor means losing historical continuity.
Tactical Takeaway:
Ask yourself: “If our customer used our product for two years, what have they accumulated that makes leaving painful?” If the answer is merely “our contract,” you lack a true moat. Build features that create accumulating value: analytics history, workflow automation, team collaboration artifacts, or literal economic assets.
The Meta-Lesson: Efficiency at Scale Requires Different DNA
My study of Valve, juxtaposed with 15+ years in B2B SaaS, reveals a crucial insight:
You cannot simply "hack" your way to Valve-level efficiency. This isn't about fractional CTOs or lean operations. It's about fundamentally different architectural decisions made at a time when efficiency might have seemed like a disadvantage.
In 2003, Steam was initially inferior to retail distribution across almost every metric:
- Slower downloads (compared to buying a physical CD).
- Required an internet connection (not universally available then).
- No used game market.
- No lending games to friends.
- Required running background software.
Valve chose digital distribution not because it was immediately better for users, but because it would eventually create dramatically superior unit economics. They were willing to be worse initially to become orders of magnitude better in the long run.
This pattern is evident in the best B2B companies as well. They make architectural choices that:
- Enable 85-90% gross margins (not 70%).
- Design for self-service (not high-touch interactions).
- Build systems (rather than hiring more people).
- Create powerful network effects (beyond mere stickiness).
- Optimize for terminal value (not just current convenience).
The results speak for themselves: Valve's employee count has remained essentially flat at 330-360 people for over a decade, while revenue has surged from approximately $2 billion to over $6.5 billion. This exemplifies the compounding power of making the right architectural decisions early on.
What This Means for Your B2B Company
If you're building B2B software today, Valve's model offers clear guidance:
- At $1-10M ARR: Make the difficult architectural decisions now. Prioritize self-service over high-touch, even if it slows initial growth. Design for 85%+ gross margins, resisting the temptation of services revenue. Build systems that eliminate the need for future headcount.
- At $10-50M ARR: Relentlessly measure efficiency. What is your revenue per employee? It should be a minimum of $300K-500K, ideally $500K-750K. Count management layers—you shouldn't have more than 3. Any decision taking over a week should be escalated as a process problem.
- At $50M+ ARR: By this stage, you've either built the foundation for Valve-style efficiency, or you haven't. If not, you're in a different category—you can still build a great business, but your exit multiple will reflect your ongoing need for capital and headcount to scale. If you did, you're building something with generational potential.
Short-Term Sacrifice for Long-Term Dominance
The true lesson from Valve isn't that every company should adopt flat hierarchies or generate $50 million per employee. It's that the decisions leading to extraordinary efficiency are often invisible and uncomfortable when your company is small.
Valve spent two years building Steam while competitors focused on shipping games faster. They developed community features while others prioritized transactions. They hired 79 exceptional individuals for Steam while competitors recruited hundreds. Crucially, they maintained this discipline, keeping headcount essentially flat for over a decade while revenue tripled.
In B2B SaaS, I observe the same pattern. Companies achieving 5-10x returns made hard, expensive, and non-obvious choices early on:
- Spending six months building self-service onboarding (instead of manual processes).
- Declining enterprise customers to preserve product simplicity.
- Investing in APIs before there was significant demand.
- Building robust analytics infrastructure before reaching $10 million ARR.
These decisions might seem counterintuitive when optimizing for next quarter's ARR. However, they are precisely correct when building for over $100 million in revenue and a generational outcome.
Valve proves the ultimate arbitrage in tech: short-term sacrifice for long-term structure. Build the foundation for efficiency when it seems expensive and unnecessary. Sixteen years later, you could be generating over $4 billion in commission revenue with approximately 80 people running the core platform, and a total headcount still under 400.
That is the dream.
Jason Lemkin is the founder of SaaStr and managing partner of SaaStr Fund ($200M), with investments in companies like Owner, Assistant UI, Alloy. Algolia, Pipedrive, Talkdesk, Salesloft, Gorgias, and RevenueCat.
