In the mid-17th century, Wojciech Bobowski, a Polish musician and polyglot, was captured by Crimean Tatars and sold into the service of the Ottoman Topkapi Palace. Renamed Ali Ufki Bey, he became a dragoman-a professional interpreter, translator, and diplomatic intermediary between the Ottoman Empire and the Western world.

Bobowski lived in the gap between what was said and what was heard. He translated the Bible into Ottoman Turkish and the hymns of the Reformation into the music of the East. His survival depended entirely on his ability to soften the sharp edges of a Sultan’s decree so it wouldn’t start a war with a European monarch, while ensuring the monarch’s reply didn’t sound like an insult.

He was a human buffer, a man whose entire career was built on the premise that direct communication was a dangerous, volatile thing that required a specialized filter to survive the journey from one mouth to another.

We have not moved as far from the Ottoman court as we like to think. In the modern world of digital product development, we call these dragomans “Account Managers” or “Project Leads.” They are the professional softeners of truth, the people who stand in the middle of the bridge, collecting a toll in the form of time and clarity, ostensibly to “protect” the people on either side.

The Anatomy of a Zoom Call

It is a Thursday morning, 10:14 AM. Sofia, a marketing director for a mid-sized fintech firm, is on a Zoom call with her agency. She has a simple question: “Can the CMS hold a second author field for the blog? We’re starting a guest-post series and need to credit both the writer and the internal reviewer.”

Ryan, the account lead, nods with a practiced, empathetic tilt of the head. He doesn’t know the answer. He doesn’t know what a “field” actually represents in the database architecture of the site, nor does he understand the difference between a reference field and a plain text string.

But Ryan is a professional. He knows that his primary job is to maintain the cadence of the relationship. “That’s a great question, Sofia,” Ryan says. “I suspect there might be some dependencies there regarding the schema and the way we’ve structured the collection. Let me socialize that with the dev team and circle back to you by EOD tomorrow.”

In reality, Leo, the developer who actually built the site, is sitting exactly thirty-two feet away from Ryan in a Toronto office. Leo is currently listening to a three-hour podcast about the history of brutalist architecture and could answer the question in four seconds.

He would tell Sofia that yes, it takes precisely nine clicks to add a multi-reference field, and he could have it live before the Zoom call ends. But if Leo speaks directly to Sofia, the illusion of complexity-the very thing that justifies the agency’s monthly retainer-might begin to crumble.

Instead, Sofia’s question is transcribed into a project management tool. It sits there for six hours. It is then “translated” by Ryan into a ticket that asks, “Can we add a guest author feature to the blog?” Leo sees the ticket the next morning, sighs because he knows the answer is simple but the “feature” description is vague, and asks for clarification.

Ryan sees Leo’s reply, doesn’t quite understand the nuance, and waits until the next status call to “update” Sofia. By the time the answer reaches Sofia, it has been seventy-four hours. It is no longer an answer; it is a “proposal for a minor scope adjustment.”

Sofia adds the status to a running document titled Questions Outstanding, which has now swollen to twenty-two pages. The common justification for this layer of interference is that it “protects the client’s time.” The theory is that clients shouldn’t be bothered with the “sausage-making” of development.

But this is a fallacy. What it actually protects is the agency’s margin. Direct contact between the person paying for the work and the person doing the work reveals an uncomfortable truth: many of the things that agencies bill thousands of dollars for are remarkably simple for an expert to execute.

The Hollow Pitch

I remember once, during a high-stakes pitch, I yawned. It wasn’t because I was bored with the client’s business-they were doing fascinating work in renewable energy-but because the account executive was explaining a “strategic roadmap” that I knew was just a series of templates we had used for three other clients that year.

My body reacted to the hollowness of the words before my brain could censor the reflex. I felt like a fraud. We were selling “strategy” when what the client needed was someone to sit down with their lead engineer and fix the malformed schema markup that was burying their search results.

Every relationship with a translation layer eventually optimizes for the translator’s comfort. The account manager wants a “smooth” call, which means avoiding technical “no’s” and inflating technical “yes’s.” This creates a narrative debt.

You spend weeks building a story about what the website is going to be, only to have reality crash into that story when the site finally launches and the Core Web Vitals are in the red because the “motion work” was never properly optimized for performance.

The Courier’s Wisdom

Avery E., a medical equipment courier I’ve known for years, understands this better than most project managers. Avery spends his days moving ventilators and surgical kits between hospitals in heavy traffic. He’s the physical link in a life-or-death chain.

“If the courier knows why the heart is in the box, they don’t stop for coffee; if they’re just moving a box, they’ll take the scenic route.”

– Avery E., Medical Courier

When you separate the “box” (the project) from the “heart” (the developer’s craft and the client’s actual business need), everyone starts taking the scenic route. The developer loses interest because they are treated as a ticket-processing machine. The client loses trust because they can sense the “softening” of the information they receive.

A Continuous Conversation

This is why the traditional agency model is failing. Companies are tired of paying for the “circle back.” They want the engineer who knows why the GSAP animation is stuttering on mobile to explain it to them directly.

They want the person writing the schema markup to be the same person who understands how that markup will be interpreted by an AI answer engine. They want the “engineers as designers” approach, where the build isn’t a handoff, but a continuous conversation.

At Coherent Agency, this barrier is intentionally dismantled. By keeping the brand identity, UX/UI, and the technical Webflow development within one tight-knit, in-house team, the “translation tax” is eliminated.

There is no Ryan. When a client asks if a CMS can hold a second author field, the person they are talking to is the person who will go into the dashboard and add it. This isn’t just about speed; it’s about accuracy.

If you are building a site for a global enterprise-the kind of project where 3D web experiences and custom app integrations are the standard-you cannot afford the lag of a translator. You need the directness of an engineer.

You need to know that the person watching the numbers after launch is the same person who wrote the architecture. The danger of the intermediary is that they eventually become the product. The meetings about the project become more important than the project itself.

The Questions Outstanding document becomes the primary deliverable, a monument to all the things that haven’t been done. We mistake the activity of “managing” for the act of “building.”

I think back to Wojciech Bobowski in the Ottoman court. He was brilliant, but his brilliance was spent on navigation, not creation. He was navigating the egos of kings and sultans, ensuring that nobody lost face.

The Cost of Face

In business, however, losing face is less dangerous than losing time. A “socialized” answer that arrives three days late is often worth less than a blunt “no” that arrives in three seconds.

Directness assumes that both parties are capable of handling the truth about technical constraints and timelines. When you remove the buffer, you find that the work moves faster, not because people are working harder, but because they are no longer walking through mud.

The second author field remained empty not because the code was difficult, but because the path to the solution was crowded with people whose job was to clear it.

We often forget that every layer of management added to a project is another opportunity for the original intent to be distorted. Like a photocopy of a photocopy, the resolution of the initial vision fades with every handoff.

By the time the developer gets the instruction, it has been stripped of its context and its urgency. It has become a task, a chore, a “ticket.” The goal should be a state of transmittance where the distance between the “why” and the “how” is zero.

This requires a level of accountability that most agencies shy away from. It requires developers who can speak the language of business and clients who are willing to hear the language of engineering. It requires a team that owns the outcome from the first sketch to the final deployment of the schema.

When the translator is gone, the conversation finally begins. You stop talking about “bandwidth” and start talking about “results.”

You stop waiting for the “circle back” and start watching the site perform. It is a terrifying way to work for those who hide behind the buffer, but for those who actually want to build something that lasts, it is the only way that makes sense.