Co-founder or employee?
Everything is sort of planned/worked out. I'm already in the coding stage. For this I could use some help (I suppose), but I'll probably will be able to manage by myself.
I told a friend of mine (who is a great coder) the concept and the mockups and he thinks it's a great idea. Even more, he wants to help as a co-founder. The code written for the site will be of higher quality and less 'hacked together' than when I would do it alone.
This is the dilemma: I don't want to split 50/50 just yet. However, I would like his input. I'm able to pay him for a bit of work, on the difficult parts of the site. Also an option would be to pay him a lower salary upfront and a small portion of shares if the site takes off.
What would you do in a situation like this? Or have you been already involved in this scenario? For who have already 'startupped', is it possible to pull it off as a one-man show, or am I stupid to even consider this?
34 comments
[ 3.1 ms ] story [ 83.9 ms ] threadCheck it with a lawyer, sign it and then leave it with the lawyer.
The guy might be a friend but it helps stops disputes occuring in the future :D (i.e. you both know where you stand).
EDIT: have you already formed the company or not? I couldn't quite make that out.
No, I haven't formed a new company yet. I do have a business permit for my one-man company.
Most people, even most entrepreneurs, don't have the right personality for it. And so it gets a bad rap. But if you do, you can clearly make more money in the long run by not giving up as much equity.
You need to assess, whether on your own or through conversations with him, where he fits into the grand scheme of things.
Employees carry out orders and implement code to a product spec
Co-Founders contribute business and product knowledge and opinion, on top of their "employee" duties.
Anything and everything is possible. Successful startups (like the previous fuckedcompany.com) have been built with just 1 guy acting as CEO, Janitor and Chief Coder. Others have been built with 1 founder and a few employees, and others with 2,3,4 or more co-founders.
At some point you'll probably want a co-founder. Both to bounce ideas off of and to give credibility to the overall business. While you're in the garage/basement phase this is not usually your prime concern. It's good to let things just "happen" for a little while until you find your ultimate direction.
For your specific case, given the limited details here, I would probably pay your friend a fair rate to act as a consultant advisor/coder. See what develops and if you feel he is of co-founder quality for this specific project. Like anything there is a tradeoff, and the tradeoff here is that if you later decide to make him an official co-founder, it will have come at the expense of his consulting salary.
I tried Googling it, but it's hard to sift through all the fluff.
From his wikipedia entry: "Writer Rogers Cadenhead drew attention to logs showing that in his edits to the page, Wales had removed references to Sanger as the co-founder of Wikipedia."
Some people are brilliant at implementing a concept, but utterly horrible at pretty much every other aspect of running or building a company.
Just because this person would be instrumental in getting the working code going does not mean that they are at all qualified to shape the business...
But even if it is a really hard coding problem that you need a star for... The big question is whether he's an entrepreneur or not.
Questions to ask him (and yourself):
1. How much traction would it take for you to quit your day job? 2. Which evenings and weekend days are you willing to set aside for this project moving forward (at a minimum). 3. How many months can you go without a paycheck (related to #1)? 4. Do you like non-coding problems? UX? Copywriting? marketing? SEO? (i.e. are you willing to evolve as a founder? I have a long post about this here: http://www.tonywright.com/2008/startup-founder-evolution/ )
In terms of parting with equity, the equation should come down to risk/value. If you're both committing to spending 10h per week on this, then he deserve a largely equal slice. If you're quitting your day job and going 40h per week (or have 300h already sunk into it), then you're risking more and deserve a bigger slice.
Be careful about overvaluing what you've done so far. A startup is a multi-year commitment. A few months of weekend and evening time is a tiny percentage of value creation compared to what's been contributed at the end.
As people have said, having somebody to bounce ideas etc. off is hugely valuable.
Another thing is that you don't have to have a 50/50 split to be co-founders. If you've got a 10+% stake in a company and come in pre-money, I'd consider that a co-founder.
If you're just worried about giving up equity, you'll need to break yourself of that. It'll kick you in the ass later on dealing with additional people coming on or when talking to investors. You'd be much better off building a team with "skin in the game". Just set out a vesting schedule with a 1 year cliff or something so that if somebody doesn't fit that there's a period of time where that can be evaluated. Be straight-up with them that that's happening.
1. He will stay motivated, even when you run of cash and motivation.
2. He is in it for more than the money and the friendship, but because he actually believes in the idea
3. When there is a disagreement, he will allow you to make the final decision, and not decide to leave
Don't go 50-50, because this guy may be a good coder, but he's just a coder. The ideas are yours. Later you may bring in 2-3 other people, what percentage do they get then?
I think your idea of a salary at the start + 10% to 15% is more reasonable. Give him an option to get to 20% if he does some particular stuff.
But take him on! A one man show is really tough, particular later when marketing becomes much more important. You'll need someone hacking away while you market.
Giving up 50% to a guy who just will do the coding at the start is too much. But if he is good at marketing, analysis, idea bringing and all the other stuff that take a company over the first year, then one can give him 50.
When the shit hits the fan it will be too late to have a friendly, productive discussion.
Make him a co-founder if his skills, motivation and interest in the company merit him being a co-founder, but don't deny him the opportunity out of greed.
Having a co-founder to share in the risk and reward of a company makes the process of building the company a lot easier. Would you rather own 50% of a growing, successful company, or 100% of a company that never left the ground?
If that's not the case, I don't really know what you should do. Few things are worse than having one cofounder work harder than the other cofounder despite an equal equity split.
The question that you should really be worried about is how to make it work (read manage conflict) between the two of you. Consider him your startups greatest opportunity as well as the biggest challenge.
Apart from the reasons others have already mentioned for having a co-founder - You need a co-founder not just to save your startup but more importantly and more frequently to save you from your startup.
If it's the first, then you're using equity as a way of paying him. You're essentially saying: "Your work would normally be worth $20,000 to me. However, I don't have the money. So I'd like to pay you in shares that have a chance at being worth a great deal more than $20,000 down the line."
In the second case, you're saying "I need a partner, especially one with a technical background. I see you as having the ability to make this venture a success, in ways I can't even anticipate right now. This is a very early stage startup, with all kinds of risk. This thing will consume your life for at least a few years, so you'd be coming in as a cofounder".
It can be pretty difficult to get well employed, well paid programmers to take either deal you're offering, but I'd say the second is probably the best bet in terms of getting him to agree to come on board. Mainly because working equity usually means you end up working for nothing.
However, I would also caution you against making someone a cofounder simply because you need his tech skills and can't afford to pay him. He's a buddy, that's great. But you need to have faith in this guy's abilities as a cofounder.
You almost certainly should vest. But a better way is to run a little trial period of three months or so, maybe with a little bit of vesting, and then negotiate. He should be happy to demonstrate his worth. If he can't you'll have to make the hard decision, but at least it will be based on something.
Keep in mind that friendship does not, in my experience, really survive a broken business relationship, unless you both go down with the ship. Even if the split is respectful and equitable.
he also needs to have skin in the game, which means a monetary investment if you have invested monetarily, and he needs to be full-time if you are full-time (as I hope you are!)