The Work You Do After the Invoice That Kills Your Rate

You finish the work. You send the invoice. You move on.

Then the client has questions about the delivered file. Then they need a small tweak that takes thirty minutes. Then they forward the deliverable to their own client and come back with three new notes.

None of this was in the quote. None of it was in the invoice. And because the invoice is already sent, you do nothing with it.

This is one of the most common places freelancers quietly lose money, and it is almost invisible because by the time it happens, you already feel done.

Why Post-Invoice Work Gets Swallowed

Invoicing creates a psychological close. The project feels finished. You are already thinking about the next thing. When a request comes in after the invoice, your brain categorizes it as follow-up, not work.

So you handle it without opening your time tracker. You fire off a quick answer or make a fast fix and get back to whatever you were doing.

Multiplied across ten clients over a year, that is a significant amount of billable time that simply never appears anywhere.

What Types of Work Show Up After the Invoice

It is usually one of a few things.

Implementation questions. The client received the thing you made and now needs help using it. If you built a website, they want to know how to update a page. If you wrote a document, they want to know how to format it for their system.

Minor amendments. Something small changed after delivery and they want the file updated. Quick, sure. But not free.

Handoff calls. You delivered remotely and now they want a call to walk through it. That call is often thirty to sixty minutes of your time.

Feedback on their feedback. They showed the work to someone else and are relaying second-hand notes. Working through those takes time even if the edits themselves are small.

How to Track It When It Feels Awkward

The discomfort usually comes from not knowing if you should bill for it. So instead of deciding, you just do the work and move on.

But tracking and billing are two separate decisions. You can always log the time first and decide what to do with it later.

Open the timer, log it to the client project, and add a note. Post-delivery support. Handoff call. Amendment request. Now you have a record.

At the end of the month, you can look at that record and make a real decision. If it was twenty minutes across the whole project, maybe you absorb it. If it was four hours, you probably should have invoiced for at least part of it.

You cannot make that decision without the data. And you cannot get the data if you never started the timer.

How to Prevent It at the Project Level

The cleanest solution is a clear scope that spells out what happens after delivery. Something like: delivery includes one round of implementation support up to thirty minutes. Additional support is billed at your standard rate.

When you have language like that in place, the conversation is easy. You are not inventing a charge after the fact. You are pointing to something both parties already agreed to.

Your time logs will back you up either way. If the post-delivery support was small and you are absorbing it, you have documented evidence of that generosity. If it was substantial, you have the hours to support a supplemental invoice.

The Habit Worth Building

Keep the project open in your time tracker until you are genuinely done. Not done-invoice-sent done. Done as in no open threads, no pending questions, nothing outstanding.

That might be a week after you sent the invoice. Sometimes two.

Log everything in that window. Even if you never bill a single hour of it, you will start to see the pattern. You will know which project types generate the most post-delivery time. And that information will change how you quote the next one.

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