May 20, 2026

When to Fire Your Dev Agency (and What to Do Next)

The signs are subtle at first: missed deadlines, vague updates, scope creep with no accountability. Here's how to know when to cut ties — and how to recover without losing everything.

Most founders stay with a bad development agency far too long. The sunk cost fallacy is powerful: you've already paid $20K, so leaving feels like losing $20K. But the cost of staying — more months of delay, a codebase you'll eventually have to rewrite, and a product that never ships — is almost always worse. Knowing when to leave, how to extract maximum value before you leave, and how to recover after are skills every founder building a product needs.

Signals That Are Fixable (Don't Leave Yet)

Not every agency problem is a reason to leave. Some are communication failures that can be corrected with a direct conversation: deliverables aren't reviewed weekly (schedule a recurring demo call), you don't understand what's been built (request a technical walkthrough on staging), scope was never documented properly (write it together now, even mid-engagement), and feedback isn't making it into the product (enforce a shared task tracker). If you haven't had a direct, uncomfortable conversation about the problem, you haven't given the agency a fair chance.

Signals That Are Red Flags (Prepare to Leave)

These patterns rarely self-correct: consistent deadline misses with confident predictions that the next deadline will be hit, deliverables that work in demos but break in basic testing, refusal to give you repository access or explain technical decisions, team turnover where the senior developer you contracted is replaced by juniors without disclosure, and invoices for work that doesn't match visible progress. One of these is a warning. Three is a pattern.

Deadline misses: 1 is forgivable. 3 is a pattern.
Demo-only quality: doesn't survive real testing or edge cases
No repo access: you own the code but can't see it — unacceptable
Undisclosed team swap: you hired Person A, Person A left, you weren't told
Invoice-to-output mismatch: billing 40 hours for 10 hours of visible work

Before You Leave: Extract Everything

Before sending the termination notice, extract all deliverables: a full export of the Git repository (all branches, full history), all environment variables and infrastructure credentials, all design files (Figma, assets), all third-party account credentials (App Store Connect, Google Play, Stripe, Vercel, AWS), and a deployment guide even if it's rough. Once you've sent termination notice, agencies legally have to comply with handoff but practically often become difficult. Get everything before the conversation.

Git repo: full clone with all branches, all history
Environment variables: every .env value, even staging/dev
Hosting accounts: you as owner, not them as owner
App store accounts: your Apple Developer ID, your Google Play account
Design files: Figma export, all icon and image assets

How to Assess What You Have

Before engaging a new agency, get an independent code audit. A senior engineer spending 4–8 hours reviewing the codebase can tell you: is the architecture sound? What's working and what's broken? How much needs to be rebuilt vs. salvaged? What are the security vulnerabilities? This audit typically costs $1,000–$3,000 and is worth 10× that by preventing you from making a new agency inherit and extend a disaster. Expect to be told that 30–60% of a bad agency's work can be salvaged — it's rarely a total loss.

How to Find a Better Agency (and Avoid Making the Same Mistake)

The mistakes that led to a bad agency engagement are almost always in the selection phase: choosing on price, not evaluating shipped work, not checking references, and not insisting on a fixed scope before signing. For your second engagement: require App Store links to live products, talk to two past clients directly, insist on a written scope document before any contract, and start with a small paid discovery phase ($1,000–$3,000) to evaluate fit before committing to a full build. The agency that does a great discovery phase almost always does a great build.

Live product links: App Store, Play Store, or live URLs — not just mockups
Reference calls: two past clients, 15 minutes each
Written scope with acceptance criteria before signing
Paid discovery phase before full build commitment