The group changed its service platform
The restaurant group wanted a more intuitive system and better support than it was receiving from its previous POS arrangement. Its hospitality marketing director, Christopher Staples, described approximately six months of research before selecting Toast. The change extended across concepts with different menus and operating requirements.
That variety gave the project a specific challenge. Standardizing software across a restaurant group does not make the restaurants identical. A common platform has value when it reduces repeated administration while retaining the distinctions that shape each kitchen’s work. Red Salt’s two-station arrangement made those distinctions visible at the point where an order became food preparation.
The displays made the shift visible to kitchen staff
At the group’s higher-end restaurants, multiple kitchen displays showed the state and history of work to cooks and other preparation staff. Staples described visibility that the previous printed tickets had not provided. The system connected front-of-house order entry with the people preparing and releasing the order.
The technical importance is the shared state of the work. A paper ticket communicates instructions at the moment it is printed. A display can also represent the order’s place in an active queue and retain a history of what has happened to it. That changes the information available when several stations contribute to one table. Staff can reason about the broader shift rather than only the ticket immediately in front of them.
This does not establish that the software automatically synchronized every dish or eliminated human coordination. The documented change was improved visibility and a more fluid path from entry to preparation. The case is stronger when that concrete mechanism remains separate from claims the project did not measure.
Menu administration moved beyond a single restaurant
Staples also managed Boulevard & Brew and Wong Gonzalez. With Toast, he could change menus remotely and review reporting across the restaurants. He described preparing an event menu in about five minutes, compared with a previous process requiring a visit to the location.
That is a different form of improvement from kitchen speed. Central access removed a location dependency from an administrative task. It also gave the group a common place to evaluate its different concepts. The restaurants could retain their own menus while the manager used a shared toolset to maintain them. The event-menu example illustrates the change in workflow without establishing that every menu task took five minutes.
The reported outcome was a more coherent service flow
The group reported quicker drinks and accurate meals reaching guests sooner, along with improved table turns. No numerical before-and-after table-turn result was published. The evidence therefore supports an operational improvement reported by the restaurant team, not a precise percentage increase in dining capacity.
Cartennas’s assessment is that this case links three changes that are often discussed separately: easier order entry, kitchen visibility and centralized menu administration. Each addresses a different point where information can slow down or become difficult to interpret. Together, they explain why the new system affected the service experience. The hardware mattered because it put the relevant information where the work happened, within a platform the group could also manage across locations.