Builders: the in-car work opportunity
The real product gaps in working from a car: handoff, capture, workstation UX, and continuity memory.
There is a temptation to treat the in-car work category as a car problem. Build a better screen, add a faster chip, put an assistant in the dash. But the hardest problems are not automotive. They are product problems about how work moves across contexts. The companies that solve them will not look like car companies.
The handoff problem
A thought starts at your desk, develops in the car, and finishes on your phone while you walk into a building. Today that thought passes through three separate assistants with no shared memory. Each one needs to be told the context from scratch. The result is friction so high that most people give up and wait until they are back at a desk. The real product opportunity is continuity: a single thread that follows the user across devices and modes, knowing what matters without being asked.
Handoff is harder than it sounds because the modes are different. Driving mode is voice-only and interruption-tolerant. Riding mode is screen-and-keyboard. A desk session is neither. A good agent does not just sync files; it understands which parts of a task fit which mode and surfaces the right interface at the right time.
Voice capture that lands
Voice is the natural input for driving mode, but most capture flows die at the handoff. You dictate a note, it becomes a transcript, and then it sits in an app you never open. The missing piece is capture that lands in real systems without a confirmation screen. Say a task and it appears in your actual task manager. Say a reply and it enters your actual email outbox. Say an idea and it attaches to the right project. None of this requires better speech recognition. It requires better integration and trust.
Riding-mode workstation UX
Put a laptop in a robotaxi and you quickly discover that nobody has designed the environment around it. Where does the screen go? How do you look professional on a video call when the cabin is vibrating? What happens to your cursor when the car turns? These are not edge cases. They are the core experience for anyone trying to do real work in a moving cabin. The opportunity is a software-plus-hardware layer that treats motion, privacy, and bandwidth as first-class constraints.
Continuity memory
The most valuable assistant in this category will be the one that remembers what you were doing last and offers it back at the right moment. Not a generic notification. A contextual prompt: 'You were drafting the Q3 review when you left your desk. You have twelve minutes until arrival. Want to finish the section on hiring?' That requires memory across sessions, an understanding of travel time, and the judgment to interrupt only when it is useful.
Builders should also think about the business model. A tool that owns the handoff owns a high-intent slice of daily attention. That is valuable to employers, to productivity software companies, and to fleet operators who want to differentiate a robotaxi from a taxi. The category is wide open because no one has yet made the experience reliable enough to become a habit.
These gaps are practical. They do not require autonomy to be solved everywhere at once. They require product builders to treat the car as a real work context instead of a demo environment. The first company that makes the handoff feel invisible will own more than the car. It will own the commute.
Get the weekly digest
One email a week: a playbook, a tool verdict, and what changed in autonomy.