# Time tracking for software teams and development agencies > Time tracking for software teams and dev agencies: hours per client and project, proposed entries, an API, CLI and MCP server, and client sign-off for T&M. URL: https://timetracking.tech/for/software-development Language: en Last updated: 2026-10-26 Developers want to ship code, not fill in timesheets. Yet a time-and-materials (T&M) contract, a fixed-price review or an R&D tax claim all need correct hours. TimeTracking keeps tracking light. On Pro, it proposes entries from last week. Your team gets an API, a CLI and an MCP server to script time data like everything else. Start free for up to 5 users. ## 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 never end up in one pile. 2. **Track with almost no effort**: Start a timer on the web or phone. Log hours from the terminal with the tt CLI. On Pro, confirm the entries proposed from last week. 3. **The client signs off**: For T&M work, the client approves the sprint or month through a secure magic link. They need no account. 4. **Export or pull through the API**: Send approved hours to your invoicing tool as CSV, XLSX or JSON. Or pull them into your own systems through the REST API and webhooks. ## Timesheets developers do not hate Most developers fill in their hours on Friday afternoon. They work from a vague memory of standups and pull requests. Predictive time tracking on Pro fixes that. It turns last week's entries and repeat work into proposed entries per client and project. In a normal week, the developer only checks and confirms. A timer in the web app and the mobile app covers the days that break the pattern. Google Calendar and Outlook sync is coming soon. Then meetings become proposals too. A browser extension and a desktop tray app are coming soon as well. - Proposed entries from last week's pattern (Pro) - 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. Time data should be no different. The REST API comes with an OpenAPI description. Webhooks are signed and retried. The tt command-line tool shows the week, adds hours, approves and exports from the terminal. Add --json to script it. The MCP server lets assistants such as Claude read and update time data. They get the same rights as the developer who connects them. The Claude Skill teaches Claude the common tasks. Ask for last month's hours per client in plain words. Or log the afternoon on a project without opening a browser. All of this is 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 approved the hours before the invoice arrives rarely disputes it. TimeTracking sends the client's approver a secure link that expires. It shows the hours per developer and day, with the notes. They approve the period, or reject a line with a comment. Their name and the time of approval are saved. After approval and export, the period is locked. Need a fix later? It becomes a new line in the next open period. No silent edits. ## Fixed price, retainers and internal products Not every project is billed by the hour. On fixed-price work, the hours still show if the estimate was right. They tell you what the next quote should be. Reports show approved hours per client, project and person for any period. Share them in a retrospective, or export them 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 steady record. Use it as input for your R&D or innovation paperwork. ## No Jira sync, and no invoicing either TimeTracking does not sync with issue trackers today. It does not create invoices. It does one job: approved hours. And it makes them easy to get out. Use CSV, XLSX and JSON exports you set up yourself, or the API and webhooks. Then link hours to tickets or invoices in your own tools. 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. Pro adds predictive time tracking and higher API limits. No seat minimum, 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. Start free today. ## 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? Not yet. Sync with Google Calendar and Outlook is coming soon. Today, proposals on Pro come from last week's entries and repeat 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 saved. ### What can the API and MCP server do? The REST API reads and writes time data and exports. Webhooks tell you about changes. The MCP server lets assistants like Claude work with the same data, with the user's own rights. ### Does it track screenshots or keystrokes? No. TimeTracking logs time entries only. No screenshots, no activity tracking.