Waze

In June 2013, Waze was acquired by Google for $1.15B. In those days, billions were large numbers; Aileen Lee would coin the term “unicorn” a few months later. It's important to stress that a unicorn was initially defined as a company with an exit value of over a billion dollars — raising money at a $1B valuation does not really make a company a unicorn.

In 2006, Israeli programmer Ehud Shabtai founded a community project known as FreeMap Israel, which aimed to create (with the crowd-sourcing assistance of community users) a free digital mapping database of Israel🇮🇱 compiled in the Hebrew language with ensured free content, updates, and distribution. In 2008, Shabtai formed a company called Waze to commercialize the initial project; in 2009, it was renamed to Waze Mobile Ltd.

What started with a few hundred drivers mapping 5,000 kilometers in Israel soon expanded. By 2008, there were 2,500 drivers and a new name: Linqmap. By 2009, that number had grown to 17,000, and the app had yet another new name. Only this time, it stuck.

Waze made its brand debut in January 2009. The app launched in the United States in May of that year and worldwide that November. Early users didn’t see much when they downloaded the app. In many places, the map hadn’t been drawn yet. But enough people saw the potential in the blank canvas, like Susana, a Map Editor in Spain.

For bigger changes, Map Editors rallied around the idea of “MapRaids,” internationally coordinated efforts to adjust specific areas of the map. They’ve edited as many as 2.5 million segments in one Map Raid.

Initially, only people with mobile connectivity on the road could see hazards in real time. Not that it stopped people like Ron Vaisman. He used a clever offline workaround. “Before I went for a drive, I would sync the latest maps from my computer so I had a ‘real-time’ report,” he says. “It’s funny to look back on that now.”

In 2011, though, real-time alerts hit the spotlight with a little event known as Carmageddon.

Facing the prospect of the 405 freeway being shut down for construction, Waze partnered with L.A.’s KABC News to share live updates from Wazers on the road and help drivers find alternate routes. Today, Wazers in more than 185 countries worldwide report 40 million incidents every month to keep each other in the know.

Using Waze for emergency response

If Carmageddon showed what Wazers can do against traffic, 2012 proved they can help in other powerful ways.

During Hurricane Sandy, the Waze Community helped FEMA address gas shortages in New York and New Jersey by reporting which gas stations were open and had fuel available. While certainly useful for people in the area, it also helped FEMA understand where to dispatch fuel trucks. The effort marked Waze’s first government partnership and was an early indicator that Wazers are always ready to help.

Over time, Wazers have become more integral to the way cities run, from their very infrastructure to how quickly they respond to traffic emergencies.

With Waze for Cities, local governments and transportation agencies can use more crowdsourced data in their planning. It’s grown from 10 to 1,800 city and public sector partners.

And in Europe, North, and South America, the Community helped launch Waze Beacons, devices placed in tunnels that send out Bluetooth®️ signals and prevent drivers from losing their GPS signal underground.

“Beacons are important because a lot of times people slow down toward the end of the tunnel to see which way they’re going to go — right or left,” explains Orbit. “That slow down actually creates either traffic or accidents or other issues. So the Beacons are a life-saver for that reason.”

Former Waze CEO and VP at Google, Noam Bardin has said the following on the lead up to the Waze acquisition by Google

Before any discussion of acquisition, we believed Waze needed a strategic partner to help accelerate user acquisition — we felt we had maxed out our organic ability to grow. We entered strategic partnership discussions with Microsoft (who was an investor in the company), Amazon and Facebook (who were building phones), and others.

Facebook was the natural fit from the product perspective — they feared dependency on the mobile platforms and wanted to own their location stack, both for their upcoming phone and their apps. We spent a lot of time together mapping out potential integration, but Facebook kept running up against the problem of “What if we help you, you become a huge platform, and then Google comes along and acquires you? We would not be able to compete with them financially.” This was on the heels of the Spotify US launch where Facebook believed they had “built Spotify's business” but did not extract any value from it.

Our strategic partnership negotiations with Facebook were at an impasse -- they wanted a Right Of First Refusal (ROFR) allowing them to match any offer someone else made, which we could not give. A ROFR would hurt our ability to negotiate a future transaction since any potential buyers would know their competitor had the right to take the deal from under their feet. We finally agreed to a compromise in which Facebook would get a ROFR only for Google. That smoothed the way forward.

Before moving too far down this path, I reached out to Google and told them, “We are about to sign an agreement with a competitor of yours that would preclude us from doing anything strategic with you. Before we sign it, I want to make sure we don't miss each other in the night. If you are interested, we should talk now.” I did this out of my fiduciary duty — never in my wildest dreams did I guess that Google would be interested. To my surprise, they wanted to meet.

So we did meet with the Google Maps team and had a fascinating talk. Since all of us were experts in the maps space, we could both appreciate what the other had done and how they did it. After the meeting, to my surprise, the Corp Dev lead called me up and said they would be interested in exploring an acquisition. We discussed price, and I made it clear that we are looking for $1B (after Instagram had recently been acquired for $1B, it seemed appropriate). I got the wrong impression that it was doable.

We went through a quick round of basic due diligence, including flying the leadership team to Mountain View and meeting Larry and Sergei. Finally, I got the call and my Corp Dev contact started by saying, “Before I send you the offer, I want to explain it, since you’ll just look at the price.” He then explained the terms and sent the offer: $450M. I was shocked — I was 100% sure we were at the $1B mark. I immediately said “No” — our valuation framework had anchored our expectations much higher. $450M would have been a great exit, and without a predetermined framework, I could have negotiated a bit and settled somewhere, but the framework gave me the confidence to just say ‘no.’ The shocked counterpart asked, “Is there no number between $450M and $1B that we could agree on?”

That question took me back to a negotiation course I took at Harvard Law School. After five days of theory, lectures, and simulating negotiations, what got burned in my memory was when, in our last hour of the course, the professor said, “But don't forget that despite everything we taught you, negotiations usually end by splitting the difference in the middle…” I knew we were worth $1B–it was not a negotiation tactic, and I had explained that. If I would have started negotiating at $450M, there was no way we would get near $1B, so I walked away.

I did go back to Facebook and told them that we got an acquisition offer from “a major tech company you would consider a major competitor.” Facebook already knew us intimately from the business negotiations, and their head of Corp Dev called me up and plainly said, “What is a number you would not shop around?” I said “$1B” and an hour later I had a term sheet for $1B in my inbox, valid for a few hours. I did not need those hours and immediately signed the term sheet and sent it back, did not shop it around. With two emails and a phone call, Facebook had basically acquired us. To this day I have respect for the speed and directness of their offer. Having our framework allowed me to sign the offer without consulting anyone, as I knew the founders were on board and, of course, the board would be ecstatic, so I moved from villain to hero (a route I seem to take back and forth often).

We began due diligence and it quickly became clear that we had some gaps. We assumed the deal was done and the due diligence was to validate everything we had discussed. Facebook, on the other hand, looked at it as the beginning of a process to determine what they should do with Waze. This gap created more and more tension between the teams –- it was not clear which team was acquiring us or who was calling the shots, and time kept slipping by. We had days where we did not know what the next step was and sat around waiting…

On top of that, we did not have good chemistry with the people we interacted with. Mark and I did not hit it off well, and the engineers doing the due diligence were very young and were confidently belittling what we had built. Our average engineer was 40 years old, top of the Israeli 8200 unit, and very experienced. They did not think what we had built was easy at all (nor had the Google engineers who were our age and experience); neither were they impressed with these young engineers sent to evaluate our system, using lots of buzzwords to say little. This age and mentality gap seeped in, and since there was no clear owner to the process, things began grinding down. We began feeling we had made a mistake and that Facebook was not going to go through with the acquisition.

Facebook had demanded 28 days for closing, a long time that they felt they needed to figure out what to do with us. I made a mistake by agreeing to it. This was (and still is) one of the biggest acquisition deals in Israel, especially for a consumer brand. With accountants, lawyers, board members, and investors involved, the news was bound to leak, and it did. Though I did not leak the information, and to this day I still do not know who did, I think Facebook and Google still believe I leaked the news. As more information kept leaking, we reduced the number of people in the know and stopped updating our board with the details.

Once news of the deal leaked, I got a call from the CorpDev person at Google, and he asked me if the news articles were correct. I replied that I could not discuss the articles or anything with him (as I was under the standstill limitation of the term sheet I signed), and he said he understood and hung up. An hour later I got an unsolicited term sheet in my inbox, from Google, for $1.15B. This put me in a bind –- I had signed a term sheet with Facebook, BUT I had a fiduciary duty to my investors to maximize the sale value: I could not ignore this offer. I disclosed it to Facebook, who blew up and accused me of leaking the news. The poor personal dynamics caused them to disengage, running down the clock on the term sheet. If we had a clear owner on the Facebook side and had developed a good rapport, we could have, together, overcome this but the lack of trust between the teams made it impossible.

As the clock ran out, Facebook did not make a counteroffer. I quickly pinged Microsoft, Amazon, and Apple, but no one could move fast enough. We signed a term sheet with Google as soon as the Facebook term expired and closed the transaction in eight intensive days.

Do I think going to Google was the right thing for Waze? At the time, the Facebook deal was a stock deal and their share price was ~$25/share. Had we closed with them, the deal could have had a 10X multiplier. Despite that, I feel that Google was the right place for us. We clicked with the engineering team, they let us stay independent and grow (from 10M MAU to 150M MAU), and knowing the damage that Facebook has done to democracies globally, I would never have lasted my four years there.

So what are the lessons I learned?

🟢Acquisitions start years before the actual sale. Get to know your potential acquirers and spend time with their product teams so that if you need to contact them, you know who to call and they know who you are.

🟢Have a clear framework among your decision-makers for what you want with real numbers –- this is a superpower for fast decision-making.

🟢Partnership discussions are the best catalyst for an acquisition. They allow the teams to spend time together, get to know each other, and imagine what a joint product could look like. Especially if the conclusion is, “But we would need to own you to do this.”

🟢Everything around acquisitions is personal –- from the reason why companies acquire, to the price and the process. Make sure to clarify who the decision-makers are and spend the time building personal relationships.

🟢Acquisitions are the first moment when founders and investors have diverging interests. This is the one time when you should be wary of feedback from your investors.

🟢And, of course, like any negotiation, whoever is willing to walk away will get the better deal -- always have a red line and hold firm to it.

So that is the real story of how Facebook almost acquired Waze, but we ended up with Google according to the former CEO of Waze.