Dear SaaStr: What Is the Biggest Difference Between Running a 10-Person Startup and a 100-Person Startup?

A 10-person startup feels like a speedboat. Everyone can see the horizon, hear the engina small fleet. It can travel farther and carry more, but only when captains know their routes, crews understand their responsibilities, and nobody assumes the founder will personally radio every boat.

That is the biggest difference: at 10 people, the company runs through direct founder involvement; at 100 people, it must run through an organization the founder has designed.

The product may look similar. The logo may be unchanged. The office may still contain suspiciously expensive coffee. Underneath, however, the company’s operating system must be rebuilt.

Note: Employee counts are useful milestones rather than magical borders. Depending on its business model, complexity, and working style, a startup may encounter these changes earlier or later.

At 10 People, the Startup Is One Conversation

In a 10-person startup, communication is almost frictionless. The founder can explain a customer problem over lunch, revise the roadmap at 2:00 p.m., and hear objections before 2:07. Most employees know which deals are shaky, why a feature is late, and who forgot to order more coffee filters.

This environment rewards generalists. An engineer may join a sales call, a marketer may edit onboarding copy, and the CEO may handle recruiting, pricing, customer support, and a leaking sink before dinner. Job descriptions are less like legal documents and more like opening suggestions.

A small team benefits from fast decisions, direct customer feedback, flexible priorities, and a culture that employees can observe every day. Yet this model depends heavily on shared context. People know what to do because they heard the original discussion, sat beside the founder, or absorbed the reasoning through repeated exposure.

That works beautifully until dozens of employees were not in the room.

At 100 People, Communication Becomes Architecture

At 100 employees, the company can no longer operate as one conversation. Information must move through managers, written plans, dashboards, meetings, project systems, and cross-functional teams.

If those channels are poorly designed, the organization develops its own folklore. Sales believes product promised one thing, product believes sales invented it, and finance would simply like everyone to stop offering discounts selected by roulette wheel.

Writing Replaces Repetition

A scaling startup needs a dependable source of truth. Important priorities, decisions, responsibilities, and operating principles should be documented so employees do not need privileged access to the founder’s memory.

This does not require a 400-page manual titled How to Breathe at Our Company. It means recording information people repeatedly need, including company goals, team responsibilities, product strategy, decision owners, hiring standards, and explanations of how work moves from idea to execution.

Clarity Replaces Proximity

In a tiny company, proximity supplies context. In a larger startup, leaders must intentionally create clarity. Employees need to know what matters now, how success will be measured, who has authority, and when a problem should be escalated.

Without that clarity, employees either freeze or send every question upward. Both outcomes turn the executive team into a very expensive customer-support queue.

The Founder’s Role Changes Completely

A founder in a 10-person startup is usually the company’s most informed operator. The founder may be the best salesperson, product manager, recruiter, storyteller, and troubleshooter because that person has touched nearly every problem from the beginning.

At 100 people, this strength can become a bottleneck. A founder who insists on approving every hire, reviewing every campaign, rewriting every sales deck, and joining every product discussion may feel admirably committed. In practice, the company is waiting in line outside one person’s brain.

The founder’s new job is to recruit capable leaders, give them clear outcomes, evaluate their performance, and ensure that they work well together. Instead of personally driving every function, the founder builds an executive team that can translate strategy into repeatable execution.

By approximately 50 to 100 employees, most startups need experienced leadership across major functions such as engineering, product, sales, marketing, customer success, finance, and people operations. Exact titles matter less than real accountability.

Delegation Is Not Disappearing

Delegation does not mean the founder vanishes into a private office and communicates only through mysterious calendar invitations. Founders should remain deeply involved in mission, strategy, capital allocation, executive hiring, culture, and decisions that could materially change the company’s future.

The goal is to stay close to the truth without becoming the approval step for ordinary work. Effective founders ask sharp questions, monitor meaningful indicators, maintain customer contact, and make high-leverage decisions. Ineffective founders edit button colors while the sales forecast catches fire.

Management Becomes a Product the Company Must Build

At 10 people, everyone may report to a founder. At 100, that arrangement is exhausting and ineffective. Teams need managers, managers need coaching, and every employee should know who sets expectations, provides feedback, supports development, and resolves problems.

Promoting the strongest individual contributor is not automatically the answer. The best engineer may not enjoy management. The top salesperson may be brilliant at closing deals but terrible at coaching others. Management is a distinct profession, not a ceremonial badge awarded for surviving the longest.

A growing startup should define what good management looks like and train new managers accordingly. Regular one-on-one meetings, clear goals, useful feedback, fair performance reviews, and prompt conflict resolution may sound less exciting than launching a product. They also prevent every personnel issue from becoming an executive emergency.

Process Changes From Enemy to Infrastructure

Early startup teams often dislike process because bad process slows learning. That instinct is healthy. A 10-person company should not need three committees to change its pricing page.

At 100 people, however, the absence of process also creates delays. Recruiting without consistent evaluation, launching features without clear owners, approving discounts through private messages, or onboarding employees through oral tradition produces confusion and expensive rework.

The objective is not maximum process. It is minimum effective process: enough structure to make common work predictable while preserving judgment for unusual situations.

A Useful Process Answers Four Questions

  1. Who owns the outcome?
  2. Who contributes information?
  3. Who makes the final decision?
  4. Where is the decision recorded?

When these answers are obvious, the company can move quickly without inviting everyone to every meeting. When they are vague, 14 people contribute comments and nobody presses “approve.”

Culture Must Move From Osmosis to Reinforcement

At 10 employees, culture is largely the founders’ behavior made visible. People see how leaders treat customers, handle mistakes, debate ideas, spend money, and respond under pressure.

At 100 employees, many new hires rarely interact with the founders. Their experience comes through managers, onboarding, promotion decisions, incentives, meeting habits, and the stories coworkers tell.

Culture is therefore not what leadership says during an all-hands meeting. It is what the organization repeatedly rewards, tolerates, and corrects.

Generic values such as “innovation,” “integrity,” and “excellence” accomplish little unless they guide actual choices. Can an employee challenge a senior leader? Does the company favor long-term customer trust over a questionable quarter-end deal? Will teams release a useful improvement or wait indefinitely for perfection?

Leaders preserve the best elements of startup culture by converting them into hiring criteria, onboarding stories, management expectations, and daily operating habits. The objective is not to preserve every early behavior. Eating dinner at the office five nights a week may be a memory, not a value.

Hiring Becomes a Talent System

The first employees often join because they know the founders, love the problem, or enjoy ambiguity. Hiring is personal, opportunistic, and heavily founder-led.

Reaching 100 employees requires a system. The company needs workforce planning, role definitions, structured interviews, compensation ranges, reference checks, and onboarding that helps new hires become productive without collecting clues like participants in an escape room.

Hiring quality can deteriorate during rapid expansion because urgency encourages compromise. One weak hire is noticeable on a 10-person team. A wave of weak hires at 100 can lower standards, slow decisions, and consume managers’ attention.

Retention also matters. Growing from 10 employees to 100 does not mean hiring exactly 90 people. Some employees will leave, some jobs will change, and some early hires will discover that they preferred the speedboat. Headcount plans must account for turnover and the time required to integrate new employees.

The Company Starts Running on Operating Rhythms

A small startup coordinates through constant conversation. A larger one needs a dependable cadence: company planning, quarterly goals, weekly team reviews, financial analysis, customer feedback, and executive meetings focused on decisions rather than dramatic readings of slide decks.

Metrics become more specialized as well. Leaders may need indicators for pipeline, conversion, customer retention, product delivery, service quality, hiring, cash runway, and operating efficiency.

The objective is not to create a dashboard museum. It is to identify problems before they become expensive surprises.

What Commonly Breaks Between 10 and 100 Employees?

  • Founder bottlenecks: Too many ordinary decisions still require one person.
  • Unclear ownership: Several teams contribute, but nobody owns the result.
  • Premature hierarchy: Titles multiply faster than leadership ability.
  • Weak management: Specialists are promoted without training or support.
  • Communication gaps: Critical context remains trapped in meetings and private messages.
  • Culture dilution: Hiring speed outruns onboarding and behavioral standards.
  • Process overload: Every mistake produces another permanent rule.

The solution is not to imitate a giant corporation. A 100-person startup should remain faster, closer to customers, and more adaptable than an established enterprise. Structure should preserve speed, not require a task force to investigate why speed disappeared.

How to Prepare for the Next 90 Employees

Document the Strategy

Explain the target customer, problem, product advantage, business model, and current priorities in language a new employee can understand. Strategy that exists only in the founder’s head cannot scale.

Clarify Decision Rights

Define which decisions belong to founders, executives, managers, and individual contributors. Push routine decisions toward the people closest to the relevant information.

Hire Leaders Before the Company Is Desperate

Executive searches take time, and rushed leadership hires are costly. Recruit people who can handle the next stage while still operating effectively in today’s imperfect environment.

Standardize Hiring and Onboarding

Use role scorecards, structured evaluation, compensation principles, and 30-, 60-, and 90-day onboarding plans. Employees should learn the company by design, not archaeology.

Train Managers

Teach managers to set expectations, provide feedback, conduct one-on-one meetings, communicate change, and make fair personnel decisions.

Protect Customer Contact

As organizational layers appear, founders and product leaders should continue speaking directly with customers. Otherwise, the company may become excellent at discussing itself.

Remove Unnecessary Process

Add structure when it solves a repeated problem. Remove it when the cost exceeds the value. Every recurring process should have an owner and a reason to exist.

Conclusion: The Mechanism of Execution Must Change

The biggest difference between running a 10-person startup and a 100-person startup is not the number of desks, Slack channels, or birthday cupcakes. It is the mechanism through which work gets done.

At 10 people, the founder personally supplies context, energy, judgment, and coordination. At 100, those qualities must be distributed through leaders, managers, written communication, operating systems, and clear accountability.

The founder stops being the person who touches everything and becomes the person who builds an organization capable of succeeding without touching everything.

This transition can feel uncomfortable because it replaces heroic improvisation with organizational leverage. Yet it is the only sustainable way to preserve speed as complexity rises. A well-run 100-person startup should not feel like a bloated version of the 10-person company. It should feel like the original ambition finally acquired enough capable handsand enough coordinationto deliver on it.

Experience-Based Perspective: What the Transition Really Feels Like

The journey from 10 to 100 employees is rarely a smooth multiplication exercise. It feels more like rebuilding an airplane while discovering that half the passengers have strong opinions about wing design.

At approximately 10 people, a founder often ends the day tired but informed. Nearly every important issue has crossed the founder’s screen. There is comfort in that visibility, even when the workload is absurd. As the company grows, the founder may become less physically busy with individual tasks but more mentally responsible for systems, leaders, and second-order consequences. Problems are now solved in rooms the founder did not enter.

One memorable turning point is the first time an employee says, “I didn’t know we had decided that.” In the early days, repeating an idea twice felt excessive. Later, a major priority may need to be explained in an executive meeting, documented in writing, discussed by managers, reinforced during an all-hands meeting, and connected to team goals.

This repetition is not necessary because employees are inattentive. It is necessary because attention is distributed across a much larger organization.

Another difficult moment comes when a talented early employee struggles in a changed role. The person who heroically handled support, onboarding, and customer success for the first 50 customers may not want to manage a department of 20 people. That does not erase the employee’s contribution. It simply reveals that different stages require different work.

Thoughtful companies create paths for early employees to grow as specialists, managers, or cross-functional operators. They do not treat management as the only promotion available or assume that every founding-era employee should lead a large department.

Founders also discover that hiring a senior executive does not create instant relief. A new vice president needs context, trust, authority, and time to evaluate the team. When a founder delegates responsibility but retains every meaningful decision, the executive becomes a messenger with an impressive title. When the founder withdraws completely, the executive may build a function disconnected from the company’s actual needs.

The productive middle is an active partnership followed by increasing autonomy.

The emotional experience of culture changes too. At 10 people, culture feels personal. At 100, it can feel inconsistent because different managers create different local environments. Leadership may insist that the company values transparency while one team shares information openly and another treats its roadmap like classified intelligence.

This is when culture work becomes operational. Manager selection, incentives, promotion standards, internal communication, and consequences matter more than inspirational slogans painted on a wall.

The happiest surprise is that effective delegation does not reduce the founder’s influence. It multiplies it. A capable sales leader improves dozens of customer conversations. A strong engineering manager removes obstacles for an entire team. A thoughtful people leader helps every manager become more effective.

The founder’s fingerprints become less visible, but the founder’s judgment travels farther.

The practical lesson is simple: do not try to preserve the exact feeling of a 10-person startup forever. Preserve its urgency, candor, customer focus, and willingness to act. Replace its dependence on memory, proximity, and heroics. That is how a startup reaches 100 employees without waking up as the slow company it once planned to defeat.