When You Finish a Project but Stay On Call

I delivered the project on a Friday. The client signed off. I marked it complete and moved on.

The following Monday they emailed with a question about implementation. I answered it in five minutes. Fine.

Tuesday, another question. Wednesday, a call to walk through something. Two weeks later, I had spent several hours supporting a project I had already closed.

None of it was on an invoice. I hadn't thought of it as billable. The project was done. Except I was still working on it.

The Post-Delivery Tail Is Real

Almost every project has one. Especially anything involving a handoff, a launch, or implementation on the client's side. They try to apply your work, run into something they don't understand, and come back to you.

This is natural. It's also uncompensated if you haven't planned for it.

The post-delivery tail is different from scope creep. It's not new requests. It's support around what you already built. But it still takes your time. It still pulls you out of other work. And it accumulates fast when you have multiple clients all expecting it from you simultaneously.

What You're Actually Agreeing To

When a client treats post-delivery questions as part of the project, they're not wrong to want that. What's missing is your agreement to provide it, and a clear boundary around how much of it is included.

Most freelancers don't define this upfront because it feels presumptuous. You haven't even delivered yet and you're already planning the exit. But the clients who ask the most post-delivery questions are often the ones you least expected to.

How to Track It Even When You Don't Bill It

Start a support log as soon as a project is delivered. Every email you write, every call you take, every file you open. Track it the same way you tracked the project itself.

Time-Trak's timer widget makes this frictionless. You're not building a case against the client. You're just keeping a record. After a few months, you'll be able to see how much post-delivery time each project type generates.

Some projects trail off in a day or two. Others produce weeks of follow-on time. That's information that should change how you quote and scope future work.

Three Ways to Handle It

First, include a defined support window in your contract. Something like two weeks of implementation support included, anything after that billed at your hourly rate. This sets an expectation before it's needed.

Second, offer a maintenance retainer. Some clients will buy it. The ones who ask the most questions often will, because they already know they rely on you.

Third, if you don't charge for it, at least track it. When you quote a similar project next time, you'll know that the delivery price needs to include the support tail, even if it's not a separate line item.

The Clients Who Never Let Go

There's a specific client type that never truly closes a project. Every deliverable becomes a conversation that continues indefinitely. If you're not tracking time after delivery, you don't know who those clients are. You just feel vaguely drained by them without understanding why.

Your time logs will show you. One client produces five post-delivery hours a month across a string of supposedly completed projects. Another asks one question and disappears. The difference is significant over the course of a year.

That data is only available to you if you tracked it. And that's only possible if you kept the timer running after the handoff email went out.

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