The account manager problem: why an agency puts a layer between you and your website

When you hire a web agency, the first person you meet is usually the nicest person in the building. They are warm, they take notes, they promise to "loop in the team". What they almost never do is write a single line of your website. That is the account manager, and understanding why they exist tells you most of what you need to know about how agency work actually gets priced and delivered.

Why the layer exists

Agencies are built to scale headcount, not craft. A developer who is good and also good with clients is rare and expensive, so the model splits the two jobs. Developers are kept away from clients to protect their billable hours. Clients are handed an account manager to keep them happy and to keep requests flowing. It is efficient for the agency. It is rarely efficient for you.

Every change you want now travels through a relay. You describe it to the account manager. They write a ticket. A project manager schedules it. A developer reads the ticket, often guesses at what you meant, and builds something. It comes back up the chain. If it is wrong, the loop starts again. Nobody in that chain is acting in bad faith. The structure itself just adds distance between what you said and what got built.

What the distance costs

Three things, mostly.

• Speed. A one-line text change that a developer could make in two minutes becomes a two-week ticket, because it has to queue behind the process rather than behind the actual work.
• Accuracy. Every handoff is a chance to lose detail. The classic version is the client who asks for "a bit more space at the top" and gets back something nobody wanted, because the instruction was translated twice before it reached the person with the keyboard.
• Money. Someone pays for the account manager, the project manager, and the meetings that keep them synchronised. That someone is you, folded quietly into the quote.

None of this shows up on the invoice as "coordination overhead". It shows up as a bigger number and a slower turnaround, and you are told that is simply what good work costs.

The alternative, and its honest limits

The other model is old and simple: you talk to the person who builds the thing. No relay, no translation layer, no markup on a conversation. When you say the heading is too big, the developer changes the heading. When you ask why a page is slow, you get a real answer from the person who can see the code, not a reassurance from someone reading a status update.

I will be straight about the tradeoff, because pretending it does not exist would be exactly the kind of sales talk this post is arguing against. A solo developer has limits an agency does not. There is one calendar, not ten. If I am heads-down on another build, you might wait a day for a reply rather than getting an instant, cheerful, and ultimately empty acknowledgement from a support desk. The way I handle that is with clear timelines set before we start, and by keeping the work small enough that it stays honest. A presentation website is a scope one person can own completely. A fifty-person enterprise platform is not, and I will tell you so rather than take the job.

How to tell which one you are buying

Ask one question before you sign anything: "Will I be able to talk to the person who writes my code?" If the answer involves the words "dedicated account manager" or "single point of contact", you now know where your money is going and how fast your changes will move. That might still be the right choice for you. It is just worth knowing what you are choosing.

If you would rather deal directly with the developer, that is the whole idea behind how I work. You can see exactly what it costs on the pricing page, and if you want to talk through your own project, the contact page reaches me, not a front desk.