Skip to content

Case · Transform — n → ∞

Bálamo

Data, diner forecasting, staff rotas, profit per dish and a website for one of the largest seafood restaurants in Spain.

Bálamo’s vertical garden, a wall of plants climbing up the dining room, with the tables laid for service and nobody there. Below, the Bálamo logo.

Swimming in the same direction.

A bálamo is a shoal of fish that moves as if it were one. It’s also one of the largest seafood restaurants in Spain: in Alcorcón, with a vertical garden climbing the dining-room wall and crowds of diners any day of the week.

From the outside, everything flows. Inside, bookings lived in one system, sales in another, stock in a third, staff time records in a fourth and accounts in a fifth. Five systems, and none of them talking. And a team that played translator every morning.

Yesterday’s numbers

The first step was for management to know, before their first coffee, how the previous day had gone. Sales and diners by area, against the same weekday last year. An arrow up or an arrow down, and on to the next thing.

Underneath, there’s a data layer that brings together what used to live apart. You can’t see it, which is exactly how it should be. Everything else rests on it.

Bálamo’s data layer: five systems and everything that rests on themOn the left, the five systems that used to not talk to each other, each named by what it does: bookings; till and orders; stock and purchasing; staff and time records; and accounts. In the centre, the data layer that brings together what used to live apart, and that you can’t see. On the right, what rests on it: yesterday’s numbers, with sales and diners against last year, for management before their first coffee; the diner forecast by service and area; the rota, made by whoever knows the floor; what each dish brings in, cross-referencing sales, costs and recipe costings; audit-ready time-keeping reports, with scheduled hours against hours worked; and the website, overhauled from top to bottom and with analytics.Five systemsBookingsdiners and tablesTill and orderswhat gets soldStock and purchasingcosts and recipe costingsStaff and time recordsshifts and hoursAccountsbooks and financeData layerbrings together what used to live apartEverything else rests on itYesterday’s numbersyesterday’s sales and dinersbefore the first coffeeThe forecastdiners per service and areaSaturdays · holidays · pandemicThe rotamade by whoever knows the floordashboard · templateEach dishwhat each one brings insales · costs · costingsThe auditscheduled hours against hours workedtime-keeping reportsThe websiteoverhauled from top to bottomanalytics where there was nothing

Hover over a part, or tab to it, to see what it does.

How many it takes

A Saturday in spring is nothing like a Tuesday in November. Nor is a public holiday. And the pandemic data is like nothing else at all.

We built a diner forecast that takes all of that into account and, from it, how many staff are needed for each service and each area. A forecast isn’t always right. But it gets it wrong less often than gut feeling at seven on a Friday.

Whoever knows the floor makes the rota

We started with the ambitious option: a tool that would draw up the rotas on its own. It worked. It produced flawless rotas for a restaurant that doesn’t exist.

The real one has holidays that don’t fit in any box, contracts of every shape and size, and shift swaps for reasons no algorithm understands. So we changed our minds: whoever knows the floor makes the rota, and we prepare the ground for them.

A dashboard that fills itself in with what used to be looked up by hand, and a template that uploads the rota straight into the HR system. No copying, no pasting and no lost afternoons.

From diners to rota: the tool prepares, whoever knows the floor decidesWe prepare the ground for them: the history from previous years, with public holidays and the pandemic set apart, gives a diner forecast per service; the forecast gives how many staff are needed for each service and each area; and all of that feeds a dashboard that fills itself in with what used to be looked up by hand. From the dashboard it goes to whoever knows the floor, who makes the rota taking holidays, contracts and shift swaps into account. A template uploads that rota straight into the HR system, with no copying or pasting. Off to one side, dashed, the first attempt: a tool that drew up the rotas on its own, flawless ones, for a restaurant that doesn’t exist.We prepare the ground for themThe historysame day, previous yearsholidays · pandemic apartThe forecastdiners per servicelunch · dinnerHow many stafffor each service and areafloor · kitchenThe rota builderdrew up rotas on its owna restaurant that isn’t realThe dashboardfills itself inwhat used to be by handThe templateuploads the rotano copying or pastingHR systemthe rota, already inno lost afternoonsWhoever knows the floorholidays · contracts · shifts

Hover over a step, or tab to it, to see what it does.

What each dish brings in

We cross-referenced sales, costs and recipe costings to see what really keeps the business going and what does less than it seems. Some of the surprises had been on the menu for years.

The anchors stay where they are. Everything else, with data.

The pricing proposal began with the hard question: what not to touch. The usual water, the children’s menus, the old-favourite desserts. The anchors stay where they are. Everything else, with data.

What you don’t see

Audit-ready time-keeping reports, with scheduled hours against hours worked. Analytics where there used to be nothing, and a website overhauled from top to bottom so that anyone looking for seafood south of Madrid can find it.

Copilots, not replacements. At Bálamo, we learnt that from a rota.

Technology doesn’t know the waiters, and it doesn’t serve tables. It serves the people who do, so they start each service with the heavy lifting already done. Like a good shoal of fish: nobody collides, and everyone heads the same way.

Bálamo’s website · balamorestaurante.es (opens in a new tab)

Other cases

  • CERMI

    Digital assessment, cybersecurity, Dynamics 365, data and training for the common home of organisations of people with disabilities.

    Transform · n → ∞