This can happen even when both sides have worked in good faith. For the client, continuing the conversation may mean finishing what was already included. For the delivery team, it may mean a request to extend the work. The difference needs to be clarified while we can still choose what to do.
Predictable collaboration links the request, the estimate, the approval and the delivery in one shared record. That way, the client understands what they are buying and the team knows what responsibility it has taken on.
There is more than one kind of “yes”
“We like the direction,” “you can start” and “this is the final version” can confirm different things. It helps to treat them separately when organizing the project.
| What is approved | What it clarifies | What may still need deciding |
|---|---|---|
| The direction | The idea, structure or solution being pursued | The volume, cost and timing of the execution |
| The work and commercial terms | What gets done, within which limits and on what pricing basis | Any requirements that come up later |
| The final delivery | The version accepted for the agreed use | Publication or other uses, if they are approved separately |
These distinctions are an organizational practice. The concrete form of an approval and its effects depend on the agreement between the parties. A simple project can have a single confirmation that explicitly covers all of them. What matters is that its meaning is shared.
The estimate, the cap and the time spent play different roles
An estimate describes the expected effort based on the information available. A cap sets the limit within which the team is authorized to work. Time spent records the work done. A fixed price sets an amount for a defined delivery. These notions do not automatically replace one another.
A fictional example. An update is estimated at three to four hours. The client confirms the work within a limit of four hours, with a check-in before going over. Later, they ask for two additional pages. The team can explain the impact and propose an extension, a smaller delivery or a phased approach. The fact that the pages were requested does not make clarifying their cost unnecessary.
If the work is billed on time spent, the record should reflect the time worked according to the agreed rules. If it has a fixed price, the invoice follows that agreement, including how changes are handled. If reserved capacity or a package is being bought, we explain what it includes and how it is used. The client should be able to identify the model before comparing the estimate with the invoice.
Several people can contribute, but the decisions need to meet
It is natural for marketing, sales and management to have different perspectives. The problem starts when each sends a separate direction without knowing what the others have asked for.
One person responsible for consolidating feedback can prevent contradictory versions and unnecessary rework. Separately, we need to know who can approve a change in cost or timing. The person who checks a piece of copy is not necessarily the person who approves the project budget.
The delivery team has a responsibility too: to flag contradictions and not choose arbitrarily between incompatible requests. A simple question can clarify the situation: we have two different directions; which one is approved, and who confirms the impact on the work?
The quick channel can stay quick
WhatsApp can be useful for a question or an emergency. Email can more easily keep a decision with several participants. A project tool can centralize versions and responsibilities. The choice depends on the collaboration.
What we need is an agreed place where the final decision is easy to find. A quick conversation can be followed by a short summary: the request, the delivery, the estimate or cost, the deadline and the person who confirms. Nobody should have to reconstruct every message at the end of the month.
Sending materials or continuing to give feedback can show a wish to move forward. As a working practice, it is safer and clearer to also state the commercial impact, rather than assuming everyone has understood it the same way.
A change can be accepted, reduced or postponed
Clarification does not have to stall the project. It creates options. If a request exceeds the resources, the client can decide what is a priority now and what can follow in a later stage.
For recurring work, there can be categories and limits approved in advance. For emergencies, we can agree on who decides, which interventions are covered and when an extra cost applies. These rules are chosen in proportion to the project; changing a line of copy and developing a feature do not need the same procedure.
Urgency does not remove the need for clarity. It makes a rule prepared in advance useful. If prioritizing means reorganizing the team or a different rate, that condition is communicated before the work is taken on, in line with the collaboration.
The invoice should close a record everyone already knows
A useful summary links the work to the requests and the relevant approvals. It shows what was included, what was additional, what was delivered and how the amount was calculated. Effort absorbed voluntarily, or material provided at no cost, can be shown separately without becoming a future obligation for the client.
Documented time and documented approval answer different questions. If a misunderstanding arises, we check them separately, together with the agreement and the deliveries. We do not reconstruct an unclear agreement after the fact, and we do not assume that what is missing from a single message describes the whole project.
How we work with this kind of clarity
NOT MORE. can take on the consulting, strategy, creative work, development and implementation needed, including alongside an in-house team or other agencies. For the agreed part, we define the deliverables, the responsibilities and how changes are handled. The client confirms the priorities, the resources and the people who can decide.
We can also start with a clear task that is already well founded. The clarity needed is proportional to what we take on. Its role is to make good execution possible and to support a relationship in which both sides know what to expect.
Continue with “A small change. What does it actually involve?” for the difference between adjustments and extending the work, and with “Pricing starts with the problem to solve.” for the link between the need, the size of the project and the resources.