About TeamTrek

We build the record, not the surveillance.

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.

TeamTrek in numbers

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.

It started with a timesheet nobody believed.

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

  • Chase four people for the hours they half remember
  • Rebuild the week from calendar invites and guesswork
  • Argue about whether a day was really eight hours
  • Invoice only what you could defend if asked

A day a week, spent on the record rather than the work.

Friday, now

  • The week is already written down as it happened
  • Idle time marked, discarded or reassigned before approval
  • Activity and apps attached to the project that was running
  • Invoice what was recorded, with the record behind it

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.

One desktop app, one record, five things it answers.

Each of these has a page of its own. This is the short version.

Employee activity tracking

Keyboard and mouse activity as a percentage of each interval, with the applications and sites that held focus.

See activity tracking

Time tracking by project

Hours against a client, a project and a task as the work happens, approved before they are billed.

See client billing

Distributed teams

One comparable record across time zones, read against each person’s own working day.

See remote teams

Delivery and estimates

What a project was quoted at, beside what it actually took to ship.

See IT and tech services

Optional screenshots

Off until an admin turns them on, blurred where a screen should not be legible.

Offuntil an admin enables it

How a rollout actually goes.

  1. 01

    Understand the week

    We start with how your team already works: who tracks what, which projects matter, and what the record has to answer.

    Discovery 1 week

  2. 02

    Configure and roll out

    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

  3. 03

    Run a real month

    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

  4. 04

    Review and adjust

    What the month showed, what to change, and which signals to turn off because they were not earning their place.

    Review Quarterly

  • Self-serve Start on the free trial and roll out at your own pace. No call required.
  • Guided rollout We configure with you, train the leads, and stay through the first cycle.
  • Enterprise Security review, procurement, retention policy and a named contact.

The people answerable for it.

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 tab

Name 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 tab

Four decisions, and what each one costs us.

A principle is only worth stating if it has been allowed to lose something. These four have.

Everyone can read their own record

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

Screenshots off until you ask

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

Idle time marked, never absorbed

Minutes away from the keyboard are separated before approval.

Costs us the bigger number on every invoice and utilisation report.

Separatefrom the total

The record leaves with you

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

The record is only useful where the work already is.

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.

Certifications and controls

What procurement usually asks for

  • ISO 27001
  • SOC 2 Type II
  • GDPR
  • HIPAA
  • SSO and SCIM
  • Data export

Placeholder. None of these is claimed as held until it has been verified and dated here.

Where this is going

A record so ordinary that nobody argues about it, and so open that nobody has to.

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.

Tell us what your week looks like.

Thirty minutes, no deck. We will tell you whether TeamTrek fits, and say so plainly if it does not.