Stop Working for Clients for Free

You have almost closed the project. You open the client’s message - and there it is: “Everything is great, just one more small thing.” Then comes a clarification, a request to change the format, add an option, and quickly explain how to use it. Each item seems small on its own. Together, they eat up an evening you had already found better work for.

At this point, it is easy to get angry with the client or with yourself. But more often than not, the problem is not anyone’s bad intent. The person sees the result and thinks a nearby change changes nothing. You see the new actions, responsibility, and time behind it. If this was not named at the start, both sides are relying on guesses. And guesses are the weak point of any project.

Unpaid work usually builds up not through one large request. It arrives as a series of exceptions that feel awkward to answer with: “That is separate.” First, you want to be attentive. Then you do not want to spoil the mood. Next, you hope this is the last request. And in the end, it turns out that your price covered only part of what you did, and you are tired not of the work itself, but of the missing boundary.

The way out is neither a harsh tone nor suspecting manipulation in every request. A client may sincerely not understand how many actions stand behind their idea. The way out is a simple rule: an agreement should describe not only the price, but also the result, the boundaries of the work, and how changes are approved.

First, separate your own mistake from a new request. If you did not do what was agreed, missed an important detail, or made a mistake in your part of the work, you should not sell the correction as an extra service. This is not a concession to the client, but the normal completion of an obligation you took on. Here, it helps not to look for a formal loophole, but to honestly compare the result with what you promised.

It is different when the result matches the agreement, but the client wants a different direction, a new feature, an additional format, or a new task. Scope of work is the list of actions and results you agreed to be responsible for in a specific project. When it changes, it is worth pausing and clarifying the terms, even if the new idea seems appealing.

Ask yourself not “how long will this take,” but “what exactly will the client receive after this request that was not there before?” This keeps the conversation from becoming a bargain over minutes. You see the change in the result. A new section on a page, another version of a material, an additional instruction, a new communication channel - all of these can be a separate part of the work if they were not in the original agreement.

When the order of work changes

Sometimes the boundary runs through urgency. The same result may remain within the service, but a request to deliver it outside the usual order changes your workload and the order of your other tasks. You do not have to refuse right away. It is enough to say honestly that the new deadline needs to be agreed separately, rather than silently moving everything else.

A hypothetical example: you are creating a website for a small business. The approved description includes a page, a contact form, and text the client provides before work begins. After seeing it, the client asks you to add a separate section for a new service, develop its content, and make one more page. This is not “an edit at the bottom.” The result you need to deliver has changed. So first describe the new part: what materials are needed, what exactly you will do, and what result you will deliver. Only then name the price and move on to execution.

Consulting also often quietly becomes unpaid work. Briefly explaining where to find a file or how to accept an already finished result is part of good service. But if the conversation turns into reviewing a new situation, choosing a course of action, or preparing a solution, you are already giving separate value. Usually, it is better to name this directly than to silently accumulate irritation and then respond sharply where you could have responded calmly.

You do not need a complex document. It is enough to briefly confirm the terms in writing in a message, email, or the project itself, so you do not later argue about who remembers what.

Write four things in plain language: what exactly you will do, what result the client will receive, what is not included in this price, and how you approve changes. This makes the agreement a shared point of reference before the start. Approval is the moment when the client looks at an interim or finished result and confirms the direction. It is needed not for bureaucracy, but so that new ideas do not get mixed with the old task.

Instead of “we are doing design,” it is better to write: “I will prepare the layout for the home page and the services page. After the first version, I will collect your comments in one message. Changes that add new pages, new sections, or change the approved direction are agreed separately.” This text does not assume conflict. It removes the empty space that each person would otherwise fill in their own way.

What else is worth documenting

Also add what you cannot start or finish the work without: materials from the client, an answer to a question, access, or approval. This is not an attempt to shift responsibility. It is a way not to pretend that the result will appear by itself while one side is waiting for the other. A broken process especially loves the phrase “I thought you already had everything you needed.”

As a rule, boundaries are easier to name before the start, when nobody has yet become emotionally invested in a specific solution. You are not justifying the price after the work is done, but communicating the order of cooperation. The client understands they can ask for more, but it will be a separate agreement, not an awkward last-minute request.

Do not try to predict every possible request. That will make the text heavy and still will not cover real life. It is better to describe the boundary by meaning: a new result, a different direction, additional material, a new channel, an urgent format, or extended consulting. If it is unclear to you where that boundary is, it will not be clear to the client either.

A new request does not require an immediate “yes” or a sharp “no.” Your first task is not to decide under the pressure of a message, but to understand what exactly it is about. Restate the request in your own words. Then compare it with the short project confirmation. If the request was already in it, say when you will complete it. If not, explain what has changed and offer separate terms.

A useful sequence is simple:

1. Thank the client for the clarification and briefly restate it in your own words.
2. Say whether it is part of the agreed result.
3. If it is not, offer a separate price or another option: postpone it, simplify it, or add it to the next project.
4. Start the new part after the client confirms their choice in writing.

What matters here is not a beautiful phrase, but the link between the request and its consequence. It is usually easier for a client to accept an additional fee when you show not an abstract “this is paid,” but a specific change in the result: there is a new page, another version, additional material, or a new solution that was not in the original agreement.

A hypothetical example: you manage social media for a coffee shop. The client approved topics for the month, then in the middle of the work asks you to urgently prepare materials for opening a new location. This may be an important event for the business, not an attempt to load you with unpaid work. But for you it is a new task: a different topic, new materials, new approvals, and a different priority. A calm response could sound like this: “I see that the opening needs support. It is not in the approved plan, so I will separately describe what I will prepare for the launch and send the price and deadline. I will take it on after confirmation.”

If the client is not ready to add work now, that does not mean the conversation has failed. You can suggest leaving the current result unchanged, replacing one part with another, or returning to the idea in the next project. You are not punishing the client for initiative. You are giving it a clear path and not making yourself work blindly.

When you are nervous, you may want either to write long explanations or postpone your answer. Having a few phrases of your own is useful: they help you avoid automatically promising too much. Adapt the words to the way you speak, but keep three parts in them: what changed, what you offer, and what needs to be confirmed.

For an additional revision: “I can make this change. It goes beyond the approved version because it changes an already approved direction. I will send separate terms, and after your confirmation I will make the revision.”

For a new task: “This is a useful addition, but it was not in the current project. I can take it separately: I will describe the result, price, and deadline so everything is clear.”

For a request for an exception: “I understand why this is important right now. This kind of work is not included in this service, so I will not be able to add it for free. I can offer a separate option or suggest what from the current scope would be better to replace.”

Do not apologize for the very existence of terms. Politeness is not agreement to any scope. At the same time, do not hide behind a categorical “those are our rules.” Explain specifically what has changed for the work and show the next step. This sounds more human and leaves the client a choice.

If you do not have an answer immediately, do not invent one on the spot. You can write: “I will compare this with the current project and come back with an option.” This pause does not make you less helpful. It protects you from an accidental promise you will later have to fulfill with your own evening.

If you keep adding the same type of work for free, do not blame it only on difficult clients. Perhaps your service is described too broadly. Or its price already hides a regular part that you did not name separately. Repetition is a reason to look not at the last message, but at your offer as a whole.

For example, clients constantly ask you not only to hand over finished material, but also to teach the team how to use it. This is not necessarily “small help after completion.” In your practice, this need may mean it is worth making the explanation a separate service or including it in a more expensive service package. A service package is a named set of work with defined boundaries, not a bag of “turnkey” promises.

Review several recent projects and write down recurring additions: what exactly clients ask for after the main work, when it appears, and whether almost all clients want it. Then choose an honest option for each such item. Either it is part of the service and should be named in its price and description, or it is separate work with a separate agreement. Do not leave it in a grey area just because that feels more familiar.

The same applies to a team. If the client writes not only to you, but also to a manager or contractor, the rule needs to be shared: nobody promises new work before checking the agreement. Otherwise, the client hears different answers, and the team learns to save the situation with its own time. Agree even on a simple pause phrase: “I will check how this relates to the current project and offer an option.”

When manual messages, confirmations, and recurring replies become too many, setting up a simple process for recording projects and rules can help bring them together in one place. But first you need to decide the substance: no tool will determine for you what is included in your service and what additional work you are ready to take on.

Today, choose one service you sell most often. Write a short confirmation for it: the result, what is not included, how changes are approved, and a phrase for additional work. Send this text to the next client before the start. This is the first step after which you will no longer have to invent the boundary every time your evening has almost disappeared.