Magento projects stall in patterns that are recognizable across retailers. The timeline keeps slipping. The launch date keeps moving. The scope keeps evolving without coherent forward progress. The agency relationship is producing more friction than value. The internal team is frustrated. The executive sponsors are starting to ask hard questions. And the original decision to choose this agency, made eighteen months ago, no longer looks like a good decision in retrospect.
The question of whether and when to bring in a new Magento agency for a stalled project is one of the harder strategic calls a retailer faces. Switching agencies mid-project carries real cost – knowledge transfer, momentum loss, contractual complexity, executive credibility risk. Continuing with an agency that is not delivering carries different cost – continued delays, mounting frustration, business impact from delayed launch. The right decision depends on the specific situation, and the framework below is what we use when retailers come to us asking whether they should switch.
The Signals That the Project Is Genuinely Stalled
The first diagnostic is whether the project is genuinely stalled or is going through a temporary rough patch. Every multi-month project has hard periods – discovery surfaces complexity that the original plan didn’t account for, integration realities turn out to be different from what was scoped, team members rotate at inconvenient times, business priorities shift in ways that affect scope. These are normal patterns, and the right response is usually to work through them with the existing agency rather than to switch.
The stall signal is different. The stall signal is not a hard period but a structural condition where the project is no longer making forward progress toward a credible completion. The signals include velocity that has been declining for three or more months without explanation, scope that keeps expanding without corresponding timeline or budget acknowledgment, multiple consecutive milestones missed without credible recovery plans, the senior people named in the proposal no longer being involved in the project, the agency’s responses to questions becoming defensive rather than collaborative, and the project’s completion date that has moved multiple times without a believable path to the new date.
The presence of one or two of these signals is informative but not necessarily decisive. The presence of three or more in combination usually indicates structural stall rather than temporary difficulty. The pattern compounds – each signal makes the others harder to address, and the cumulative trajectory is downward.
The Diagnostic Conversation
Before deciding to switch agencies, the retailer should have a candid diagnostic conversation with the current agency’s senior leadership. The conversation should not be a complaint session. It should be a structured assessment of the project’s actual state and what would have to change for it to reach successful completion with the current agency.
The questions to bring to this conversation include: what is the agency’s honest assessment of the project’s current state and trajectory, what specific changes would the agency commit to that would address the patterns the retailer is seeing, what is the realistic completion date and budget given current state, and what is the agency’s accountability mechanism for the commitments they make in this conversation.
The agency’s response tells you a lot. A healthy agency facing project stall will engage substantively with the conversation – acknowledge the patterns, propose specific changes, commit to revised timeline and budget with explanation, and accept accountability mechanisms that make the commitments credible. An unhealthy agency facing project stall will deflect, blame the retailer for scope changes that the agency could have managed differently, propose vague changes without specific commitments, and resist accountability mechanisms.
If the response is healthy and the proposed changes are credible, the right move is usually to give the existing agency the chance to execute on the commitments. The cost of switching is real, and a productive recovery conversation is often less expensive than a full agency transition. If the response is unhealthy or the commitments are not credible, the case for switching becomes stronger.
The Cost of Continuing
The cost of continuing with a stalled project is often underweighted in the switching decision. The direct cost is the continued agency fees for work that is not producing commensurate progress. The indirect costs are typically larger – delayed launch produces opportunity cost (revenue from the delayed capability, competitive position from earlier launch), continued operational fragility produces incident cost, accumulated technical debt produces future remediation cost, and team morale impact produces hiring and retention cost.
The continued cost has a half-life problem. Most retailers underweight the future cost because the future is uncertain. The honest cost analysis should include the realistic future cost over the projected continuation period – six months of continued agency fees plus opportunity cost plus team impact often exceeds the cost of switching agencies and accepting the transition friction.
The cost analysis should also include the option value of switching. Continuing locks the retailer into the current agency’s trajectory; switching opens the option of a different trajectory. The option value is real even if the switching cost looks high on the surface – the worst case after switching (a new agency that is no better than the current one) is bounded by another switching decision, while the worst case of continuing (the project never completes successfully) is unbounded.
The Cost of Switching
The switching cost is also real and should not be underweighted. The direct costs include the new agency’s discovery and ramp-up time (typically two to three months at full agency cost during which limited progress is being made), the knowledge transfer cost (time from both internal team and outgoing agency that doesn’t go to forward progress), and the contractual complexity (winding down the outgoing agency, executing the new agency contract).
The indirect costs include the operational risk during the transition (the outgoing agency’s cooperation is uncertain, the new agency’s context is incomplete, production issues during the transition are harder to handle), the morale risk for the internal team (transitions are stressful, and team members who liked working with the outgoing agency may not adapt well), and the credibility risk for executive sponsors (the original decision to choose the current agency is now being reversed, which raises questions about the broader judgment quality).
The switching cost is bounded but real. The retailer who treats switching as a binary “do it or don’t” decision often underweights the practical execution complexity. The retailer who treats switching as a structured project – with a transition plan, a knowledge transfer protocol, an operational continuity plan, and a clear accountability structure – manages the costs effectively.
| Decision Signal | Continue With Current Agency | Switch Agencies |
|---|---|---|
| Stall duration | Recent issues, recovery plausible | 3+ months of declining velocity |
| Senior involvement | Pitched architect still engaged | Senior people rotated off |
| Agency response | Substantive, committed, accountable | Defensive, vague, deflecting |
| Commitment credibility | Realistic plan with accountability | Promises without mechanism |
| Operational risk | High switching disruption | Continuing produces incidents |
| Internal morale | Team still motivated | Team disengaged or demoralized |
| Executive patience | Sponsors still supportive | Sponsors questioning the project |
| Path to completion | Visible, achievable | Unclear, ever-receding |
| Budget runway | Sufficient for credible recovery | Burning without progress |
When to Switch
The right time to switch is when the diagnostic conversation has not produced credible commitment to change, when the continued cost of the stalled project exceeds the cost of switching, when the operational risk of continuing is higher than the operational risk of switching, and when the internal team is sufficiently engaged to support the transition.
The right time to switch is also when executive sponsors are still engaged. The window for switching closes once executive support has eroded – at that point, the project itself is at risk, not just the agency relationship. A switch that happens while executive support is still solid can produce a successful recovery; a switch that happens after executive support has eroded often produces project cancellation rather than recovery.
The right time to switch is rarely “immediately.” The deliberate switch – with a transition plan, a structured discovery for the new agency, a clear knowledge transfer protocol, and an operational continuity plan – produces better outcomes than the emergency switch driven by crisis. The retailers who switch deliberately typically take six to twelve weeks from the decision to the transition completion. The retailers who switch in crisis often end up with sub-optimal new agency choices and longer post-switch recovery periods.
How to Structure the Switch
The structured switch starts with a rigorous selection process for the new agency. The selection should not default to the agency that is most easily available or the agency that was second in the original procurement. The selection should treat the new engagement as a fresh evaluation, with the additional information that the retailer now has from the stalled project. The retailer knows what kinds of failure modes to filter for – they have seen them firsthand.
The selection should specifically evaluate the candidate agencies on their ability to handle the inherited situation. The questions include: how do you handle inherited codebases that have known issues, what is your discovery process for projects in mid-state, how do you structure knowledge transfer from outgoing agencies, what is your operational continuity plan during transitions, and what is your accountability mechanism for the commitments you make about timeline and budget. The candidates who give specific answers with documented process are signaling the discipline they will bring; the candidates who give generic answers are signaling the opposite.
The transition plan should specify the dates, the deliverables, and the responsibilities for each party. The outgoing agency’s knowledge transfer obligations should be contractually specified with reasonable payment terms tied to KT completion. The new agency’s discovery deliverables should be specified with explicit checkpoints. The operational continuity ownership should be specified by severity level, with the outgoing agency typically available as fallback for high-severity issues during the first sixty days.
The communication plan with internal stakeholders should be structured. The team needs to understand why the switch is happening, what the new agency will be doing, and how the team’s work will change during the transition. Without clear communication, transitions produce uncertainty that compounds the operational risk.
When Not to Switch
Some situations look like agency problems but are actually retailer-side problems. The pattern includes scope that keeps changing because the retailer’s product organization has not been disciplined, requirements that emerge during implementation because the retailer’s discovery was insufficient, and frustration with the agency that reflects internal team conflict more than agency performance.
The diagnostic move is to ask whether the patterns the retailer is frustrated with would change if the agency changed. If the patterns are driven by the retailer’s own processes, switching agencies will produce the same problems with a different vendor. The right fix is to address the internal patterns first, then evaluate whether the agency relationship needs to change.
The other situation where switching is not the right move is when the project is close enough to completion that the switching cost exceeds the completion cost. A project that is in the final stabilization phase, with the major work behind it, is usually not the right candidate for switching. The right move is to complete the project with the current agency, address the patterns through a deliberate post-launch review, and apply the lessons to the next agency selection.
Bemeir’s rescue project practice handles the inherited stalled project scenario specifically. The first conversation with prospective rescue clients includes an honest assessment of whether switching is the right move – sometimes the right answer is to continue with the current agency, and we say so. When the switch is the right move, Bemeir’s structured transition process addresses the operational continuity, knowledge transfer, and discovery work that determines whether the switch succeeds. For Hyvä-themed projects in particular, the additional theme expertise often surfaces in stalled projects where the previous agency lacked Hyvä depth.
For deeper reference on agency transitions and project recovery patterns, the Adobe Commerce Solutions Partner directory provides the broader partner landscape, Magento Open Source community resources provide ecosystem context, and broader research from Forrester on commerce services transitions and the Project Management Institute on project recovery provides additional structured frameworks for the broader decision pattern.
