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
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...
Due to politics the MVP had 2 false starts at other agencies before the third company built it in a crazy short timeframe. The third company was only going to built Android/iOS apps to an API specification provided to them, but ended up doing the entire backend too.
The false starts were down to lack of clear guidance as to _what_ the client wanted from the agency and very slow feedback loops regarding progress. The first attempt was absolute overkill (and very slow velocity), the second attempt was nothing like the intended idea and development stopped after 12 months. Runway was getting shorter so third agency built it.
The biggest mistake was the client hiring a fresh junior as their first in-house developer, and them not having sufficient experience to identify parts of the platform that would become obvious scaling problems. Later on these became very expensive problems!!
Just to understood, the team you joined was at what stage when they hired the agency? Like was it completely new startup that had capital but not enough man-power?
How big the MVP was? From what I understand it seems more like full blown product that the company wanted to develop?
The MVP being built was the foundation for a totally new direction the company was heading. The team I joined was the beginning of transition from agency to in-house, and we had to convert this scrappy MVP into production ready to handle 1000s of customers.
The agency built a wooden bicycle which we had to convert into metal...while still riding it :-)
Despite unflagging and upvoting, I still don't see this in the ask section again. Certainly didn't mean to negatively impact your question's progression. Hopefully @dang or @sctb can restore its position.
Very sorry about that!