Project management, timesheets and invoicing for software agencies
An agency sells developer hours against a scope the client keeps changing. Clock Clerk keeps the board, the conversation with the client and the hours in one place, so the invoice at the month end is built from what the board already shows.
Thirty days of the Team plan, no card.
Three tools, and a reconciliation every month
Most agencies plan sprints in Jira or Trello, talk to the client in email or a shared chat, and collect hours in a time tracker or a spreadsheet. Each holds part of the truth. At the month end somebody matches hours to tickets by hand, chases the developers who did not log, and works out which of the hours are billable before an invoice can go out.
The cost is not only the afternoon it takes. A ticket that ran over its estimate is noticed after it is billed, the client's agreement to extra scope is buried in an email thread, and an hour edited after the invoice went out quietly makes the two disagree.
The card you move is the task you bill for
A board per client project, logged against directly.
Every project has a board with columns named your way. Each card is a task on the developers' week sheet, so the hours land on the card and its bar fills against the estimate as they do.
- Import the sprint from Jira, Azure DevOps, Trello or Notion, with their columns and people mapped onto yours.
- Estimates in view. A card shows hours logged against its estimate, counting everyone's time on it.
- A thread on every card, and a project thread for everything else; type # to point at a task and @ to bring somebody in.
A project's board: cards in Backlog, In progress, In review and Done, each showing the hours logged against its estimate and who is on it.
Approved hours become the client's invoice.
Developers file their hours a month at a time and their manager approves each filing. Finance picks the client and the month, and the draft is made of the approved, billable hours at your rate card.
- Rates at four levels, from a standard rate down to one developer on one project.
- Billed hours are locked, so the timesheet and the invoice cannot drift apart.
- Threads shared with the client, where they ask about the go-live and see nothing else of yours.
Team and Enterprise
The invoices list: each invoice with its customer, its status, from draft and sent to part paid, overdue and paid, and its amount.
What it does not do
Clock Clerk replaces the time tracker and the invoicing step, and can replace the board. It is not a full engineering platform, and these are the gaps an agency usually asks about.
Imports, not a sync
Tasks come in from Jira, Azure DevOps, Trello or Notion once, as a copy you pick. Nothing is written back, a later change in the tracker does not reach the card, and descriptions are not brought over.
No timer
Hours are typed against a day, or stepped up a quarter-hour at a time in the day view. There is no stopwatch to start and stop.
No sprints, story points or code links
A board has columns and cards with an estimate in hours. There are no sprints, velocity charts, story points or links to commits and pull requests.
No files in threads
Messages are plain text. Specs, designs and screenshots stay wherever you keep them today.
Invoices in US dollars, one tax rate
An invoice carries one flat tax rate and is written in US dollars. There is no tax engine, no other currency and no online payment page for the client.
Which plan includes it
Boards, threads, the week sheet, approvals and rate cards are on every plan. Client threads start on Starter; invoicing, task imports and export to QuickBooks are Team.
| What is included | Free | Starter | Team | Enterprise |
|---|---|---|---|---|
| Price | $0 | $3 per filer / month | $6 per filer / month | Talk to us |
| Project boards with your own columns | ● | ● | ● | ● |
| Project and card threads, direct messages and mentions | ● | ● | ● | ● |
| Approvals per filing, with send-back reasons | ● | ● | ● | ● |
| Per-person and per-project rates | ● | ● | ● | ● |
| Discussion threads shared with your clients, with guests invited by email | ○ | ● | ● | ● |
| Import tasks from Azure DevOps, Trello, Jira and Notion | ○ | ○ | ● | ● |
| Invoices from billable hours, with payments and locked hours | ○ | ○ | ● | ● |
| Export hours and cost to QuickBooks Online and Desktop | ○ | ○ | ● | ● |
Reviewers, administrators and finance readers are free on every plan; Starter and Team charge only for the people who log hours that month. Compare plans in full
Asked while evaluating
Does the board replace Jira or Trello?
It can. Where the engineers stay in Jira, Trello, Azure DevOps or Notion, link the project to it instead and import their items as cards, so the hours are still logged against the work they track.
Can we bill a fixed-fee project?
Yes, though the fee is set by hand. A fixed-fee project is still drafted from its hours at your rate card; the fixed-fee template prints only a description and an amount, and manual and discount lines bring the amount to the agreed fee. Nothing yet compares the fee with the hours as the work goes on.
Do our developers pay for the board?
Only the people who log hours in a month are charged, once each. A project manager who only moves cards, approves and talks to the client is free.
Bill the client for the work your board already shows
Thirty days of the Team plan, no credit card required. When the trial ends, your data stays and stays readable. Start with your work email and set a password from the link we send you.