CruizGo forced me to be fair to the incumbent. Google Maps already handles arrive-by and traffic prediction well. The more interesting product question is whether there is a recurring behavior layer around that capability that deserves its own experience.
THE SIGNAL
Google Maps already supports “Depart at” and “Arrive by.” Its help documentation says users can choose a future departure or arrival time and receive route estimates based on expected traffic or transit schedules.
Google has also described how Maps combines live conditions with historical traffic patterns and machine learning to predict travel times. Its 2020 technical explanation said ETA predictions were accurate for more than 97% of trips at that time.
So the product question should not be:
“Why can’t Google Maps tell me when to leave?”
It can.
That is an important correction because good product strategy begins by being fair to the existing alternative.
THE QUESTION
The more interesting question is:
Is “calculate an arrive-by route” the same product job as “help me make a recurring departure decision every day”?
I do not think they are necessarily the same.
A recurring commuter may care about things that sit around the route calculation:
- my tolerance for arriving early;
- parking/gate/walk time after reaching the map destination;
- which days I repeatedly leave late;
- whether a calendar meeting makes today unusual;
- employer shuttle or corridor behavior;
- how I respond to reminders;
- what happens after I miss the recommended window.
Those are hypotheses for a product like CruizGo. They are not claims that Google Maps cannot support them.
THE OBVIOUS ANSWER
“Just integrate Google Maps.”
That might actually be the correct technical strategy.
A new product should not rebuild world-class routing.
It could treat route/traffic prediction as infrastructure and differentiate on the repeated decision around it.
This is the difference between building a map and building a behavior layer on top of mobility intelligence.
THE TENSION
I think there are two related but distinct jobs:
| Navigation job | Departure-decision job |
|---|---|
| What route should I take? | When should I leave to meet my arrival goal? |
| What is the ETA? | What departure window balances punctuality and unnecessary earliness? |
| What is traffic like? | Has the risk changed enough to interrupt me? |
| Re-route during trip | Recompute after I miss the planned departure |
| Optimize individual trip | Learn recurring corridor / schedule behavior |
Google Maps already covers parts of both columns, including commute planning and arrive-by time.
So the product opportunity has to be narrower and more behavioral than “better navigation.”
ETA · traffic · routing · re-routing during the trip
arrival window · early-arrival tolerance · access time · missed-window recovery
MY PRODUCT TAKE
If I were building this, I would frame the product as:
arrival-first departure intelligence for recurring commitments
The moat hypothesis would not be traffic data.
It would be:
personal calibration + recurring context + behavioral history + organization/corridor integrations
And even that needs to be earned.
The right product may ultimately become a feature, partner layer or employer mobility product—not a standalone consumer navigation competitor.
WHAT I WOULD TEST
I would recruit recurring commuters and measure:
- how often they manually check traffic before departure;
- how often they arrive materially early/late;
- whether they value a window more than a point estimate;
- whether parking/gate/walk time changes the real arrival job;
- whether proactive alerts reduce late departures;
- whether they keep the behavior after four weeks.
The strongest signal would not be app opens.
It would be:
percentage of recurring commitments reached inside the user’s acceptable arrival window.
WHAT WOULD CHANGE MY MIND
If users already feel that existing commute/arrive-by tools solve the decision sufficiently, I would not build a standalone consumer product.
That would not make the exploration a failure.
It would make it good product discovery.
Secondary research
- Google Maps Help: Depart at / Arrive by — https://support.google.com/maps/answer/144339
- Google Maps commute planning — https://support.google.com/maps/answer/7565193
- Google Maps traffic prediction explanation — https://blog.google/products-and-platforms/products/maps/google-maps-101-how-ai-helps-predict-traffic-and-determine-routes/