TimeToGo: audience and demand research

If any already-engaged testers or requesters are reachable, invite a small number of drivers with repeat routes and some departure flexibility to use the current app on real commute opportunities. Observe setup, alert delivery, whether an alert changes departure, and whether they use it again. If none are reachable, account for the founder time required to recruit rather than assuming distribution is free.

Why this test: Early customer and substitute signals point to a recognizable task, but say little about whether people will set up a separate app, act on its alerts, or return. Behavior with the current product is a more direct learning signal than favorable reactions alone.

Success signal: A participant completes setup, receives and responds to a relevant threshold alert, and returns to use the app on later commute opportunities; record setup friction and missed or unhelpful alerts as well.

Counter-signal: The evidence is sparse and mixed in age and context. Map tools are a substitute, app-store descriptions do not establish adoption, and a single historical customer anecdote cannot represent a market. TimeToGo's installs, activation, retention, revenue, and acquisition channels remain unknown.

Candidate segment to examine: Drivers with a repeat commute and discretion to shift departure time, such as some work-to-home commuters.

Why examine it: An early customer-review anecdote describes using a threshold alert for a work-to-home trip, and the founder's product description centers on a repeat commute while working. This is a direction to examine, not a selected niche or evidence of its size.

Key assumption: For a reachable group of drivers, departure is flexible enough and traffic varies enough that a timely, sufficiently reliable threshold alert changes what they do on repeated trips.

Why it matters: Without both the ability to delay departure and an actionable change in travel time, the alert may add little beyond checking a map; whether that behavior supports ongoing use is unproven.

Built-in map tools already let users save trips and inspect current or typical traffic; one older alert-app listing also contains customer reports of both usefulness and address-entry problems. These are early risk signals, not evidence about TimeToGo's current quality or retention.

Consequence: Even if the problem is recognizable, a separate app may not earn repeat use if built-in maps are adequate, the user cannot delay leaving, or traffic changes rarely make the alert actionable. Inaccurate or late alerts and setup problems could also undermine trust.

Early check: During real commute use, observe setup completion, whether alerts arrive in time and match the route experience, whether users act on them, and whether they return. Compare this behavior with how they currently use map apps.