For software, create a plan to build what you'd normally code... preferably, something you want. Figure out how to sell it, how long it would take to build (time === money), the business model required including marketing plan to reach profitability, and whatever else you need to launch it. Then build a 10-20 slide deck with a designer about the idea (not a prototype), learn how to present it (don't waste it coding, let others do that in the future) and start pitching at least once or twice during those 2 weeks.
In the end, I hope you'll become a successful technical CEO and great company because you've learned a lot more than an API or two.
No not at all, code is especially cheap, almost worthless. He/She already knows how to do that - so don't waste time on something you already know. Focus on:
1. Ensure there is market / product fit
2. How long to get to develop the product
3. Break-even point
Or write a bunch of code, and be left with another if-I-build-it-they-will-come FAIL.
Obviously you need both, that's why I'm suggesting the focus should be on the biz.
I disagree that it's rare or expensive, it's quite the opposite. Most knowledge associated with it has little lifetime value and is constantly tending towards zero - a 5 year old code base that generates little income has a value of near zero or is a liability. You can hire an engineer for a year to build web apps, depending on country, for the price of a medium sized sedan.
Comments
For software, create a plan to build what you'd normally code... preferably, something you want. Figure out how to sell it, how long it would take to build (time === money), the business model required including marketing plan to reach profitability, and whatever else you need to launch it. Then build a 10-20 slide deck with a designer about the idea (not a prototype), learn how to present it (don't waste it coding, let others do that in the future) and start pitching at least once or twice during those 2 weeks.
In the end, I hope you'll become a successful technical CEO and great company because you've learned a lot more than an API or two.
Are you being facetious? He wants to build a prototype not hit hype cycle funding.
No not at all, code is especially cheap, almost worthless. He/She already knows how to do that - so don't waste time on something you already know. Focus on:
1. Ensure there is market / product fit
2. How long to get to develop the product
3. Break-even point
Or write a bunch of code, and be left with another if-I-build-it-they-will-come FAIL.
good quality code is not cheap. doing both biz and tech is not mutually exclusive at an early stage
Obviously you need both, that's why I'm suggesting the focus should be on the biz.
I disagree that it's rare or expensive, it's quite the opposite. Most knowledge associated with it has little lifetime value and is constantly tending towards zero - a 5 year old code base that generates little income has a value of near zero or is a liability. You can hire an engineer for a year to build web apps, depending on country, for the price of a medium sized sedan.
that's also true. but at such an early stage it really helps if you do it yourself. you can and should hire later