Reviews

Not a wall of five-star paste.

These notes refer to actual modules on this site. One of them includes a reservation on purpose. If a review cannot name a clock or a map, we do not publish it.

“After Ticket Anatomy I stopped sending a single ETA to the founder group. Our Friday 19:40 page now splits kitchen and corridor. I still think the homework load in week 3 is heavier than the brochure implies.”

Ploy R., head of ops, Bangkok marketplace

Chiang Mai

Took Night Market Demand. The vendor close-time join explained our Sunday collapse better than any promo dashboard. Rain bands were useful; festival calendar still needs local editing.

Bee

Platform rating · 4 / 5

Partner Margin Ledgers. Clear on contribution after rider incentive. Dry tone. Would not call it entertaining. Would call it usable in a CFO meeting.

Verified learner

Client in dark-kitchen networks: Repeat Order Cohorts showed our second-order spike was voucher-driven and died on day nine. We cut one SKU promo instead of raising the whole catalogue.

Rider SLA & Fatigue made idle minutes visible by block. Our Phuket hotel loop looked “efficient” until consecutive long trips showed up. The heat-exposure proxy is rough — they admit that in class.

Anand, rider logistics lead

“Nalinee’s porte-cochère example in Heatmap Studio was the first time a map embarrassed me in a useful way.”

Fon T., city manager

Case study · Sukhumvit kitchen blamed, corridor guilty

Courier waiting with a delivery backpack

A multi-brand kitchen on Sukhumvit was on a “performance plan” because average delivery time sat above the marketplace SLA. Logicpacketgrid’s Kitchen Cycle Diagnostics track, taken by their ops lead, split ticket-to-bag from bag-to-door.

Prep sat under nine minutes on 81% of dinner tickets. The delay clustered at a two-block pickup where riders waited behind a hotel drop-off. The team moved the handover pin and stopped threatening the kitchen with delisting.

Limitation they kept on the slide: the POS still cannot export item-level fire times for one of four brands, so that brand’s prep clock remains estimated.

Case study · Yaowarat late window

A marketplace demand lead finished Night Market Demand and rebuilt the 21:30–23:00 forecast using vendor close-times instead of amphoe averages. The “mysterious” 22:10 drop aligned with three high-volume stalls packing down, not with rider shortage.

They stopped inflating rider incentives for that window and negotiated later close with two stalls. Refund complaints on cold noodles fell the following month. They noted in their debrief that tourist-bus nights still break the model — a reservation we agree with.

Restaurant interior with set tables