A comprehensive look at SAFE notes. We break down the complex legal jargon into actionable steps for early-stage founders.
The Counterintuitive Truth
In SAFE notes, the best practitioners often do less, not more.
The lesson: the market doesn't care about your roadmap. It sounds simple. It's incredibly hard to execute.
The Framework That Actually Works
Here is a simple framework for evaluating SAFE notes. It's not complicated, but it requires discipline.
Step 1: you should focus on one thing and do it exceptionally well
This is where most people go wrong. They skip this step entirely and jump straight to execution. Don't do that.
Step 2: the best solutions are often the simplest ones
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 SAFE notes right treat it as an ongoing process, not a one-time project.
The AI Angle
Any discussion of SAFE notes in 2026 has to include AI. As someone who's invested in Anthropic, OpenAI, Scale AI, and Hugging Face, I have a front-row seat to how AI is transforming this space.
The short version: AI makes good practitioners better and bad practitioners worse. It's an amplifier, not a replacement.
Some teams use AI to get far more out of SAFE notes. Others spend heavily on AI that solves the wrong problem. The difference comes down to understanding what you're actually trying to achieve.
This connects to broader themes around fundraising, SAFE notes, startup law that I've been thinking about a lot lately.
Final Thoughts
There are no shortcuts in SAFE notes, but there are smarter paths.
The strongest teams treat SAFE notes as a competitive advantage, not a checkbox. They invest in it early, measure it obsessively, and never stop improving.
If you're just getting started with SAFE notes, don't be intimidated. Everyone starts somewhere. The key is to start with the right mindset and the right framework, and then execute like your company depends on it. Because it probably does.
Frequently Asked Questions
Q:How can I apply this thinking to my own situation?
Start by identifying the core principle behind the opinion, not the specific example. Then ask yourself: does this principle apply to my context? If yes, test it in a small, low-risk way before going all in.
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.
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.