.@GustoHQ co-founder @tomerlondon on why they don’t build minimum viable products: "The problem with a minimum viable product is you get something out there that works, but it solves the problem in a very local way without thinking end-to-end across the whole experience. A minimum viable product is the smallest thing you can ship that checks the box of saying you did what you said you'd do. The problem is you launch it, you're proud you shipped it fast, and then people don't use it. So you go, I guess it was a bad idea, let's throw it away. That doesn't work for us. We went with the Minimum Lovable product from the beginning. Because for Gusto to grow and get new customers, people had to love the product. You can't launch anything that's not lovable. So what does lovable actually mean? There are a few parts to a great experience. First, it works. If you're getting your employees health insurance, it actually works when they go to the doctor. That's the functional side. Second, it's intuitive. For a small business owner, the bar for intuitive is really high. You shouldn't need to watch videos or read manuals. You click a button and it just works, and you know where to go. And the third part, the one that turns viable into lovable, is delightful. A delightful product anticipates your needs. It looks at you and already knows: this is your first time getting health insurance. So instead of making you go find a comparison tool, it tells you proactively that companies like you, in your industry and your area, usually offer this package, and here's what it costs. The MVP version builds a benefits-benchmarking tool and buries it in a tab you have to find. The lovable version answers the question already forming in your head, right when you have it." Full conversation with Tomer: