The hardest part of evaluating a Magento agency relationship is that most of the warning signs are quiet ones. There is rarely a single catastrophic incident that crystallizes the decision. Instead, the failure mode is cumulative: a slightly slower ticket here, a missed roadmap commitment there, a recurring conversation about “scope” that never seems to resolve. Six months in, the retailer’s internal team has stopped expecting the agency to be a strategic partner and has started managing them as a vendor. That shift is the failure, even if the contract is technically still being honored.
This article catalogs the twelve signals we see most often when retailers reach out to Bemeir’s Magento development team for an outside read on whether to make a change. Some of these signals are fixable with a frank conversation. Some are structural and signal a relationship that has reached the end of its useful life. The diagnostic question at the end of each section is the one we would actually ask, in order to know which category a given situation falls into.
1. Ticket throughput is dropping, but the team size hasn’t changed
The cleanest signal of an agency in trouble is a steady decline in resolved tickets per sprint without a corresponding decline in the team you’re paying for. This usually means the agency has redeployed their best engineers to other clients and is staffing your account with junior or shared resources. The diagnostic question: ask for the named engineers on your account this sprint vs six months ago. If you cannot get a clean answer, you have your answer.
2. The senior architect stops showing up to status meetings
The senior architect on a Magento engagement is the person who keeps the platform from accumulating technical debt. When that person disappears from your status calls, it usually means they have been quietly reassigned to a higher-priority client. Adobe Commerce platforms decay rapidly without senior architectural oversight, especially around custom module patterns, performance regressions, and security patching. The diagnostic question: when was the last time you got an architectural memo or proactive recommendation from your agency, unprompted?
3. Roadmap commitments slip without renegotiation
A healthy agency relationship has a roadmap that lives, breathes, and gets renegotiated when reality changes. An unhealthy one has a roadmap that “slips” silently, with quarterly milestones quietly disappearing into the next quarter and then the next. The diagnostic question: pull last year’s roadmap and compare what was delivered to what was committed. If the gap is more than a third, the agency does not have the capacity it claimed.
| Roadmap signal | Healthy relationship | Failing relationship |
|---|---|---|
| Slip discussions | Initiated by agency, with proposed alternatives | Initiated by client, after the deadline has passed |
| Quarterly review | Strategic conversation about platform direction | Tactical review of open tickets |
| Architectural decisions | Documented in ADRs (Architecture Decision Records) | Live in a senior dev’s head, undocumented |
| Sprint planning | Agency proposes, client refines | Client demands, agency commits without pushback |
| Capacity changes | Discussed openly, renegotiated quarterly | Discovered after the fact through throughput |
4. Production incidents are explained, not prevented
Every Magento platform has incidents. The question is whether the same class of incident keeps happening. If your agency’s incident postmortems include “we will improve our monitoring” or “we will add a check for this” and you see the same incident again six months later, the postmortem culture is theater. The diagnostic question: of the last five production incidents, how many had genuine, traceable corrective actions that were actually implemented?
5. The infrastructure invoice keeps growing faster than traffic
Adobe Commerce hosting and infrastructure costs should scale roughly linearly with traffic, with some step changes around major scaling events. If your monthly AWS or Adobe Commerce Cloud bill is growing 30% year-over-year while traffic grows 10%, the agency is either over-provisioning or has not invested in the optimization work that mid-market platforms need. According to AWS’s eCommerce optimization guide, a properly tuned Magento environment should see roughly 60-70% steady-state utilization on its primary compute, not the 25-30% common on over-provisioned setups.
6. Hyvä, headless, and B2B updates aren’t being proposed
The Magento ecosystem is moving. Hyvä is the dominant frontend trajectory, Adobe Commerce B2B has shipped meaningful improvements, and headless architectures are no longer experimental for retailers with the team to support them. If your agency has not raised any of these conversations with you in the last twelve months, they are either not paying attention to the ecosystem or are deliberately steering you away from architectural changes that would reduce their billable hours. Bemeir’s Hyvä migration practice has seen retailers stay on legacy Luma frontends for two or three years past the point where the migration math made sense, almost always because the incumbent agency had no Hyvä capability and did not want to surface that fact.
7. The agency’s other client roster is shrinking or stagnating
Public client logos are a soft signal but not a meaningless one. Agencies in growth mode add logos; agencies in contraction quietly lose them. If you cannot point to any new named clients your agency has added in the last twelve months, that is a signal. The harder version of this signal is whether the agency is hiring or churning. LinkedIn is the public answer. The diagnostic question: how many engineers has your agency hired in the last year? If the answer is “fewer than they have lost,” you are watching contraction in real time.
8. Security patching arrives slowly, if at all
Adobe ships Magento security patches on a documented quarterly cadence. A healthy agency partner has applied a security patch to your production environment within two weeks of release, with a clear changelog and a regression test summary. An unhealthy one applies patches months late, batches them quietly into “maintenance windows,” or misses them entirely. The Adobe Commerce security center publishes severity ratings for every patch. The diagnostic question: of the last four security patches Adobe shipped, when were they applied to your production environment?
9. Performance metrics are not part of the conversation
Mid-market retailers cannot afford to treat Core Web Vitals as an SEO concern. Performance drives conversion. If your agency does not raise LCP, INP, or backend response times in your monthly review, they are not paying attention to the part of the platform that actually moves revenue. According to Google’s Core Web Vitals research, retailers in the top quartile for LCP have roughly 24% lower bounce rates than the bottom quartile. The diagnostic question: what is your current LCP on the product detail page, and does your agency know without looking it up?
10. Documentation is in someone’s head
The single most diagnostic question for an agency relationship is this one: if your senior architect on this account went on a four-week leave tomorrow, who could continue the work? If the answer is “no one,” the agency has built a knowledge concentration risk into your platform. Reputable Adobe Commerce agencies treat documentation as a deliverable, not an afterthought, and the best ones use formal architecture decision records and runbooks rather than relying on tribal knowledge.
11. Pricing conversations get tense
A healthy commercial relationship has clean conversations about scope and price. An unhealthy one has tense conversations where the agency feels squeezed and the client feels overcharged. When pricing becomes the dominant topic of every quarterly review, the relationship has shifted from partnership to negotiation. That shift is rarely reversible.
12. Internal teams have started routing around the agency
The final, most telling signal: when your merchandising or marketing teams start asking your in-house developers to make changes “because the agency is too slow,” the agency has lost its position as the platform’s center of gravity. From that point, the agency is a vendor for tickets the internal team does not want to do, and the strategic partnership is gone. This is the signal that decides whether the relationship is salvageable.
What to do next
Three or four of these signals can describe a fixable relationship. Eight or more describes a relationship that is consuming more energy than it is producing. The retailers who handle this well do not wait for ten signals before they act. They commission a second-opinion Magento technical audit from a different agency, compare the audit findings to what their current partner has been saying, and make the call from there. The audit alone, even if you stay with your current partner, is one of the highest-ROI investments a mid-market Adobe Commerce retailer can make. The platform has too much money flowing through it to leave the strategic conversation to a partner who has stopped showing up.
