How do you compete when every startup has access to the same powerful, off-the-shelf AI models? The answer isn't to build a better model. I'll share my framework for building a defensible AI SaaS business through proprietary data, unique workflows, and brand.
The Counterintuitive Truth
In usage-based pricing, the best practitioners often do less, not more.
The lesson: you should focus on one thing and do it exceptionally well. It sounds simple. It's incredibly hard to execute.
The Framework That Actually Works
Here is a simple framework for evaluating usage-based pricing. 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: most founders overthink this and underspend on execution
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 usage-based pricing right treat it as an ongoing process, not a one-time project.
Why Most Approaches Fail
Many common approaches to usage-based pricing 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 Numbers Don't Lie
Investing early in usage-based pricing can be the difference between raising your next round and running out of runway.
One of my portfolio companies went from struggling to profitable in under a year after they finally got serious about this. The founder told me later that they wished they'd started sooner.
This connects to broader themes around AI APIs, serverless AI, usage-based pricing, cloud AI services that I've been thinking about a lot lately.
What's Next
Best practice in usage-based pricing 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 usage-based pricing 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: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: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.