Sprint and time tracking for agencies
Client work lives or dies on where the hours actually went. Time tracking is on every issue, not in a separate tool.
Agency delivery has a problem product teams do not: the same week has to be legible to the team, to the client, and to whoever raises the invoice. Most agile tools solve the first and leave you reconciling spreadsheets for the other two.
What usually gets in the way
- Time tracked in one system, work tracked in another, and the two never agree
- No clean answer to "what did we spend on this project last month?"
- Per-project visibility that requires an admin to set up each time
- Clients asking for a status view you have to assemble by hand
Estimates and actuals in the same place as the work
Every issue carries an original estimate, logged work and remaining time. Because it is on the issue rather than in a parallel timesheet tool, the numbers describe the same reality the board does.
- Original estimate, time logged and time remaining per issue
- Time reports per project and per person
- Exports in CSV, JSON and PDF for billing and reconciliation
Several projects without several setups
Each client project gets its own board, backlog, statuses and permissions, while roll-up reporting stays available across them. Projects are separated without each one becoming a configuration exercise.
- Unlimited projects on every plan
- Per-project roles and permissions
- Org-wide analytics and executive reporting on Business
Access control that respects client boundaries
Client work carries confidentiality obligations that internal product work usually does not. Access is enforced on the server for every request, not hidden in the interface, and Business adds issue security levels and custom roles for finer separation.
- Every record scoped to an organisation
- Project-level roles and granular permissions
- Audit log recording old and new values, on Business
Common questions
Can clients be given access to only their project?
Yes. Access is granted per project, and authorisation is checked server-side on every request rather than enforced only in the interface.
Does time tracking handle billable versus non-billable?
Not as a dedicated flag. Time is recorded as estimate, logged and remaining per issue, and exported for whatever your billing process needs. If a billable flag is essential, this is worth raising with us before you commit.
Can we export time data for invoicing?
Yes — CSV, JSON and PDF exports are available on every plan, at any time.
Coming from Jira?
Most teams reading this are already running something. Our honest comparison against Jira covers where Jira is still the better tool and exactly what our importer does and does not carry across.
Move your team over this week
Create a project, pick your statuses, and have your first sprint running the same afternoon.
Cancel any time · Export your data whenever you like