Founders · Technology

Becoming a successful technology cofounder

Anonymous

May 29th, 2013

I have decided to pull together an open source program/set of courses to educate/grow/upgrade technology cofounders, to increase their chances of success in their role.  

The first step will be to collect ideas/experience/wisdom from the community and then pull it into a bunch of classes that a person can work through at their own pace.  It is my intention to build it so anyone could actually run it as face to face classes, in their local area.

I would love to hear your questions? What do you not know that you need to know? What the areas you are worried about that knowledge or skills could help with?

You fears, worries, successes are all welcome, come help us build this program
A-level teams with B-level ideas succeed. B-level teams with A-level ideas fail. This course provides a comprehensive roadmap for building a standout team, teaching everything from hiring to structure, compensation, and culture.

Blake Caldwell

May 29th, 2013

I think that one of the more under-stressed aspects of a tech co-founder's arsenal is their knowledge of types of productivity tools that they can utilize in their company (code hosting, repository, bug tracking, IDE's, deployment server options, etc) to help manage their technological team (or to help be prepared for a team once it starts growing). 

John Wallace President at Apps Incorporated

May 30th, 2013

As founders, we are jacks of all trades and master of some. Just like a non-technology co-founder needs to understand something about technology, the technology co-founder needs to understand something about business. I'm assuming the technical co-founder knows how to build the product (building an MVP plan -> architecting the client/server/mobile software -> writing the code -> QAing and deploying the product, and maybe managing development/QA teams if need be). He should also have a basic understanding of: • accounting (read the excellent "Accounting Game: Basic Accounting Fresh from the Lemonade Stand" available on Amazon) • legalese (no good references here, however contracts are like small programs; especially important to understand the error handling (Terminations) section and the correct structure and syntax of a contract) The more you know about other business issues (negotiating, business development, investor relations, marketing, sales, project management, HR, payroll, insurance, corporate structure and governance, etc.) the better, but ignore accounting and legal at your peril.