The first version of the product spec included an auto-scheduler. You'd connect your calendar, tell it your priorities, and it would move things around to optimize your week. It was technically interesting. Users we talked to said it sounded compelling.
We built a prototype. It worked. And then we decided not to ship it.
The Temptation of Automation
Auto-scheduling feels like a solved problem. There are algorithms for this. You can optimize for focus time, meeting batching, commute windows, energy levels as proxies. The output looks clean. The numbers improve. Technically, it is impressive.
The problem is what automation removes: agency. When an algorithm moves your meetings, you don't understand why they moved. You lose the reasoning. You become a passenger in your own week.
Context the Algorithm Can't Access
Calendar decisions involve information that doesn't live in a calendar. The meeting you moved might be with someone whose relationship is fragile right now. The focus block you protected might need to shift because a teammate is struggling. The Thursday afternoon you cleared might be the only time your collaborator in London is available this month.
Algorithms optimize for the data they have. Calendar optimization algorithms have event titles, durations, and labels. They don't have relationship context, project momentum, or the knowledge that this particular meeting can't be moved without a consequence that won't show up in any data.
Our Actual Thesis
The right tool gives you better information, not fewer decisions. Visibility makes you better at deciding. Automation makes the decisions for you.
These produce different people. A user who has spent six months looking at their calendar analytically understands their work patterns, knows their thresholds, can identify when something structural is going wrong. A user who delegates their calendar to an algorithm has an optimized week — until the algorithm encounters a situation it wasn't trained on, which is constantly.
What We Built Instead
Tempo shows you what's happening. Where time actually goes. When patterns are problematic. When your priorities and your calendar are misaligned. And then it waits for you to decide what to do about it. That's not a limitation. It's the point. The outcome we want is a user who understands their calendar deeply — not one who has delegated it.