Skip to content
TimeTracking

Time tracking for software teams and development agencies

Developers want to ship code, not fill in timesheets. Yet a time-and-materials contract, a fixed-price retrospective or an R&D tax claim all depend on hours that are right. TimeTracking keeps tracking light, proposes entries from last week, and gives your team an API, a CLI and an MCP server to work with time data the way they work with everything else.

Start freeSee pricing
Animated demo: a developer confirms a week proposed from last week, logs Friday afternoon from the terminal with the tt CLI, and the client signs off the sprint through a magic link. Proposed from last week, Logged from the terminal, Client signs off, Out through the API.

How software teams use TimeTracking

  1. Set up clients and projects

    Each client contract or internal product gets its own project, so maintenance, new features and support hours never end up in one pile.

  2. Track with almost no effort

    Confirm the entries proposed from last week, start a timer on the web or phone, or log hours from the terminal with the tt CLI.

  3. The client signs off

    For time-and-materials work, the client approves the sprint or month through a secure magic link, without creating an account.

  4. Export or pull through the API

    Approved hours go to your invoicing tool as CSV, XLSX or JSON, or are pulled straight into your own systems through the REST API and webhooks.

Timesheets developers do not hate

Most developers fill in their hours on Friday afternoon, from a vague memory of standups and pull requests. Predictive time tracking turns last week's entries and recurring work into proposed entries per client and project. On a normal week, the developer only checks and confirms.

A timer in the web app and the mobile app covers the days that do not follow the pattern. Google Calendar and Outlook sync, so meetings become proposals too, is coming soon, as are a browser extension and a desktop tray app.

  • Proposed entries from last week's pattern
  • Timer on the web and in the mobile app
  • Coming soon: calendar sync, browser extension and desktop app
  • No screenshots, no keystroke or activity monitoring

API, CLI and MCP server

Your team automates everything else, so time data should be no exception. The REST API comes with an OpenAPI description and signed webhooks with retries. The tt command-line tool shows the week, adds hours, approves and exports from the terminal, and --json makes it easy to script.

The MCP server lets assistants such as Claude read and update time data with the same permissions as the developer who connects it, and the Claude Skill teaches Claude the common tasks. Ask for last month's hours per client in plain language, or log the afternoon on a project without opening a browser. All of these are live today.

  • REST API with OpenAPI description
  • Signed webhooks with retries
  • tt CLI with JSON output
  • MCP server and Claude Skill

Client sign-off for time-and-materials work

On T&M contracts, the hours are the invoice. A client who has approved the hours before the invoice arrives rarely disputes it. TimeTracking sends the client's approver a secure, expiring link with the hours per developer and day, including the notes. They approve the period or reject a line with a comment, and their name and the time of approval are stored.

After approval and export the period is locked. If something needs correcting later, it becomes a separate line in the next open period instead of a silent edit.

Fixed price, retainers and internal products

Not every project is billed by the hour. On fixed-price work, the hours still tell you whether the estimate was right and what the next quote should be. Reports show approved hours per client, project and person for any period, ready to share in a retrospective or export for your own analysis.

Many teams also track time on internal products or R&D. Hours per project with a note on each entry give you a consistent record that can serve as input for your R&D or innovation administration.

No Jira sync, and no invoicing either

TimeTracking does not sync with issue trackers today and does not create invoices. It does one job, approved hours, and makes them easy to get out: configurable CSV, XLSX and JSON exports, or the API and webhooks, so you can link hours to tickets or invoices in your own tooling.

Native apps for Zapier and Make and a Slack integration are coming soon. Each integration page shows its current status.

Fair pricing for growing teams

Free for up to 5 users, then €1 per user per month on Core or €3 on Pro, which adds predictive time tracking and higher API limits. There is no seat minimum and there are no add-ons, so adding a contractor for one project costs one euro a month on Core.

Customer data is stored in the EU, in Ireland.

Frequently asked questions

Is there a browser extension or desktop timer?

Not yet. The web app and mobile app have a timer today. A browser extension and a desktop tray app are on the roadmap.

Does TimeTracking integrate with Jira or GitHub?

Not natively. You can connect hours to your own tools through the REST API, webhooks and the tt CLI.

Can hours be proposed from our calendars?

Calendar sync for Google Calendar and Outlook is coming soon. Today, proposals are built from last week's entries and recurring work.

Can clients approve hours for a T&M contract?

Yes. Clients approve through a secure magic link without an account. Their name and the time of approval are recorded.

What can the API and MCP server do?

The REST API reads and writes time data and exports, webhooks notify you of changes, and the MCP server lets assistants like Claude work with the same data under the user's own permissions.

Does it track screenshots or keystrokes?

No. TimeTracking records time entries only. There are no screenshots and no activity monitoring.

Related pages

Try TimeTracking free

Free for up to 5 users. Core from €1 per user per month, everything included.

Start freeSee pricing