Skip to main content

WhatsApp, Revisited

While researching for my blog entry about the Facebook purchase of WhatsApp, I wanted to get the opinion of someone who has industry experience in this sort of thing.  So I reached out to my good friend and former colleague Mark Pilipczuk who is a marketing veteran with 25 years of experience and a former SVP at AOL.  My question to him was simple:  did the purchase make sense when taking the cost into consideration.  His answer is below.

"I haven't spent any real time thinking about whether the $19B was a good/bad/indifferent deal.  What I have been thinking about is the YouTube acquisition by Google a few years back. Many thought the purchase for $1.65B in stock was excessive, particularly for a startup that had no real revenue model and had some serious potential copyright issues. In fact certain three letter ISPs looked at YouTube a couple of times prior to that and couldn't make the math work for an acquisition.

What Google was betting on--it turned out correctly--was the explosion of interest in the sharing and mashing up of video content. Google wasn't paying for a certain number of MAUs
(Monthly Active Users. -Larry) or how that rate of increase might continue or accelerate. Instead, they were betting that the number of minutes of video uploaded was going to explode and that the consumption of those minutes would also explode, shifting attention (and therefore media dollars) away from TV to online.

I believe Facebook's purchase of WhatsApp makes sense in general for the following reasons:

  • Facebook "and..." Facebook is no longer the "one-stop-shop" for social networking. It's also not dying among teens, regardless of what you might see in the headlines. Rather people are tending to use multiple networks and applications, depending on their needs. The basic one is Facebook supplemented by something like Instagram, Snapchat, Vine, etc.
  • Social networking moves to mobile. With the greater capabilities of mobile phones, it's easier and more convenient to do almost everything from our phones. There's no need to go back to the desktop to accomplish too much creation and all the consumption can be done from the handset.
  • All time spent online moving to mobile. It's not just social networking moving online. It's all time online moving to mobile.
If you're Facebook, you'd like that second/third app to be in your family of brands. Even if you don't monetize WhatsApp and put ads on those screens, you can certainly use the data to monetize Facebook. Getting access to that transactional and behavioral data is a good thing as it keeps it in-house and eliminates the need to license the data separately.

I think of the acquisition in terms of getting access to lots of data and gaining share of handset, particularly among the 2nd/3rd app being used for social networking. With the acquisition, the Facebook social graph on users gets more robust.

I think we'll continue to see Facebook acquire fast-growing apps, even if they don't have revenue models for the foreseeable future.

Now is $19 billion a good price? Absolutely no idea and I honestly don't believe anybody who's trying to model it out has a clue. If you're trying to value it on a per-user basis, which implies that the acquisition has some expected break-even, you're missing an important thing. Facebook, much like Google, isn't beholden to Wall Street. Zuckerberg and other insiders have control of the company's voting shares. They are already fabulously wealthy and can afford to play the long game, much like Brin and Page at Google. They don't have to justify the purchase price to anybody else and, if other shareholders don't like it, there's nothing they can do except sell the stock.

I think that for sure we'll look back and think tactically this was a good purchase. We may have a different opinion on the price, but I think that like the YouTube purchase, it'll be a few years before the jury returns.
"

Thanks for the amazing insight, Mark.

Popular posts from this blog

"Ni jiang yi yang de hua ma?"

Last week, I wrote about the necessity of having a clear message . Because this topic is so important I decided to follow-up with another entry on this general subject. This week we will approach it from another angle. (For the curious, the title says " Do you speak the same language? " in pinyin, which is a transliterated Mandarin Chinese.) Recently, a good friend of mine (who is Chinese, ironically) and I were playing pool. He had to bank the 8-ball in the pocket to win the game, and since it was an informal game and bank shots are my area of expertise, he asked me for advice. I told him, "you just need to strike the cue ball with medium speed so that it hits the 8-ball right in the middle." He didn't believe me so we marked the positions of the balls, and then he took his shot only to watch the 8-ball sail past the pocket. "A-ha!" he exclaimed. "I told you it wasn't that easy." But when we reset the positions and I made an attemp

It's Easier to Fail at DevOps than it is to Succeed

Slippery when wet Since the term DevOps was coined in Belgium back in 2009, it is impossible to avoid the term whether in discussions with colleagues or in professional trade magazines.  And during the years while this movement has gained momentum, many things have been written to describe what elements of a DevOps strategy are required for it to be successful. Yet in spite of this, there is an interesting data point worth noting: not many organizations feel there is a need for DevOps.  In a Gartner report entitled DevOps Adoption Survey Results (published in September 2015),  40%  of respondents said they had no plans to implement DevOps and 31% of respondents said they hadn't implemented it but planned to start in the 12 months after the survey was conducted. That left only 29% who had implemented DevOps in a pilot project or in production systems, which isn't a lot. "Maybe it's because there truly isn't a need for DevOps," you say.  While that

Is No/Low-Code the Key to IT Nirvana?

 Unless you've had your head in the sand for the past year or so, you've seen the phrases low-code  and no-code  bandied about quite frequently everywhere you look.  You've probably wondered if this is something new that's here to stay or just a "flash in the pan."  Although the terms have been in the fore of the IT trade publications recently, Low Code Development Platforms (LCDP) (and the corresponding No Code Development Platforms) have been in existence since 2011.  Their roots can be traced to the 90's with 4th generation programming languages and GUI-assisted programming paradigms, e.g. IBM VisualAge for Basic, which was discontinued in 1998. For those of you who aren't familiar with either, the premise is that these platforms allow someone to quickly build applications using a WYSIWYG interface and a "click and configure" paradigm to Isn't this the source code to Roblox? rapidly build full applications with little or no coding requ