Sounds like OP has some personality issues that need to be worked out. And, I got a distinct "mad with power" vibe, as well. Early stage company founders do not need a boss. If they do, they're already doomed to failure. It sounds like this fellow just likes the idea of being chief of something, and isn't all that good at it. Many nerds have started companies without management chops or a good personality, but they made up for it by producing code that solved a problem. I'm getting the distinct impression the OP (who may or may not be strong on the code front) is definitely weak on the management and personality front, but wanted to spend all of this time managing and "networking".
I don't claim to be an expert on this stuff, but I am a nerd, and I do produce (when it's my place to do so, though in my current startup, I produce far less code than my co-founder), and I think I would have ditched this startup, too. Nerds, in general, aren't good at being bossed around, and the kind that start companies definitely aren't good at being bossed around.
But, I agree with you. The guy probably does actually have a good company in him (because dedication and a healthy appetite for risk are the primary requirements...everything else pales in comparison). He just needs to keep assessing how he can do things better next time, particularly when it comes to interacting with co-founders.
Wow-- I think the OP failed to learn a few lessons. The biggie is the seeming lack of empathy for his partners and his apparent belief that he's in charge.
At this level, it's a partnership. As a CEO, it's not your job to lead and have your partners follow. It isn't your job to make unilateral decisions on how you spend your time (networking versus coding). With a small team, you can be a cheerleader, a tiebreaker, and a buck-stops-hear guy... But for the most part-- it's a damn partnership.
And it's pretty clear to me that the poster didn't treat it like one, which is a shame.
I think he's very right about the team needing to have the same level of commitment... His deeper commitment is probably why he felt entitled to "lead", even when PG suggested that that might be the problem.
A couple of things I should probably point out: the SXSW was supposed to be a team trip and the point was for everyone to have the experience of interacting with a bunch of top notch startup people (we aren't from the valley) and I only proposed it a few weeks ahead of time after we had a lot of people telling us that it was the single most useful thing to attend all year (I didn't even know about it before then). Only two of us ended up going, but that wasn't my intention.
When we landed the YC interview, it meant flying from NYC to LAX for a ten minute interview. We were told that only I needed to fly out, but I said everyone should go because they deserved the trip. This was obviously not the cost-efficient approach, but I think it was a lot better for the team.
As for the Goldman comment, I find this to be a typical programmer retort to any questioning of what they are doing: "If you're so great, why don't you do it yourself?" In fact, I didn't question what he was doing for way too long precisely for that reason, and I think that was a mistake. Now as for doing it myself... there are some areas of technical knowledge that I do not have, which is why I brought people on. Now that I'm on my own again, I'm doing my best to get it done myself.
Hey, you probably wouldn't want me as a cofounder, fair enough. I appreciate the better luck next time comment though.
Kudos to you for sharing.
However, it may be worth noting that tptacek and SwellJoe both have (fairly) successful startups. I don't, and neither do most of the rest of the people here. So when they say something, it's probably worth listening to.
Something I've noticed about writing postmortems: focus on "What would I do differently?" and "What mistakes did I make?"
Other people are who they are. You aren't going to change them, and they usually have good reasons for what they do.
Most startups fail because of team issues. Mine did - I tried to keep it going for 2 months after my cofounder left, but couldn't. But then, this is my fault. If we'd been further along in development, he might've felt that the startup was a better bet. If I'd listened to him and released the easy version he was proposing, we might've been further along in development (but then, we had good reasons for not doing so...startups are hard). And he certainly had good reasons for leaving - hell, if I'd gotten into HBS, I probably would've left too.
Here we have a CEO that refuses to step down to keep the company together, that gets two votes in group decisions while his partners gets one, and that places all the blame for failure on his cofounders when things go south. The arrogance approaches the comical, it becomes more and more outrageous as one reads along.
What is the first lesson he learned? "Getting the team right". You see, he had a bad TEAM. That explains the company failure. Yep. Not him. Nothing to do with the guy that chased away perfectly competent people that wanted to work with him. Nothing to do with the guy IN CHARGE.
Leadership is a two way street. You can't have control without responsibility! I don't think there is any team that wants to work with that kind of leader. You will never "get the team right" if you see your position that way!
His second "lesson learned" is to connect with people, and by "people" he means networking with potential investors, advisors, other businessmen, etc. Yet he never connected with his own teammates!
Next, he finally finds fault in his own leadership. You see, he is too much of a consensus seeker so he can't get things done quick enough! Obviously, he places too much trust in his cofounders. THAT is what he believes his problem is.
Then there's this little gem: "Then I decided not to take Paul Graham’s advice to make the other partner our CEO for the sake of civility (a decision I stand by fully), which effectively ended the company." You would rather your company fail than not be in charge? What kind of leader is that? You still stand by the decision that killed the company? What does that say about you?
Good leaders are famous for taking credit for failure, even when it is not entirely their fault. They also DON'T take credit for success. They let others give the credit to them unbidden. That's what causes their subordinates to at first respect them, and eventually love them.
Dear author: does that sound like you?
I'm sorry if I'm a little harsh; as I read this it is blowing my mind a little more with every paragraph.
I placed a great deal of trust in my team for nearly a year and some of that came back to bite me. Yes I did list a lot of flaws, but they were not flaws that everyone had in common, they were the things that stood out to me as being problematic across the length of the venture and, well, I thought I mentioned a lot of things I thought I should do differently. But I am open to hearing more.
In a three-person (or two-person, by the time this particular piece of drama came to a head) company, there is a team, and there are players, and if the team is running well there's a team lead --- who's there because the team believes they'll function better with a leader. If the team wants to sound "all grown up", they'll call the leader a "CEO". My team still doesn't call Dave the CEO.
Using the word "CEO" in this situation is a "tell". Think about what you're saying.
How was the other person not more suited for the position? The company couldn't survive under you, it might have under him. Do you care more about being in charge or having a successful business? Can you picture yourself working in a successful startup where you are not the CEO?
If you're just getting started, and you have no leverage, picking up part-time founders makes perfect sense.
They will never be as devoted as you will be. They will never be as committed. Sure they may be talented and will write tons of code for you - but what happens if they leave and you have to figure out how all of their code worked?
I'm sure you've read all the articles written by other entrepreneurs about how much dedication it takes to build a company. There are always exceptions to the rule (del.icio.us), but I'd say most successful startups require your full attention.
Vest everyone's shares too - if I bail on you early, I might just have a few % of the company when I leave.
I think it's OK to have varying levels of commitment. Of course, the CEO should be 100% in the game. But I've worked with developers part-time, as partners, and found them reliable and committed with a lower number of hours.
* "Lack of conviction" reads like a moral judgement on the rational business decision to leave a startup that isn't working.
* "Fear" is an emotional word that (to me) implies irrationality; "concern" or "wariness" might be more appropriate, especially because you don't give much context. What are they "afraid" of? A company with no revenue and a 3 month runway?
* In a three-person startup, the "half developer half CEO" probably shouldn't be picking out the ex Goldman developer as good-but-not-excellent for not turning out a feed reader fast enough; why didn't you get it done then? And especially...
* ... when the CEO of that pre-revenue pre-product decides to have the company pay to fly him to SXSW during that dev crisis.
I mean, look, you can do everything right and fail, and everything wrong and still win; startups are a huge risk, keep trying, etc etc --- but you wrote this to get feedback from people, and mine is:
* I wouldn't want you as a cofounder (hey --- my cofounders probably don't want me --- I work my ass off to mitigate that!)
* You seem more engaged with the "lifestyle" of a startup --- lawyers, "networking", advisors, incorporation, "voting" --- than with the reality, which is a mindbending daily grind of work and fear and effort hopefully aimed at getting to cash flow neutral as soon as possible, but most likely aimed right off a cliff.
You're obviously going to do this again; all knocks aside, you read like this stuff is in your blood. Better luck next time.
[edit: toned down very slightly].