Blog · 30 June 2026
The hidden cost of AI agent waiting time
When you direct an AI agent and it runs for half an hour, you're working: reading the output, steering the next step. But your keyboard is still. Every activity-based time tracker reads that stillness as idle and drops the time. Here's what that costs, in euros.
The simple math
Recovered billable time comes down to three numbers: the hours a day you spend attending agents, your hourly rate, and the working days in a month (about 21). The result is the money that activity trackers drop, and that you forget to log on a manual timer:
| Attending / day | Rate | Lost / month | Lost / year |
|---|---|---|---|
| 1 h | €80/h | €1,680 | €20,160 |
| 2 h | €90/h | €3,780 | €45,360 |
| 3 h | €120/h | €7,560 | €90,720 |
| 4 h | €150/h | €12,600 | €151,200 |
At a middle-of-the-road two hours a day and €90 an hour, that's €3,780 a month, or €45,360 a year, invisible on every other tracker.
Why every tracker misses it
Activity trackers decide you're working by watching for input. No input for a minute, and you're flagged idle, which is exactly what supervising a running agent looks like. Manual timers don't watch anything; they depend on you remembering to press start, and in the flow of directing an agent, you don't. Both were designed before "work" routinely meant a machine running on your behalf while you watch.
The fix: a third state
Counting all idle time would overcharge. The trick is to distinguish two kinds of stillness: attending a running agent (billable) versus beingaway (not). Atend adds that third state. It watches whether a known agent is running and whether you're present, counts the attending time, and leaves out the time you genuinely stepped out. This runs automatically, from metadata only, with no keystrokes or screenshots involved.
See your number
Atend reconstructs your real day automatically, including the attending hours.