3 ms·
I think it is worth coding the working mvp , even though you know that it is going to be re-done if you take off. This will help one to demonstrate his seriousn
by europa 16y ago
I think it is worth coding the working mvp , even though you know that it is going to be re-done if you take off. This will help one to demonstrate his seriousness and something visual to show when he/she pitches to developer/co-founder instead of pitching a random idea.
- MJR 16y agoBut clearly this isn't your forte, so why not find someone who can focus on that area. That leaves you to manage product development, vision and to test the work that's been done to create a product. I'm just not of the mindset that doing something twice is the right way to go. Especially when speed is a factor.
- candre717 16y agoExactly. Developers have their pick of non-technical co-founders. It's a lot harder to approach someone with just "an idea." What are you offering in return? How do you contribute to a startup in those initial months? Sure, I've read plenty of posts on what non-technical co-founders can do in a startup - lots! But, it pales in comparison to the bread and butter of a startup: building a product. If you're looking to build the next Google or Wolfram Mathematica, find an expert or 2. The guys at SeatGeek built their initial product - a crude prototype but decent enough to promote at TechCrunch. Now, they're funded and growing. They were not programmers, but they needed something and they didn't have the resources to find someone to build it. Coding is a bottleneck for a lot of non-technical folks. Do what you got to do to get through it, scotch tape and all.