Home
About
Approach
For Founders
Contact
How to build an MVP that actually works

I've learned that the key to building a successful MVP is understanding what "minimum" really means. It's not about building the smallest possible product, it's about building the smallest product that can deliver real value to users.

The best MVPs I've seen were the ones that focused on solving one problem really well, rather than trying to solve many problems poorly. They were simple, focused, and designed to learn quickly.

MVP Principles
Four beliefs that guide how I think about MVPs

Start Small

An MVP should be the smallest possible version that can deliver value to users. Focus on the core problem you're solving and build just enough to test your assumptions.

Validate Quickly

The goal of an MVP is to learn, not to impress. Build something that lets you test your key assumptions quickly and cheaply. Speed matters more than polish.

Focus on Users

An MVP should solve a real problem for real users. Don't build features that look good but don't address actual user needs. Let user feedback guide your development.

Iterate Fast

An MVP is just the beginning. Plan to iterate quickly based on what you learn. The faster you can build, test, and improve, the faster you'll find product-market fit.

Building a Better MVP
Practical tips for creating effective MVPs
1
Identify your core value proposition
2
Build only what's necessary to test it
3
Get it in front of real users quickly
4
Measure what actually matters
5
Be prepared to pivot based on feedback

The MVP Mindset

Building an MVP is about more than just creating a minimal product, it's about creating a learning tool. The goal is to learn as much as possible with as little effort as possible.

The best MVPs I've seen were the ones where we were clear about what we were trying to learn and built just enough to test those assumptions. When you focus on learning, you build better products.

A Personal Reflection

I used to think that MVPs were about building the smallest possible product. Now I think they're about building the smallest product that can deliver real value to users.

The most successful MVPs I've seen were the ones where we focused on solving one problem really well, rather than trying to solve many problems poorly. They were simple, focused, and designed to learn quickly.

Exploring new ideas? Me too.

I’m always curious about early-stage projects, especially the ones that move fast, test early, and aim to solve something real.