3 ms·
first and foremost, if you don't feel comfortable undertaking a project like this, for all of the reasons you listed, then don't. if you're going to do this, y
by noodle 19y ago
first and foremost, if you don't feel comfortable undertaking a project like this, for all of the reasons you listed, then don't. if you're going to do this, you need to jump in head first. asking if your situation is "worth" it is a value decision that would have a different answer for each individual person. if its not a good fit for you, then don't do it.
having said that, if you do go for it, make sure to set them straight. you might not need an official business plan, but you do need to at least have a road to profitability written somewhere on a napkin before you get started. it needs to be shown that it can be done. make sure the startup follows a good path and make sure that your investors/partners understand what needs to be done. introduce stability so you can maintain a stable paycheck.
and i think its been said elsewhere on YC, so i'm probably stealing the idea, but being a startup founder doesn't mean that you can expertly produce the startup from start to finish by yourself. it means that you have the knowledge and leadership required to make sure that the task gets completed. if you guys need better coders, hire some freelancers or new employees.
- aichcon 19y agoThanks for the feedback ... the idea that these folks haven't thought things through as much as I would in their situation is scary but I guess not a deal-breaker as long as they can lead.
- noodle 19y agono problem. this sounds like a heavily technical project. before jumping in to it, you should assert majority control on the direction of the project. not necessarily ownership or anything, but would you want a team of lawyers with no piloting experience flying a plane? no, the pilot should be at the wheel, making the directional decisions. such is this project. a developer should be in the lead of building an application. you're the developer, so make sure that they understand that while you'll seriously consider everything everyone says and bow to others in their areas of expertise, the final decisions lie with you because at the end of the day, you're building an application. that'll probably make you more comfortable :)
- aichcon 19y agoExactly. My biggest fear is that they will try to assert control where they do not have expertise. If they gave me the control I need to build the software correctly -- instead of just saying I have control but then making unreasonable demands later -- I would feel good about it.
- noodle 19y agothen make that clear to them, perhaps with a good employment agreement contract.