For the client, it is natural to judge a change by what they see. For the team doing the work, the responsibility is to explain what needs to be done and why, in language concrete enough to support a decision.
The visual size of a change is not a complete measure of the effort. Effort is assessed by the requirement, the dependencies, the uses and the checks needed. All of that effort also has to be organized efficiently, not used to justify any amount of time.
First, we establish what kind of change it is
Before talking about hours, it is worth clarifying how the request relates to what was agreed. An implementation mistake, an included revision and a new idea start from different places.
| Situation | What we check | What needs explaining to the client |
|---|---|---|
| The delivery does not meet the agreed requirement | The gap against the brief and who is responsible for correcting it | How and when we fix it; we do not automatically present it as an additional request |
| Feedback during the revision stage | The limits and uses already included | How we apply the consolidated feedback |
| The approved direction changes | What can be reused and what has to be redone | The impact on the work and the timeline |
| A new use appears | The formats, features or channels being added | Which adaptations and checks are needed |
Commercial rules are set within the collaboration. The table helps the conversation; it does not decide on its own who pays for each intervention. A professional team explains the differences and takes responsibility for its own part.
The work can extend beyond the file being changed
A fictional example. A brand asks to replace the main photo on a page. The image is already approved and has the resolution needed. In this case, the work may include preparing the file, updating the page and checking how it displays.
Then the request changes: the product has to be shown in a different context, the image has to work on the page and in ads, and the text must stay legible in every composition. Now there is image selection or production, framing options, adaptations and separate checks.
The first version should not be padded with unnecessary steps, and the second should not be reduced to pressing a button. The estimate has to describe the work actually needed in that situation.
Dependencies change the size of the project
On a website, the same piece of information can feed several pages, filters or integrations. If we change a name, we need to know whether it is only visible text or also identifies a category used by other components.
In a campaign, a revised offer may require updates to the materials, the landing page and scheduled communications. The checks are there so people do not receive contradictory information.
Having these dependencies does not mean every change is complex. A well-organized implementation can greatly reduce repetitive effort. If every simple update becomes expensive, the system we work in is also worth reviewing: there may be a reusable component or an automation that would solve the cause.
Iterations need a clear question
A creative process can include attempts, selections and adjustments. They make sense when they pursue a direction or solve an identified problem. “Let’s try something else” becomes hard to estimate if we do not know what we want to improve.
Useful feedback describes the problem and the context: the product is hard to recognize, the offer cannot be read on mobile, the mood does not support the positioning, the comparison between versions is unclear. The team can then propose solutions and explain its choices.
When several people review the same delivery, consolidating their comments avoids contradictory rounds. It is not a request to limit the client’s involvement. It is a way to turn contributions into a direction the team can implement.
Fast tools should reduce the work where they can
An AI tool or an automation can speed up part of the process. We still have to assess whether the result fits, whether the information is correct, whether it is consistent and which uses it needs to serve. The time it takes to generate something does not always describe the whole delivery process.
At the same time, the efficiency gained has to be treated honestly in the commercial model. When billing on time spent, the record follows the time worked under the agreement. With a fixed price, the client buys the delivery and the agreed terms. We do not mix the models only when one produces a result more convenient for the supplier.
Explaining the work is meant to make the offer understandable. There is no need to hide the use of tools or to add steps to make the process look more valuable.
What an estimate that helps the choice looks like
A useful estimate states what needs to be done, what information it is based on and what could change the effort. If we cannot estimate responsibly without an initial check, we define that check and what it will produce.
A fictional example. For a new page there are two options: reuse an existing structure with approved materials, or also build an interactive comparison between products. The client can decide based on the objective and the resources. They are not obliged to buy the option with the most features.
Sometimes the right proposal is a limited intervention now and an improvement later. At other times, repeating the same work often justifies rebuilding a component. The recommendation should show why that choice is worthwhile in the context of the business.
Checking is part of the delivery
A change that has been built in has to be checked where it will be used. For copy, an editorial review may be enough. For an interactive component, functional and display checks may be needed. Their scope follows the change and the consequences of an error.
The client should be able to understand what they are receiving and what has been checked, without working through an unnecessary technical list. The team should be able to show the result and any limits that remain.
NOT MORE. can assess the request, propose the right size of intervention and do the work: visual direction, content, software, integration or distribution, depending on the need. We can also contribute to a project led by the client’s team or by another agency.
The link between a request and the working terms is developed in “You asked for a change. What did we actually approve?”. For the role of visual adaptations, continue with “Size matters. So does context.”. A good explanation lets the client choose with full information, and lets the team deliver what was agreed.