Skip to content
Blax Blax Group
Billing · Trust

Every minute, with a note.

We bill our customers by the second, and we write a note for every minute. Open the invoice, see what we did, when, and why. There is no agency math, no rounded hours, no padded discovery phase.

A silver mechanical stopwatch with its chain on a black background.
Fabian Wagner, founder of Blax Software

Fabian Wagner, founder of Blax

Published

ResolutionSeconds
Every minuteCarries a note
Padded discovery phaseNone

How we actually bill

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.

Why notes matter

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.

What this prevents

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.

Where the clock stops

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.

What customers do with 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.
Memory loses against an invoice every time. Notes are accountability twice over.
Why we bill the way we do

More perspectives

Engineering

Why we build WebSocket-first

Guide

PHP 8.2 end of life: move WordPress to PHP 8.4 without the critical error

Guide

Hacked WordPress: the first steps

Guide

What a security check covers, and what it does not

Guide

Website relaunch: when it pays off and how existing URLs keep working

Guide

WooCommerce or Shopify for an Austrian shop

Guide

Accessibility in online shops: what applies since June 2025

Operations

Docker by default, Traefik on top

Operations

Linux everywhere

Business model

Open source by default

Workflow

How we work with AI

Product · Craft

We build for the morning user

How we engage

Built with startups

Curious how this plays out in practice?

These essays are the why. The how shows up in the projects we ship. Drop us a note and we can talk about your specific case.

Build with us Perspectives