Do you disagree with the methodology? How? Let's talk about that, and not what you think about the blog author's personal life.
She doesn't appear to consider any of this. At least, I don't see any numbers that take this stuff into account.
Those are all good questions to ask. Some of them are questions she considers, some of them aren't.
Ultimately, though, the question of how you --- a prospective employee --- value equity is orthogonal to the question this post engages with, which is "how do I take the valuation for my role that I arrive at and effectively communicate it to the prospective employer so as to improve my initial offer". And, in that regard, I think this is a very good and useful post.
I mean, would you take advice about how to move up in a company the same from the son of the founder?
I personally worked with a married couple as founders, and would never do this again (a lot had to do with them in specific, but the general failure mode of any relationship problems spilling over into business, on top of them always ganging up on others, seems general). I'd probably work at a company with siblings as founders, and maybe at a company where a couple were in different roles (founder + employee).
The negotiation was awkward, but I'm personally convinced that we're a stronger team because of our close personal bonds. It's not for everybody or every team, of course, but I believe it works for us.
If she's not reporting to the CEO, how does her new manager feel about having a team member who's his bosses' fiancee? Would he be comfortable firing her if she fails to perform?
I know this seems hypothetical, but I think anyone who's been around startup has seen some variant of this play out multiple times. It's bad enough when it's friends; it's even more treacherous when it's a fiancee/wife.
Yes. Strictly speaking, if you get into business with your significant other, you are increasing the cardinality of the set of things that can go wrong with your team. For people that think like us, maybe that's where you stop thinking, and if so, fine. But the set we're talking about is very large, and I also know high school statistics, and so can observe that the relationship stuff is unlikely to be the event that blows up your team.
Believe in working with your spouse (or close friends, or whatever) or not. Either way: it has nothing to do with negotiating for a job, and it's a little creepy to bring it up here.
It would be different if we were inserting Michelle into some rigid organization structure, especially if she was reporting to somebody other than our CEO. We don't have that kind of structure, though, and even if we did, we would never tell a frontline manager to hire somebody based on nepotism. That's a sure-fire way to kill a company in my book.
Even if she's reporting directly to the CEO now, that raises its own questions, in particular for other employees. If I'm at her same level, do I feel like I'm going to get a fair shake if she and I are gunning for the same promotion? Down the road, as the organization grows, is she forever tied to reporting to the CEO? How do you ensure there's never a quid pro quo exchange that opens you to a lawsuit?
It's those kinds of questions that scare most organizations away from having direct reports romantically involved. It's especially fraught in a relatively unstructured organization like a startup where things like promotions and org changes can be fairly sudden and subjective.
Even if the reality is that there's no favoritism, it opens you up to lawsuits both from the people who are involved, and from their coworkers. If they break up, and then he demotes her or lets her go, lawsuit city.
I've seen this firsthand at a major venture startup (but wasn't involved in it myself) - a fiancee/employee decides to leave an officer for one of the other officers of the company. Disastrous for the company.
Anyway, it's their company, and I respect that they can do whatever they want - I only raised this issue because it happens fairly often in the startup world that a very tiny company wants to hire someone in a relationship with an existing employee, and there's a lot of issues you bring on board when you do that.
I finally realized that, no, in fact they are engaged to each other, but that was after she'd started referring to herself in the third person:
Michelle: “What should I do? ..."
I hope that someone else wrote this article on her behalf.The founders also set expectations that we'd adjust salaries to market value in the event of a Series A, though that isn't something I relied on as a part of my decision.
I thought the analysis was generally quite good though and she seems to be quite intelligent. Please don't take my critique to mean that I thought the point she was making was incorrect.
Finally (and most importantly): Did she run the numbers about what that 1.25% might realistically be worth? She compared the offer to her current position and (without the equity) there's a ~$55,000 difference. That's a shit-ton! How much of an exit would Keen.io have to have in order for that to pay off if she's on a reduced income for, say, four years? She'd have to get a couple hundred grand off of that exit. Will her share of equity get her that?
Anyway. This isn't a negotiation. And she didn't fully run the numbers.
[Edit]
I also wrote up my experience negotiating with a start-up [http://auscillate.com/post/238]. I'm pretty naive about this stuff, but at least I attempted to answer some of the issues of the value of equity.