If you think of your business as a castle, a moat is something that stops others from taking your castle from you. This could be anything from a network effect (Facebook, LinkedIn), economies of scale (Amazon, Walmart), to patents (most biotech companies) to brand (Coke).
The way he put it was something like, "If you gave me 100 billion dollars to take Coke's market, I can't. They've been investing in infrastructure and brand all over the world for decades. Even if I could make a better tasting beverage, people would still buy Coke. They have a moat".
http://www.valuewalk.com/2015/09/warren-buffett-on-economic-...
Though they are making good things, so it's hard to be too critical.
I don't for a second blame the founders of Mailbox for doing what they did. When the market creates a strong set of incentives like this you can't really expect anyone to do anything other than take the $100m. But this is the side-effect.
That doesn't mean they're bad companies, but there's definitely a funding gap for the type of company that will require $3M in investment up front and be worth $10M in 5 years. That's still a great return, but right now it's the domain of private equity.
- good for founders - they get a big fat paycheck and a chance for a job in a big company
- good for VCs - a payoff, even if small, is better than no payoff at all, so they want their 9 not-so-good startups to be bought
- good for the buying company - they can literally just kill the competition by throwing money at them, + they get some proven and experienced employees, which may be worth it given the unreliability of the standard hiring process
Care to guess who this deal is not good for?
Startups are (and are being heavily marketed as) a get-rich-quick scheme. Most of the people involved are self-selected to follow this process. And all this talk about providing value to the users? That's the part of the scheme where you get used.
My view on acquihires is that to some extent it's a trick the acquiring company plays on itself. Some manager is getting to hire a few good people using money (the acquisitions budget) they wouldn't otherwise have access to.
Also, there's generally some amount of IP and customer data involved as well.
For about 6 months to a year, after which time most of them have left, or have gone into "waiting for the golden handcuffs to come off" zombie-worker mode on a project they have no inherent interest in.
Totally anecdotal but the couple of acquihires I've seen from the inside have gone like this and it seems to be the natural state of them based on what I've heard second-hand from others.
Any acquisition involves a lot of turnover. Guaranteed that this turnover is built into the models they use when evaluating acquihires. Consider how expensive most company's talent acquisition costs are though (upwards of $100k+ per candidate hired for top talent) and it starts to make sense.
And many times, there's no other exit option for the VCs. Does it suck for users? Absolutely - which is why companies often have lots of apprehension about being early adopters of a startup's technology. It's why B2B startups are really hard, and why they tend not to hockey-stick because the customer acquisition costs are high and don't shrink with scale.
It's up to the founders to convince their VCs to pass on the acquihire because they think the company still has hockey-stick potential. Zuckerberg did this a number of times - it was still really arrogant, but it paid off for Facebook and shows why founders need a bit of arrogance to be successful. It's a lot harder to do this if you're running a startup that doesn't have a lot of market traction.
You get acquihires when the assumptions behind the company's business model have been proven false and there's basically no way to solve it other than rebooting the company. Arguably this is an argument to not take VC until you've got the hockey-stick trajectory, so you can pivot & reboot at will without dissolving an existing organization. But even this sucks for customers, if you have any.
Doesn't that make them bad though? I mean it's like saying "It's not that the mafia are bad people who want to screw over people, but their business model requires them to blackmail and occasionally kill" (not comparing levels of "badness" of course, merely showing the problem in said reasoning).
It's not like following a particular "business model" is not a decision people get to make. And if people take the VC model that favours acquihires, then they very much have decided to do stuff that screws with users.
The opportunity was the team, not the product they were producing.
Say you had a room full of math prodigies, but all they were doing was watching TV all day. You hire these math prodigies for $X and put them to work solving math problems - this doesn't mean that watching TV is worth $X, in fact it likely means the opposite, that their value is underutilized by whatever they're doing right now.
So there isn't enough money in making email apps, but a team capable of producing a great email app can be put to use doing things that do make a lot of money - but it sure isn't making email apps.
And that's unfortunate, because as users we're missing out on a lot of great products. The dark side of the immense growth in software (and immense growth in software salaries) is that entire products and services are no longer economical, even though we'd all love to see them. The VC system that drives these early acquisitions and acquihires is just one more factor among many that limit the field of what can be economically produced.
Too much money! I don't care how big of a genius you are you're not worth that as a developer of an email client, and honestly to write an Email client is not genius level shit. The UI was dope, and their invite process was funny, that's all.
Looks like Dropbox fucked up, that's all, bad business decision, trying to copy Google and do better than them in the end they did the same.
[1] http://techcrunch.com/2013/03/15/mailbox-cost-dropbox-around...
Not exactly. Could be the other way round too. It depends on whether the stock of the company is worth more or less than cash in the long run.
Except since it is the company issuing stock in itself you can't really think of it as fungible. If it ends up being worth more than the strike price then literally one of the events that led to that price was the purchase stock being issued. Of course that doesn't mean the is a causal link, but in a very real sense the stock was free for the company itself.
The only cost to the company is opportunity cost.
Stock always has value, especially to management.
Unless the company has poor self-esteem. :)
The reason so many technology companies today make acquisitions using stock is because they (correctly) understand their stock to be inflated, relative to intrinsic value. If that were not the case, if they understood their stock to be undervalued, then they would definitely not be giving it away in transactions. They would be making all-cash offers instead.
But that's the key isn't it? I think you're looking at this from too narrow a point of view.
Yeah, email clients aren't worth much money, so its development isn't worth much either (when's the last time anyone you know paid for an email client?).
The point isn't to acquire a "developer of email clients" it's to acquire a "developer of top-of-class mobile apps", which is considerably valuable. Think of the average quality of a mobile app you use on your phone, the bar is pretty low. Producing truly amazing mobile apps (like you said, the UI was dope) is hard, and requires the flawless, cohesive operation of a lot of facets from engineering to UX design.
Truly excellent mobile teams are very rare, and worth a lot of money. To the tune of $7.6MM over 2 years? Beats me, but it doesn't seem completely out of the question.
Talented developers are worth a lot of money - teams of talented developers, designers, and product people who have a track record of producing stellar work together are worth a multiple of their individual values.
> " and honestly to write an Email client is not genius level shit."
It's not genius level shit, but it's a surprisingly rare skill, and by that I mean writing very, very good frontends. Most people here can write a functional email client if they had to, but how many of them can write a really fucking good one, so good and so easy to use that people - and not just the technorati - sing its praises from the rooftops and get their friends and family to download it?
The Mailbox team was operating at a level well above nearly all mobile app teams, and the quality of their work was easily an order of magnitude better than the industry norm of its time. This may not justify their acquisition price, but I think you're selling them short a bit. They're a team of people known for exceptional quality work, and command a high price for it.
Dropbox could have thought that and just been wrong. Even in the normal economy, per The Economist about half of all acquisitions destroy value. In our little hothouse, I'd expect a much larger percentage of value-destroying takeovers.
But there are plenty of other reasons deals get done than a company-wide coherent calculation of economic value. E.g., I've heard of acquisitions happening because a CEO needs to demonstrate to the board that they're doing something. Or incentive structures set up to reward an M&A team based on how many deals they do. Or executives wanting to bring in their old buddies from another company. Or, "gosh, money is so cheap right now we'd better spend it because our competitors are spending."
If we're being ultimately generous with Dropbox then what they are doing is exactly correct - taking a team that can create a $100M+ product and reassigning them somewhere that they can fulfill that potential. But that's of scant consolation to all the people that want to continue using the email app.
Because if that's your goal, you clearly aren't passionate about what you're doing. You might as well go work for a 9-5 company doing CRUD apps. /s
I'm not sure that's true (see: Sparrow). I just don't think there is enough demand for people to want to pay for an email client. I imagine for a huge majority of people, default mail client's work fine enough for personal use.
Part of the problem is, unlike say Pinboard, an email client doesn't feel like 1-3 devs worth of work. The protocols are horrendous, you have to understand the quirks of lots of servers, etc. Plus all the UI and backend and search work. I'm not sure it's approachable as a small indie company.
There's also, of course, bad behavior by large companies such as mozilla: Thunderbird made it very difficult to build an indie email client because you have to compete on merits and against free, but they eventually got bored and just quit making it. Not to mention competing with free/ad-supported. And the semi-annual YC/vc supported email client company.
Not to mention what is coming close to active sabotage of productivity apps by the ios and mac app stores (lack of trials, lack of upgrades, etc).
"We now live in a world where people pitch tantrums about paying $10 for an app"
Where do users/customers get these expectations? Call it market forces, race to the bottom, whatever... do a little root cause and not blame joe public please.
It's still a prominent, maybe even the most prominent, item on my personal list of "reasons I shouldn't build an email app."
To make me switch, you would have to show me why the new thing was so much better. Like how Google search results were always better than Yahoo! (IMHO, no objective measurements used) so I switched. You would also have to explain it in a sentence I could immediately understand, whereas all the recent clients I've ready about either (a) claim to make things better but don't tell/show me how before I get bored of the page, or (b) use manager speak that I can't understand or is vague and abstract promises to increase collaboration or something. Therefore I've given almost no attention to any recent attempt to change email.
I use Thunderbird on Linux and Windows. It "works for me," in the sense that it's stable and predictable and doesn't lose my data. But it also has lots of niggly little problems that annoy me, like UI decisions that made more sense ten years ago than they do today and limited tools to support people like me who have a ton of mail.
So while I use and recommend Thunderbird, I also would love to see something come along that is so much better that it makes me fall in love with it, instead of just shrugging my shoulders and resigning myself to this being as good as things get.
Yeah, this is definitely what I saw with Sparrow. For it to become popular it has to be adopted by a substantial number of people. However, I find that only really tech savvy people cared about Sparrow and its streamlined interface. When I showed it to other people, they were reluctant to use anything else because they were afraid to move from their Apple Mail. I'm guessing if Sparrow had existed for windows it would've been the same thing with people using Outlook.
And then there's people who don't even use e-mail, who think it's outdated and prefer PM messaging as a form of communication. It's easy to see why a lot of these promising mail client apps don't really take off the way other apps and services do.
Nevertheless, Sparrow will always have a home in my Mac, as long as it keeps working on OS X.
I guess Mailpile isn't trying to be commercial, so perhaps it will keep soldiering on the power of donations for as long as that keeps up.
We've structured our business to... actually have a business. Our team spent the first year selling APIs to developers [1] which already power lots of paid apps. The N1 mail app we released two months ago[2] follows this and will have paid features next year.
Plus both are open source free software, and quite popular on GitHub. [3]
What is Nylas? The website doesn't seem to be written for me, but for PHBs. Apparently you have great business, design, and APIs, but what is it that those things do? Are you an email client? A server? A webmail service?
What makes you different from Gmail or from Mailpile?
1. APIs for developers that replace IMAP/SMTP/Exchange. Use this to build any app that integrates with a user's mailbox, calendar, or address book.
2. A new extensible email app, built on web technologies (Chromium+NodeJS). This is called N1 and was released about 2 months ago.
We sell the APIs as an infrastructure business (like AWS).
I went to the "releases" tab on GitHub and it looks like the last one was in 2014. I see things in the GitHub repo that suggest there are Dockerfiles and Debian packages, but I don't see an actual Debian package repository or an entry on the Docker Hub. Is the recommended way to use it today just cloning the git repo? Or is there a stable release of the sync server that's tested/known to work with the binaries of the client?
We don't have "releases" because we are constantly releasing to production. Check out the `production` branch on GitHub for what we're running right now. Usually it's just a handful of hours behind master (at most).
I think certain enterprise-y email solutions have this, but there's no way to have that happen in the distributed email ecosystem unless all your messages were just links to a website that could delete the content centrally, or similarly, jpg's of rendered text that were somehow forced to be remotely fetched each time.
I know I had a former boss that loved to try using the outlook "unsend the stupid thing i sent" feature.
Little did he know the cients could turn that bit of functionality off. He hated when we replied to the emails he had "purged".
other than that, i don't think receivers like the idea that others can control what's in their inbox.
Or, more correctly, there isn't enough money to be made to satisfy VC investors. Mailbox and the like could have lived quite comfortably as paid-for apps with comfortable but small levels of profit, but that isn't what Silicon Valley rewards.
EDIT: also, IIRC Apple's restrictions on background processing meant that they needed to have every user's account set up on their servers to process push notifications. Did that ever change? If not that's a non trivial expense/complication to scaling, especially when you're up against an OS-integrated app that doesn't have those restrictions.