The Scaling Crucible: Navigating the Hardest Decisions When Growing from 10 to 100
The journey from 10 to 100 employees isn't just growth—it's a fundamental transformation that will challenge every assumption you have about your company, your leadership, and yourself. Here's a framework for the decisions that will define your next chapter.
Listen to this article
The Transformation Nobody Warns You About
Somewhere between employee number 23 and employee number 47, something strange happens. The company you built stops feeling like your company. The culture you cultivated through late nights and shared meals begins to dilute. People you've never met are making decisions in your name.
This isn't failure. This is scaling.
The journey from 10 to 100 employees is arguably the most treacherous passage in a company's life. You're too big to operate on instinct and too small to have the infrastructure of a mature organization. Every day brings decisions that feel impossible—and many of them are irreversible.
After speaking with dozens of founders who've navigated this passage (some successfully, some with battle scars), I've identified the five decision categories that consistently prove most difficult. More importantly, I've found frameworks that can help you approach them with greater clarity.
Decision One: When to Let Go of Your First Believers
Here's a truth that keeps founders awake at night: the people who got you to 10 often aren't the people who will get you to 100.
Your first marketing hire was brilliant at scrappy, guerrilla tactics when you had no budget. But now you need someone who can build a team, manage a seven-figure spend, and create scalable systems. Your original engineer who built the prototype with duct tape and genius is struggling to lead a team of twelve and implement proper code review processes.
These aren't bad employees. They're miscast employees. And the decision about what to do with them will reveal what kind of leader—and what kind of company—you're building.
The Framework: The Honest Conversation First
Before making any personnel decisions, have what I call the "two futures" conversation. Sit down with the person and paint two honest pictures:
- Here's what this role will look like in 18 months
- Here's where I genuinely see your strengths
Sometimes, these align beautifully—and you've just retained a loyal employee by showing them the growth path. Sometimes, they don't—and the employee often realizes it before you have to say it.
The key is approaching this conversation not as a performance review but as a shared exploration. What do they want? Where do they see themselves thriving? You might discover your first marketing hire actually hates managing people and would love to become an individual contributor specialist. Or you might discover they've been quietly taking leadership courses and are hungry for the challenge.
The worst decision is the one you avoid making. Carrying someone in a role they can't grow into hurts them, their team, and ultimately the customers you serve.
Decision Two: Which Processes to Formalize (And Which to Leave Messy)
At 10 people, you can operate on shared context and hallway conversations. At 100, that's a recipe for chaos. But here's the trap: over-systematizing too early creates bureaucracy that strangles the very agility that made you successful.
The question isn't whether to add process—it's which processes matter most.
The Framework: The Pain-Point Audit
Instead of implementing processes based on what "real companies" do, start with a simple audit:
- What decisions are being made inconsistently across the company?
- Where are balls being dropped repeatedly?
- What questions do new employees ask most often in their first month?
Formalize the answers to these questions first. Everything else can wait.
For example, if you keep having incidents where customer commitments conflict with engineering capacity, you need a process for how customer-facing teams communicate with product. If new hires consistently feel lost for their first two weeks, you need onboarding documentation.
But if your product team has a quirky, informal way of brainstorming that produces great results? Leave it alone. Not everything needs to be systematized. Some of your best work emerges from productive chaos.
Tools like thonk can help here by letting you consult multiple perspectives on which processes truly need structure. Sometimes an outside view reveals that what feels like chaos is actually working—or that what feels fine is actually causing downstream problems you can't see.
Decision Three: When to Hire Ahead of the Curve
One of the most common pieces of scaling advice is to "hire ahead"—bring in people before you desperately need them so they're ramped up when demand hits. It sounds wise. It's also how companies burn through runway and create org chart bloat.
The counter-advice is to stay lean and hire only when you're drowning. This sounds prudent. It's also how companies miss market windows and burn out their best people.
Neither approach is universally right. The real skill is knowing which roles require which strategy.
The Framework: The Ramp-Time Matrix
Consider two variables for each potential hire:
- Time to productivity: How long until this person is fully effective?
- Cost of vacancy: What's the real impact of not having this role filled?
Roles with long ramp times and high vacancy costs (engineering leadership, enterprise sales, specialized technical roles) require hiring ahead. The cost of being late is too high.
Roles with short ramp times, even if important (many operations roles, some marketing functions, customer support), can be filled more reactively. You can catch up quickly.
This framework prevents both premature hiring and dangerous understaffing by forcing you to think about the dynamics of each role rather than applying a one-size-fits-all philosophy.
Decision Four: How to Preserve Culture While Changing Everything
Here's the paradox of scaling: to keep what matters about your culture, you have to change almost everything about how it's transmitted.
At 10 people, culture is absorbed through proximity. New hires learn how things work by watching, by osmosis, by the dozen informal interactions they have each day. At 100, most employees will never have a meaningful conversation with you. Culture must be explicitly designed, documented, and reinforced through systems.
This feels like selling out. It's actually growing up.
The Framework: The Culture Archaeology Exercise
Before you can scale your culture, you need to understand what it actually is—not what you wish it were or what your website says.
Gather your leadership team and ask:
- What behaviors do we celebrate when no one's watching?
- What do we tolerate that we probably shouldn't?
- What would a new employee find surprising about how we actually work?
- What would make a high performer leave?
The answers to these questions reveal your real culture. Now you can make conscious decisions about what to preserve and what to change.
Maybe you discover that your culture of "work hard, play hard" has quietly become "work constantly." Or that your commitment to transparency has eroded into selective information sharing. Or that your early scrappiness has become an excuse for underinvestment in tools and training.
You can't preserve something you haven't honestly examined.
Decision Five: When to Bring in Outside Leadership
Eventually, you'll face the question that strikes at the heart of founder identity: should you hire executives who've "done this before"—even if they might change the company in ways you didn't anticipate?
The argument for experienced leadership is compelling. Someone who's scaled a company from 50 to 500 brings pattern recognition you simply don't have. They've seen the failure modes. They know which problems are coming before they arrive.
The argument against is equally compelling. Career executives can bring bureaucratic habits from larger companies. They may not understand what made your company special. They might optimize for what they know rather than what you need.
The Framework: The Three Questions
Before hiring any senior executive, get clear on three things:
-
What specific capability gap are we filling? Not "we need a VP of Sales" but "we need someone who can build a repeatable enterprise sales motion and develop our current team."
-
What stage experience do they actually have? Someone who's been VP of Sales at a 5,000-person company has different skills than someone who's built a sales team from 5 to 50. Match the experience to your stage.
-
What are we unwilling to change? Be explicit about the non-negotiables. If you're committed to remote work, or a specific approach to customer relationships, or a particular decision-making style—say so upfront. The right executive will embrace these constraints. The wrong one will try to "fix" them.
This is an area where gathering diverse counsel proves invaluable. Your board sees one perspective. Your team sees another. Your customers see a third. The best decision emerges from synthesizing all of these views—something we explore often on thonk as a core principle of sound judgment.
The Meta-Decision: How You Decide
Perhaps the most important scaling decision isn't any single choice—it's establishing how your growing organization will make decisions.
At 10 people, decisions happen through consensus or founder fiat. Neither scales.
Consensus becomes impossible when you have 100 people with 100 opinions. Founder fiat becomes a bottleneck that slows everything down and disempowers your leaders.
You need a decision-making framework that clarifies:
- Who has authority to make which decisions
- Who needs to be consulted vs. informed
- How disagreements get resolved
- When decisions can be revisited
This isn't bureaucracy. It's clarity. And clarity is kindness when you're asking people to move fast in uncertainty.
The Patience Required
I'll leave you with this: the passage from 10 to 100 typically takes 2-4 years. That's a long time to live in the crucible.
There will be days when you question everything. When the decisions feel impossible and the right path seems hidden. When you miss the simplicity of the early days and wonder if scaling was worth it.
In those moments, remember that every company you admire went through this same passage. The ones that emerged stronger weren't the ones who made perfect decisions—they were the ones who made thoughtful decisions, learned from the outcomes, and kept moving forward.
The crucible doesn't last forever. But who you become inside it—that lasts.
Take your time with these decisions. Seek counsel from those who've walked this path. Trust that clarity often comes not from having all the answers, but from sitting patiently with the questions until the right path reveals itself.
Make Better Decisions
Assemble your own AI advisory council on thonk and get diverse perspectives on any decision.
Try thonk freeRelated Posts
Beyond the Gut Check: Building a Hiring Process That Actually Works
Most hiring decisions are made in the first five minutes of an interview, then rationalized for the remaining fifty-five. Here's how to build a process that honors both intuition and evidence—and consistently finds the people who will actually thrive.
The Hiring Paradox: Why Your Best Interview Might Produce Your Worst Hire
We've built elaborate rituals around hiring—behavioral interviews, case studies, reference checks—yet most organizations admit their hit rate is barely better than chance. Here's how to escape the theater of confidence and build a hiring process that actually predicts success.
The Pivot Paradox: How to Know When Your Startup Needs a New Direction
The hardest part of pivoting isn't the execution—it's knowing whether the signals you're seeing demand a course correction or simply more patience. Here's a framework for cutting through the noise when your startup's future hangs in the balance.