Loading
Because they are a separate chore with no connection to the work. The task list is in one place, the timesheet in another, and nothing links a logged hour to the thing it was spent on.
So the week is reconstructed from memory and a calendar. The totals are roughly right and the allocation is roughly wrong, which is exactly the wrong way round for billing.
Time logs against a task, which already knows its project, its phase and whether it is billable. There is no second coding step, because the coding is inherited from the work.
Approved time becomes cost against the project and, where billable, a line on the next invoice in Books at the rate the contract holds.
Project margin is live rather than a month-end calculation. A project going over shows while there is still something to do about it.
Estimates get better because estimated and actual hours sit on the same task, so the gap is visible per person and per kind of work rather than as a company-wide average.
It does not watch anyone. There is no screenshotting, no idle detection and no activity scoring — it records what people say they did, which is the only figure worth billing from.
It also will not approve its own timesheets. Submission and approval are separate, because the approval is what makes it billable.
Nothing here is an integration. Each line is two products reading the same record from different sides.
Time logs against a task, which already knows its project, its phase and whether it is billable. There is no second coding step, because the coding is inherited from the work.
Project margin is live rather than a month-end calculation. A project going over shows while there is still something to do about it.
It does not watch anyone. There is no screenshotting, no idle detection and no activity scoring — it records what people say they did, which is the only figure worth billing from.
Fourteen days, every module, no card. Or half an hour with someone who will run it on your own records and tell you where it does not help.