A structure that fits your org — not the other way around.
Customer, project and task form a clear hierarchy. Freely named, two or three levels deep. Billability and rates inherit top-down — and can be overridden at any level.
Three levels, clearly separated
As flat or deep as you need.
Customers
The top level. Sets the default billability and default rate that projects inherit.
Projects
Belong to a customer. Can carry their own rate and billability — or simply inherit from the customer.
Tasks
The finest level. Billability controllable per task — e.g. internal meetings on a paid project.
Inheritance with override
Values flow customer → project → task. You always see where a value comes from — and can change it anywhere.
How it works
Create customers
With a default billability and optional rate as the default for all their projects.
Projects & tasks
Projects per customer, tasks per project. List or grouped view, collapsible.
Track & analyse
Time entries land cleanly in the hierarchy — and can be reported at any level.
Frequently asked
Do I always need three levels?
No. Two levels (customer · project) are enough if you don’t need tasks. The third level is optional.
Can I rename the levels?
Customer, project and task are freely named so they fit your industry.
How does billability work?
It inherits customer → project → task and is taken as the default on each time entry — overridable per entry.
Where do I set rates?
On the customer as a default and optionally per project. The resolution project → customer → workspace is shown transparently everywhere.