Ninety-three percent of the energy expended during an agency’s pursuit of a new contract is generated by people who will never touch the client’s actual files.

It is a statistic that lives in the quiet spaces between the grand proclamations of “partnership” and the reality of the monthly retainer. I was contemplating this number at 5:02 am this morning, courtesy of a man named Frank who called my cell phone under the impression that I was a plumber named Steve. Frank had a burst pipe in his basement.

He was frantic, his voice cracking with the specific kind of desperation that only rising water can produce. When I told him he had the wrong number, he didn’t hang up. He asked if I knew when Steve would be back. He wanted the expert he had been promised by a Google search, and instead, he got me-a virtual background designer sitting in the dark, clutching a lukewarm coffee, entirely useless in the face of a flood.

This is exactly what it feels like to enter week three of a high-stakes digital project.

The Whiteboard Masterclass

The first meeting, back in February, was a masterclass in professional competence. Dan, the founder of a scaling B2B SaaS platform, sat across from a strategy director who possessed the rare gift of synthesizing complex onboarding flows into elegant, digestible diagrams.

This director drew on the whiteboard for forty minutes, his markers squeaking with a rhythmic authority that made everyone in the room feel safe. He understood the product’s nuance in less time than it takes to order lunch. He spoke of “reducing friction” and “value-based architecture” not as buzzwords, but as inevitable outcomes of their collaboration. Dan signed the contract before the ink on the whiteboard had even been erased.

The Week Three Pivot

Then comes the Wednesday call in week three. Dan logs on, expecting to see the strategy director’s face. Instead, he is met by a project coordinator he has never seen before, a pleasant but clearly overwhelmed person who shares their screen to reveal a spreadsheet that looks like a digital graveyard.

The coordinator asks if the company sells primarily to enterprise clients or self-serve individuals. This question was answered in the second paragraph of the brief Dan wrote six weeks ago. It was the central pillar of the forty-minute whiteboard session.

But the strategist is gone. He is currently in another boardroom, three zip codes away, drawing a different set of boxes for a different founder who is about to fall in love with a promise that will be delivered by someone else.

The senior director’s notes are a messy scrawl; the coordinator’s understanding is a brittle framework of keywords; the project’s momentum is a stalled engine in a winter storm; one realizes, with a cold sinking in the gut, that the expert was merely the bait.

Let us consider the anatomy of the pitch as a theatrical performance. We are conditioned to believe that the people who “sell” us on a vision are the same people who will “build” that vision, but the economics of the traditional agency model make this almost impossible. Pitching is unbillable work.

Agencies staff these moments with their most persuasive, highest-paid senior talent because the cost of losing the pitch is too high to delegate to a junior. However, once the contract is signed, the agency must recover that unbillable cost. They do this by shifting the actual labor to the most affordable, available resources they have. The seniors move on to the next “unbillable” theater, and the client is left with a translation of a translation.

Vague Language as Camouflage

This is not a personal slight against the client, though it is always felt as one. It is not that a better-paying client took your slot. It is simply that the model was designed for the seniors to leave the room the moment the signature was dry.

The work that follows is often the result of a “telephone game” where the original strategic intent is diluted through layers of management until the final output looks like a generic version of the breakthrough that was promised.

Precision in professional services is a dangerous thing for a legacy agency. If a specification document were too precise, the client would immediately notice when the person executing the work lacked the context to understand the details. Vague language is the camouflage of the handoff.

By keeping the “what” and the “how” in a state of soft-focus, the agency maintains the flexibility to staff the project based on their internal margins rather than the client’s actual needs.

This habit has infected nearly every corner of the professional world. We see it in legal firms where the founding partner appears only for the introductory dinner, leaving the actual brief to be written by an associate who hasn’t yet passed the bar.

We see it in consulting, where the “Global Head of Insight” disappears after the first slide deck, replaced by a cohort of recent graduates who are learning the industry on the client’s dime. We see it in construction, where the master builder is a ghost, and the site is managed by a series of subcontractors who have never seen the original blueprints.

The friction of this handoff is where projects go to die. Every time a piece of knowledge is passed from a senior to a junior, or from a strategist to a developer, a percentage of the “truth” is lost. The nuance of why a specific button needs to be in a specific place-the “why” that Dan and the strategist spent forty minutes refining-is rarely captured in a Jira ticket.

Eliminating the Telephone Game

When the team that scopes the work is the same team that builds it, the “telephone game” is eliminated. There is no loss of fidelity because the person who heard the founder’s frustration is the same person who is writing the code to solve it.

This is why a studio like

Coherent Agency

can deliver a product that actually reflects the initial vision. There is no “Steve” who is perpetually out of the office; there are only the people who were in the room when the leak was first described.

The whiteboard is a map of a country the guide never intends to visit.

The Cost of Institutionalized Deception

Let us reflect on the cost of this institutionalized deception. It is not just a matter of lost hours or redundant meetings. It is a slow erosion of trust. When a founder realizes they have been handed off, their engagement with the project changes.

They stop being a collaborator and start being a micromanager. They feel the need to check every pixel and question every line of code because they no longer believe that the person on the other end of the call “gets it.” This micromanagement further slows the project, driving up costs and creating a cycle of resentment that poisons the final delivery.

I think back to the 5:02 am call. Frank didn’t need a sympathetic listener; he needed someone who knew where the shut-off valve was. He needed someone who had seen a hundred burst pipes and knew exactly how to stop the water without tearing down the drywall.

But the work is the only thing that remains after the theater lights have been dimmed. The Figma files don’t care how charismatic the strategy director was. The React components don’t remember the whiteboard session. They only reflect the skill and the context of the hands that built them.

If we are to move forward, we must demand a collapse of the hierarchy. We must seek out the practitioners who are willing to stay in the room. There is a profound dignity in the person who says, “I will help you figure out what this needs to be, and then I will sit here and make it so.”

It lacks the glamour of the high-flying consultant who drops in for a singular moment of brilliance before jetting off to the next engagement, but it is the only way to build something that lasts.

The Midnight Launch Test

The next time you find yourself in a pitch, ignore the slides for a moment. Look at the people in the room. Ask them if they will be the ones answering the phone in week three. Ask them if they will be the ones debugging the CSS at midnight before a launch.

“If the answer is a vague gesture toward a ‘dedicated support team’ or a ‘robust project management framework,’ you are not buying a solution; you are buying a ticket to a play.”

And once the curtain falls, you will be left in the dark, standing in the rising water, wondering where Steve went.