In 2024, I worked with an enterprise client that looked, at first, like the kind of account every agency wants.
The company was established. The budget was meaningful. The work could strengthen our reputation and lead to larger opportunities. Compared with the smaller Web3 companies I had spent years working with, this client appeared more structured and predictable.
That assumption lasted until the project started moving.
The original scope was clear enough on paper. Then new requests began to appear. Each one looked reasonable in isolation. A small addition here. An extra round of work there. Something that had become urgent internally and now needed our support.
None of these requests seemed large enough to justify a confrontation. So I kept saying yes.
I told myself that flexibility was part of good service. I believed an agency proved its value by helping clients solve problems, including problems that were not visible when the contract was signed.
There was some truth in that belief. The mistake was treating flexibility as a substitute for structure.
The scope changed quietly
Scope creep rarely begins with a client announcing that they want twice the work for the same fee. It grows through a sequence of requests that sound temporary.
Could we help with this one item?
Could we make another adjustment?
Could we join one more discussion?
Could we support another stakeholder who had recently become involved?
Each request made sense in the moment. The problem only became visible when I looked at the project as a whole. The engagement we were delivering had become materially different from the one we had agreed to.
The timeline had not expanded with it. Neither had the budget.
This is the basic project management constraint I understood intellectually but had failed to enforce in practice. Scope, time, and cost move together. When one changes, at least one of the others must change as well. Keeping the same deadline and budget while adding work simply pushes the cost somewhere less visible.
In our case, the cost moved inside the agency.
It appeared as more coordination, more revisions, more internal discussion, and less time for other clients. It also created emotional pressure. Once a team has repeatedly accepted extra work, the next request becomes harder to challenge. What began as flexibility slowly becomes the new baseline.
The client assumes the work belongs inside the agreement because we have been doing it.
The agency knows it does not, but feels responsible because we failed to object earlier.
That is how a commercial problem becomes a relationship problem.
I blamed the client before I blamed the system
My first reaction was frustration.
I thought the client kept changing its mind. I thought too many stakeholders were involved. I thought the account had become demanding in a way that could not have been predicted.
Some of that may have been true. Enterprise clients often have several departments, reporting lines, and approval layers. The person who signs the agreement may not be the only person influencing the work. New requirements can emerge because internal priorities change or because another stakeholder sees the project and decides it should solve their problem too.
But those conditions were part of the job.
The harder conclusion was that I had allowed the situation to develop.
I had not created a strong enough mechanism for handling change. We had a scope, but we did not have a clear process for what happened when the scope changed.
That distinction matters.
A contract can describe the work at the beginning of a project. It cannot prevent new needs from emerging. A working change process gives both sides a way to respond when they do.
Without one, every new request becomes a small negotiation conducted under time pressure. The agency worries about looking unhelpful. The client worries that the agency is becoming rigid. Both sides begin interpreting ordinary project decisions as evidence about the relationship.
A simple operational question becomes personal.
Should this request be included?
Are they trying to charge us for everything?
Are they taking advantage of us?
Do they understand how much work this requires?
By the time those questions appear, trust has already started leaking out of the engagement.
I had confused service with availability
The deeper mistake was in how I understood client service.
I thought being easy to work with meant reducing friction for the client. In practice, I was often absorbing the friction myself and passing it to my team.
That can look generous for a while. It can even make the relationship feel strong. The client asks for something, and the agency finds a way to deliver it. Everyone keeps moving.
But an agency cannot build a stable business on invisible concessions.
The work still has a cost, even when the client does not see an invoice for it. Someone works later. Another project receives less attention. A team member rushes a review. The founder spends time rescuing delivery instead of improving the company.
The cost may also appear in quality.
When the amount of work grows but the schedule stays fixed, the team has fewer good options. They can work more hours, reduce the depth of the work, or delay delivery. None of those outcomes improves the client relationship.
I began to see that clear boundaries were part of the service itself.
A boundary tells the client what the team can deliver well. It also makes trade-offs visible before they damage the project.
The rule I use now
The principle I took from that client is simple.
Every new request needs a home.
It must fit inside the existing scope, replace something already planned, or become additional paid work with its own timeline.
There is no fourth category where the work quietly enters the project and everyone pretends that nothing changed.
This does not mean responding to every unexpected request with a quotation. Some changes are minor. Some are worth absorbing because they strengthen the outcome or the relationship.
The difference is that the decision should be conscious.
Today, when a client asks for something outside the original plan, I try to make the trade-off clear without turning the conversation into a dispute.
We can include this by moving another deliverable.
We can add it and adjust the timeline.
We can treat it as a separate workstream.
That language is more useful than a blunt yes or no. It keeps the focus on resources and priorities rather than intentions.
I also pay more attention to the boundaries between broad responsibilities.
For 43to.one, this matters because Vietnam market entry crosses several areas at once. Compliance groundwork can affect localization. Community feedback can influence content. Business development conversations can reveal operational gaps. A fractional local unit must be able to respond to what it learns.
But responsiveness still needs an operating structure.
The same is true at BlockPR. Trust, reputation, content, media, and community work often overlap. A client may begin with one need and discover three others. Our role is to help them see the connections while remaining honest about what the current engagement covers.
That honesty protects both sides.
What I believe now
I used to think boundaries were mainly a defence against difficult clients.
Now I see them as part of building a good client relationship.
A clear boundary prevents hidden resentment. It gives the team room to do good work. It gives the client a realistic view of what their budget and timeline can produce.
Most importantly, it creates a way for the relationship to grow without becoming confused.
The enterprise client in 2024 taught me that agencies do not lose control of scope in one dramatic moment. They lose it through a series of small decisions that feel polite, helpful, and temporary.
The lesson was not to become less flexible.
It was to stop offering flexibility without naming its cost.
Share this post