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

Advice for non-technical founders building a product

Going through these threads, I often see a lot of non-technical founders trying to build products who don't know where to start. Thought i'd share this resource as it helps give a good outline of what you should know prior to engaging someone.


This advice comes from an engineer. If you have any other advice feel free to add below. Would love to hear other perspectives.

2 Replies

Andrew Tan
0
0
Andrew Tan Advisor
Fall 2015 Class Company at Boomtown Accelerator
Great find! Nothing revolutionary but a very nice concise summary for non technical founders to start strategically before embarking on a project.
George Calvert
1
0
George Calvert Entrepreneur
Senior Exec
Building on the article, I'd add / emphasize:

Requirements
There's no substitute for mockups (a la Balsamiq and its ilk). At the very min, there should be a reasonably rigorous list of requirements. These then get discussed, prioritized and estimated (roughly).

Estimates

Any dev team should be estimating the effort for various chunks -- and offering alternatives if the effort doesn't align with the value. Engineers, particularly those more junior, tend to blow their estimates -- so get used to doubling or tripling those numbers to cover stuff like testing and stabilization, gaps and minor rework.

Roles
For me, a founding team sets roles something like:
1) 75% sales/revenues; 5-10% business ops; 15-20% product requirements
2) 40-50% sales; 50-60% product requirements, demo data and testing (!)
3) 85% front-end (including testing); 15% helping elsewhere
4) 85% back-end (ditto); 10% infrastructure (build, servers); 5% helping elsewhere

Key here is that the more #1 & 2 rely on 3 & 4 to determine the functional requirements -- particularly the UI -- the slower the development goes. Lastly, you want somebody to have a decent aesthetic so the app is pretty :-)

This stuff is pretty context dependent, but hope that helps.
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?