Scores by kind of claim
Each kind of claim is scored on its own, out of 100: the share that held up, with the range it likely falls in. Fewer resolved claims give a wider range.
-
Factual claims
Statements about the present or the past, checked against the record: did they hold up?
72 65 79 -
Predictions
Statements about events outside the person's control, checked once they fell due: did they come true?
66 54 78 -
Promises
Commitments to the person's or organisation's own future action, with something to deliver: was it delivered?
Insufficient record: 1 promise resolved, 5 needed for a score.
All types combined: 71 (likely 64 to 77, high confidence), from 79 claims: 60 factual claims, 19 predictions. It mixes kinds of claim in different proportions for different people, so compare people kind by kind.
Balaji Srinivasan's claims
251 claims · page 3 of 3
“So, very roughly, about two years of monetization gets $19B in revenue.”
Balaji Srinivasan, writing on X 31 December 2019 Post by @balajis on X, 2019-12-31 (X)
Roughly two years of monetizing WhatsApp at Facebook's ARPU would yield about $19B in revenue, the amount Facebook paid for WhatsApp.
Mostly false False in substance, right in a detail.
The second judge would not resolve this claim; the verdict shown is the first judge's.
What would count as true or false
The claim is an arithmetic estimate, hedged ('very roughly'). Facebook's WhatsApp purchase price was announced in 2014 as about $19B. Compute: WhatsApp users (as cited at the time of the claim, about 1.5–2B) × Facebook's annual ARPU (from Facebook's 10-K or quarterly reports around 2019; use the global or relevant ARPU the argument implies) × 2 years. True: the result is within about 25% of $19B, and the $19B acquisition price is correct. Mostly true: the result is within about 50% of $19B, or the acquisition price detail is slightly off (for example the final $21.8B). Mixed: the result is roughly half or double $19B, depending reasonably on which ARPU or user base is chosen. Mostly false: under any reasonable inputs the figure is off by more than a factor of 2, though the method is sound. False: the calculation or the inputs are badly wrong (for example, the purchase price was not about $19B and the numbers are off by an order of magnitude).
Evidence
- The Social Conglomerate Stratechery (Ben Thompson) · 20 February 2014
“I think that's the first thing to understand about the $19 billion Facebook paid (including $3 billion in RSUs); WhatsApp as a standalone company, at least as presently constructed, with a miniscule staff and $1/user/year revenue model, was not worth anything close to $19 billion.”
- WhatsApp hits 2B user mark, hails encryption practice Mobile World Live · 13 February 2020
“It was acquired by Facebook for $19 billion in February 2014, when the app had nearly half a billion monthly active users.”
- Document (Facebook, Inc. Form 10-K for fiscal 2019) U.S. Securities and Exchange Commission (filed by Facebook, Inc.)
“Our annual worldwide ARPP in 2019, which represents the sum of quarterly ARPP during such period, was $25.57, an increase of 14% from 2018.”
- Will WhatsApp Be the Death of Venmo? How Facebook Plans to Monetize the Messaging Giant Observer · 24 January 2020
“Since plunking down $22 billion for the enormously popular messaging app in 2014, Facebook has grown WhatsApp’s user base almost four-fold, but has yet to monetize the tool or its 1.5 billion users worldwide.”
Reasoning
The $19B purchase price is supported by E1 and E2; E4 gives about $22B as the final figure. Using the inputs the criteria specify, WhatsApp had about 1.5 billion users (E4). Facebook's 2019 worldwide annual revenue per person was $25.57 (E3). Two years at that rate comes to roughly $77B, or about $100B with 2 billion users. That is about four to five times $19B, more than a factor of two off, even though the method of users × ARPU × years is sound.
Cite this claim
Balaji Srinivasan, “Roughly two years of monetizing WhatsApp at Facebook's ARPU would yield about $19B in revenue, the amount Facebook paid for WhatsApp.” (said 31 December 2019). Verdict: mostly false. Reliability API, claim c_1e6c7847b8e1, method 0.1.0+c876030c. https://epistacklabs.com/claims/c_1e6c7847b8e1
Claims without a verdict
- Unresolvable 148
- Not yet due 21
- Own records only 2
- Not researched 227
- Not checkable 1,091
Is a verdict here wrong, or do you speak for Balaji Srinivasan? Reply on the claim's own page, with the form at its foot (how replies work). Verdicts are made automatically; how verdicts and scores are made.