§ CASE 03 — LOGISTICS
Logistics workflow automation
From a daily standup chasing status updates to fully automated routing that runs unsupervised.
Client identities protected under NDA. Reference calls available as part of serious engagement conversations.
§ THE PROBLEM
The morning standup was 30 minutes of "where are we with X?"
Status updates across the Completed and Packed groups in Monday.com required manual daily review. Someone had to check each item, identify what changed, and Slack the right person to take action. The morning ops standup was 30 minutes of "where are we with X?" The team's days were structured around chasing status, not delivering.
Worse: a previous freelancer had built a Make.com router with 32 nested conditions that broke any time the workflow changed. Every workflow tweak meant a half-day of debugging branches nobody had documented.
§ THE BUILD
Switch-based routing, driven by a Monday.com mapping table.
We rewrote the entire routing system using Make.com's switch() module instead of nested conditions. Replaced the brittle 32-condition router with a single switch block driven by a folder-ID-to-person mapping table. Added timestamp-based filters so only recent status changes trigger routing.
Wired Slack notifications that go to the specific person responsible, not a general channel. The morning standup stopped happening because the information was already where it needed to be — in the right person's DMs, attached to the right item, before they opened their laptop.
§ OUTCOME
50–70 hrs/mo
Fifty to seventy hours a month of coordination work eliminated. The daily status chase stopped happening because it wasn't needed. The ops team got their mornings back — and got the latitude to focus on the actual fulfillment work that drives the business, not the meta-work of finding out who needed to do what.
§ THE SHIFT
The morning standup stopped happening.
Not because we cancelled it — but because nobody had questions. Routing decisions stopped landing in DMs and started landing in the right person's task list. The team's days stopped being structured around chasing status. The 32-condition router that nobody understood was replaced by something a new team member could maintain by editing a Monday.com board, not automation code.
§ TECHNICAL DETAIL
One switch() module, one mapping board, zero nested conditions.
The big architectural decision was moving routing logic out of Make.com and into Monday.com. The switch() module reads a folder-ID-to-person mapping table maintained in Monday.com — meaning the ops team can update routing rules by editing a board, not by editing automation code.
// Replaced 32-condition router with a single switch() module driven by a Monday.com mapping table. New team members can update routing logic by editing a board, not by editing automation code.
- Routing engineMake.com switch()
- Mapping tableMonday.com folder→person
- FiltersTimestamp-based
- NotificationsSlack DM (per assignee)
Want a system like this?
Every engagement starts with a 30-minute audit call. Tell us what's broken and we'll tell you whether we can help.