Can I divorce a co-founder


9

There are currently 3 cofounders and 1 of them is an engineer other 2 are sales representatives. Many of the times technical cofounder doesn't agree with our views and is backed by his team containing mostly his friends. While all the technical team is at early twenties graduated from top colleges, sales reps are having atleast 15 years of experience. Because of generation gap, difference in background, sales reps idea won't match with technical founder.

Can we divorce technical founder. We got angel investment of few hundreds of thousands and will be going for first round of VC. Most probably the whole technical team(3 in total) will back the founder as they are from same college and are friends from long ago.

We are in to enterprise business and sell our softwares to them. sales reps take care of market etc. technical founder has minor equity.

Answering few comments: One of the main disagreement we see is in strategy. We want them to take as many engineers as they can say 10s of people in next few months and sell the software with some customisation to 100s enterprises.They have their own reasons and believe in hiring slowly and carefully. they cite different reasons like growth needs to be organic, scalable etc. They also feel they are not given much importance during the decision making. We have investment and client s mostly because of sales contacts though technical team also has done their part of hardwork by developing it.

I am afraid I cannot replace the whole team because the product which is a software as a service will stop working. Sales reps don't even know where the code is and how to run that.

We have huge contacts and believe that the existing technical team is making strategic mistake by not scaling very fast thereby loosing revenue. Currently 2 sales reps are not able to work to capacity because of small technical team. We believe they are not building team as fast as they should.

Co-Founder Founders

asked Dec 4 '12 at 21:51
Blank
Santu
156 points
  • Presumably when you set up the business you made arrangements for how to proceed in this situation. If not, you can try to buy them out, but you can't just "divorce" them if they have equity. Try to manage the situation calmly and not turn it into a massive fight. – Steve Jones 11 years ago
  • It sounds like you already have made up your mind. What makes you think that if you get another technical team that will solve you issues? – Tim J 11 years ago
  • I think this is a good question. Why downvote? The problem does exist, it must be faced and solved. – Billy Chan 11 years ago
  • When the entire technical team disagrees with the sales team, the sales team is either **not** doing their job in explaining what they want to the technical people **or** the sales team wants something that is impossible and the technical team knows this. – Gary E 11 years ago
  • Adding to what GaryE and TimJ said, you need to be honest with yourself about where the issues are here, as this kind of situation is very destructive and can quickly get out of hand. – Steve Jones 11 years ago
  • Does the technical team have a seat at the 'strategy table' or are they treated as a black box - requirements in one end, code out the other? Your IT team should be involved strategically, moulding your company and working through issues. – Bryan Rehbein 11 years ago
  • It sounds like you need some strong leadership to encourage everyone to share a single vision, whatever that is, and all move in the same direction. Regarding the fact that the tech team can't be replaced, you could bring in an external consultant to do a review of the whole business and make recommendations. This doesn't have to be like Office Space and can help you discover all the issues in the business, including where the code is. I've done this kind of thing before when I was the consultant and the clients found it useful to get an outside overview, without all the history and politics. – Steve Jones 11 years ago
  • Probably needs to be said here that 9 women don't make a baby in 1 month. Sometimes finding and recruiting good technical talent is hard. You can find people with credentials, but not necessarily the mojo you need. I had to dismissa CS guy with a Masters Degree because he just couldn't deliver usable code. If you have the money to go poaching for employees, they need to know that, and probably need a recruiting firm to go looking for them, bringing in candidates. Building a team takes time, and building a good team takes even longer. – Mark0978 11 years ago

3 Answers


9

You can try to buy them out. Depending on what type of agreement is in place (what do you mean you don't have a shareholders agreement?) the method, price, and structure of such a buyout would be determined.

However, bear in mind that there are 2 major issues raised in your question, though you only ask about one of them. The one you ask about, getting rid of a co-founder, is only half the problem. The other half is that you've indicated there's a clear split between sales and technical.

There are multiple possible causes for this split. One, as you've indicated, is that the two groups have differing loyalties, and so it would not be possible for these two groups to resolve those differences.

The other, as pointed out in comments on the question, is that the technical team either knows something the sales team does not, or the two teams are not communicating with one another effectively. Either way, the resolution would revolve not around getting a new technical team (or a new sales team, for that matter) as the new pairing would result in the same issue down the line.

You may be better off getting someone to come in and mediate between the teams, to first ensure that the two teams do understand one another, and the expectations of each team is reasonable and possible. Only if that's determined to be the case, and the issue is of differing priorities and loyalties, should a split up be considered.

Addendum In response to the addition to the question:

  1. Scaling a team quickly is usually a bad idea - without sufficient time to figure out both the qualifications of candidates and the chemistry with the existing team, this can rapidly backfire. You can still hire aggressively, but the reasons you cite for being slower and more careful are valid.
  2. As you pointed out, without the developers, your business would be in trouble. That in turn means that you have to work things out with them. If you can't do it on your own, bring in a mediator to help work things out.
answered Dec 5 '12 at 04:12
Blank
Elie
4,692 points
  • +1 this. You really need to understand the reasons *why* the tech guys don't want to grow the ream. In my experience as a tech guy, it can be hard to explain to non-tech people how hard it is to scale a development team. Sales people in particular seem to be under the impression that doubling the size of the team will instantly double productivity; in fact, it's much more likely to halve productivity for months while the new people learn the codebase, and will never double the speed of development because communication overhead increases with the square of the number of devs. – Giles Thomas 11 years ago
  • +1 for suggesting an external mediator, someone who can *appreciate* the beauty of good code/infrastructure that the tech team want to create, and the joy of executing a sales plan and making good money... and then explain them to each side. – Darren Cook 11 years ago

1

Because of generation gap, difference in background, sales reps idea
won't match with technical founder.

[flame suit on]

At best, this sounds like rationalization... at worse age discrimination. And I'm not part of the 20 something club.

Everyone can have an "idea" - the problem comes from determining whether the idea will produce busy work or materially improve the companies objectives.

If the justification is that "because we are sales guys" or "because we are tech and know better" then you are at an impasse and will never move forward. If neither group understands or appreciates the work that goes into performing the task, they both will underestimate the magnitude of the task - further exasperating the problem.

And "simply divorcing and recreating" is a cop out - it assumes that development is simply something that you purchase. What about the domain knowledge gained from building and facing your customer base?

I would take a hard look at the company culture and determine where the communication problem is - and attempt to fix this first.

First problem: Why would someone from a sales position push the agenda of hiring more developers as a solution? Shouldn't the discussion revolve around what the business goal is, and than let the technical part of the company weigh in with their recommendation on how to achieve the goal? Consider the reverse - I doubt one would feel that adding 10 more sales people to improve deal flow under the auspices that the current staff is incapable of meeting objectives wouldn't be warmly received either.

Planning and product development should be a collaborative effort - not a "push the features under the door and wait for a response". In addition, a tech founder can't just be a lead developer - yes, coding is important - but also address many of the tasks typically reserved to a CTO (here is a good article that talks about the founder developer gap).

Some collaborative product / customer development methodologies could also help you mend the "us vs them" chasm and refocus toward delivering value to your customer base. Search this board for some Agile / Lean recommendations - they may offer some additional ideas. Or bring in a advisor who is technical to help.

Best of luck with your efforts.

answered Dec 8 '12 at 05:12
Blank
Jim Galley
9,952 points

1

The short answer is there is a way to divorce but it would fall to the articles of organization and to the laws of where the business was organized in. There will need to be an attorney and if an amicable agreement isn't completed it could be quite costly.

The positives that I read in what is posted is there is interest in what is being offered by those that have money but doing. So I suggest ask what is it that got them interested in the funding? Was there anything about the mock ups, intellectual property, technical members or any design pieces that attracted the first investments?

What can two sales guys be doing this early on? Is the product/service already being sold? Do they have a marketing plan, focus groups, contacts in businesses? The early work for a firm that is doing something in technology is typically strongly technical with some marketing type of feedback. Really product development type of stuff. What is it that the sales guys adding to this part of the process? What do they understand of it? There are real risks that the golden egg maybe in the technical team and that the sales people have gotten over emphasized.

So I suggest reviewing what is it that is causing the break? Is the disagreement on features and functions is it a disagreement on tools? Or is it a disagreement on how it will be sold? So likely you have some type of business plan and in it there is a description of the product/service along with who will buy it and how big that market is and how it can be marketed and sold to them. In that there are assumptions that need to be validated that describe how this will be met. Developers are typically persuaded by numbers. I suggest showing what needs to be achieved and what that will mean by the numbers.

Good luck

answered Dec 5 '12 at 05:38
Blank
John Bogrand
2,210 points

Your Answer

  • Bold
  • Italic
  • • Bullets
  • 1. Numbers
  • Quote
Not the answer you're looking for? Ask your own question or browse other questions in these topics:

Co-Founder Founders