Your Guest Data Belongs to You
In January 2026, DoorDash acquired SevenRooms for $1.2 billion. A delivery company buying a reservation and guest management platform. Let that sit for a moment.
A month later, OpenTable launched an ad network built on diner reservation data. And they've been pushing what Restaurant Business calls a "system of record" mandate, positioning themselves as the central platform restaurants should run everything through.
These aren't unrelated events. The reservation wars are about one thing: controlling the relationship between restaurants and their diners. And restaurants are caught in the middle.
What's actually happening with your data
Here's what the major platforms do, in practice, with the guest data your restaurant generates:
They market to your guests. After someone dines at your restaurant, the platform may send them emails promoting other restaurants. Including direct competitors in your neighborhood. Your guest. Your data. Their marketing.
They build profiles they own. The platform aggregates data from every restaurant a guest visits, building a diner profile that belongs to the platform, not to you. You contributed the data. You don't control it.
They monetize the data. OpenTable's new ad network is the clearest example yet. Restaurants pay per-cover fees, generate data, and then that data becomes the foundation for an advertising business. I wrote about this in the context of per-cover fees. The pricing model and the data model are two sides of the same strategy.
They make switching expensive. When years of guest history, preferences, and contact information live inside a walled garden, leaving means losing access to all of it. That's not a bug. That's a retention strategy.
None of this is hidden. It's in the terms of service. But nobody reads terms of service, and it's rarely explained clearly upfront.
Why this matters for your restaurant
Guest data is a business asset. Maybe your most valuable one.
When you actually own it, you can personalize the experience. Your host knows a regular's name, preferred table, wine preference, and that they're celebrating an anniversary next Tuesday. That information lives in your guest profiles, if you control them.
You can market directly. Invite your top 50 guests to a wine dinner. Send a holiday greeting to regulars. Announce a seasonal menu. You need a guest list that belongs to you, not one locked inside a platform that's simultaneously showing your guests other options.
You can build loyalty on your terms. Guest relationships are strongest when they're direct. Not mediated by a platform whose business model depends on those guests also booking at other restaurants through them.
And you can make informed decisions. Who are your best customers? How often do they visit? What do they spend? That intelligence should inform your decisions, not sit in a dashboard you can't fully access or export.
bavoli's approach
We built bavoli around the principle that guest data belongs to the restaurant. Our guest CRM is designed around this. In practice, that means:
We don't market to your guests. When someone books through bavoli, we don't email them about other restaurants or use their information for anything other than serving your restaurant.
You can export everything, at any time. Names, contact info, visit history, notes, tags, preferences, no-show records. Standard format. Take it anywhere.
No lock-in. If you leave bavoli, your data leaves with you. We don't make the export difficult or charge for it.
We're a new company. I won't pretend we have a decade-long track record on this. But the architecture is built around it, the policy is published, and it's a commitment I take seriously.
The question to ask any platform
If you leave this platform in two years, what happens to your guest data?
If the answer is complicated, conditional, or unclear, that tells you everything about who really owns the relationship with your guests.
