04 Time

Several sessions per ticket, billable one by one.

You track time right on the ticket, as often as you work on it. Half an hour on Monday, two hours on Wednesday, every session with its own date and its own description. To bill, you bundle any sessions into a billable line item and attach your invoice number to it.

  1. 01 Any number of sessions per ticket, each with date, duration and description
  2. 02 Reporting grouped by ticket, so you can see when you did what on which task
  3. 03 Filter by billed, in billing, and not yet in any billing run
  4. 04 Billed sessions are write-protected and do not resurface on the next run
  5. 05 A conversation can be the subject of a session too, so the client meeting is billable as well
  6. 06 On request the AI writes the line-item text your client will read, based on what was actually done

What gets billed is the individual session, not the ticket. That is why you can keep working on a task that was billed long ago and simply book the new time. It goes into the next billing run while the old one stays untouched. In many systems this is where it ends.

// Step by step

How this works

01
Record the time

A session belongs to a ticket, to a meeting, or simply to the project. Date, duration, one line about what you did. As often as you work on the thing, without having to split the task for it.

02
Word it for the client

Next to the internal description sits a second field, and that is the only one your client reads. On request the AI writes it from what was actually done. You read it and correct it before the sentence leaves the house.

03
Bundle

Any sessions go into one billing group, across several projects of the same client if need be. Several at once, not one after another.

04
Bill it, then carry on

You enter the invoice number from your invoicing software and mark the group as billed. From then on its sessions are read-only. New time on the same task is unaffected and goes into the next run.

// Honestly

What it does not do

Three things other time trackers do and this one does not. Better you know now than after the move.

  • No stopwatch. You enter date and duration; no clock runs in the background.
  • No amounts. Lalabase knows no hourly rates and writes no invoices. It hands you the line items; the invoice you write where you write it today.
  • No accounting integration. The way out is a CSV file, not a synchronised interface.
// Frequently asked

What people ask at this point

What happens when I keep working on a task that has been billed?
Nothing special, and that is the point. The billed sessions stay locked, you book the new time on the same ticket as usual, and it goes into the next billing run. No need to open a second ticket just to keep the books clean.
Does everyone on the team see everyone else's hours?
Only if you say so. Seven switches per role govern this, separately for own and other people's time and separately for viewing, editing and deleting. The default is that everyone records and sees their own, and not the others'.
How do the hours reach my invoice?
As a CSV file from the billing group, carrying date, ticket number, subject, internal description, client description and duration. Semicolon-separated, so Excel opens it without asking. Time attached to a meeting has no ticket number, and then the column stays empty rather than inventing one.

Look at it
rather than take our word for it.

Productive in under 5 minutes. No sales loop.

Create account See pricing

Particular data protection or compliance requirements? Talk to us. For cases like that we usually find a way.