The pitch was excellent. A sharp technical lead walked you through the architecture, asked the right questions, and clearly knew what they were doing. You signed. Three months later that person is nowhere to be found, your project is staffed by people you never met, and the work does not feel like what was sold. This is the single most common complaint about software agencies, and it cuts across every price tier and firm size.
Why the team that pitched is not the team that builds
Senior talent is expensive, so agencies ration it. The people who are great in a sales meeting, who can read a room and design on a whiteboard, are the same people the agency most wants closing deals. Putting them on your day-to-day build for six months is, from the agency's point of view, a waste of their highest-margin skill. So they pitch, they win, and they hand the work to a delivery team that was never in the room.
It is not always cynical. At larger firms, sales and delivery are genuinely separate organizations, and the handoff is a process rather than a trick. But the effect on you is the same whether it is deliberate or structural. The judgment you evaluated and trusted is not the judgment building your product. Most clients do not discover this until they are three months into the contract, staring at mediocre progress, wondering where the person who won their business went.
What actually changes when the team swaps
The gap is not usually about raw coding ability. Junior engineers can write fine code. The gap is judgment: knowing which corners are safe to cut, when to push back on a bad request, how to sequence work so the risky parts surface early. That judgment is exactly what the pitch showed you, and exactly what does not transfer when the work moves to people who were hired to execute a plan rather than shape one.
You feel it in small ways first. Questions that the pitch lead would have anticipated now come back to you as tickets. Decisions that should take an hour take a week because nobody on the delivery team has the authority or the context to make them. The architecture that looked clean in the sales deck drifts, because the person who designed it is not the person implementing it and no one is guarding the intent. By the time it shows up in the demo, you have lost weeks.
How to protect yourself before you sign
The fix is almost entirely upfront. Once the contract is signed, your leverage is mostly gone.
- Ask who will actually do the work. Get names. Ask specifically whether the person pitching will be on the build, and in what role and for how many hours a week.
- Put the named team in the contract. "Key personnel" clauses are standard. Name the lead, specify their minimum involvement, and require the agency to notify you before swapping them out.
- Interview the delivery lead, not just the pitch lead. If the agency will not let you meet the person who will run your project day to day, that is your answer.
- Treat "our whole team is senior" as a claim to verify, not a comfort. Ask for the specific people and their track record on work like yours.
If an agency resists naming the delivery team, that resistance is the signal. The green flag is the opposite: the people who pitch are visibly part of delivery, and they say so without being pushed. This is a close cousin of the classic agency bait-and-switch, and the defenses overlap. When you compare agency bids, weight the staffing answer as heavily as the price, because a cheaper bid staffed by people you will never meet is not actually cheaper.
How to catch it after you have signed
If you are already in it and something feels off, run a quiet audit. Ask for the git history and look at who is actually committing code. Ask to join a working session, not a status call, and watch how decisions get made. If the technical lead from the pitch has not touched your project in weeks and the people who have cannot answer architecture questions with confidence, you have found your problem. At that point the conversation is about escalation: invoke the key-personnel expectation you set, or bring in an outside technical read to tell you whether the work is salvageable. An independent technical teardown of what has actually been built will tell you more in a day than another month of status updates.
None of this means agencies are dishonest. Most are running a rational business where senior time is scarce. Your job is to make sure the scarce time you evaluated is the time you actually get, and the only reliable way to do that is to nail it down in writing before you sign.
FAQ
Is the pitch-team swap illegal or just annoying?
Usually just how the business works, not fraud. It becomes a real problem when the agency implied the pitch lead would run your project and then quietly swapped them out. That is why a named key-personnel clause matters: it turns an implied promise into an enforceable one.
What is a key-personnel clause?
A contract term that names the specific people assigned to your project and requires the agency to keep them on it, or to get your approval before replacing them. It is standard in professional services and completely reasonable to ask for.
How do I know if my delivery team is junior?
Look at who commits code, sit in on a working session, and ask architecture questions in real time. Junior teams give you tickets instead of answers and take days to make decisions that judgment would resolve in an hour.
Can I do anything once the good people have already left?
Yes. Invoke any key-personnel expectation you set, ask for the people back or for a credit, and get an independent read on the work. If you want a neutral assessment of whether the build is on track, book a call before you sink another month into it.