Building an AI startup is anything but glamorous. I want to take you behind the curtain and share the unfiltered reality of our journey. From the heated debates over our roadmap to the bug that almost derailed our launch, this is the real story of what it takes to build and ship an AI product.
The Framework That Actually Works
Here is a simple framework for evaluating A/B testing. It's not complicated, but it requires discipline.
Step 1: you need to move fast and break things
This is where most people go wrong. They skip this step entirely and jump straight to execution. Don't do that.
Step 2: timing is everything in this game
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 A/B testing right treat it as an ongoing process, not a one-time project.
The Counterintuitive Truth
In A/B testing, the best practitioners often do less, not more.
The lesson: the best solutions are often the simplest ones. It sounds simple. It's incredibly hard to execute.
Lessons From the Trenches
I want to share a few specific lessons I've picked up over the years. These aren't theoretical. They come from real companies, real failures, and real successes.
Lesson 1: The best time to start thinking about A/B testing was yesterday. The second best time is now. Don't wait until you have the perfect plan.
Lesson 2: Hire for attitude, train for skill. The best people at A/B testing are rarely the most technically gifted. They are the most curious and persistent.
Lesson 3: Your competitors are probably getting this wrong too. That's your opportunity. While everyone else is following the same playbook, you can zig when they zag.
This connects to broader themes around a/b testing ai, build vs buy, case study that I've been thinking about a lot lately.
What's Next
Best practice in A/B testing 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 A/B testing 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'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: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.