Employee activity tracking
Keyboard and mouse activity as a percentage of each interval, with the applications and sites that held focus.
About TeamTrek
Time and activity tracking for teams that have to answer for their hours — built so the people being measured can read everything recorded about them.
2018
founded
0
teams tracking
0.0M+
hours a month
0
countries
0%
still here after a year
As of March 2026. Figures shown for demonstration — replace with verified numbers before launch.
Four of us were running a services team in 2018 and losing a day a week to reconstructing the other four. We built the record we wanted to have had.
Friday, 2018
A day a week, spent on the record rather than the work.
Friday, now
Twelve thousand teams later, the same rule as week one: whatever it records, the person it describes can open.
Founding year and the detail around it are placeholder content until they are confirmed.
Each of these has a page of its own. This is the short version.
Keyboard and mouse activity as a percentage of each interval, with the applications and sites that held focus.
Hours against a client, a project and a task as the work happens, approved before they are billed.
One comparable record across time zones, read against each person’s own working day.
What a project was quoted at, beside what it actually took to ship.
Off until an admin turns them on, blurred where a screen should not be legible.
Offuntil an admin enables it
We start with how your team already works: who tracks what, which projects matter, and what the record has to answer.
Discovery 1 week
Signals, roles, retention and schedules are set before anyone installs anything, and the team is shown the same screen their lead sees.
Rollout 2 weeks
One full cycle of tracking, approving and reporting, so the first invoice or payroll run comes from evidence rather than estimate.
First cycle 30 days
What the month showed, what to change, and which signals to turn off because they were not earning their place.
Review Quarterly
One line each on what they think the product is for. Longer biographies are a careers page problem.
Name placeholder
Co-founder and CEO
“Monitoring that only one side can read is a trust problem wearing a software costume.”
LinkedIn , opens in a new tabName placeholder
Co-founder and CTO
“If the desktop app is not boring and quiet, nothing else we claim matters.”
LinkedIn , opens in a new tabName placeholder
Head of Product
“Every signal has to earn its place. Most feature requests are a report somebody could not find.”
LinkedIn , opens in a new tabA principle is only worth stating if it has been allowed to lose something. These four have.
Every member opens the same figures their manager sees.
Costs us the feature every third prospect asks for: a manager-only view.
100%readable by its subject
App and URL history answers it without a camera on a room.
Costs us the demo that sells fastest: a wall of thumbnails persuades.
Offby default on every plan
Minutes away from the keyboard are separated before approval.
Costs us the bigger number on every invoice and utilisation report.
Separatefrom the total
Hours and activity export by person, project or client.
Costs us the lock-in that makes churn look lower than it really is.
CSVand PDF, any range
Partnerships
TeamTrek sits beside the payroll, accounting and project tools a team already runs, rather than asking anybody to move. We build those connections with the people who make, resell and operate those systems — and we would rather integrate than replace.
What procurement usually asks for
Placeholder. None of these is claimed as held until it has been verified and dated here.
Where this is going
What we are building now: approvals that survive an audit, exports that fit the tools finance already runs, and defaults that keep getting quieter rather than louder.
We hire slowly and mostly from people who have run the kind of team this is for. Roles are posted when they are real.
Thirty minutes, no deck. We will tell you whether TeamTrek fits, and say so plainly if it does not.