In general though, you definitely should work on figuring out if customers want your product without building it if at all possible, and most times it is possible. I run a SaaS that's a project management tool (todo list + calendar, basically, at https://getartemis.app) and the main page is simply a video demo that I made with Figma and an animation tool called Principle. People signed up and it works great for showing users what they'd be getting in the future.
This is not true, the video used a few clever techniques (cutting/editing) to make it seem snappier and more responsive, but Dropbox was very much a real (albeit beta and buggy) product when the video was made.
I think strategies differ depending on:
- How new the market is for that particular product
- How big of a risk is it to adopt your product vs alternatives
- How polished it looks (inverse relationship to how many solutions already exist)
In some cases, you may need a much more polished MVP to get people to bring out their credit cards. If your product is the only one of its kind (and is in high demand), the UI is less important in v1.
It's important to at least have a strong growth hypothesis that you've validated to some degree.
That's all I have right now - hypotheses.
This blog post captures some of the differences: https://archive.is/wip/tnm2D (skip to conclusion). This one elaborates what an MLP is: https://medium.com/the-happy-startup-school/beyond-mvp-10-st...
I've never done this, but it makes sense. Why spend the engineering effort to go from Demo --> BVP --> MVP when you can just do the first jump and test the idea.
Everything is on a spectrum and -- given the vast graveyard of random ideas engineers build as side projects -- we should figure out a better way to drive better yield.
On the other hand, I've seen organizations using this "BVP" approach for absolutely everything they build, which I've come to view as a sort of product development antipattern, reflecting some lack of ambition/conviction/vision at the top. It's like the polar opposite of a moonshot: building things in such tiny increments that you can only ever achieve a local maxima, because the higher summit requires a bigger leap.
Sure, but my assumption would be -- if you suddenly get registrations, signups, or even conditional trial accounts, great! Now I have some validation, and I'd jump in immediately and start building out the product fully.
...then, if I get even more engagement, even greater! Now I can start planning some scale-out.
https://nascar.nbcsports.com/wp-content/uploads/sites/9/2020...
Google Identity reference to NASCAR Login: https://developers.google.com/identity/toolkit/images/federa...
NASCAR logins are particularly great (easy entry to convert interested users) and at the same time having a huge number of super-ugly edge cases:
1. If you log in with [email protected] but originally had registered your gmail as johnqdoe, then your login automatically changes to the non-dot form.
2. If you have already registered via email on [email protected], then you cannot login-with-Google in the above case, as both accounts are separate and distinct in the host system.
3. If you have two accounts under your school and work account, but log-in-with-Facebook, and Facebook has both your emails, it gets confused.
4. There are cases where you simply cannot log in due to the network of conflicts across the identity services.
...and yet this is also awesome because you get to convert a registered user ASAP in 95% of the cases.
I don't like this new startup trend[1][2], nor do I think it actually works.
Literally all of those examples are the opposite of what the blog post is claiming. They did have a product: Hotmail had the service built out, Eventbrite had the service built out, and there was a Dropbox before you could refer your friends to it. There are examples of what the author is claiming, but most are gimmicky Kickstarter-style (and often derivative) products.
I mean, think about Dropbox or Slack or Instagram: how could you possibly sell (or even validate the idea of) those products without actually giving some sort of demo? Without people actually using that thing? It might work for something like the product in the post (people understand what "video chat" is), but I don't really see it working for any kind of particularly novel or value-generating product.
Followup: grabbed a coffee, and this post got a bit of attention. To be clear, I think that an MVP should be just that: a minimum viable product. By definition, you shouldn't be able to go leaner. I also think that sometimes people conflate "fake it 'til you make it" with PG's "do things that don't scale" -- these two are not the same.
[1] https://tommorkes.com/lean-launch-how-to-sell-an-idea-before...
[2] https://hbr.org/2013/12/sell-your-product-before-it-exists