Few questions to understand the context. At what stage were the startup you worked with mostly?
Did you ever encountered a "proper" hand-off of the MVP? If so, what was it like or what would you suggest?
I guess the idea for me is to have the MVP developed based on getting angel investment and start looking for PMF together with already looking for seed and tech co-founder & inhouse tech team and then after you find the PMF rebuilding it completely anyway.
But you are right that finding PMF is continuous process and might take years and many iterations and the big question is what kind of answers you can get from 1 MVP/prototype built in 3 weeks or so (it should not take longer than that as I agree with what you say - make it as small as possible)
p.s. thanks for the articles, great reading. I agree that before MVP there should be prototypes that validates the hypothesis.
I was inspired by this article btw. https://www.groovehq.com/blog/technical-co-founder
After the _second_ botched attempt I don't understand why building in-house was decided - instead the company inherited a super rushed barebones MVP with zero docs and spaghetti code...
So yes - experience with hiring agency - all negative.
Given you're asking for an MVP I'd suggest you make it smaller. There are tons of ways to learn about your customers' problem and whether you can solve it for them without writing code. We've built landing pages using Keynote which we then tested with customers, ran entire processes that were supposed to be automated manually, and even prototyped a machine learning algorithm by manually coming up with our best guesses for a users' search query. Because the purpose wasn't scientific validation, the purpose was learning. All these three we built in a day. For more: https://hackernoon.com/the-mvp-is-dead-long-live-the-rat-233... http://paulgraham.com/ds.html