MotorFlow Parts Case Study

The Challenge

MotorFlow Parts had been using the same territory division system for a decade. When the company was smaller, Darnell Washington and the operations team drew boundaries on a map, carved the Detroit metro into zones based on geography and driver seniority, and assigned territories accordingly. Each driver owned their zone. Customers in that zone called that driver. The system was simple and worked fine for a business managing 80-100 deliveries per day.

Then the business grew. Revenue doubled. The territory system didn’t scale.

The problem became visible in the numbers. Average delivery time had degraded to 3.2 hours from initial pickup to final delivery. Some drivers were handling 35+ stops per day and finishing by mid-afternoon. Others were juggling 10-15 stops and still running until evening. The workload variance across the fleet had grown to 300%—some drivers had three times more work than others, yet the 18-driver fleet was structured as if everyone had the same load.

The consequences showed up in customer relationships. Body shops and repair garages that needed critical parts couldn’t get them fast enough. When a shop had a customer’s car waiting on a hydraulic pump or alternator, a 3.2-hour delivery window was unacceptable. They started checking Amazon. And Amazon could deliver in 2 hours. MotorFlow lost three accounts worth $15,000 monthly to commodity purchases on Amazon. They weren’t choosing Amazon for quality or pricing. They were choosing it because MotorFlow couldn’t guarantee speed.

The specific problems were compounding:

• Decade-old territory zones created severe workload imbalance: The original map reflected seniority, not optimization. Senior drivers got the dense downtown zones with high-value accounts. Newer drivers inherited the sprawling suburban territories with more miles, fewer stops, and less revenue per route.
• Average delivery time of 3.2 hours: Customers who needed parts urgently couldn’t use MotorFlow for rush deliveries. The company lacked the operational agility to prioritize emergency orders.
• No rush order prioritization system: Every order was treated equally. A routine restock order got the same priority as a critical same-day part needed to get a car off the rack. The operation had no mechanism to identify and accelerate rush requests.
• Three major accounts defecting to Amazon: Commodity parts purchasing migrated to Amazon, representing $15,000 monthly in lost recurring revenue. The account managers were frustrated because it wasn’t a quality or pricing issue—it was pure logistics speed.
• 75 status inquiry calls daily: Without real-time visibility, body shops called constantly asking “Where’s my part?” The customer service team spent more time answering position questions than handling new orders.
• Poor driver retention: Drivers assigned to sprawling suburban territories resented the longer hours and lower pay compared to downtown counterparts. Turnover was running higher than industry standard.

The Solution

Darnell knew the territory system was the problem, but redrawing zones by hand wasn’t feasible. The manual approach that had worked a decade ago was too slow and prone to recreating the same biases. He needed a system that could restructure the territories mathematically, optimizing for actual workload balance and speed rather than historical boundaries.

Upper’s route optimization engine was built for exactly this problem. Instead of political boundaries, Upper would treat territory optimization as a pure mathematical challenge: balance workload across 18 drivers based on stop density, drive time, and geography.

Complete Territory Restructuring Using Optimization

The implementation started with data. Darnell exported the customer list with addresses, daily order frequency, and revenue per account. He loaded it into Upper along with the driver information and asked the system to build optimal territories. Upper ignored the decade-old map and built new territories from scratch based on geographic proximity and workload balance.

The new territories looked nothing like the old ones. Customers that had been assigned to the same driver for ten years were shifted to new drivers if it improved overall fleet efficiency. Dense downtown zones were redrawn to include some of the high-density suburban areas that had been fragmenting routes. The computer optimized what human intuition could never achieve: perfect balance.

The result was a 44% reduction in average delivery time—from 3.2 hours to under 1.8 hours. More importantly, the system now had capacity to handle rush orders in under 90 minutes.

Rush Order Prioritization With Three Urgency Tiers

Darnell established three urgency tiers within the Upper platform. Standard orders were scheduled normally. Priority orders were flagged for same-day delivery but could be batched with other stops. Critical orders were treated as immediate dispatches with the nearest available driver sent directly to the customer location, bypassing the normal queue.

The distinction mattered to customers. A body shop calling with a critical part need knew they could get delivery in under 90 minutes. That promise was now achievable and guaranteed. MotorFlow regained competitive parity with Amazon on speed, but with the advantage of a real relationship and flexible terms that online retailers couldn’t match.

Real-Time Visibility and Automated Notifications

The old system left customers guessing about delivery status. With Upper’s customer notification system and live fleet tracking, shops received automated SMS updates: “Your order is en route with driver Marcus. Estimated arrival in 12 minutes.” The specificity eliminated the uncertainty that had driven status call volume.

Status inquiry calls dropped 75%. The customer service team that had been fielding “Where’s my order?” questions all day could now focus on selling and customer retention. Customers appreciated the proactive notifications more than they appreciated having to call and wait on hold.

Proof of Delivery and Driver Accountability

Each delivery was documented with a timestamped photo and driver signature using Upper’s proof of delivery feature. The documentation created an accountability record that protected both MotorFlow and customers. Disputes over whether a part was delivered on time were resolved with evidence rather than he-said-she-said conversations.

The Impact

MotorFlow’s transformation was felt immediately by drivers and customers alike. The workload variance that had been creating resentment and turnover dropped from 300% to under 15%. Drivers who had been working 10+ hour days on sprawling suburban routes suddenly had predictable 8-hour days with reasonable mileage. Drivers who had been coasting on dense downtown routes now carried more volume but with optimized sequencing that kept the day manageable.

Driver retention improved. Satisfaction surveys showed drivers appreciated the fairness of balanced territories and the clarity of optimized routes. Several drivers commented that their new routes made them feel more professional—they weren’t guessing, they were following a system.

The real win was recapturing lost accounts. Two of the three accounts that had defected to Amazon returned to MotorFlow within six months. The third account remained with Amazon for some categories but brought back their critical same-day needs to MotorFlow, representing a partial recovery of the lost $15,000 monthly revenue. Darnell added $10,000 monthly to his revenue projections based on the retained accounts alone.

The speed advantage became a competitive differentiator. MotorFlow was acquiring new accounts at a higher rate because shops could rely on the 90-minute rush delivery window. Twelve new accounts signed within the first year, many citing MotorFlow’s demonstrated speed and reliability as the reason they switched from Amazon for high-priority parts.

Darnell developed a philosophy around the transformation: “Amazon can ship a box. We deliver a relationship. What we delivered here was reliability and speed, which is what the relationship is built on.”

Performance Metrics