Every hour you bill,
every dollar your agents burn
Every billed hour points at a real commit, priced at the rate in force the day it was worked. Agent spend lands in the same margin, against the task it served, from the day the task was created to the day it shipped, so you can decide what to quote, what to cut, and where AI is actually pulling its weight.
Which hat do you wear?
Hours you can trace back to code
Every hour on the invoice points at a commit with a timestamp behind it. Nothing is reconstructed from memory at the end of the month, so the number you bill is the number that happened, and you can show a client exactly where it came from.
Put a price on every hour
Give each job role a sell rate and a cost rate, and every hour logged carries both: what you bill for it, and what it costs you to deliver it. That spread is what turns a timesheet into a margin.
Catch the overrun while it's still fixable
A budget and a target margin per project, drawn down automatically as hours and agent spend land. You find out a job is under water in time to renegotiate, not when the invoice fails to cover what it cost.
Put AI on the P&L, not the card statement
Model bills arrive as one lump sum with no idea which client they served. Clocktopus attributes agent spend to projects, tasks and people, so AI becomes a cost of delivery you can price into a quote instead of overhead you absorb.
Every task priced from idea to production
Each task carries the human hours and the agent spend that went into it, from the day it was created to the day it reached production. You see what a feature actually cost to deliver and how long it took, instead of reconstructing it from invoices and a board nobody kept current.
- CreatedCreated in Linear
- In progressAgent session on apo-171-export-invoices
- In reviewPull request #48 opened
- Ready to ship#48 merged into develop
- DeliveredWaiting to reach main
Built for teams, priced for them too
Unlimited organisations and projects, clear roles, and per-project access so commercially sensitive work stays with the people delivering it. You pay per seat, never per feature. Everything on this page is on every plan.
The numbers behind the invoice
Per-project and per-person breakdowns priced at the rates in force, agent spend in the same view. Enough to bill a client, plan next quarter, or work out that a retainer is not worth renewing.
Know whether delivery is getting better
Hours tell you what a quarter cost; these tell you how the work moved. Review turnaround, rework and the mix of quick wins against heavy lifts, so you can tell a team that needs more people from one that needs fewer interruptions.
One command sets up every agent on the team
clocktopus agent setup gives Claude Code, Codex and OpenCode the skills and the MCP server in one step, so every session is tied to its task before it changes code. Agent spend lands on the work it bought instead of in an unattributed pile, without anyone being asked to tag it.
The tracking tool people don't quit
Time tracking fails when it demands a habit nobody wants. This one lives inside the terminal your developers already work in, which is why the data still arrives in month six.
Ask the business a question, get an answer
Connect your assistant to Clocktopus alongside your other tools and ask which clients are profitable, which projects slipped, and where the AI spend went. No dashboard to learn, nobody to brief.
APO-142 and APO-156 are over estimate (14.5h vs 6h, 9h vs 4h). The other 6 tasks are tracking on time.
Hours that stay inside a working day
A clock-in and a clock-out bound every day, so tracked time never drifts into numbers you'd have to defend to a client. Nobody bills fourteen hours because they pushed once before bed.
Free for single developers.
Per-seat when the team grows.
Every feature above is included on every plan.