Signs your company has outgrown its operating systems (a 20-point checklist)

Most founders don’t notice the moment their company outgrows its operating systems, because there isn’t one moment. It’s a slow accumulation of small workarounds — a process someone invented under deadline pressure in year two, a spreadsheet that quietly became a system of record, a person who became a department without anyone deciding that on purpose. None of it looks like a crisis at the time. It just adds friction, a little at a time, until the friction is the operating model.

Below are twenty signs we see repeatedly in founder-led companies between roughly 20 and 250 employees. You won’t have all of them. If you recognize more than half, the business has likely outgrown the systems that got it here — and hiring your way through it, one role at a time, will keep feeling like it should be working without actually working.

People and decisions

1. Most important decisions still route through you, even ones your title says someone else owns.
2. New hires take months to become productive because “how we do things” only lives in senior people’s heads.
3. Two people asked the same question get two different correct-sounding answers.
4. You’ve said “let me just do it myself” about something below your level in the last month.
5. Your best people are your biggest single points of failure — if they left tomorrow, something important breaks.

Hiring

6. Hiring quality varies from great to expensive mistake and nobody can say why.
7. There’s no consistent interview process — it depends on who happens to be free that week.
8. You can’t clearly describe what “good” looked like on your last few hires versus your last few misses.
9. Roles get filled reactively, after someone’s already burning out covering the gap.

Numbers and reporting

10. Reporting is inconsistent, late, or requires interpretation before you can trust it.
11. Margins are eroding and nobody can point to exactly why.
12. The monthly close routinely lands weeks later than it should.
13. Different people quote different numbers for the same metric in the same meeting.
14. You find out about problems from a customer or a bank balance before you find out from a report.

Technology and process

15. Your tech stack is a dozen disconnected tools held together by a spreadsheet layer.
16. At least one “system” in the business is actually a person who remembers how things work.
17. AI or automation experiments are happening but disconnected from any specific business outcome.
18. Data gets re-typed between systems because nothing talks to anything else.

The overall pattern

19. Headcount keeps growing but coordination cost grows faster than output does.
20. The business is increasingly running you, instead of you running it.

What the checklist is actually telling you

None of these twenty items is, by itself, a functional problem with a functional fix. A recruiter can’t fix item 20. A new reporting tool can’t fix item 3. They’re symptoms of a business that scaled its revenue faster than it scaled its systems — and the systems debt shows up everywhere at once because it’s one underlying thing, not twenty separate things.

The useful next step isn’t to pick the item that hurts most this week and go fix it in isolation. It’s to figure out which of these are symptoms of the same upstream constraint — because they usually are — and fix that first. That’s the diagnostic work we walk through in detail on How We Work. A lot of the reporting and process items above (10 through 14) trace back to operations that were never designed in the first place — see Operations for how we approach that specifically.