How Freelance developers use Temporal.ist
Per-repo billing
Configure one watched path per client. Sessions get tagged by project automatically. End-of-month invoicing is filtering by client and clicking 'create invoice from sessions'.
Async client demo trail
Show clients a per-session activity log: which files were touched, which PRs reviewed, total focused minutes. More informative than a screenshot, more truthful than a manually-typed timesheet.
Side-project vs client work
Excludes paths you don't want tracked. Your weekend FOSS work doesn't get billed to anyone — it just doesn't show up.
- Edit a file → a session starts. Switch repos → a session switches. No timer to start.
- Per-repo and per-branch attribution makes 'how much time did the Dunder Mifflin refactor take?' answerable in a glance.
- Invoicing is in the same tool — generate a draft from last month's sessions, edit, send.
If you ship code for clients, you've reconstructed a week from git log more than once. Temporal.ist exists to make that the exception, not the routine.
Built for freelance developers
You bill by the hour. You context-switch between three repos a day. You end Friday with a vague memory of the week and a bill to write. Temporal.ist watches the directories you tell it to (~/code/clients/* is the obvious one) and creates sessions as you actually work. The browser extension catches the time you spend in GitHub PR reviews, Linear tickets, and stack-overflow rabbit holes. At the end of the month you don't reconstruct — you review.
Pricing for freelance developers
Free during early access while we figure out fair pricing. We won't charge per-seat for solo freelancers in v1.