The conversation about replacing a Magento agency rarely starts with a clean diagnosis. It starts with the CTO frustrated about a missed deadline, the COO frustrated about a budget overrun, and a quarterly review where the agency-side account manager promises that things will get better next sprint. The instinct in that moment is to either tolerate it for another quarter or fire the agency entirely. Both can be wrong. The middle path, a structured renegotiation, is the right move in roughly half of these situations, and getting the diagnosis right is what determines whether the next six months are a recovery or a continued slide.
This piece is a framework for engineering leaders who suspect their current Magento partner is underperforming. It separates problems that respond to contract changes from problems that require an actual replacement. The framework comes out of Bemeir’s experience inheriting projects from previous agencies, where the patterns of “should have been replaced six months ago” and “could have been salvaged” are remarkably consistent.
The Two Categories That Matter
Most agency dysfunction falls into one of two categories. The first is structural: the contract is wrong, the team assignment is wrong, the cadence is wrong, or the scope is unbounded. These are fixable with paperwork and meetings. The second is fundamental: the agency lacks the skills, the agency lacks the capacity, or the trust has been broken in ways that cannot be rebuilt. These require replacement.
Distinguishing the two requires honesty from the in-house team about what is actually broken. The temptation is to attribute everything to agency failure when sometimes the brief was vague, the access was denied, the priorities shifted without notice, or the in-house engineering review process was the bottleneck. A renegotiation has the best odds when both sides can name what they each did to create the current situation.
Symptoms That Point to Renegotiation
If the agency has demonstrated technical capability on past deliverables but the current quarter is sliding, the problem is usually structural. Look for these patterns:
- The senior engineer who shipped your last successful project has been rotated off your account
- Velocity has dropped because the agency is now charging blended rates and using junior developers for senior work
- The retainer hours are consumed by status meetings and discovery calls rather than committed work
- Communication has degraded because the agency reorganized and your account manager changed
- The contract scope no longer matches your business reality, but neither side has formalized the change
Each of these is a renegotiation problem, not a replacement problem. The team that did good work before can do good work again if the structure supports it. The contract amendments that fix these issues are usually straightforward: name specific senior engineers, restructure rate cards, reset cadence expectations, formalize scope.
Symptoms That Point to Replacement
Replacement is the right call when the failure pattern is about underlying capability, not surface dynamics. Watch for these signals:
- Code reviews surface architectural choices the team cannot defend technically, they made the choice because they did not know better
- Performance problems that the agency cannot diagnose despite being explicitly engaged for performance work
- Repeated regressions on functionality the agency has touched before, indicating no test discipline
- A pattern of “this is just how Magento works” answers when the actual issue is the agency’s implementation
- Delivery slippage with no honest accounting of what went wrong, the postmortems are PR exercises rather than learning exercises
- Security incidents traced to the agency’s choices, especially if the agency resists transparent root-cause analysis
These signals are not fixed by a contract amendment. The team in front of you cannot do the job, and rearranging the contract will not produce skills they do not have.
The Diagnostic Conversation
Before deciding, run a single structured conversation with the agency. Frame it as a quarterly health check. Ask them to articulate:
- What is currently going well in the engagement and why
- What is not going well and why, in their assessment
- What would need to change on the agency side to fix it
- What would need to change on the client side to fix it
- What the agency would do if the relationship were reset tomorrow
The substance of these answers matters less than the quality. An agency that can engage with question four honestly, naming things the client could do differently, is showing the kind of partnership behavior that renegotiation depends on. An agency that gives only sales answers, deflects, or treats the conversation as a threat is showing you that they do not have the maturity to recover.
Bemeir runs this conversation with every retainer client quarterly because we have learned that the relationships that thrive are the ones where both sides can name uncomfortable truths early.
The Cost Comparison
A common reason teams stay with a failing agency longer than they should is the perceived cost of replacement. The actual math is usually less dramatic than the fear.
| Cost category | Renegotiation (existing agency) | Replacement (new agency) |
|---|---|---|
| Onboarding time | None | 4-8 weeks ramp-up |
| Knowledge transfer cost | None | $15-50k depending on codebase |
| Productivity gap | Immediate improvement possible | 6-12 weeks before full velocity |
| Risk of continued underperformance | High if structural diagnosis was wrong | Moderate during transition |
| Contract negotiation effort | Amendment, 1-2 weeks | Full RFP and SOW, 4-8 weeks |
| Long-term ceiling | Capped by existing team capability | Reset to new team’s ceiling |
If the team you currently have has a low ceiling, which is what the replacement signals above are telling you, paying the transition cost is the right investment. If the ceiling is high and the current situation is structural, renegotiation buys you the same upside for almost no cost.
How to Run a Renegotiation
If the diagnosis points to renegotiation, structure the conversation around outcomes, not blame. Bring a written list of changes you want: named team assignments, revised cadence, restructured rate cards, scope clarifications, escalation paths. Ask the agency to bring their own list of changes they need from the client side. Schedule the conversation for a working session, not a status meeting, and bring procurement so that contract amendments can be drafted in the room.
Renegotiations work when both sides can commit to changes they believe will hold. They fail when one side is performing politeness while planning to leave anyway, which is why the diagnostic conversation above matters so much. If the in-house team has already lost faith, renegotiation is theater. Skip it.
How to Run a Replacement
If the diagnosis points to replacement, the next decision is the transition shape. Some teams cut the existing agency immediately. Some run a parallel transition where the outgoing agency stays on a defined wind-down scope while the incoming agency ramps up. The parallel approach costs more in the short term but reduces the risk that a critical issue surfaces during the gap.
Bemeir specializes in rescue engagements where we onboard a Magento codebase from a previous agency in parallel with their wind-down. The pattern is documented in our Magento development practice page. Most of these engagements include a thirty-day overlap where both teams have access, the new team builds the audit, and the outgoing team responds to documented questions. For Hyvä migrations that have stalled with a previous agency, the same pattern applies on the Hyvä practice, and for stores considering a platform change as part of the transition, the Shopify Plus and Shopware practices both follow the same overlap-and-onboard model.
The Decision
The decision between renegotiation and replacement is rarely about money. It is about whether the team you have can do the work you need. If they can, fix the structure. If they cannot, do not pretend otherwise. The cost of an extra six months of underperformance, in delayed revenue, accumulated technical debt, and team morale, almost always exceeds the cost of transitioning to a partner who can actually deliver. Industry surveys from Digital Commerce 360 consistently show that mid-market retailers who postpone agency changes lose more than the transition would have cost them. Be honest about which category you are in. The framework above is meant to make that honesty easier.
