MobTouch Inc. · Product
Route & Ride — operations beyond the map
Intelligent route planning for businesses that need to coordinate drivers, deliveries, schedules, customers, and the unexpected changes that happen throughout the day.
Role: Founder / Product engineer
- Route optimization
- Field operations
- Product architecture
Origin
The story
Route & Ride began with a simple observation: most businesses do not just need directions. They need to coordinate people, deliveries, schedules, customers, and the unexpected changes that happen throughout the day.
Traditional mapping software is excellent at getting someone from Point A to Point B. But drivers need optimized routes, dispatchers need visibility, customers need updates, businesses need proof that work was completed, and plans need to change without disrupting the entire day.
I built Route & Ride around those operational realities. Its purpose is not simply to calculate routes. Its purpose is to help businesses execute them.
The product brings planning, driver workflows, route adjustments, live progress, customer communication, and proof of delivery into one connected system.
The goal is not to optimize a route in isolation. It is to optimize the entire day.
Journey
The operating system behind the route
Beyond route optimization
Route optimization is only one part of the workflow. A delivery business must plan the work, coordinate the people performing it, respond to change, communicate progress, and preserve a trustworthy record of completion.
Route & Ride brings those responsibilities together instead of making teams bridge several disconnected systems.
- Manage customers
- Plan daily work
- Assign stops
- Track drivers
- Adjust routes throughout the day
- Record completed work
- Capture proof of delivery
- Communicate with customers
- Monitor overall progress
Built for real businesses
One of the best validations of the product has been watching a customer depend on it every day as a core operational platform.
Their drivers begin each morning with a route optimized specifically for that day’s deliveries. As the day progresses, new jobs appear, customers reschedule, and priorities shift. Instead of rebuilding the day manually, the team can adjust routes while preserving overall efficiency.
“The route is optimized every morning, but the real value is that it can continue adapting as the day changes.”
That flexibility transformed Route & Ride from a planning tool into an operational system.
Today it is an essential part of the company’s daily workflow.
Proof of delivery
Route optimization answers one question: Where should we go? Businesses also need to answer another: Did the work actually happen?
Route & Ride extends beyond navigation through integrated proof of delivery. Deliveries can be completed with the recipient’s name and customer signature directly inside the driver workflow.
Instead of relying on separate systems for routing and confirmation, the entire delivery lifecycle remains connected, creating an operational record from planning through successful completion.
Dynamic operations
Real-world operations are constantly changing. Drivers encounter traffic. Customers become unavailable. New deliveries are added. Priorities shift.
A routing engine should not force a business to restart planning from scratch whenever reality departs from the original plan.
Route & Ride supports operational adjustments throughout the day while preserving route quality. The software adapts to reality rather than expecting reality to follow the morning plan.
Product evolution
One of the most useful lessons from Route & Ride was discovering what the product should not become. Early in development, I explored expanding it into personal travel planning.
The more I worked on the idea, the clearer it became that business logistics and personal travel are fundamentally different problems. Businesses optimize operational efficiency. Travelers optimize experiences.
That distinction led to a separate product: MyTravelBuddy.ai. Route & Ride remained focused on commercial operations, deliveries, dispatch, and field service. Separating the products allowed each to evolve around its own users instead of compromising both.
Engineering challenges
Building Route & Ride required deterministic optimization to work inside an environment that is anything but deterministic.
The engineering challenge was not merely finding a mathematically efficient path. It was preserving useful plans and shared operational context while people, traffic, customers, and priorities kept changing.
- Multi-stop route optimization
- Time-window scheduling
- Dynamic route recalculation
- Mapping and geospatial systems
- Driver-centric mobile workflows
- Customer communication
- Proof of delivery
- Shared operational state
- Offline considerations
- Real-time synchronization
The product philosophy
Businesses do not need another map. They need software that helps them complete work. Navigation tells a driver where to go; operations software helps an entire business deliver reliably.
Route & Ride was designed around a simple principle: every completed delivery should move seamlessly from planning to execution to proof without requiring people to stitch together multiple disconnected systems.
The goal is not to optimize a route. The goal is to optimize the entire day.
Context
The problem and my role
Problem
Traditional mapping software is excellent at getting someone from Point A to Point B. Business operations require much more: optimized routes, dispatcher visibility, customer updates, proof that work was completed, and plans that can change without disrupting the entire day.
Role
Designed and built Route & Ride as an end-to-end delivery operations platform—from multi-stop planning and driver assignment through live execution, dynamic route adjustments, customer communication, and signature-based proof of delivery.
Constraints
- Optimize multiple stops while respecting traffic, time windows, travel modes, and operational priorities
- Allow schedules and routes to change throughout the day without forcing dispatchers to start over
- Keep drivers, dispatchers, customers, and delivery status aligned around shared operational state
- Design driver-centric mobile workflows that remain useful under real-world connectivity constraints
- Connect delivery confirmation and customer signatures to the route that produced them
- Support organizations, zones, address books, drivers, CSV imports, subscriptions, and billing
System
Architecture
System map
The route and delivery lifecycle
A delivery moves through one connected workflow, from the morning plan to an auditable record of completion.
- 01
Daily planning
Import customers and stops, apply schedules and time windows, then generate an optimized route.
- 02
Assignment and dispatch
Assign routes and zones to drivers while giving dispatchers shared visibility into the day.
- 03
Navigation and execution
Guide drivers through multi-stop routes while tracking stop state, location, progress, and ETAs.
- 04
Dynamic replanning
Respond to traffic, rescheduling, new deliveries, and shifting priorities without discarding the whole plan.
- 05
Proof of delivery
Capture recipient details, signatures, delivery confirmation, completion history, and an audit trail.
- 06
Communication and record
Share status and ETA updates while preserving operational visibility from planning through completion.
System map
The operational capability stack
Route & Ride combines the systems a delivery business needs around the route—not only the routing engine itself.
- 01
Planning
Daily route generation, stop optimization, driver assignment, time windows, and scheduling.
- 02
Operations
Driver workflows, route adjustments, live progress, customer management, and dispatch support.
- 03
Navigation
Mapping, turn-by-turn routing, ETA estimation, distance optimization, and multi-stop routing.
- 04
Proof of delivery
Customer signatures, delivery confirmation, completion history, and audit trail.
- 05
Communication
Customer notifications, ETA updates, delivery status, and internal operational visibility.
Execution
What I built
- Built daily route planning around departure time, traffic models, time windows, travel modes, toll preferences, and multi-stop optimization.
- Integrated Google Directions waypoint optimization to reorder stops while preserving the business context around each destination.
- Modeled organizations with shared address books, drivers, CSV imports, polygon zones, and driver-to-zone assignments.
- Separated planned routes from executable rides with stop states, progress tracking, periodic GPS points, and live operational visibility.
- Designed route adjustments as part of the normal workflow so dispatchers can respond to new work and changing priorities without recreating the entire day.
- Connected per-destination recipient names and signatures to the route and stop record for auditable proof of delivery.
- Built customer, subscription, transaction, and platform administration capabilities around the operational product.
Tradeoffs
Technical decisions
Optimize the operation, not only the path
- Decision
- Treat routing as one capability inside a broader planning, execution, communication, and completion workflow.
- Why
- A mathematically efficient route has limited value if dispatchers cannot assign it, drivers cannot adapt it, customers cannot follow it, or the business cannot prove completion.
- Tradeoff
- This requires a larger domain model and more operational state than a standalone route calculator.
Separate plans from executable rides
- Decision
- Model the optimized plan independently from the driver’s live ride and individual stop states.
- Why
- The original plan remains understandable while execution records what actually happened and supports changes throughout the day.
- Tradeoff
- Plan and execution state must be synchronized carefully so operational changes remain visible and auditable.
Make replanning a normal operation
- Decision
- Support incremental route adjustments without requiring the dispatcher to rebuild the entire day.
- Why
- Traffic, rescheduling, new jobs, and changing priorities are expected conditions in field operations, not exceptional failures.
- Tradeoff
- Preserving overall route quality while honoring work already in progress is more complex than optimizing a fresh route.
Keep proof inside the delivery lifecycle
- Decision
- Capture recipient details and signatures at the destination and attach them directly to the stop and ride record.
- Why
- Planning, execution, and confirmation form one business process; separating proof creates gaps, duplicate work, and weaker auditability.
- Tradeoff
- The driver workflow must balance trustworthy confirmation with speed and usability at the doorstep.
Use zones to make ownership visible
- Decision
- Represent service areas as polygon zones that can be assigned to drivers and used during planning.
- Why
- Operational teams often organize work geographically, and explicit zones make responsibility and coverage easier to understand.
- Tradeoff
- Geospatial boundaries add data-management and edge-case complexity around overlapping or changing territories.
Separate business logistics from personal travel
- Decision
- Keep Route & Ride focused on commercial operations and develop personal travel as the independent MyTravelBuddy.ai product.
- Why
- Businesses optimize efficiency and completion; travelers optimize experiences and flexibility. Each product needed a different model and interaction design.
- Tradeoff
- Maintaining two products creates more work, but avoids weakening both with a compromised shared experience.
Value
Product impact
User impact
Gives drivers an optimized plan that adapts during the day, dispatchers shared operational visibility, customers useful status updates, and every delivery a connected proof-of-completion record.
Business impact
Has become an essential daily operating platform for a customer by unifying planning, dispatch, execution, communication, and proof instead of requiring several disconnected tools.
Results
Outcomes
- A customer now relies on Route & Ride as an essential part of its daily delivery workflow.
- Drivers begin with optimized morning routes that can continue adapting as jobs, customers, and priorities change.
- Dispatchers retain operational visibility throughout the day instead of losing the plan once drivers leave.
- Integrated signatures connect delivery execution to proof of completion in one workflow.
- A live product at routenride.com supporting real-world planning and delivery operations.
Reflection
Lessons learned
- “The best route is not only efficient when generated; it remains useful as the day changes.”
- “A routing product becomes operations software when it closes the loop from planning through execution and proof.”
- “Proof of delivery belongs to the same lifecycle as route planning because completion is the real business outcome.”
- “Products become clearer when fundamentally different users and optimization goals are allowed to evolve separately.”
Tools
Stack
Next case study
MyGut.io — AI health companion for IBD →