The Case Against Complex Time Trackers (For Designers Who Just Want to Bill).

Every few months a freelance designer posts something like "I've tried every time tracker and they're all terrible." The replies always converge on one of the big names — Toggl, Harvest, Clockify, TimeCamp, Timing — and the thread becomes a comparison of which complex tool is the least bad.

No one in those threads asks the obvious question: why are freelancers using tools built for agencies?

The answer is that the market built what agencies would pay for. Agencies have procurement budgets and IT departments and twenty stakeholders who need reports. Freelancers have a browser tab and a Friday afternoon. The tools that got funded and distributed were agency tools, so they're the ones designers find when they search for "time tracker."

What complex trackers actually optimize for

The feature sets of the major time trackers are a map of agency concerns, not freelancer concerns:

• Project codes and workspace hierarchies — for an accounts team billing multiple clients across multiple retainers simultaneously, tracking to project codes prevents mis-billing. For a solo designer with five clients, this is overhead you're managing for no one.
• Approval flows — an account manager reviewing junior timesheets before invoicing. Not relevant when you're the only person on the account.
• Capacity planning dashboards — for studios allocating resources across concurrent projects. For a freelancer, "capacity" is "am I booked this week or not."
• Integrations with project management tools — Jira, Asana, Linear. Useful when your time tracker needs to match a ticket number someone else assigned. Not useful when your ticket system is a Notion doc you wrote yourself.
• Seat-based pricing — makes sense when you're adding teammates. For a freelancer, seat-based pricing means you're paying for the architecture of a team you don't have.

What a freelance designer actually needs from a time tracker

Three things. Exactly three:

1. A timer that rounds correctly. Freelance designers bill in increments — most commonly 0.5h. The tracker needs to round on stop, show you the rounded value while the timer is running (so there are no surprises), and handle manual entry for sessions you forgot to start the timer on. That's it. No project codes, no hierarchies.

2. A label for each session. One field. "Acme — homepage redesign." "Northwind — brand refresh." The label is the project, the client, and the context, all in one field. You don't need a separate client dropdown and a separate project dropdown and a separate task dropdown. You need one text field per session, filled in at the time.

3. Invoice-ready output. The tracker should be able to take a selection of sessions and produce text that drops straight into a FreshBooks / Wave / QuickBooks line-item field. Not a CSV. Not a report PDF. Paste-ready text that a human invoice tool can receive. This is the step that complex trackers almost universally fail at — they track time, but they don't close the loop to the invoice.

That's the whole list. Everything else is overhead.

The features that quietly hurt you

Some complexity is just friction. Some actively costs you money:

Required project setup. Any tracker that requires you to create a project before you can start a timer introduces a tax on starting. The moment you think "I should track this" and hit friction before you can start the timer is the moment you decide to "just track it later" — and then don't. Required setup is the reason most time trackers have a 60% abandonment rate in the first two weeks.

Paywalled invoice export. Several major trackers track time for free but charge you to get the data out in invoice form. This is structurally backwards. The tracking isn't valuable without the output. A tracker that charges for its output is charging you for the thing you actually need.

Mobile apps that require account sync. If your tracker goes offline — because you're on a train, or at a client site with bad Wi-Fi, or in a hotel with a captive portal — and loses your session because it couldn't sync, it's failed its primary job. The session you tracked should live locally first, sync second.

On integrations specifically

The dream of a time tracker that talks directly to FreshBooks or QuickBooks — auto-creating invoice line items from tracked time — sounds compelling. In practice, it almost never works well for solo designers because:

• The integration requires setup, OAuth, and periodic token refresh.
• The field mapping ("which Toggl project maps to which FreshBooks client?") needs maintenance every time you add a client.
• The output format the integration produces rarely matches what you'd write by hand — invoice descriptions become cryptic codes, or every session becomes its own line item instead of being grouped by project.

For most solo designers, a clean clipboard export that you paste in yourself is faster, more readable, and less likely to break than a fragile OAuth bridge to an accounting SaaS. Integrations are for volume — if you're generating 200 invoice lines a week, the automation justifies the setup cost. If you're generating eight, do it by hand with a good clipboard output and spend the saved engineering on client work.

What "good enough" actually looks like

The ideal solo time tracker is one you forget is there. It's open in a tab. You hit Start when you start working, Stop when you stop. You label the session in one field. On Fridays you tick the sessions for each client, click Generate, paste into the invoice. Done.

That's ClockSplit's entire design brief. Not because we couldn't add project codes or approval flows — but because adding them would solve a problem you don't have, at the cost of making the problem you do have harder to solve.

The next time you find yourself configuring a fifth tag in your time tracker, ask whether any of those tags will appear on an invoice. If the answer is no, you're maintaining a taxonomy for its own sake. Delete the tags. Start the timer. Do the work.