Every minute, with a note.

A time tracker runs while we work. When the timer starts on your project, a note describing what we are about to do is required, not optional. When it stops, the note is final and goes into your invoice. We can produce the line items for any month in plain language: "Tuesday 09:14 to 09:31, scoped the new permissions table; 09:31 to 09:47, drafted the migration; ...". If you want to read what happened in three minutes on the 14th, you can.

Notes are accountability twice over: they let you challenge an entry that does not match what you saw on the demo, and they let us remember why we billed that block six months later when you ask. Without notes, both parties end up trusting their memory against an invoice with hours and totals. Memory loses every time.

Rounded-up half-hours. Sandbagged estimates. A four-week discovery phase that exists because someone has to pay the agency rent. The kind of contract where the deliverable is a Gantt chart, not software. We bill the work, not the time we could have padded the scope into.

While we extract a reusable piece of our code into a package on Packagist, the clock is off (see Open source by default). Same for tooling that lives on after the project, internal documentation that benefits future Blax customers, or quick fixes obvious in hindsight. If the work is ours, you do not pay for it.

They read it. We have customers who have never opened an invoice line item, and we have customers who walk through every block and ask follow-up questions on the entries that surprised them. Both are fine. The point is the option is there, in plain language, every month. It is one piece of the broader operating playbook; the rest is on the services page.