3
3 Comments

What to do when your MVP is a *different product* than your full vision?

I'm struggling with deciding how to proceed.

I have a 'grand vision' for a product that will scratch my own itch, and I want to identify an MVP to test the market.

Here's the problem: I have an idea for an MVP, but it serves a related but slightly different purpose, rather than simply being a 'simple version' of the Grand Vision. Basically, the MVP would be a single feature of the Grand Vision rather than a simple version of all the core features.

So should I use a different name/marketing plan tailored specifically for the MVP and then pivot later? Or should I stick with the Grand Vision name/marketing plan even though I'll only have a single feature actually built out?

  1. 3

    I'd stick with the single feature MVP and see if that gains any kind of traction. It should be a lot faster to build and a lot faster to get product-market fit.

    If you gain traction, you can always offer to upsell later (and depending on interaction between grand vision and single feature, it could be an add-on, or grandfather original users up to grand vision, or whatever).

    1. 1

      Good points. In the end I think you're right. Thanks!

  2. 4

    This comment was deleted 7 years ago

    1. 1

      Thanks! I like your idea of listing the future features concretely to give an idea of direction/roadmap.