⚡ Executive Summary
The people you meet during an agency's sales process are usually not the people who write your code. The architects and "20 years of experience" leads close the deal, sketch the architecture, and hand delivery to the cheapest engineers the agency can staff — while you're billed as if the people from the sales call stayed in the room. Here's how the switch works, five signs it's happening on your project, and the three things to demand instead.
How does the junior hand-off actually work?
There's a bait-and-switch running through the agency industry that's so normalised nobody calls it what it is. It isn't a rogue-agency problem — it's the standard economic model. Agencies profit on the spread between what they charge for a seat and what the person in the seat costs. The steeper the seniority drop after signature, the better the margin.
So the seniors do what maximises revenue: they sell. They turn up to your calls, produce an architecture document, then move to the next prospect. Delivery goes to whoever costs the agency least, with the seniors "providing oversight." The client is the only party in the room with no way to see it happening.
Why don't clients notice?
Because delivery is a black box. Clients see demos, staged updates, and a project manager narrating progress — they don't see commits, pull requests, or who actually resolved yesterday's blocker. Ask an agency "who wrote this file?" and watch the answer route through three layers of account management.
The opacity isn't incidental. It's what makes the model work.
What are the signs that juniors are writing your code?
- You can't name the engineers on your project. Not the account lead — the people committing code. If you don't know, that's the answer.
- No direct access to the task board or PR history. "We'll send weekly updates" is a substitute for visibility, not a form of it.
- "Senior oversight" language in the contract. Oversight means juniors write it and a senior skims it. If seniors were writing it, the contract would say so.
- Velocity drops after month one. The seniors built the scaffold and moved to the next sale; the hand-off is where timelines quietly slip.
- Questions get answered by people who didn't do the work. Technical answers arriving via a PM, with a delay, mean the person who knows isn't client-facing.
What should you demand instead?
Three things, none of them exotic:
- Named engineers, contractually. The people writing your code, identified in the agreement — not a team description.
- Direct read access to the task board and pull-request history. Not summaries of them. The raw record of who did what, visible to you at any time.
- The right to ask the person who wrote the code about the code. Directly, without a translation layer.
Any competent agency can grant all three. The ones that won't are telling you why.
Where Esseal stands
At Esseal this is structural, not aspirational: 100% of code is written by a partner or a directly supervised senior engineer, and every client gets direct access to task boards, PR histories, and architecture logs from day one. Not because transparency is a nice value — because it's the only arrangement under which "senior-led" is verifiable rather than a claim. We publish this so clients can hold us to it.
Frequently asked questions
What does "senior oversight" mean in an agency contract?
In practice: junior engineers write the code and a senior reviews some of it, sometimes. It's the contractual language that makes the junior hand-off legal without making it visible. If seniors were doing the writing, the contract would say "written by," not "overseen by."
How do I find out who is actually writing my code?
Ask for the three things above — named engineers, direct task-board and PR access, and direct contact with the authors. You don't need to read the code; the commit history shows who does the work. An agency that refuses read access to its delivery record has answered the question.
Aren't junior developers cheaper for the client?
Cheaper for the agency — that's the point of the model. The client pays the same seat rate either way; the difference is margin, not savings. The client's cost shows up later, as slipping velocity and rework. We've made the full cost-and-outcome argument in Senior-Led MVPs vs. Junior Teams.
Ask your current agency these five questions
If you're mid-engagement and this post felt uncomfortably familiar, put the checklist to work. Ask your agency: Who, by name, committed code to my project last week? Can I have read access to the task board and PR history? Does my contract say "written by seniors" or "overseen by seniors"? Why did velocity change after month one? And can I speak directly to the engineer who built the last feature?
Their reaction will tell you most of what you need to know. If you'd like a second opinion on what you find, write to inquiry@esseal.co.uk.