A Founder Is Not a King
The Dream
Most founders I know have a similar story: they’re tired of working for The Man, they’re frustrated by poor leadership, they believe they can solve the problem better, faster, and with more heart than the incumbents. They think they can do it all. For entrepreneurs, particularly in the age of AI-driven development, they think that founding their own company can give them all of that. They can be the benevolent dictator that drives a billion dollar valuation.
It’s a seductive story, one that I’ve felt myself. You had the idea. You took the risk. You built something from nothing, often while those around you said that it would never work, that you’re nuts. That story is so real, so relatable. It’s the reason we start companies in the first place.
But, to bastardize Sun Tzu, that dream doesn’t survive contact with reality, the kind of reality defined by term sheets, employee agreements, customer contracts, and the legal system. The dream says that founding means you answer to no one.
That dream is often a nightmare.
The counter-intuitive reality is that, as a founder, you answer to more people than almost anyone else in the building. And the consequence of getting that wrong? They’re far more personal than any of your employees.
What You Actually Signed Up For
Before I go any further, I need to make a disclaimer: I am not a lawyer. I am not your lawyer. This is not legal advice. This is a set of observations about what I’ve learned about where the rights of founders begin and end. That’s it.
With that out of the way, let’s discuss what you signed up for.
When you incorporated your company, you became an officer of a legal entity. That sounds like a title, like a knighthood as an Officer of the British Empire or something. But in many ways, it’s a Sword of Damocles above you, a set of obligations that constrain your actions.
Fiduciary duty isn’t a bunch of buzzwords on a contract. It’s not a technicality. It means you are legally required to act in the best interest of the company. Not your preferences, not your convenience, not your vision of what the company should be. The company as it actually exists, with its actual stakeholders. Duty of care means you have to act like a reasonably prudent person in your role. Duty of loyalty means you can’t subordinate the company’s interests to your own.
These aren’t abstract ideas or fancy words to scare you. They’re the basis of lawsuits. Very expensive ones. They’re the reason officers get named personally in litigation. Your employees can be fired and walk away. You can be sued.
The Stack You’re Actually At the Bottom Of
The org chart might show you at the top of the pyramid. You’re the Big Boss, the Head Honcho, the King of the Hill. But when you look at the contracts you signed, you see a different story.
If you have a board, you’re accountable to your board through your shareholder agreements. You’re accountable to your investors through the representations you made when they wrote you a check. You’re accountable to your employees through labor law, which governs everything from how you can treat them to payments to retaliation. You’re accountable to your customers through your contracts. And you’re accountable to regulators through statute, whether you’ve read the relevant ones or not.
This is an example where ignorance of the law is not an excuse.
Kings answered to no one, and most of them eventually lost their heads. The modern founder has more counterparties with legal recourse than almost any other role in business. The modern crown is mostly decorative.
A Clean Example
Say someone notifies you of a contracted deliverable, one that you are uniquely qualified to resolve. They ask you in person. They ask you in email, in Slack, through a Jira ticket. There’s documentation of the deliverable. Months pass. You’re reminded occasionally, but you defer. No action is taken.
That’s not a backlog problem. That’s a paper trail of willful negligence, and depending on the nature of those deliverables, it may already be a breach of your contractual obligations to customers, your duties to investors, and potentially various regulatory frameworks. “I’ll get to it eventually” is not a defense. Quite the opposite, it’s Exhibit A in a lawsuit that will drain you of money, time, your reputation and energy.
Nobody had to accuse you of anything. The timeline did it for you.
The Good News
If there’s one thing I’ve noticed about the founders who don’t end up in these situations, they’ve figured out, early, that the obligations aren’t a cage. They’re a map.
When you understand that you have a duty of care, you don’t resent folks who tell you something’s wrong. You thank them for creating an opportunity to fulfill an obligation you already had, and you may not have even known it. When you understand fiduciary duty, you stop making decisions based on what’s convenient for you and start making them based on what’s best for the company. That’s not a constraint on your vision or your ability to execute. I prefer to think of it as a big flashing neon sign pointing the way to success. It’s what successful execution actually looks like.
The founders who treat accountability as an affront and an obstacle to their personal playground are the ones who confuse the feeling of having built something with the legal reality of what they built. Those are different things. The company isn’t you. You are a steward of the company.
The best founders I’ve seen know this. It doesn’t make them less bold. It makes them more precise. And like almost all successful people, those with constraints are the most innovative.