Budget: 20000 UAH Deadline: 30 days
I will build a fault-tolerant ecosystem on Airtable + Make with Atomic Updates logic, which eliminates the duplication of driver assignments and automatically decomposes complex routes into independent operational units.
How will we address the Race Condition issue in the "Accept/Decline" mechanism: what happens if two drivers simultaneously press the order acceptance button in WhatsApp due to a delay in the Make.com webhook, and how will Airtable block duplicate entries to prevent sending two cars for one trip? This is the "dirty secret" of such systems — without server-side verification of the "On Hold" status in milliseconds, your MVP will turn into a conflict generator among drivers.
Budget and deadlines will be discussed in private correspondence. 🤝