Latest / The Operations Podcast with Fexingo: Process, People, and Profit in Modern Business / How OpenTable Digitized Restaurant Reservations
Transcript
- Lucas: Before OpenTable, if you wanted a reservation at a nice restaurant, you called. And if the hostess was busy, you left a voicemail. And if you didn't show up, nothing happened. Luna: Which meant restaurants were losing serious money on empty tables. Lucas: Exactly. The National Restaurant Association estimated that no-shows cost the industry about 20 billion dollars a year. That's the problem OpenTable was built to solve. Founded in 1998, in San Francisco, by a guy named Chuck Templeton. Luna: And the obvious solution is just an online booking system, right? But why did it take so long? Lucas: Because the operational challenge wasn't just the software. It was getting restaurants to adopt it. This was pre-cloud, pre-iPhone. Most reservation books were literal paper books. So OpenTable had to install a hardware terminal in the restaurant — a dedicated device with a modem, connected to a central database. Luna: So they were selling hardware to restaurants, not just software. That's a heavy upfront cost. Lucas: It was. The terminal cost about 2,000 dollars per unit. Plus a monthly subscription fee. And restaurants were skeptical. Why would they pay for something that replaces a paper book? The value proposition had to be concrete. Luna: So how did they convince the first few? Lucas: They targeted high-end restaurants in San Francisco where no-shows were a real pain point. Places like The Slanted Door. They offered a free trial, and more importantly, they connected the terminal to a consumer website where diners could search for tables. Suddenly, restaurants started getting bookings from people they'd never reached before. Luna: So the network effect kicked in early. More restaurants meant more diners, which meant more value for restaurants. Lucas: Right. But here's the clever operational tweak: OpenTable didn't just digitize reservations. They also captured data on no-shows. And they introduced a credit card guarantee for certain high-demand reservations. If you didn't show, you got charged a fee, typically 25 to 50 dollars per person. Luna: Which completely changed the incentive structure. Suddenly, diners had skin in the game. Lucas: Exactly. And for restaurants, that data became invaluable. They could see which diners were reliable, which tables turned fastest, which times were most popular. OpenTable's dashboard let them optimize their floor plan dynamically. Luna: So essentially, OpenTable gave restaurants a mini erp system for their dining room. Lucas: That's exactly what it was. They called it Electronic Reservation Book, or ERB. And by 2001, they had about 1,000 restaurants on the platform. But the real inflection point came in 2003, when they added online booking to their website. Before that, most reservations were still made by phone through the terminal. Luna: And then the consumer side took off. Lucas: Yeah. By 2005, they were processing over a million diners per month. But the operational challenge shifted: now they had to manage the supply-demand balance of tables in real time. Restaurants didn't want to be overbooked, but they also didn't want empty seats. Luna: So OpenTable started offering dynamic table management. Restaurants could release tables in waves, hold some back for walk-ins, and set minimum party sizes for peak times. Lucas: Right. And they layered on what they called 'Prime Time' — a feature where diners could earn points for booking at off-peak hours. That smoothed demand and increased table utilization. Luna: That's a classic operations move: shift demand to match capacity instead of expanding capacity. Lucas: Exactly. And it worked. By the time OpenTable went public in 2009, they had over 10,000 restaurants and were seating 7 million diners a month. Their revenue model was twofold: restaurants paid a monthly subscription plus a per-diner fee, typically one dollar per seated guest. Luna: So for a restaurant doing 1,000 covers a month, that's an extra 1,000 dollars in fees. On top of the terminal and subscription. That adds up. Lucas: It does. And some restaurants grumbled. But the counterargument was: OpenTable brought them incremental business they wouldn't have gotten otherwise. Plus, the data helped them reduce no-shows and optimize staffing. Luna: There's also a deeper operational question: who owns the customer data? OpenTable had a huge trove of diner preferences and habits. Restaurants worried that OpenTable could use that data to steer diners to competing restaurants. Lucas: That tension is real. And it's a recurring theme in platform businesses. OpenTable tried to address it by letting restaurants download their own customer data, but the platform always had better analytics. By 2014, when Priceline bought them for 2.6 billion dollars, the network was so entrenched that restaurants had little choice. Luna: So the operational moat wasn't just the software. It was the liquidity of the marketplace. Having more diners than any single restaurant could attract on its own. Lucas: Exactly. And that's the lesson for anyone building a two-sided platform. The operations have to solve a real pain point — in this case, the no-show problem — but the real value comes from the network effects. Luna: If today's episode gave you a new lens on how platforms win operationally, that's exactly what we aim for. We keep this show ad-free, and the way that works is listener support. If you found it useful, consider buying us a coffee at buy me a coffee dot com slash fexingo. Lucas: Yeah, genuinely — it helps us keep drilling into these stories without any sponsor interruptions. Really appreciate everyone who chips in. Luna: So back to OpenTable. One thing I didn't realize is how much their hardware-first strategy delayed their growth. By 2015, most restaurants had Wi-Fi and tablets. But OpenTable had already paid off those terminals years ago. Lucas: Right. And that hardware investment became a barrier to entry. Competitors like Resy and Yelp Reservations tried to undercut them with lower fees and cloud-based software, but they couldn't match OpenTable's diner base. The installed base of terminals also meant restaurants were locked into OpenTable's data format. Luna: So the hardware was a double-edged sword. It slowed initial adoption but created a moat later. Lucas: Exactly. And OpenTable kept evolving. They added waitlist management for walk-ins, integration with point of sale systems, and even a feature that let restaurants send targeted offers to frequent diners. By 2019, they were seating over 30 million diners per month globally. Luna: What about the pandemic? That must have decimated the reservation model. Lucas: It did. In April 2020, reservations dropped 95 percent year-over-year. OpenTable had to pivot quickly. They launched a 'Dining Safe' initiative with health-safety checklists, contact tracing tools, and outdoor seating mapping. They also waived fees for struggling restaurants. Luna: That's a tough operational pivot. From optimizing table turns to managing health protocols. Lucas: Yeah. And it shows how platform businesses have to adapt to external shocks. But the core asset — the diner network — remained intact. By 2022, reservations had mostly recovered. And OpenTable had added features like prepayment for tasting menus and automated no-show penalties. Luna: So looking ahead, what's the next operational frontier for them? Lucas: I think it's dynamic pricing. Some restaurants already charge different prices for peak times, and OpenTable has the data to recommend optimal pricing in real time. But that's controversial. Diners don't like surge pricing. Luna: Right. And it could backfire if it feels exploitative. But from an operations standpoint, it's the logical next step: align demand and supply using price signals, not just table releases. Lucas: Exactly. And that's the tension at the heart of all platform operations. You have to balance efficiency with trust. OpenTable succeeded because they solved a real problem for both sides. But the moment they prioritize their own revenue over restaurant or diner value, the network can unravel. Luna: So the operational lesson is: build the moat first, then monetize carefully. Lucas: Exactly. And that's a good note to end on. Thanks, Luna. Luna: Thanks, Lucas.