Pages

Friday, May 10, 2019

Uber CEO says he's building the next Amazon, even though growth is slowing

Uber CEO Dara Khosrowshahi plans for 2019 to be the company's peak year for losses, and that the company should be compared to Amazon's rise.

"That would be our intention, although there can't be any guarantee," Khosrowshahi said of Uber reaching peak losses this year in an interview with CNBC's Andrew Ross Sorkin on "Squawk Box" Friday ahead of Uber's market debut. Lyft executives said on their first earnings call Tuesday that 2019 would be their peak year for losses, leading several analysts to raise their price targets on the stock.

Like Lyft, Uber's path to profitability has been a key area of concern for analysts as the company prepares its IPO. Amid speculation of its ability to turn a profit, Uber's market cap has fallen from lofty expectations as high as $120 billion, according to early reports, to $75.46 billion on a non-diluted basis based on its IPO price of $45 per share.

In its IPO filing, Uber posted an adjusted EBITDA loss of $1.85 billion in 2018. But Uber executives have leveraged its losses as a way to compare the company to another infamously unprofitable company at its IPO: Amazon. While Uber's financials still look different from Amazon's at its IPO as a much bigger company already with slowing revenue growth, Khosrowshahi said in his CNBC interview that he stands behind the comparison.

"It's a fair comparison at the wrong time," he said. "So a lot of private companies now are holding off much longer before they go public. We are much bigger, much more mature as a company as we go public, and if you do look at the growth rates, our audience is growing 33% on a year on year basis, transactions are growing 36%. To be able to grow transactions 36% on a $50 billion base is pretty incredible, and we hope to keep it going."

Subscribe to CNBC on YouTube.

Watch: Why Uber is losing money and what it will take to become profitable

Let's block ads! (Why?)

from Top News & Analysis https://cnb.cx/2PYvnKR
via IFTTT

No comments:

Post a Comment