The Ops Stack for a 20-Person Company

At 5 people, you don't need an ops stack. Everyone knows what's happening because they're in the same room. At 100 people, you need dedicated ops infrastructure. But at 20 people — that's where the choices you make determine whether scaling to 50 is smooth or painful.

The principle: integration over features

At 20 people, the biggest ops risk isn't using the wrong tool — it's having the right tools that don't talk to each other. Every disconnected system creates a data gap that someone fills manually. Those manual bridges become bottlenecks as you grow.

The single most important decision at this stage: pick tools that connect, and then actually connect them. A simpler CRM that syncs with your scheduling, billing, and project management is worth more than a powerful CRM that operates alone.

The five components

1. CRM: Your single source of truth

Every client interaction — lead, conversation, project, invoice — should be visible in one place. At 20 people, HubSpot (free tier or Starter) handles this well. Salesforce is overkill. Spreadsheets are insufficient.

The critical requirement: your CRM must integrate with your other tools. If your scheduling platform can't sync to your CRM, either connect them with a custom integration or switch to tools that play together natively.

2. Project management: Track work, not just tasks

At 20 people, you need visibility into who's working on what, where projects stand, and what's blocked. Asana, Linear, Monday, Notion — the specific tool matters less than using it consistently.

The common mistake at this stage: using project management for task lists but not for actual project tracking. Your PM tool should show project health at a glance — not just whether individual tasks are done, but whether the project is on track.

3. Communication: Connected, not scattered

By 20 people, communication has likely fragmented across Slack, email, text, phone, and whatever other channels people prefer. You can't control how people communicate, but you can ensure important communication gets logged.

The minimum: connect your email to your CRM so client communication is tracked. Better: set up channels in Slack for specific projects and integrate them with your PM tool. Best: establish clear norms — client communication happens in these channels, internal coordination happens in those.

4. Financial visibility: Integrated billing

At 20 people, you need to know revenue, expenses, and cash position without asking your accountant. QuickBooks or Xero, connected to your CRM and invoicing tool, gives you real-time financial data.

The integration that matters most: billing data flowing into your CRM. When an account manager can see payment history alongside client relationship data, they make better decisions about upsells, renewals, and retention.

5. Reporting: Automatic, not compiled

If anyone on your team spends more than 30 minutes per week compiling reports, you have a reporting problem. At 20 people, you need dashboards that update themselves — not spreadsheets that someone fills in every Monday morning.

This is where the "integration over features" principle pays off. If your tools are connected, reporting is a view on top of real-time data. If they're disconnected, reporting is a weekly archaeology project.

The integration layer

Having the right five tools isn't enough. They need to be connected. The integration layer is what turns a collection of tools into an ops stack.

At 20 people, you have three options for integration:

Native integrations: Many tools connect natively. Use these first — they're free and low-maintenance. The limitation: native integrations usually handle basic data sync but can't handle complex logic.

iPaaS (Zapier, Make, n8n): Good for simple automations — "when X happens in tool A, do Y in tool B." These work until your automations get complex or your volume gets high, at which point they become fragile and expensive.

Custom integrations: Built specifically for your workflow, with error handling, monitoring, and the ability to handle your business logic. This is what we build at Yolk for teams that have outgrown the first two options.

Most 20-person companies need a mix: native integrations where they exist, an iPaaS for simple automations, and 1-2 custom integrations for their core business data flow.

Common mistakes at this stage

Over-tooling. You don't need 15 SaaS products. You need 5-7 that are well-connected. Every additional tool is another integration to maintain and another place where data can get out of sync.

Under-connecting. Buying the right tools and not connecting them is almost worse than not having them. You end up with more places to check and more manual data entry.

Premature optimization. You don't need enterprise-grade ops infrastructure at 20 people. You need simple, connected systems that work today and can scale to 50. Don't build for 200 when you're at 20.

Ignoring process. Tools don't fix broken processes. Before you invest in ops infrastructure, make sure the underlying processes make sense. If your sales process is inconsistent, a CRM won't fix it — it'll just make the inconsistency more visible.

The investment

Tools: $500-2,000/month for a 20-person company. CRM ($0-200), PM tool ($100-300), communication ($100-200), billing ($50-200), reporting ($0-300), plus 2-3 specialty tools for your industry.

Integration: If you need custom integration work, budget $5-15K for initial setup plus $200-500/month for hosting and maintenance. This is the investment that turns your tools from a collection into a system.

Maintenance: Plan for 2-4 hours/month of ops maintenance — updating workflows, fixing integrations, adjusting reports. This can be a fractional engagement or an internal responsibility, but someone needs to own it.

The total investment is modest compared to the cost of operating without it — which we've estimated at 20-30% of revenue for teams with disconnected operations.