Guestwork Book a demo
Articles

Origin story

Why Quandoo closing helped shape Guestwork

Quandoo is shutting down globally after an unsustainable business model and an unsuccessful portfolio review by its parent company, Recruit Holdings. For Guestwork, this is not just industry news. Our operator experience includes restaurants that adopted marketplace booking early, then watched costs spiral as the relationship changed and better operational alternatives remained hard to find.

Guestwork growth centre shaped by operator-led hospitality experience

What restaurant owners need to know

The shutdown is being phased across Quandoo's active markets, including the UK, Australia, Italy, and Switzerland. Restaurants remain open as usual, but diners and merchants need to understand the key dates.

September 30, 2026 is the final day to discover restaurants, place new bookings, and redeem loyalty points. On October 1, 2026, consumer services end, and account functions and reservations are no longer accessible. By December 31, 2026, the app, website, and digital infrastructure are due to go permanently offline.

When Quandoo arrived, it solved a real problem

Independent restaurants needed help. Customers were moving online, phone bookings were not enough, and restaurants wanted to appear where diners were searching. For a restaurant operator, signing up made sense. If a platform could bring new guests, fill quiet tables, and make booking easier, it was hard to ignore.

That early adoption made sense. Online booking had clear value, and restaurants needed to keep up with guest behaviour. The problem was not technology. The problem was technology that did not stay aligned with restaurant control.

Then the costs started to feel different

Over time, the cost of using the platform became harder to accept. It was not only the headline price. It was the feeling that more and more of the restaurant's own customer base was being pulled through a paid channel.

Operators saw customers who already knew the restaurant start booking through the app. Those were not always new customers created by the platform. Many were people restaurants had earned through years of food, service, reputation, family visits, and local loyalty. When they booked through the app, that relationship became another charge against the restaurant.

Restaurants were caught because there was no better option

This is the difficult truth for many independent restaurants. You can be unhappy with the cost of a system and still feel trapped by it. If the booking flow is already running through that platform, leaving feels risky. Staff are used to it. Customers are used to it. The diary is there. The habits are there.

Things become comfortable, even when they are not healthy. That comfort can be expensive. Restaurants keep paying because the alternative feels uncertain, and hospitality is already full of uncertainty.

Why did it happen?

The business model had a problem on both sides. Low monthly subscription fees were not enough to carry the platform, while per-cover commissions became too expensive for many small restaurants to maintain. The unit economics failed to scale properly, and Recruit Holdings' portfolio review led to a wind-down rather than a rescue.

From the restaurant side, the deeper lesson is clear. A marketplace can start by promising new demand, then gradually become part of the restaurant's basic infrastructure. Once that happens, restaurants may pay not only for new guests, but for regulars and direct-demand customers they already had.

That is a fragile foundation. Restaurants operate on tight margins. If the cost of bookings keeps rising while the platform is also capturing existing demand, the value becomes harder to justify. Eventually, the industry starts asking whether the tool is helping restaurants or feeding from them.

Quandoo closing changed the urgency

Quandoo closing down could have been treated as another problem to manage. Find a replacement, move the diary, train the team, carry on. For Guestwork, it sharpened the need for a better operational alternative.

The team brings hospitality experience, floor pressure, technical delivery, and a clear belief that restaurant booking software should start from how service actually works.

Guestwork started from a real restaurant problem

Guestwork did not start from an abstract software idea. It started from seeing the same gaps appear during real service. A restaurant could take a reservation, but the software did not always make it easy to control tables, separate room areas, handle no-shows, keep useful guest records, or understand how pressure was building across the room.

That matters because restaurants do not run from a neat booking list alone. They run from judgement: which table is right, how long it is available, whether a guest should be moved, and whether the team can handle the next wave of arrivals.

Hospitality experience plus technical understanding

Guestwork sits between hospitality operations and software delivery. It is technical enough to become a serious booking product, but practical enough to care about the small details that affect real staff during a busy shift.

That combination matters. Independent restaurants need software that respects the way they already work: fast screens, clear table states, useful guest notes, simple booking edits, and confidence that the system was designed by a team that understands the pressure of a full dining room.

Guestwork came from that frustration

Guestwork is not being built to copy another booking app. It is being built because independent restaurants need software that starts from their reality: thin margins, busy service, table pressure, staff handovers, late changes, regular guests, and the need to keep control of the customer relationship.

The aim is not just to collect bookings. The aim is to help restaurants run the floor better, protect their margin, remember their guests, and avoid being caught again by systems that become expensive but hard to leave.

What trust looks like in the product

Trust is not only an origin story. It has to appear in the product. That is why Guestwork focuses on floorplan view, table availability, room tabs, staff day view, matrix view, booking edit flow, cancellation handling, and audit trails. These are the tools that help a team know what changed and what to do next.

A better option for a struggling industry

Hospitality does not need more tools that treat restaurants as a cash cow. It needs tools built by people who understand what a full dining room really costs, what a wasted table means, and how much pressure sits behind every service.

Quandoo closing reinforced the need to stop accepting the old model. Guestwork is the team's answer to that moment.

Moving on from Quandoo?

Book a Guestwork demo and see a booking system built from the restaurant side.

Book a demo