Solution Whitepaper | Amsterdam Technologies
Timemaster: Natural Language Time Tracking with Automatic Clockify Synchronization
Modern knowledge workers, particularly in software engineering and IT operations, interact with a highly fragmented ecosystem of tools. A typical daily…
The Problem
Modern knowledge workers, particularly in software engineering and IT operations, interact with a highly fragmented ecosystem of tools. A typical daily workflow spans issue trackers (Jira), version control systems (Git), communication platforms (Slack), and scheduling software (Microsoft Outlook). While these systems contain a precise, timestamped audit trail of a professional's day, time tracking and billing systems exist in complete isolation from this data.
Consequently, professionals are forced to manually reconstruct their work weeks, copy-pasting ticket numbers, meeting durations, and commit messages into rigid timesheet interfaces. This structural gap results in severe operational friction. Organizations face delayed billing cycles due to incomplete timesheets, while professionals lose hours each week to tedious data entry. Existing time tracking solutions fail to address this because they rely on either manual form-based entry, which disrupts focus, or intrusive surveillance tools, which degrade trust and violate privacy norms. The landscape demands a paradigm shift: time tracking must become a seamless byproduct of natural language notes and existing digital exhaust.
Solution Overview
Timemaster directly resolves the friction of timesheet generation by treating time tracking as an aggregation and natural language processing problem. Operating as a lightweight, always-available desktop application, Timemaster automatically gathers context from the user's daily tools—capturing Slack huddles, Outlook meetings, Jira tickets, and local Git commits.
The fundamental architectural insight of Timemaster is the application of structured Large Language Model (LLM) orchestration to unstructured human input. Instead of demanding that users fill out complex dropdowns for clients, projects, and tasks, Timemaster allows users to write free-form daily notes. The application then uses advanced AI to parse these notes, cross-reference them with the gathered tool context, resolve complex project hierarchies (such as Jira EPICs), and map everything to a typed schema compatible with time tracking backends like Clockify. By supporting fully localized LLM execution alongside cloud models, Timemaster delivers this automation without compromising on data privacy or intellectual property protection. The product is currently in production, offering both a standalone desktop client and an optional, fully self-hosted team tracking backend.
Key Capabilities
AI-Powered Time Entry Analysis
Timemaster eliminates manual data entry by processing unstructured, natural language work notes. The application utilizes Firebase Genkit for LLM orchestration, specifically leveraging tool-calling capabilities to force the AI to return data through a strictly typed schema rather than volatile, free-text JSON. Users can utilize over 25 cloud models via OpenRouter (including Claude, GPT-4o, and Gemini), authenticate directly with an Anthropic Claude Teams plan, or run inference entirely locally using a bundled Ollama runtime with models like Qwen or Llama. This structured output matches natural language task descriptions to specific clients, projects, tasks, and durations, heavily reducing the cognitive load of timesheet creation.
Automated Context Gathering
The application continuously monitors background activity across core productivity tools to pre-populate the user's timesheet context:
- Slack Huddles & Zoom: Utilizing Slack Socket Mode via a persistent WebSocket connection, Timemaster detects real-time Slack huddles and Zoom calls, recording participants, channels, and exact durations into a local SQLite database.
- Microsoft Outlook Integration: Via the Microsoft Graph API and OAuth 2.0, the application imports calendar events, automatically rounding durations and extracting attendee lists. An advanced rule engine allows the application to automatically decline incoming meeting invitations if the subject line lacks a valid Jira ticket identifier, enforcing strict organizational time allocation policies.
- Git Commit Scanning: The application scans configured local Git repository paths, filtering commits by the user's configured
user.emailto generate a chronological log of daily development work.
Advanced Jira Ticket Matching
Timemaster supports multiple Jira instances simultaneously, accommodating both Cloud (API key) and Server/Data Center (Personal Access Token) deployments. The application injects the user's assigned ticket context directly into the LLM prompt. Crucially, it performs EPIC-based project matching: the system extracts ticket keys from the user's notes, queries Jira for the parent EPIC, and maps the activity to the corresponding Clockify project and client automatically.
Clockify Synchronization
Reviewed and structured time entries are pushed directly to Clockify workspaces. The synchronization engine performs automatic project and task discovery, running background syncs to ensure local project mappings remain accurate. To ensure reliability against API rate limits and network instability, Timemaster implements a pending submission recovery system—failed API calls are persisted locally and automatically resumed upon the next application launch.
Self-Hosted Team Platform (For Teams)
Beyond the desktop client, Timemaster offers a comprehensive, multi-tenant team tracking platform deployable via Docker. This platform includes a high-performance Clockify importer that can seamlessly migrate historical workspace data. The team tracker handles project management, invoicing, leave management, and capacity planning. Furthermore, it exposes a secure Model Context Protocol (MCP) server, allowing AI assistants like Claude Code or Cursor to interface directly with the tracker to query team capacity, generate PDF invoices, and approve time-off requests via loopback-authorized tool calls.
Architecture & Technical Design
Timemaster is engineered with a local-first, privacy-centric philosophy. The desktop application is built using Wails v3, combining a highly concurrent Go backend with a responsive, framework-free HTML/JS frontend. This architecture allows the application to maintain a minimal memory footprint while offering deep, native operating system integrations.
On macOS, the primary deployment target, Timemaster operates as a frameless system tray application (ActivationPolicyAccessory) utilizing native visual effects like Liquid Glass. It employs Carbon hotkey APIs for global accessibility and handles atomic, background auto-updates by manipulating downloaded DMG images directly.
Data flow is strictly controlled. Local caching relies on an embedded, pure-Go SQLite database, ensuring zero external database dependencies for the desktop client. Drafts are safely persisted using a dual-write mechanism to both browser localStorage and the Go backend to prevent data loss during sudden termination.
For privacy-sensitive environments, the architecture supports entirely air-gapped AI analysis. By routing inference requests to a local Ollama server, no proprietary code names, client details, or strategic project information ever traverse the public internet. Integration security is enforced via strict OAuth 2.0 flows with PKCE, storing all access tokens in the native OS secure enclaves (macOS Keychain or Windows Credential Manager).
Use Cases & Scenarios
The Software Engineer
Challenge: An engineer works across three different local codebases and handles multiple Jira tickets daily, struggling to accurately distribute logged hours across different client projects at the end of the week. Solution: Using Timemaster's global hotkey, the engineer opens the application and switches to the Git tab, bulk-inserting the day's commits into their notes. The AI analysis engine reads the commit messages, identifies the associated Jira ticket numbers, resolves the Jira EPICs, and perfectly allocates the hours to the correct client projects in Clockify. Outcome: Timesheet accuracy increases dramatically, and the weekly administrative burden is reduced to minutes.
The Engineering Manager
Challenge: A manager's day is fragmented by ad-hoc Slack huddles, 1:1 meetings, and cross-functional Zoom calls, making it nearly impossible to track time accurately for departmental budget allocation. Solution: Timemaster's Slack Socket Mode integration automatically tracks every huddle and call throughout the day, recording the participants and exact durations. Combined with the Outlook calendar import, the manager's schedule is entirely reconstructed. Outcome: The manager gains a precise audit trail of communication time without manual stopwatch tracking.
The Privacy-Restricted Contractor
Challenge: A consultant working in defense or finance is strictly prohibited from sending client data, project codenames, or internal ticket descriptions to third-party cloud AI APIs like OpenAI or Anthropic. Solution: The consultant configures Timemaster to utilize the bundled local Ollama integration. They pull a local model (e.g., Llama 3.2) equipped with tool-calling capabilities. Outcome: The consultant benefits from AI-accelerated timesheet structuring while maintaining 100% data residency and complying with stringent NDA requirements.
The Operations Administrator
Challenge: An operations team needs to generate monthly invoices and track team capacity, but navigating their existing time tracking web portal to extract CSVs and cross-reference leave balances is tedious. Solution: The team deploys the Timemaster Team Tracker backend via Docker. The administrator connects their Claude.ai interface to the tracker using the Model Context Protocol (MCP). They simply type, "Preview an invoice for ClientX for last month, and tell me who has under 20 hours allocated next week." Outcome: Complex administrative reporting and invoicing are executed instantly via natural language conversation with the organization's data.
Pricing & Plans
Timemaster is a desktop application purchased as a downloadable client with subscription and lifetime license models.
| Plan | Price | Billing | Key Features |
|---|---|---|---|
| Monthly | €8 | Monthly | AI Time Analysis, Clockify, Jira, Slack, Git, Outlook Integrations, Cloud/Local AI |
| Yearly | €79 | Yearly | Everything in Monthly, 2 months free, Priority Support |
| Lifetime v1 | €129 | One-time | All v1.x updates, No recurring fees, All integrations included |
| Enterprise | Custom | Custom | Unlimited usage, dedicated instance (for Team Tracker), SSO/SAML, SLA guarantee, on-premise options, dedicated account manager |
Pricing Philosophy: We offer flexible licensing to suit individual professionals and large teams. Subscriptions provide continuous feature updates, while the Lifetime plan offers predictable expenditure for the current major version. The Enterprise tier provides the dedicated infrastructure and governance required for deploying the self-hosted Team Tracker at scale.
Frequently Asked Questions
Does the AI analysis require sending my data to the cloud? No. While Timemaster supports cloud providers like OpenAI and Anthropic via OpenRouter, it fully supports local execution. You can use the bundled Ollama integration or connect to any local OpenAI-compatible server on your network, ensuring your notes and ticket details never leave your machine.
What operating systems are supported? Timemaster is optimized for macOS (Apple Silicon and Intel) as a native menu bar application. It also compiles and runs on Windows and Linux, supporting core AI and integration functionality, though certain OS-specific features (like native visual effects or automated atomic updates) are exclusive to macOS.
How does the Outlook auto-decline feature work? When enabled, Timemaster reads your pending Outlook invitations and checks the subject lines against a configurable ticket pattern (e.g., Jira keys). If an invitation lacks a valid ticket, it can automatically decline the meeting and notify the organizer, enforcing organizational rules that require meetings to be attached to trackable work.
Can we host the time tracking backend ourselves? Yes. For organizations that require total data sovereignty, the Timemaster Team Tracker is available as a multi-tenant, Docker-deployable platform that can completely replace third-party SaaS trackers while seamlessly migrating existing data.
Why Amsterdam Technologies
Amsterdam Technologies designs software for professionals who value precision, privacy, and performance. Headquartered in Amsterdam, our engineering-first culture focuses on solving structural workflow inefficiencies rather than building superficial interfaces. Timemaster exemplifies this approach by treating time tracking as an integration and automation challenge, utilizing advanced LLM orchestration while respecting local execution boundaries. As we continue to expand the Model Context Protocol capabilities of the Team Tracker, Timemaster is positioned to become the central nervous system for autonomous administrative operations in modern engineering organizations.
- Website: https://time-master.app
- Contact: support@amsterdam-technologies.com
- Company: amsterdam-technologies.com
Product screenshots





