Should the Computer Science Guy Be CEO? 150
compuguy84 asks: "I'm a Computer Science major. A Finance Major friend and I are starting a business based on an innovative idea I had. I came up with the concept and developed the overall model we would use. He loved it, and we've been working on our business plan ever since. We've both donated our respective expertise, covered major ground, and agreed from the start that everything will be split 50-50 (ownership, power, etc). Unfortunately, the time has come to incorporate, and potential investors have advised against assigning Co-CEO's. So who should be the CEO? Should the Finance Major get the job based solely on his Business knowledge, or should the Computer Science guy get the job because it was his idea? We've both have shown ourselves to be savvy business folks, but I don't have the 'schoolin'. All signs so far point to giving him the job, but I can't shake the feeling I'm getting robbed. If it was my idea, shouldn't I call the shots at the end of the day? Has anyone been through this? What did you do?"
You (Score:3, Interesting)
-m
Re:There are plenty of shots to go around (Score:5, Interesting)
Re:There are plenty of shots to go around (Score:3, Interesting)
This would be like as you suggested with the exception of the CEO having a duty to involve the other person on major decisions. I guess if there is a disagreement, something could also be implemented to fix that too. I was involved with a small company and was one of the three owners. I took more of a behind the sceens employee type role. This is how we did it except we had three people and there wasn't any stalmates. We set it so anythign costing over $5,000 required informing all of us and the consent of at least one of us. This number grew as the business did. Eventualy I cashed out to pursue another venture but it continued on for another 5 years or so before it was bought up by one of our local competitors who still runs the company as a seperate entity. (wish I had stayed for that:)
Re:Who has more business sense? (Score:5, Interesting)
It all worked out in the end; my father started his own business (100/0
You need no stinking business expert! (Score:3, Interesting)
You need to develope the thing.
2nd you need to sell the thing.
3rd you need to do some paper work.
4th discuss with investors if you cannot do above well without pouring more money to it.
The 2nd part happens after most important risks related to business have already taken. And 3rd part isn't big deal until you have your start hiring people. 4th part is only important if you plan to hire or cannot sustain your living entire developement time.
So basicly if your thing isn't ready nor the business person do not add value to your business so you are already getting ripped off by giving him 50% of your business. And if its ready the business person should invest the money atleast equal to 5 times the salary you would of taken when developing the thing, in order to match your investment on the business.
I'd say read the Eric Sink:s articles beginning here. They teach part of the business part that geeks need to know. Basicly business part is easy if you need to know it. And computer guy is far better in the helm of software company than a business person. Since software person understands whats possible, and what not and proper technical trade offs.
Of course if he can do developement too and his domain expertice is needed for making the product then it wouldn't be obvious who should get bigger part. Oh and 50%
http://software.ericsink.com/bos/Geeks_Rule.html [ericsink.com]
What are the roles? (Score:5, Interesting)
Honestly, I think it's a question of both what you want to do and what you think would most likely make the company succeed. Take and guard your ownership stake. Then stick yourself where you think you'll be most valuable. If the company can't survive without you, that's the value that you have. Just make clear from the begining that you intend the company to be run by consensus, not CEO fiat. If you've got a partner who is doing work that you can't or don't want to do but which needs to get done, that's a good thing. A CEO isn't all powerful, and if you two agree on that, I think you can be very happy and effective as a CTO.