Corporate or Owner-Run? Size Isn't What Separates Them

During a stretch of consulting work, I walked in and out of two different companies in the same week. At the first one I wanted to add a small library to the project: three separate approvals, one security review, ten days. At the second I mentioned the same need to the owner, he said “just add it,” and it was in production by that afternoon.

What stayed with me that week wasn’t which one was better. It was that neither one was free. At the first company I lost ten days. At the second, six months later, that library sat unmaintained and nobody remembered why it had been added in the first place.

That’s what this series digs into: the type of company you work at determines how much of your work is actually yours — and nobody puts that in the job ad. This first post sets the vocabulary: what actually separates these two types, and what doesn’t.

What doesn’t separate them: headcount

This is the most common misreading. “Corporate” makes people think large; “owner-run” makes them think small.

I’ve seen four-hundred-person owner-run companies with real revenue and offices in three countries, where every meaningful decision still came out of one room. I’ve also seen twenty-five-person teams that operated with surgical discipline and wrote their decisions down — companies where the founder could vanish and nothing would stall for two years.

Size is a consequence, not a cause. Growth increases the pressure toward institutionalisation, because the owner’s head doesn’t scale. But pressure isn’t law.

The four axes that do separate them

If you want to read a company in your first week, don’t look at the org chart. Ask these four questions.

1. Where are decisions made? Does a role decide, or a person? When you ask “who approves this?”, is the answer a title (“the tech lead”) or a name (“you’d have to ask Ahmet”)? The difference looks small. It is the whole thing.

2. How much is written down? Not the code — the reasoning. Does the answer to “why did we pick this database?” live somewhere, or does it require finding a slot in one specific person’s calendar?

3. Who gets billed for mistakes? When something breaks, is the first thing anyone looks for a cause or a person? That single reflex gives away a company’s character; I’ve given it an entire post later in this series.

4. How far ahead does the company look? Is it thinking about this quarter or the next three years? In an owner-run company the horizon is usually the cash-flow horizon. In a corporate it’s the budget cycle.

Being institutional means the decision can be separated from the person. Being owner-run means the decision stays with the person. Process, meetings, approval chains, performance systems — all of it is downstream of that one difference.

Not two types — four states

Don’t finish this and conclude “corporate good, owner-run bad.” Over the years I’ve seen both types healthy and both types sick. The real distinction isn’t the type; it’s the state it’s in.

	Healthy	Sick
Corporate	Decisions are role-bound, process grew out of a real incident, ownership is clear	Process reproduces itself, nobody owns a decision, “that’s the procedure” counts as an answer
Owner-run	Fast, end-to-end visibility, the decision has an obvious owner	Decisions track the owner’s mood that day, no boundaries, no record

The years I spent in a healthy owner-run company taught me more than the months I spent in a sick corporate. The reverse is also true. The name of the type tells you nothing. Its state tells you everything.

Question: How do I tell which state a company is in? Answer: One question: “Is there a process you removed in the last year?” A healthy corporate gives you a concrete example. A sick one doesn’t understand the question — because there, process gets added, never removed. In an owner-run company the answer is usually “we don’t really have processes.” That’s an answer too.

Three desks

Every post in this series has a section like this one. The reason: nothing that happens inside a company has a single correct reading. The same event looks completely different depending on which desk you’re sitting at — and every desk has a legitimate constraint.

From the senior engineer’s desk. What you want is predictability: to know the reasoning behind a decision, to know where your job starts and ends, to trust that good work will be noticed. Your constraint: you usually don’t know the cash position, the customer pressure, or what the owner can’t afford to risk. Because you don’t know, some decisions look arbitrary to you. Some of them are. Some of them aren’t.

From the manager’s desk. What you want is room to manoeuvre. You’re standing between a target handed down from above and the capacity of the team below, and you have to say “no” in both directions. Your constraint: budget is fixed, timeline is fixed, headcount is fixed. The only elastic variable you have is usually the team’s patience — and once you spend it, it doesn’t come back.

From the owner’s desk. What you want is speed and survival. You carry the risk out of your own pocket; a bad decision isn’t a rough quarter for you, it’s your money. Your constraint: you can’t know everything, but you feel obliged to decide everything. As the company grows, the knowledge in your head turns into the company’s bottleneck — and you are usually the last person to notice.

These three constraints collide. The engineer’s “why are we so slow?” and the owner’s “why are we so expensive?” are two ends of the same event. Both are right. Both are incomplete.

So what is this good for?

Reading a company’s type isn’t a way to complain. It’s a way to calibrate.

Grumbling that “there’s no process here” in an owner-run company is wasted energy. What’s valuable there is the speed itself; your job is to notice where that speed spills into decisions you can’t undo, and put a brake there. Not everywhere.

Grumbling that “everything is slow here” in a corporate is just as empty. What’s valuable there is that decisions don’t depend on any one person; your job is to translate good work into a language the system can read. Not to sulk at the system.

I’ve watched a lot of engineers make the same mistake in both places: refusing to use the strength of the type they’re in, while resenting its weakness. That is the most expensive and quietest waste in a career.

What’s next in the series

This first post built the vocabulary. From here on, it’s where those four axes hit the ground:

• How decisions actually get made — approval chain or single signature?
• When does process protect you, and when does it become a shackle?
• Role boundaries, knowledge flow, promotion and pay, meetings, crisis.
• And exactly what breaks when a company grows.

For now, I’ll leave you with this. In your next interview, before you ask about salary, ask this: “Who can reverse this decision?” The answer will tell you more about the company’s type, its state, and the two years you’d spend there than the entire job ad does.