After analyzing our last 12 investments, a surprising pattern emerged. The founders who negotiated this one specific clause in the cap tables consistently outperformed. I'm breaking down the data and showing you the exact language that correlates with a higher chance of success.
The Framework That Actually Works
Here is a simple framework for evaluating cap tables. It's not complicated, but it requires discipline.
Step 1: customer feedback is the only metric that matters
This is where most people go wrong. They skip this step entirely and jump straight to execution. Don't do that.
Step 2: you should focus on one thing and do it exceptionally well
Once you have the foundation right, this becomes much easier. I've watched founders struggle with this for months when the answer was staring them in the face.
Step 3: Iterate relentlessly
Nothing works perfectly the first time. The companies that get cap tables right treat it as an ongoing process, not a one-time project.
Why Most Approaches Fail
Many common approaches to cap tables are flawed at the root.
The root cause is usually one of three things:
Copying what big companies do without understanding why they do it. What works for Google doesn't work for a 10-person startup.
Over-engineering the solution when a simple approach would work better. I've seen teams spend six months building something that could have been done in two weeks.
Ignoring the human element. Technology is the easy part. Getting people to actually use it is where the real challenge lives.
The Counterintuitive Truth
In cap tables, the best practitioners often do less, not more.
The lesson: timing is everything in this game. It sounds simple. It's incredibly hard to execute.
Real Talk: What Actually Matters
Here is what actually matters in cap tables.
First, execution speed beats perfection. Every time. Companies rarely fail because they moved too fast on cap tables. Many fail because they moved too slowly.
Second, measure everything. If you can't measure it, you can't improve it. Set up tracking from day one, even if it's basic.
Third, talk to your users. It sounds obvious, but many founders make decisions about cap tables in a vacuum. Get out of the building. Talk to real people.
This connects to broader themes around syndicate investing, secondary markets, term sheets, portfolio construction, cap tables that I've been thinking about a lot lately.
What's Next
Best practice in cap tables is changing fast. What worked last year might not work next year. That's both the challenge and the opportunity.
My advice: stay curious, stay humble, and stay close to the people who are actually doing the work. Read less thought leadership and do more experiments. Talk to fewer consultants and more practitioners.
If you're building in this space, the best time to get cap tables right is before you need to. Don't wait for a crisis to force your hand.
I'll keep sharing what I learn. This stuff matters too much to keep to myself.
Frequently Asked Questions
Q:What experience informs this perspective?
This perspective comes from over a decade of building companies in Silicon Valley, two successful exits (RemoteTeam to Gusto, MovieLaLa to Gfycat), and investing in 234 startups including Anthropic, OpenAI, and Scale AI. I write about what I've lived.
Q:What's the most common pushback you get on this?
People often push back by citing exceptions or edge cases. And they're usually right that exceptions exist. But building a strategy around exceptions rather than patterns is a losing game for most founders.
Q:How has this view evolved over time?
My thinking on most topics has changed significantly over the years. Early in my career, I held many conventional views that experience proved wrong. I try to update my beliefs when the evidence changes.