The Client I Billed From a Text Message

The project started with a text.

Not a contract. Not a brief. A text message that said something like "can you help me sort out my site, shouldn't take long."

I said yes. I started working. I did not open my time tracker.

What I Was Thinking

It felt too small to formalize. A few hours here, a few there. I knew roughly what I was doing. I figured I would pull it all together at the end and send something reasonable.

That is a sentence I have regretted more than once.

The project ran three weeks. "Shouldn't take long" turned into a new page layout, three rounds of copy edits, a plugin conflict I spent six hours debugging, and two calls I never billed for because I forgot to write them down.

At the end, I sat down to invoice. I had a text thread, a few browser tabs still open, and a vague memory of working a lot.

I sent an invoice for twelve hours. It felt like I had worked closer to twenty-two.

The Math I Could Not Do

I had no data. I could not argue with myself, let alone with the client. Twelve hours felt defensible. Twenty-two felt like I was guessing upward and hoping nobody noticed.

So I billed twelve. The client paid. I moved on.

A week later I found a note in my phone with a list of tasks I had completed that I never put on the invoice. Stuff that took real time. Stuff I had just quietly done and then forgotten.

I had billed ten hours less than I worked. On a text-message project I thought was going to be simple.

What Actually Fixed It

I started running a timer the moment a client sends anything that resembles a request. Even a text. Especially a text.

Not because I am paranoid, but because informal projects have a way of expanding in the gaps between conversations. The work happens. It just does not get recorded anywhere unless you make a habit of recording it.

Time-Trak has a floating timer widget that sits on your screen. It is small enough that it does not get in the way, but visible enough that you actually start it. That visibility matters more than any feature list. If you have to go find the tool, you will not use it when things feel small and fast.

I also stopped using "project" as a mental category that required formality before it counted. If someone asks me to do something, that is a project. It gets a timer. It gets entries. It gets an invoice line.

The Habit Change

I now log the first minute of any new request as "intake," even if the whole thing takes thirty minutes total. That forces the tracker open. Once it is open, I keep logging.

It sounds fussy but it takes almost no time. What it saves is the end-of-project reconstruction where you try to remember what you did across three weeks based on a text thread and browser history.

You will never reconstruct it accurately. Nobody does. You will either undercharge because you cannot prove what you did, or you will overcharge and feel guilty about it. Neither is a good place to build a client relationship.

The Real Cost

That twelve-hour invoice versus twenty-two hours of actual work is not just ten hours of lost billing. It is a number that trains you to quote that kind of project too low next time.

You internalize bad data. You think the project cost twelve hours because that is what you charged. So next time someone asks for something similar, you say sure, it is about twelve hours.

And then you do it again.

The text message that started that project cost me more than one invoice. It reset my mental price for a whole category of work. Good data fixes that. A timer running from the first reply is where good data starts.

Track your time, bill every minute.

Time-Trak is a native Mac and Windows time tracker with a floating timer, automatic screenshots, and one-click invoicing.

Free during beta.

macOS + Windows · Floating widget · Auto screenshots