Personal blog of Yzmir Ramirez

Sometimes, the best missions are the hardest to fund.

For the founders of RapidSOS, improving the quality of emergency response by adding useful data, like location, to 911 calls was an inspiring objective, and one that garnered widespread support. There was just one problem: How would they create a viable business?

The roughly 5,700 public safety answering points (PSAPs) in America weren’t great contenders. Cash-strapped and highly decentralized, 911 centers already spent their meager budgets on staffing and maintaining decades-old equipment, and they had few resources to improve their systems. Plus, appropriations bills in Congress to modernize centers have languished for more than a decade, a topic we’ll explore more in part four of this EC-1.

People obviously desire better emergency services — after all, they are the ones who will dial 911 and demand help someday. Yet, they never think about emergencies until they actually happen, as RapidSOS learned from the poor adoption of its Haven app we discussed in part one. People weren’t ready to pay a monthly subscription for these services in advance.

So, who would pay? Who was annoyed enough with America’s antiquated 911 system to be willing to shell out dollars to fix it?

Ultimately, the company iterated itself into essentially an API layer between the thousands of PSAPs on one side and developers of apps and consumer devices on the other. These developers wanted to include safety features in their products, but didn’t want to engineer hundreds of software integrations across thousands of disparate agencies. RapidSOS’ business model thus became offering free software to 911 call centers while charging tech companies to connect through its platform.

It was a tough road and a classic chicken-and-egg problem. Without call center integrations, tech companies wouldn’t use the API — it was essentially useless in that case. Call centers, for their part, didn’t want to use software that didn’t offer any immediate value, even if it was being given away for free.

This is the story of how RapidSOS just plowed ahead against those headwinds from 2017 onward, ultimately netting itself hundreds of millions in venture funding, thousands of call agency clients, dozens of revenue deals with the likes of Apple, Google and Uber, and partnerships with more software integrators than any startup has any right to secure. Smart product decisions, a carefully calibrated business model and tenacity would eventually lend the company the escape velocity to not just expand across America, but increasingly across the world as well.

In this second part of the EC-1, I’ll analyze RapidSOS’ current product offerings and business strategy, explore the company’s pivot from consumer app to embedded technology and take a look at its nascent but growing international expansion efforts. It offers key lessons on the importance of iterating, how to secure the right customer feedback and determining the best product strategy.

The 411 on a 911 API

It became clear from the earliest stages of RapidSOS’ journey that getting data into the 911 center would be its first key challenge. The entire 911 system — even today in most states — is built for voice and not data.

Karin Marquez, senior director of public safety at RapidSOS, who we met in the introduction, worked for decades at a PSAP near Denver, working her way up from call taker to a senior supervisor. “When I started, it was a one-man dispatch center. So, I was working alone, I was answering 911 calls, non-emergency calls, dispatching police, fire and EMS,” she said.

RapidSOS senior director of public safety Karin Marquez. Image Credits: RapidSOS

As a 911 call taker, her very first requirement for every call was figuring out where an emergency is taking place — even before characterizing what is happening. “Everything starts with location,” she said. “If I don’t know where you are, I can’t send you help. Everything else we can kind of start to build our house on. Every additional data [point] will help to give us a better understanding of what that emergency is, who may be involved, what kind of vehicle they’re involved in — but if I don’t have an address, I can’t send you help.”

The influence of a founder on their company’s culture cannot be overstated. Everything from their views on the product and business to how they think about people affects how their company’s employees will behave, and since behavior in turn informs culture, the consequences of a founder’s early decisions can be far-reaching.

So it’s not very surprising that Expensify has its own take on almost everything it does when you consider what its founder and CEO David Barrett learned early in his life: “Basically everyone is wrong about basically everything.” As we saw in part 1 of this EC-1, this led him to the revelation that it’s easier to figure things out for yourself than finding advice that applies to you. Eventually, these insights — and the adventurous P2P hacker attitude he nurtured alongside his colleagues and Travis Kalanick at Red Swoosh — would inform how he would go about shaping Expensify.

It’s striking how Expensify has managed to maintain this character 13 years later, even on the threshold of an IPO. How did this happen? During a series of interviews in February and early March, we found the answer is tied to the level of thought and effort this expense management business puts into its culture.

You see, the people at Expensify are prepared to invent their own playbook, develop it and, if needed, rewrite it completely. Its HR policies and strategy are tailored to find people who would have fun building an expense management product. It has a unique growth and recognition scheme to offset the drawbacks of a flat organizational structure. It’s even got a “Senate” that vets all major decisions. No kidding.

All this, and more, has ultimately helped Expensify reach more than 10 million users and achieve $100 million in annual revenue with just 130 employees. Let’s take a closer look at how Expensify makes it happen.

“We want the fewest people necessary to get the job done”

It’s clear Expensify’s unusually high employee-to-revenue ratio is intentional: “We want the fewest people necessary to get the job done,” Barrett says. But how do you actually achieve it? How do you hire and keep people who can deliver such results? Barrett had to learn how the hard way.

Expensify’s first team was based in San Francisco and comprised Barrett’s old Red Swoosh and Akamai colleagues, who joined a few months after Akamai fired him. A small team was enough to get started, but it was much more difficult to hire additional people. Barrett is eager to clarify the Valley is not really the best place to recruit talent: “Sure, Silicon Valley has a ton of really awesome people, but all of them have jobs!,” he says.