Apps · Developers

Minimum Viable Product Development

Russell In Taking a gap year to pursue a startup

January 8th, 2017

I have phone meetings with a few developers this week about developing the MVP for my app. Besides having an extremely detailed plan of what features I want for the MVP, what else should I be prepared with/for?

Christopher Barklem UX Design Specialist / Saas Product Designer

January 8th, 2017

Russel, don't fall into the trap of seeking a development team without a proven product.


Look into Lean startup and Lean UX principles. Use lean UX and iterate until you have a proven prototype built (built in one of the many prototyping software's).

Steve Owens

January 8th, 2017

Write a Requirements Document (I can send you a template if you like).


Do not pick the firm for its low price - pay a market rate. There are lots of white papers on how to choose a good PSF. You get what you pay for.


Do not do fixed price - pay by the hour - but make sure you get an estimate and break the job into small parts - getting an estimate each for each part as you move forward in the project.


Make sure you get all source code and IP.


Pick a firm you really trust to be a true expert in product development (not just the technical stuff) and work with them as if they were a trusted partner - that is listen to their advice.


Stephanie Wagner Founder at Agile Bloom, LLC

January 9th, 2017

Be prepared to be a salesperson. Before and after it exists.


You could have a waiting list, or do a "pre-order" approach while you work on the MVP, to get an idea of how interested people are. Make sure to write updates (as blog posts probably) on progress. You could also create an incentive to get people to sign up early (like an "early bird" discount).


When the MVP is done, you try to sell it. Use Google Analytics or equivalent and know who your users/customers are. You also have to keep in touch with them, convince them that your product will help them with whatever problem they have.


Also, I don't think you need to have an "extremely detailed plan" for what an MVP will have. It's good to know exactly what you want implemented, but keep in mind that this is the very first version of your product, and it's going to change, especially once you get feedback from users.

Usman Zubair Ex-MSFT/ DevFactori Apps / CTO (2 startups which raised funding) / Full Stack Engineer

January 8th, 2017

Hi Russell,


MVP is a major milestone in the life of a startup. One of my venture works closely with such startups and conducts a two day workshop which would cover the following.


DevFactori agrees to meet with the client and conduct a 2-day discovery workshop in which we will help plan out his/her software project and we agree to deliver the client with the technical architecture of his project.


Devfactori and the client will cover the following material during the workshop:

• Product strategy

• Acquisition strategy

• User retention

• Competition and positioning

• Monetization strategy

• Referral/Virality/Reward system strategy

• Strategy for minimizing risk

• Preparing client for development


DevFactori will provide a deliverable including the following after the workshop:

• Finished user stories (features)

• Mapped-out development processes

• Business road-map

• User acquisition strategy

• Technical analysis

• Risk analysis

• detailed pricing per the user stories


If you would like to discuss more in person on how we can help you from user stories to MVP development let's discuss more. Please send me an email at usman@devfactori.com and let's connect over phone as well.


Regards,

Usman

Todd Kovalsky

January 8th, 2017

Hi - do you have any sales? Did you try selling your product? Start there...then build your app. Try reading a Steve blank book...good luck!!

Vladimir Budilov

January 14th, 2017

Create the wireframes, write down what you want the end-product to be (basing it off of the future users), and definitely don't pay by the hour when outsourcing it :) Make sure you set the requirements and price upfront.

Artem Golub

January 17th, 2017

Detailed requirements doc, if your not technical then don't suggest technology that you may have read about in blogs etc.. that you think will keep the price down and speed things up (ie. Ruby on Rails, MongoDB). Don't be CHEAP!! You get what you pay for. Hire a developers and you will end up with something that wont work, or at best will need to be completely rewritten IF your MVP picks up.


Also, I would highly suggest hiring a small development company to develop the MVP as opposed to a "developer" who will be basically waiting for you to manage him/her every single step of the way.

hannahtoku lesli WELL AM VERY KIND AND LONELY SINGLE LADY MOOD

January 18th, 2017

You could have a waiting list, or do a "pre-order" approach while you work on the MVP, to get an idea of how interested people are. Make sure to write updates (as blog posts probably) on progress. You could also create an incentive to get people to sign up early (like an "early bird" discount).

hannahtoku lesli WELL AM VERY KIND AND LONELY SINGLE LADY MOOD

January 14th, 2017

Oh well thanks i do appreciate that...?

hannahtoku lesli WELL AM VERY KIND AND LONELY SINGLE LADY MOOD

January 18th, 2017

You could have a waiting list, or do a "pre-order" approach while you work on the MVP, to get an idea of how interested people are. Make sure to write updates (as blog posts probably) on progress. You could also create an incentive to get people to sign up early (like an "early bird" discount).