Why most agency relationships fail (it’s not what people think)
Agency-client breakups almost never happen because the work was bad. They happen because of mismatched expectations, hidden ownership terms, communication breakdowns three months after launch, or cost surprises that weren’t surprises to the agency. The work itself is usually fine. The relationship around the work is what falls apart.
The good news: every common failure mode shows up in the answers to five specific questions. If your prospective agency answers all five clearly and without dodging, you’re probably in safe hands.
Question 1: Who literally writes the code?
This sounds simple. It is not.
What you want to know: is your project being built by the team you met in the sales call, or is it being subcontracted to a different team, often offshore, often through chains the agency hasn’t disclosed?
Subcontracting isn’t automatically bad. Many great agencies use specialist subcontractors for specific layers (security, performance, certain integrations). What’s bad is undisclosed subcontracting, where the people you trust to build something turn out to be a project-management layer between you and a team you’ve never met.
What to ask specifically: “Who, by name, will be writing the code? Are they full-time employees? Do they work for you directly, or through another company?”
A clean answer names people, confirms their employment status, and matches the team you’ll see during the kickoff. A messy answer dodges into “we have a team,” “we use the best resources,” or “we have partners we work with.” Push for specifics. If the answer stays vague, you have new information about how this relationship will run.
How we answer at AVMDEVS: You meet our team on the About page and during your discovery call. We don’t run hidden subcontracting chains. If we need a specialist (rare), we tell you upfront and you meet them too.
Question 2: What happens at month 3 when you stop replying for 5 days?
Every agency-client relationship has a stretch where the client goes quiet, usually because something on their side became urgent. The question is what happens during those silent stretches.
Bad agencies stop working completely. They use your silence as permission to deprioritise. When you come back, the project has lost two weeks and they want a budget extension for “scope changes” that weren’t.
Good agencies have a process for these stretches. They keep working on what’s clearly scoped, document any decisions that need your input, and pick up exactly where they left off when you return.
What to ask specifically: “Walk me through your project management process. What happens if I’m slow to reply for a week? Do you keep working, or does everything pause?”
The answer should describe their actual workflow, typically a project management tool, a regular standup or update cadence, and clear documentation of decisions that need your input. If the answer is just “we’ll handle it,” that’s a soft answer to a hard question.
Question 3: Who owns the code, the design files, and the domain?
This is the single most important contract clause most clients never read.
By default, in the absence of an explicit contract clause, ownership of a website is murky. Some agencies retain ownership of design files and use that as leverage for retainer contracts. Some host your domain under their own account, which means you can’t move providers without their cooperation. Some keep the source code in their private GitHub and only deliver the compiled site, which makes future changes impossible without them.
None of this is automatically illegal. Some of it is even reasonable. But you should know before signing, not discover during a divorce.
What to ask specifically: “After we pay the final invoice: who owns the code, who owns the design files, who owns the domain, and who owns the hosting account? Will you transfer everything to me upon request, at no additional cost?”
Question 4: What’s your post-launch process, and what does it cost?
Launch is the start of the relationship, not the finish. The agencies that quietly disappear after invoice clearance are the ones who cause the most damage, bugs go unfixed, security patches are missed, small changes accumulate into “we need a rebuild” within 18 months.
You want to know two things: does the agency have a post-launch process, and what does it cost.
What to ask specifically: “What does the first 30 days post-launch look like? What about month 3? Month 12? Is maintenance bundled, billed hourly, or on retainer? What’s the response time for urgent issues?”
The answer should distinguish:
- Bug fixes (issues with originally-scoped work) typically free for 30–60 days post-launch
- Minor changes and updates (small content tweaks, small new features) typically billed hourly or in monthly retainer
- Security and platform maintenance (plugin updates, security patches, SSL renewal) typically retainer or included in hosting
If an agency hand-waves through this answer (“we’ll figure it out, don’t worry”), they don’t have a process. Anything they figure out later will be expensive.
Question 5: Show me the case study most similar to my project
This is the question that filters out agencies whose portfolio depth doesn’t match their sales pitch.
If you’re building an e-commerce store for a fashion brand, ask to see an e-commerce store they built for a fashion brand. If you’re building a multilingual real estate site, ask to see a multilingual real estate site they built. If they can’t show you something within two degrees of your project, they’re learning on your project, which can work, but you should know it.
What to ask specifically: “Show me the case study of the project you’ve shipped that’s closest in scope, industry, and complexity to mine. Walk me through what worked, what didn’t, and what you’d do differently.”
The “what didn’t work / what you’d do differently” part is critical. Agencies that can’t acknowledge anything they got wrong are either hiding things or genuinely don’t review their work, both bad.
Bonus: 3 red flags that should end the conversation
If any of these three things happen during your evaluation, walk away. They are not nuance situations.
1. The agency won’t put pricing in writing. Whether it’s a fixed quote or a clear hourly rate range, the agency should commit to something on paper. “We’ll send you a proposal” is fine for week 1. Five emails in, if you still don’t have numbers, you have your answer.
2. The agency talks about “industry-leading” or “award-winning” without specifics. Award names exist. Industry rankings exist. Verifiable third-party reviews exist (Clutch, GoodFirms, DesignRush). Vague superlatives without proof are a tell.
3. The agency promises something unrealistic. “We can launch your e-commerce store in 7 days.” “We can guarantee #1 ranking on Google.” “We’ll deliver this for 30% below market rate without compromising quality.” Pick one as a tell.
We welcome all five
If we lose a deal because someone asks us these five questions and finds our answers wanting, we want to lose that deal. The agencies who don’t want clients asking these are not the agencies you want to work with.
Send us your hardest version of any of them at info@avmdevs.com.
Frequently asked questions
Should I get quotes from more than one agency? Yes. Two minimum, three is healthy, more than four becomes a procurement exercise that delays everything. The goal is calibration, not picking the cheapest.
What’s a fair payment structure? Typical: 40–50% on kickoff, 30–40% at milestone (usually staging-environment delivery), 20% on launch and handover. Anything that asks for 100% upfront is a no.
How long should a discovery call be before signing? At least one 30-minute structured conversation. Often 2–3 calls for projects above $10K. If an agency tries to close in a single call, slow them down.
Should I sign an NDA before sharing project details? For sensitive projects, yes. Most reputable agencies will sign your NDA without resistance. If an agency refuses, ask why, usually the reason is fine (“we have a standard mutual NDA we prefer”), but you want the conversation.
What’s a typical project deposit in the UAE? 40–50% on kickoff is standard. Less than 30% upfront is unusually generous; more than 60% is unusually demanding. Either extreme deserves a question.
