Capture the engineering time nobody logs
Engineers are honest and terrible at time tracking, and the reason is structural: the work that gets logged is the work that looks like a task. Reviewing a colleague's pull request, triaging a flaky build, answering a client in Slack and pushing the hotfix that followed are all real billable work, and all of it is invisible to a tool that waits to be told. ActivityPulse observes the work instead of asking about it.
What goes wrong today
If none of these are familiar, this probably is not your problem.
- Review, triage and incident time never reaches a timesheet because it never looked like a ticket.
- Context switching across three client codebases in a day, reconstructed as one round number.
- Engineers who will not accept screenshot-based monitoring, so nothing gets deployed at all.
- Utilisation figures that everyone privately knows are wrong.
What changes
With privacy-by-default metadata tracking.
- Time captured from the foreground application and attributed to the repository, project or task in front of it.
- The short, frequent work — reviews, triage, quick fixes — represented instead of rounded away.
- A rollout engineers will accept: no keystroke content, no screen recording, and a visible pause button.
- Utilisation built from observed time rather than from what people remembered on Friday.
What the design guarantees
- no-keystroke-logging
- Keystroke content is never captured — there is no code path that records what a person types.
- transparent-agent
- By default the person being monitored can see what is being captured on their own machine and can pause capture. The one exception is a covert investigation, which is Enterprise-only, unavailable in the EU, capped at 90 days, and audited.
- no-productivity-score
- ActivityPulse reports what happened and does not grade the person it happened to — there is no productivity score.
Questions from teams like yours
Will engineers accept this?
That is the constraint the product is designed around. Keystroke content is never captured, there is no screen recording by default, the agent shows what is being collected on the person's own machine, and capture can be paused.
Does it read our source code or repository contents?
No. The agent reads window and process metadata — which application and which window title are in the foreground. It does not read file contents.
Does it score engineers on productivity?
No. Producing a headline productivity score is an explicit non-goal, and the dashboard is deliberately built not to compute one.
What if an engineer works across two machines?
Overlapping time from two devices belonging to the same person is resolved before it reaches a report, so a laptop and a desktop do not produce two hours for one.
See where the hours actually went
Free for up to three people. Windows and macOS. No keystroke content on any plan, and screenshots off unless an administrator turns them on.