Marcus, who had been staring at the same line of React code since the afternoon sun abandoned the office at 4:22 PM, let his breath out in a long, rattling sigh when the notification chime echoed against the glass walls.

It was 6:40 PM on a Thursday. The subject line read “one tiny thing,” followed by two sentences of text that contained no question marks and a total lack of urgency that felt, to Marcus, like a physical weight.

I know exactly what Marcus was feeling because I once cost a boutique design firm $4,830 in billable hours because I wanted to be helpful for exactly seven minutes. I was younger then, and I believed that “yes” was the shortest distance between a problem and a solution.

A client asked for a different shade of blue-a “punchier” navy-on a Tuesday afternoon. I changed the hex code in the global styles, pushed the commit, and went to lunch feeling like a hero.

I didn’t realize that the new blue lacked the necessary contrast for the ADA-compliant footer, which triggered a warning from their legal department three days later, which required a weekend rollback, which then broke the cache on their staging server. By the time we were done, the “seven-minute fix” had consumed a week of four people’s lives.

The email Marcus just received is the eleventh such message this month. It’s a request for a testimonial from a new customer to be added to the homepage. It’s a reasonable request. It is a small request.

But Marcus, whose project was technically supposed to ship in late October and is now drifting toward the middle of January, is looking at a calendar that has been devoured by reasonable requests.

In every creative and technical industry, from home renovations to high-end digital builds, we have a collective hallucination that the cost of a change is equal to the effort required to make it. If it takes twenty minutes to add a fourth column to a pricing table, we think the cost of that change is twenty minutes. This is a lie that both the buyer and the builder tell themselves to keep the relationship polite.

The Tax on Re-Entry

The actual cost of a change is not the effort; it is the re-entry.

When Marcus opens that email, he isn’t just “adding a testimonial.” He is performing a series of invisible, expensive maneuvers. He has to stop the deep work he was doing on the API integration-a state of flow that took him forty minutes to achieve and will take another forty to regain.

He has to open the project repository and pull the latest changes. He has to find the specific component in Figma to see if the new testimonial’s length breaks the established grid. He has to check three different mobile breakpoints because the client’s new customer wrote a testimonial that is four paragraphs long, while the design was built for two sentences.

Then comes the approval loop. The change has to be staged. The client has to look at it. The client’s boss has to look at it. The boss decides they don’t like the headshot provided by the customer and asks for a different crop.

Each of these steps is a “switching cost,” a tax on the momentum of the project that nobody puts in the initial estimate because we all want to believe in a world where things just happen.

What started as a twenty-minute task becomes a four-hour overhead. When you do this eleven times in a month, you haven’t just added a few hours of work; you have effectively deleted a week of progress.

This is how relationships between builders and buyers sour. It isn’t usually over a single massive disagreement or a catastrophic failure of talent. It is a slow, rhythmic erosion.

The buyer feels they are being “reasonable” because each individual request is minor. The builder feels they are being “exploited” because the aggregate weight of these requests is crushing the life out of the project. Eventually, Marcus sends a version of the scope-creep email that is too blunt, or the client asks why the “simple site” is taking four months, and the trust evaporates.

If you look at the way Coherent Agency approaches a build, you see a deliberate attempt to solve for this invisible tax. They don’t just throw bodies at a problem or pass off the design to a different team for development.

By keeping the branding, UX/UI, and full-stack engineering under one roof, they create a closed-loop system where the switching cost is minimized, but the awareness of it is maximized. When the person who designed the grid in Figma is the same person building it in Webflow, the “tiny change” is seen for what it actually is: a ripple that moves through every layer of the architecture.

Lessons from a Ship’s Meteorologist

In my years as a cruise ship meteorologist-a job that is 90% waiting and 10% terror-I learned that you don’t worry about the massive, obvious storm on the horizon. You see that coming from three hundred miles away. You have time to turn the ship.

The “scope creep” isn’t a mountain; it’s a current. Marcus deletes his first draft of the reply. He had written a long, defensive paragraph about the “cumulative impact of minor revisions.” He realizes as he reads it back that it sounds like he’s complaining about doing his job.

He deletes the second draft, which was an itemized list of every “small thing” they’ve done for free over the last eleven weeks. That one sounds like a ransom note.

He settles on a version that says, “Sure, we can do that.”

He sends it because he wants to be helpful. He sends it because it’s only one tiny thing. But as he clicks send, he knows he has just pushed the launch date back another two days. He knows that when he finally does deliver the site, the client won’t remember the eleven “yeses” he gave them; they will only remember that he was eleven weeks late.

This is the paradox of the professional service. You become a waiter instead of an architect. And while a waiter’s job is to bring you whatever you ask for, an architect’s job is to tell you that if you move that wall, the roof is going to cave in.

True expertise isn’t the ability to say “yes” to every change; it’s the authority to price the re-entry. It is the honesty to say that a logo change isn’t just a logo change; it is a re-calibration of the entire visual hierarchy.

We treat “no” as a social failure, but in the world of high-stakes building, “no” is often the highest form of respect you can show a client’s budget. It is an acknowledgment that their time and their money are finite resources that shouldn’t be spent on the friction of opening and closing files.

If we want to stop the eleven-week drift, we have to stop pricing the effort and start pricing the continuity. We have to realize that the most expensive part of any project isn’t the work itself-it’s the cost of starting it over again every Thursday at 6:40 PM.

“The project didn’t die from the weight of the testimonial; it died from the friction of the nineteen hands required to move it.”

Marcus finally closes his laptop at 9:14 PM. The testimonial is live. It looks fine. But as he walks to the subway, he isn’t thinking about the site or the code or the “punchy” navy blue.

He is thinking about how he used to love this project, and how now, after eleven weeks of being “helpful,” he just wants it to be over.

The relationship didn’t fail because of a big fight. It failed because of a thousand tiny permissions. We need to stop asking for “one tiny thing” and start asking what it actually costs to stay on course. Because the price of a change is never what’s on the invoice; it’s the loss of the momentum you’ll never get back.