When to work
Availability, time windows, working areas, and platform options became a plan a driver could review before leaving.
Earlier product / Mobile and web
Qwkroute
Qwkroute is a productivity and analytics product I built for gig drivers. It brings demand, weather, fuel costs, working areas, and past-shift context together before a driver decides when and where to work.
Why I started it
Drivers make shift decisions with information scattered across separate places.
Demand can change by time and area. Weather, events, fuel costs, and the mix of available platforms can change whether a shift is worth taking. Drivers often have to assemble that picture themselves.
Planning approach and privacy
I started Qwkroute to organize those signals around the decision a driver is actually making: when should I work, where should I start, and which app looks strongest for that shift?
The product is designed without requiring continuous location tracking or direct access to a driver’s delivery-platform account.
Product model
The planning model covered the whole shift, not one heatmap.
Qwkroute explored how the signals around gig work could be organized around four decisions a driver repeatedly has to make.
Where to position
Demand, weather, and local-event signals were organized around the areas and times that might affect working conditions.
Which app to open
The product compared platform and shift context without employing drivers, dispatching work, or claiming affiliation with the gig platforms.
Whether the work was worth it
Reported earnings, fuel, and other working costs gave the driver more context than gross pay alone.
My role
Product scope, interface, data flow, and privacy boundaries.
I defined the product, organized the planning flow, built the web and application interfaces, connected data sources, and decided how driver information should be handled.
A central product challenge was separating useful context from false confidence. Qwkroute was built to support a decision, not promise that demand or earnings would behave a certain way.
Product lifecycle
Qwkroute is scheduled to be discontinued in April 2027.
The announced sunset closes active product development on a defined timeline. This page remains as a record of the problem Qwkroute was built to solve, the product decisions behind it, and the lessons that carry into my current work.
Current availability
At the time of this portfolio update, the public Qwkroute site remains available. Availability may change as the April 2027 shutdown approaches.
Visit QwkrouteProduct development / Planning tools