3 ms·
The story does not seem as clear-cut to me as your post suggests. From reading between the lines it seems that your partner is responsible for some if not most
by trevelyan 18y ago
The story does not seem as clear-cut to me as your post suggests. From reading between the lines it seems that your partner is responsible for some if not most of the coding work, and that you're responsible for other things including financing, community management and possibly marketing.
If this is the case you should have no complaints about the money. And if you've been rushing at the project for more than a year and were in desperate crunch mode three months ago, the slow-down in code growth is natural. Products routinely oscillate between new feature development and bug-fixing. It isn't uncommon for the code base to hold constant or shrink as it is tightened up following launch. You should evaluate whether your founder is doing/has done his job by the reliability of the system you have built under the constraints of money/time/effort. If he moved heaven and earth for you 12 weeks ago, you have no right to complain about a little lethargy now that the ball is in your court.
Your post does not include any suggestions that the tech side of things has been up-and-down or unreliable, or that your partner has failed to do his job on this front. Merely a complaint about the pace of new feature development. If this is the problem perhaps your co-founder is simply burned out and needs a vacation. The best way to motivate him may be to start hitting home runs yourself.
If the company is going into debt and you can't hold up your earlier division of labor/finance, that is a problem for the business. If it were me I'd work to make any new financial obligations shared going forward. This should help motivate your friend to cut his losses if he does not believe in the viability of the business anymore.
First and foremost though, you are out of the development crunch and are presumably at the point where you are being expected to deliver results and problems will surface with scalability. You need to be really careful your attitude towards him is not being caused by your own frustrations at how your business is developing, and/or a desire to find a scapegoat for slow growth or underpar performance.
- skmurphy 18y agoThese are some very good points. It sounds to me like he has effectively been your employee for some time. If there is a third party that both of you trust perhaps you can have a three way conversation where you focus on the current situation and the best way forward that's fair to everyone. The key is to focus on "going forward from where you are." That's the challenge you are faced with. Why do you need to buy him out completely? Are you going to need him to help new employees get up to speed? Find a way to keep the conversation going and reach an amicable solution.