Contrary to what some people may think, I actually recommend not having a team before testing the MVP. And I’ve got a solid argument to explain myself.

If you wonder what’s an MVP, I have you covered. And this is why it’s important to use one to validate your idea.

If you want to watch something, rather than read, watch me talking about the MVP at the end of this post, in a short, 2 inutes video. For more similar videos, subscribe to the YouTube channel.

Can I build an MVP without a team?

Technical or non-technical MVP?

If it’s a deeply technical MVP and you don’t know how to do technical stuff, you kinda need at least one partner: the technical one. Here’s how you can find a startup cofounder and convince them to join you. Still, Dropbox is a really technical product that had an MVP that was just an email. So maybe you can avoid having a technical founder even then.

If it’s not something technical, then yes, you can build an MVP without a team. It actually is better if you can build an MVP before hiring the team because you shouldn’t hire the team if you’re not sure that the company creates a product that has a market. Also, if you don’t really know the product and the market, how can you hire the right people in the right positions?

So, yeah, build it without a team if you can. If you can’t, try to find a co-founder instead of hiring someone and then build the MVP. If there is no other solution, obviously, find some team and work with them but it’s not the the most important thing when you’re building an MVP you just need to have something to show to your potential market.

For more similar videos, subscribe to the YouTube channel.