Here is the pattern, and it is one of the most reliable ones in agency work. The person who runs your sales call is sharp. They ask good questions, they push back on your assumptions, they clearly know how to build the thing you are describing. Their name is on the proposal as your technical lead. You sign, partly because of them. Then, four to eight weeks in, they are quietly reassigned to the next sales cycle, and your product is being built by a mid-level developer with a senior title you never interviewed. You are still paying the senior rate.
This is the bait-and-switch, and in 2026 it is consistently named as one of the biggest risks in outsourced software development. It works because the two things a non-technical founder uses to judge an agency, the sales conversation and the invoice, are exactly the two things the agency controls most tightly. The quality of the pitch tells you about the pitcher. It tells you nothing about who writes your code.
Why the swap is so common and so hard to see
The economics make it almost inevitable at a certain kind of shop. Senior engineers are the scarcest, most expensive people an agency has, and their highest-leverage use is closing deals, not billing hours on a delivered project. So the senior is real, but they are a closer. Once you sign, keeping them on your build is money the agency would rather redeploy to win the next client. The junior or mid-level engineer who inherits your project is billed to you at a blended rate that assumes senior involvement that has quietly ended.
You cannot see it because the interface stays the same. Status reports still come from the account manager. The senior's name might still appear on documents. The work slows down, the questions coming back to you get shallower, the bugs take longer to fix, but none of that arrives labeled "your senior engineer left." It shows up as a project that is mysteriously harder than it should be, and by the time the pattern is obvious you are three months and a lot of money in. This is a close relative of the risk in managing an offshore team you cannot technically evaluate: when you cannot read the work, you are judging the seniority of the people doing it entirely on trust.
The specific mechanisms to watch for are a matched set. Blended rate billing hides who is actually on the keyboard. IP assignment conditional on full payment removes your leverage to complain. And a refusal to let you interview the actual builders, as opposed to the account team, keeps the swap invisible by design.
How to make the swap expensive for them
The fix is to bind the people to the contract, not just the price. Ask, before signing, who specifically will be on your team, by name, and insist on interviewing the actual developers rather than the account manager and the closer. An agency that will not let you talk to the people who will write your code is telling you something, and it is the one thing they most want to obscure.
Then write it down. Put the named lead into the SOW with a clause that says a change of key personnel requires your written approval. This does not guarantee the senior stays forever, but it converts a silent reassignment into a conversation you get to have, which is most of the battle. The agencies that quietly swap staff rely on there being no document that makes the swap a breach.
Ask two questions the sales team rarely expects. What share of your engineers are senior, and how long is the average senior tenure here? A shop where most engineers are junior and senior tenure is under two years is a shop where the senior on your call is either an outlier or a hired gun, and the person who inherits your project will be neither. And ask what the technical screen is and who runs it, because an agency that screens its own engineers rigorously will be proud to tell you; one that staffs by availability will get vague.
The most effective single move is to refuse to commit a large project up front and to structure a paid trial instead. A short paid pilot forces the agency to put real working people on your problem immediately, and it shows you the actual builders' output before you have wagered a quarter's budget on the pitch. An agency that refuses any paid trial, insisting you commit to the full engagement to "see what we can do," has told you which team you are getting. If you want a second set of eyes on the proposal and the people behind it before you sign, that is what a call is for.
The agency says naming individuals in the contract is not how they work. Fair?
It is a real operational constraint for large shops that rotate staff, but it is also exactly the flexibility that enables the swap. The compromise is a key-personnel clause: they do not have to promise a specific junior stays, but they do have to get your sign-off before changing the named lead. If even that is off the table, you are being asked to trust a process built to keep the swap invisible.
How do I catch a swap that has already happened?
Look for a change in the texture of the work. Responses to your questions get shallower, review comments get thinner, simple bugs take longer, and the person answering technical questions changes or goes quiet. Ask directly who is currently writing the code and when they joined the project. An honest answer resolves it; evasion confirms it.
Isn't a mid-level engineer fine for a lot of startup work?
Often, yes, and there is nothing wrong with mid-level engineers doing mid-level work. The problem is not the seniority of the person; it is paying a senior rate for junior output and making the architectural decisions that shape your product for years without the judgment you thought you were buying. If a mid-level team is fine for your project, you should be paying a mid-level price and knowing it, not discovering it in the code review a year later.