Big News: FounderDating is joining OneVest to build the largest community for entrepreneurs. Details here
Latest Notifications
You have no recent recommendations.
Name
Title
 
MiniBio
FOLLOW
Title
 Followers
FOLLOW TOPIC

Question goes here

1,300 Followers

  • Name
    Entrepreneur
  • Name
    Entrepreneur
  • Name
    Entrepreneur
  • Name
    Entrepreneur
  • Name
    Entrepreneur
  • Name
    Entrepreneur
  • Name
    Entrepreneur
  • Name
    Entrepreneur

What should be demanded of a development house when asking them to build a first prototype?

I am considering having a development house build me a first MVP based on my market research so far. It will not be anything crazy, I want to start small. What do I make sure I demand of them so I can make sure I am getting the most out of my time and money?

16 Replies

Anthony Zeoli
8
0
Anthony Zeoli Entrepreneur • Advisor
Digital Strategy and WordPress Consultant and Trainer
Alison,

As a vendor, I have worked with a number of startups on their MVPs. What I have found lacking from almost every client without experience are two very specific things. I put this question back on you to provide your development house with the following:

1. A comprehensive business requirements document, including user stories that defines every possible pathway a user could take in the product - from entrance to exit. If you don't know from your market research how the user is going to interact with your product, you're going to spend an inordinate amount of time with your development house, who will build what you want, but ultimately you have to extremely confident in the product architecture.

2. Basic information architecture documentation that defines the login/logout path for the intended audience to enter and exit your site, desktop, or mobile application. This doesn't just include click this and go here and you're done. This includes all the possible errors one might encounter when navigating your software product. You must define success and you must define errors and what happens when a user gets to success or gets blocked from completing the story that you defined in the business requirements document.

What you really need is to hire someone to help you "architect" your product first. That would be a product manager or a CTO, but more like a product manager. A CTO is going to define the technology stack you're going to build on and how you're going to support the technology you build in the short and long term. The product manager is going to help you write your business requirements and possibly do basic wireframing of all site pages with a site map to hand off to the development shop.

If you don't have this upfront and rely on your development shop to not only build your product, but architect it as well, you're going to want to see examples of past work - formal business requirements documentation and information architecture documentation that explicitly spells out exactly what you're going to build, so there is no confusion.

Without this basic information in hand in the beginning, you are going to go through round after round of trying to get it right. You don't have time or budget allocated for that, so you have to be extremely detailed in your documentation prior to engaging with the development house. Then, you can bring that documentation to them and they can give you a better sense of what's possible.

If you don't know how to do this, then you're going to have to learn and learn quickly, because you don't want to burn money in the confusion that ensues from not having a plan.
Mark Tomizawa
2
0
Mark Tomizawa Advisor
NowCivic | @Dares2Care.com | Join my drive to skills 99 and followMe 2 YOUR great
Coding is like making sausage. Keep the community of users involved. Here's a way to do it anytime at any stage. Paper test it how well the Decision User Interface makes it easy for the users. Play the role of Computer. Each index card is one decision/action on a flow chart. Prototype for clarity. Watch for hestitations and uncertainty. Try this with a variety of people.
David Albert
3
0
David Albert Entrepreneur • Advisor
Founder & Principal at GreyGoo
I agree with Anthony. Seek a development shop who specializes in concept to launch--not just a firm who can take in requirements and build what you ask. If you've done market research and idea validation you'll need a firm who can:
1. Help you write requirements
2. Create User Stories (essentially what are the scenarios in which a user will interact with the app and how)
3. Create user flows (visual diagrams of the user stories)
4. Wireframes (basic low-fidelity visual representations of the user interface of your app and its various view states)
5. Design a UI and create a simulated prototype of your app before it goes into formal coding.

By planning this way, you're going to emerge with a complete blueprint for your MVP so the path to development and launch is clear.
David Albert
2
0
David Albert Entrepreneur • Advisor
Founder & Principal at GreyGoo
Oh and I should add--you'll get varying opinions as to how extensive and complex each of these deliverables should be. I've seen firms create very verbose user stories and flows for apps that are quite simple (read: unnecessary). Find a firm where you're comfortable with the amount of planning they propose based around your goals and the vision for your MVP.
Ib Olsen
2
0
Ib Olsen Entrepreneur
Energy Storage, CleanTech, and Sustainability
I agree with David based on my own experience. If you do not hire a product manager that can 'translate' your requirements into code requirement, you will have to interview and find the development shop that can do it with you. I would also recommend to read up a little on wireframes and maybe sketch some pages out in Balsamic (you can get it for Chrome) as a visual usually make it easier to discuss functionality.
Steve Owens
0
1
Steve Owens Entrepreneur • Advisor
Finish Line - A Better Way for Small Companies to Develop Products
You might find this information helpful: http://www.finishlinepds.com/#!why-outsource/c1y25
Patrick Hidalgo
0
2
Patrick Hidalgo Entrepreneur • Advisor
Financial industry executive who is now writing software.
Roman Pichler and Mike Cohen have a lot of free tools online that will help you understand and speak agile Product Management language if what is mentioned above by others is not clear.

Also, an MVP should be something that allows you to charge the customer money.
James Hardy
1
0
James Hardy Entrepreneur
Director at Live Fit
From recent first hand experience of being in your position (first ever app build, prototype) and having the project run away from me slightly I would say you need to think about what you demand of yourself as much as your development house.

All the above comments are very true;
- if you don't have experience find a product manager
- run through your user stories twice as much as you think necessary
- distill what you want down to very clear objectives (tech spec but with wiggle room for lateral thinking)
- book in update calls with your dev team, you will need to stay in touch

Don't skip this, even if you have other pressing issues. You will spend money you don't have on something you don't want. If your company is tech heavy, what could be more important right now..

Measure twice, cut once.
Good luck
James
Jay Kelly
2
0
Jay Kelly Entrepreneur
Co Founder at Locked In Sports & COO at 9Tribe
Great comments from everyone on your question, Alison. I would add that you should give preference to a dev group who will push back on what they consider unnecessary complexity.

First time app builders often include too much functionality too soon instead of letting market feedback drive additional features.

When a dev group encourages you to simplify, that typically means they're making less on the project. If they're willing to do that, that's a strong signal they have your best interests in mind.
Randall Shane, PhD
0
0
Randall Shane, PhD Entrepreneur • Advisor
Data Scientist at Bodybuilding.com
MVP is highly dependent on architecture. If you'd like to speak, drop me a line - my thoughts are free. Very exciting!!


Join FounderDating to participate in the discussion
Nothing gets posted to LinkedIn and your information will not be shared.

Just a few more details please.

DO: Start a discussion, share a resource, or ask a question related to entrepreneurship.
DON'T: Post about prohibited topics such as recruiting, cofounder wanted, check out my product
or feedback on the FD site (you can send this to us directly info@founderdating.com).
See the Community Code of Conduct for more details.

Title

Give your question or discussion topic a great title, make it catchy and succinct.

Details

Make sure what you're about to say is specific and relevant - you'll get better responses.

Topics

Tag your discussion so you get more relevant responses.

Question goes here

1,300 Followers

  • Name
    Details
  • Name
    Details
  • Name
    Details
  • Name
    Details
  • Name
    Details
  • Name
    Details
  • Name
    Details
  • Name
    Details
Know someone who should answer this question? Enter their email below
Stay current and follow these discussion topics?