How two founders run like a 200-person company

Most early-stage companies are missing three roles: a CFO, a COO, and a Chief of Staff.

You can’t hire them yet. The numbers don’t justify it, and even if they did, finding all three at the right level for a six-person company is functionally impossible. So founders do what founders do: they absorb the work themselves, badly, in the margins.

The result is predictable. The books are mostly right. Operations are mostly running. Decisions are mostly tracked. Mostly — across every dimension, every week, forever — adds up to a company that’s slower, foggier, and more fragile than it needs to be.

The interesting question isn’t how to hire those three roles earlier. It’s how to install the operational substrate they would build, before you can afford any of them.

What a CFO actually does

Strip away the title and a CFO does three things: closes the books with accuracy, models scenarios with rigor, and makes the numbers narrate the business so leadership can act on them.

The first is automatable. Modern accounting tooling handles the mechanics; the CFO’s contribution is structural — chart of accounts, accruals, audit trail, board-grade reporting.

The second is harder. Scenario modeling is judgment-dense. But the infrastructure for scenario modeling — versioned forecasts, live cash and burn, fork-and-compare — is now table stakes. You don’t need a CFO to run scenarios. You need a system that lets you run them yourself without rebuilding the model from scratch every quarter.

The third is the real CFO move: making the numbers tell the story. That’s a function of how the data is structured. If every line item traces back to the decision that produced it, the narration writes itself. If not, you’re stitching spreadsheets at 2am to explain a variance.

What a COO actually does

A great COO does one thing exceptionally well: they create institutional memory for execution.

The hire that didn’t work out — they remember why, and the lesson shapes the next hire. The vendor that overpromised — they remember the tradeoff that led to choosing them, and the next vendor decision starts smarter. The cross-team project that stalled — they know what the failure mode was, and they design the next one to avoid it.

This is what’s missing in most early teams. Not the execution itself — founders are usually good at execution. The memory of execution. The pattern recognition that comes from logging every decision, attaching its reasoning, and watching what happens.

You can’t shortcut this with a hire — even a great COO needs context to be effective. But you can build the substrate from day one. Every decision logged with its rationale. Every workstream attached to its history. Every tradeoff captured before it disappears.

By the time you do hire a COO, they walk into accumulated judgment instead of a blank slate.

What a Chief of Staff actually does

Chiefs of Staff are routers. They sit between functions and make sure context travels between them — that the marketing team knows what engineering decided, that finance knows what sales committed to, that the founder knows what’s actually happening across every team without having to attend every meeting.

This is the function most early teams skip entirely. And it’s the function that shows up most painfully when context fails to route — when finance is modeling on assumptions ops has already abandoned, or when engineering is building toward a strategy sales has quietly pivoted away from.

You can’t hire a Chief of Staff for a six-person company. But you can install the routing layer they would build. Decision logs the right people automatically see. Cross-functional visibility without cross-functional meetings. A single surface where the state of the company is queryable, not assembled from twelve separate tools.

The compounding payoff

The argument for installing this infrastructure early isn’t just that it makes you faster today. It’s that every decision you make becomes a permanent organizational asset.

The first hundred decisions a company makes are foundational. They establish how things get done, what tradeoffs are acceptable, what the company values. If those decisions are captured with their context, the company that hires its hundredth employee inherits all of that judgment automatically. If they’re not, the hundredth employee inherits a folklore version of the company’s history, with most of the reasoning lost.

Two founders won’t run like a 200-person company because they have 200 people. They’ll run like one because they built the operational backbone of one — before they had to.