3 ms·
I see what you're saying about the value of the prototype. How would you account for whatever risk the non-technical cofounder took on to build it? Risk has to
by nathanh 16y ago
I see what you're saying about the value of the prototype. How would you account for whatever risk the non-technical cofounder took on to build it? Risk has to coordinate with value added though, so if a prototype didn't really generate any new value, it's worthless. Perhaps there is some value in "lessons learned" from messing up the initial prototype, but maybe future investors/partners shouldn't be penalized for them.
You're right about not accounting for business skills the technical cofounder brings to the table. I need to state that somewhere. Great point.
- donw 16y agoWow, you're on the ball. :) We have a very convenient way of expressing value here. If the prototype has proven solid enough to support an active and growing user population, then it has value, because it's cleared the first hurdle of software design -- making something people want and can use. A few iterations on said prototype before bringing in a technical cofounder is also a big plus-point. Those iterations are where you find out whether or not your prototype will be flexible enough to turn into a real product.