EAT PLAY LOVE: labour cost and revenue per bar, live during the festival
- Industry
- Festival: street food, wakeboarding, techno
- about 100
- Staff
- 5 and 2
- Bars and entrances
- 3 weeks
- Built in
- 205
- Automated tests
Starting point
EAT PLAY LOVE is a festival at a lake: street food, wakeboarding and techno. I had built the festival's website, ticketing and network before. Staff planning, shifts, time tracking and check-in ran on scattered Google Forms and spreadsheets. What a bar cost in staff and what it took in, the team only knew after the festival.
Solution
One app for about 100 staff, 5 bars and 2 entrances: shifts and time tracking, check-in for guests and vehicles. Every change is logged, and only admins see salary data. During the festival the app shows labour cost per person, day, bar and department live. It pulls revenue per bar automatically from the card terminals and shows it alongside. The question "is this bar worth it?" is answered the same evening. After the festival there is an Excel export, a staff rating and a list of who the team wants to invite again. The app is built for several years: the 2026 festival is stored as one event, and the next one starts clean.
Result
- Live instead of afterwards: labour cost and revenue per bar are available during the festival, not only after it.
- One app instead of scattered forms and spreadsheets, for about 100 staff, 5 bars and 2 entrances.
- In production at Festival 2026, built in three weeks from 29 May to 18 June 2026.
- Data migration checked against a copy of the production data, without a cent of difference.
There is no language model in it. It is process automation with live reporting, and exactly the data foundation a reporting agent needs.