The Transfer Pattern: Five Ways an Agency Project Goes Quiet (proposed; old title in the notes)
If that sounds familiar, it probably isn't bad luck. Stalled agency projects tend to stall the same way, and the signs show up months before the missed deadline. Each one is easy to explain away on its own. The team is busy. The feature was harder than expected. Put side by side, they form a pattern, and once you've seen it you can't stop seeing it.
Here are the five parts of that pattern, roughly in the order they appear, and what to do when three or more of them match your project.
1. The engineer who pitched is gone
You signed because of the senior engineer on the sales call. Two months in, that person is on another client and you're working with someone you've never met. The agency calls it team flexibility. For you it means the person who understood your product has left, and the new one is learning it on your invoice.
2. Standups fade out
In the first month there are daily Slack updates and Loom videos. By month three there's a Friday call that gets moved twice and then becomes "async". In a stalled project, async usually means nobody is writing anything down.
3. The demo schedule slips quietly
You used to see working software every two weeks. Then every three. Then the team wants to wait until the auth flow is polished. The polish was supposed to take a week, and it has been a month. A team that can't demo usually has nothing that runs end to end.
4. The invoices outgrow the feature list
Add up what you've paid and compare it to what a user can actually do in the product. Say the total is $40K and the feature list reads in thirty seconds. Then look at where the hours went. "Integration" and "infrastructure" are real work, sometimes. Neither shows up for a customer, and neither belongs in your investor deck.
5. The agency's founder stops joining calls
At signing, the agency's founder was on every call. Now you deal with a project manager whose name you have to look up. That's rarely malice. It usually means your account is no longer a priority, and the agency's best people are on the accounts that are.
Check your project against the five patterns
Describe your current engagement in a paragraph. ChatGPT will tell you which pattern is furthest along and the one question to put to your agency this week.
“|”
Why one more sprint rarely works
When founders see these signs, the usual response is to wait one more sprint. It feels cheaper than a change, and the agency will usually promise that the next one is different. But none of the five patterns is a sprint-sized problem. A team that stopped demoing doesn't start again because the calendar turned over. An agency founder who stopped showing up won't come back for a deadline that's already been missed.
What changes things is moving the work, and that doesn't mean starting over. A transfer keeps what survived: the code that runs, the design, the product decisions and the data. What moves is ownership of the repository and the accounts, and control of the schedule.
What a transfer looks like
It starts with ownership, not code. The repository moves into your GitHub organization and the cloud accounts move to you. Then every key the old team could see gets rotated, and only after that does anyone start finishing features. We wrote the sequence up day by day in our 14-day transfer playbook. The email that starts it is in You're allowed to fire your dev team.
A caveat, because it matters: not every stalled project fits in two weeks. If the database is damaged or most of the scope was never written, the plan gets longer. You should hear that right after the audit, before you've paid for the transfer itself.
If three of the five patterns match your project, you don't need another sprint. You need a plan for moving the work.
Do three of the five patterns sound familiar?
Agency Transfer starts at $500, and the price is flat. We audit the code and the contract, then quote the transfer before any work starts. Send your email and we'll set up a 30-minute call within 24 hours.
The five-minute check
Answer honestly. Each "yes" is one pattern.
- Is the engineer who pitched the project no longer working on it?
- Have regular updates dropped to once a week or less?
- Has it been more than three weeks since you last saw working software?
- Does the total spend look out of proportion to what a user can do in the product?
- Has the agency's founder stopped joining your calls?
Three or more means it's time to plan the transfer, ideally while the final invoice is still unpaid.
Related reading
- You're allowed to fire your dev team. Here is the email: the email, and the four things to have ready before you send it
- Our 14-day transfer-and-ship playbook: day by day, from audit to production
- Getting your code back: what to demand before you walk away: the handover list to hold the final invoice against
The service: Agency Transfer. Stuck with a team that went quiet: transfer rescue. Comparing options: agency vs Start Matter.
Enjoyed this article? Share it with others
Related Posts
Seven Defects We Check First in Any Vibe-Coded App (proposed; old title in the notes)
AI coding tools make the same mistakes because they get asked the same questions. Here are the seven defects we look for first in a vibe-coded app, from paywalls enforced in the browser to AI features with unguarded tools, and a check for each.
You're Allowed to Fire Your Dev Team. Here Is the Email.
Founders keep paying agencies that stopped shipping because firing them feels harsh. They were paid and they didn't deliver. Here is the email to send, the four things to have ready first, and what to do the morning after.
Our 14-Day Transfer-and-Ship Playbook
What happens in the two weeks between letting the old team go and a working production deploy. Day by day: what the audit checks, what you own by day 3, what ships first, and the three steps founders most often skip.