They spent the first hour asking about our nasi lemak station, not about charts. The brief later showed Friday GrabFood tickets stacking when the sambal batch was still reducing — we moved prep earlier and the late-order complaints eased within two weeks.
The menu signal session was blunt: three of our “signature” app combos barely moved except when we discounted them into thin margin. We kept one for brand reasons and parked two. I wish they had also flagged photo quality; we had to notice that ourselves.
Our KK and Shah Alam outlets looked similar on monthly sales, but the compare brief showed Shah Alam abandoning dessert add-ons after 8pm while KK kept them. We stopped pushing the same night promo calendar to both cities.
Extended story: rainy-season tickets in Kota Kinabalu
A waterfront café asked Sitegardenhub to read six weeks of Foodpanda and in-house web orders after staff insisted “the app is broken” every monsoon evening. The performance review found no technical outage pattern. Instead, average prep notes from riders clustered when the café accepted large mixed grill tickets during peak rain without adjusting the tablet’s prep-time estimate.
Together with the chef, we tested a rain-hour menu subset — fewer grill items, clearer modifier limits — for three weekends. Rider wait complaints dropped; total app sales dipped slightly on those hours but kitchen overtime fell enough that ownership kept the subset. The brief also noted that breakfast web orders were healthy and did not need the same treatment — a useful restraint, since the team had been ready to redesign the entire catalogue.
Read how an engagement is structured if you are considering similar work.