You’ve hit product-market fit. Customers are pulling your product out of your hands, revenue is compounding, and the team has grown from a scrappy dozen to a working 30. Then someone says the words that make every founder’s stomach drop: “We need to go from 30 to 100.” That stretch — the chaotic 10-to-100 headcount phase — is where most startups break. The product isn’t the bottleneck anymore; operations are. And the ops checklist nobody shares is exactly the one you need right now. This is not about IPO-ready processes or enterprise-grade governance. It’s about building just enough operational scaffolding to let your team move fast without tripping over each other.
The Morning After Product-Market Fit
PMF is intoxicating. You spend months inventing a SalesOps process, then you wake up with 40 employees and realize nobody owns the onboarding flow, your expense policy is a group chat, and your “documentation” is a Notion page with three orphaned tabs. The transition from PMF to 100 employees is not a scale-up; it’s a rewiring. And most advice about it is either too abstract (“build a culture”) or too premature (“implement OKRs everywhere”).
The first truth is that operational rigor at this stage should be invisible. You’re not building bureaucracy; you’re building predictability. Every process you add must either remove friction or reduce cognitive load for your team. If it doesn’t, it’s waste.
Reinventing Communication Before It Breaks
At 10 people, communication is natural. At 50, it’s chaos. The biggest operational failure in the 10-to-100 phase is assuming that if everyone is “aligned,” you don’t need a communication structure. You do. But the wrong structure can be worse than none.
Asynchronous by Default, Synchronous by Exception
One of the smartest moves you can make in 2026 is to declare asynchronous communication the default for everything except idea generation, tough feedback, and crisis response. This isn’t about remote vs. in-office — it’s about giving people focused time.
- Adopt a lightweight “working document” culture for strategy and project updates rather than endless status meetings.
- Limit Slack/Discord channels to 80% noise reduction. Create a “decision log” channel where every major decision and its rationale is posted.
- Replace daily standups with a written progress note that takes three minutes to read.
None of this needs new software. It needs discipline.
Performance Management Without the HR Theater
When you cross 20 employees, you’ll feel the pull to “professionalize” performance reviews. Don’t. A 40-page performance review template will not help a company that still hasn’t defined what good looks like for a sales engineer or a product designer.
The 3×3 Performance Check
Instead of a heavyweight system, use a 3×3 framework: three expectations, three check-ins per quarter, three outcomes. At the start of each quarter, every employee and manager agree on three priorities that directly connect to company goals. Then they have a 20-minute check-in every month, not to score, but to unblock.
At 70 people, you’ll need a real compensation band and a promotable-leveling rubric. But build those only when you have at least three people in the same role. Before that, you’re just creating paperwork.
Financial Ops: From Back-of-Envelope to Boardroom
The cash-burn spreadsheet that served you at 8 people is dangerous at 40. In the 10-to-100 phase, financial ops is not just about not running out of money — it’s about knowing your unit economics inside out, at the team level.
- Move to a modern accounting stack that integrates with your bank and your billing platform. This is not optional.
- Build a rolling 12-month cash forecast that is updated every two weeks. Review it with your leadership team, not just your finance person.
- Create a cost-per-head map: understand all-in employee cost (comp, benefits, tools, recruiting, onboarding) for each department. It changes how you think about hiring.
- Institute a “procurement light” rule: anything over $500 gets a quick approval, but under that, no one needs to ask. This keeps velocity while preventing chaos.
If you don’t have a finance person beyond a part-time accountant, now is the time to hire a strong finance operations lead — not a CFO, but someone who can build the dashboards and own the workflow.
Building Your Ops Stack Without Buying Bloat
The SaaS landscape is a trap. Every vendor will tell you that you need a “single source of truth” for everything. In reality, the 10-to-100 phase is about using as few systems as possible, but integrating them well.
Core Systems to Adopt at the Right Time
- HRIS: At 15+ employees, you need one for payroll, time-off, and data. Try to avoid the Frankenstein approach of multiple tools that don’t talk to each other.
- ATS: The moment you plan to hire more than 2 people in a month, get a real applicant tracking system. Yes, it feels like overkill until it’s not.
- Customer platform: Your CRM should already be there. But make sure it’s the system of record for sales, support, and product feedback. Don’t let each team pick its own.
- Internal knowledge base: A not-ugly wiki (Slite, Guru, Notion, or your HRIS’s built-in) where the only acceptable content is how-to guides, policies, and project docs. No random thoughts.
Remember: every tool you add creates an operating cost in training, password resets, and cross-tool context. Integrate early, but don’t automate what you don’t understand yet. Manual workflows are easier to change when you’re small.
The Human Ops Layer: Onboarding, Culture, and Firing
Ops isn’t just data and workflows. The most critical operating system is the one that helps humans feel oriented and empowered.
Onboarding as a Structured Experience
By the time you pass 25 people, “just shadow someone” is a terrible onboarding plan. Build a 30-day onboarding checklist for every new hire: role-specific skills, company context, and buddy-system introduction. Document it, and assign an owner.
Culture is a Commitment, Not a Poster
At 10 people, culture is vibes. At 50, culture is your operating system for decision-making. Write down your operating principles — not values, but actual decision rules like “we optimize for revenue per employee” or “we default to transparency internally.” Then use those rules to resolve disputes.
The Hardest Ops Discipline: Performance Ejections
Hiring mistakes happen. The ops playbook nobody shares includes a clear, humane process for letting someone go before they poison a team of 40. Build a documented performance improvement plan process that is fair and fast, not legal theater. Every week of delay in a bad hire costs you exponential team morale.
A Practical Ops Checklist for the 10-to-100 Grind
Here’s a checklist that will keep you sane. Use it ruthlessly, and revisit it whenever you feel like you’re operating by echo.
- Build a leadership team cadence — one weekly meeting with written agendas and decisions posted.
- Define your 3 company-level KPIs for the next quarter and cascade to team-level metrics.
- Create a cost-per-employee dashboard and review it monthly.
- Maintain a “micro-manual” of operating procedures that is easy to search.
- Set a policy for expense limits, travel approval, and remote equipment — don’t rely on ad-hoc exceptions.
- Assign one person (often an operations generalist) to own the entire employee lifecycle, from offer letter to offboarding.
- Schedule a quarterly “process cleanup” where you remove five things that are no longer needed.
- Encourage a peer-feedback mechanism that isn’t tied to performance reviews.
- Make sure every manager has at least 1-on-1s with their direct reports every two weeks.
- Track involuntary attrition — if it’s low but satisfaction is low, you’re just avoiding the hard conversations.
The Ops Checklist Nobody Shares is a Mindset Shift
The most overlooked operational skill in the transition from PMF to 100 employees is knowing what not to do. Discipline is about subtraction, not addition. Every time you implement a new process, ask: “Will this let a capable person make a better decision faster?” If the answer isn’t a clear yes, cut it. The chaotic 10-to-100 headcount phase is survivable when you build an operating rhythm that is explicit enough for 100 people to trust, but light enough for 5 founders to pivot. That’s the secret. It’s less about control and more about clarity.
As you go from 30 to 60, you will be tempted to over-engineer. Resist. Instead, build the smallest set of repeatable rituals around communication, performance, finance, and technology. That is the ops checklist nobody shares — and the one that will carry you to your next hundred without your team losing its soul.
