The conversation about Adobe Commerce retainer pricing usually starts in the wrong place. Merchants ask “how much” before asking “what for,” and agencies quote a number before asking what the actual usage pattern will look like. The result is mismatched expectations on both sides, the 40-hour retainer that runs out by the second week of every month, the 160-hour retainer that the merchant never fully uses, the agency that resents the scope creep while the merchant resents the bill. The underlying problem is that retainer hours are not interchangeable, and the price-per-hour comparisons that procurement loves to make are usually missing the context that determines value.
This piece walks through what the typical Adobe Commerce maintenance retainer tiers actually include, what they exclude, and how to choose the right size for your store. It is written for eCommerce leaders, COOs, and operations directors who are responsible for the ongoing Magento or Adobe Commerce relationship at their company. The patterns below come from Bemeir’s retainer practice across stores ranging from twenty million to a quarter billion in annual revenue, and they reflect what we have learned about which tiers actually fit which kinds of merchants.
What a Retainer Hour Is and Is Not
A retainer hour is not just developer time. The agencies that price retainers honestly include a mix of senior engineering, junior engineering, project management, QA, devops, account management, and incident response, and the blend matters enormously. A “40 hours” retainer at one agency might be 30 hours of senior engineer time. At another, it might be 35 hours of junior engineer time with a part-time PM. The two are not the same product even at the same price.
When evaluating retainer proposals, ask explicitly:
- What is the named team composition?
- What seniority level is in the blend?
- Is QA inside or outside the hour count?
- Is devops inside or outside?
- Is incident response and after-hours availability inside the hours, or is it billed separately?
- What is the response time SLA for production incidents?
These answers determine what the retainer is actually buying.
The 40-Hour Tier: Maintenance Only
A 40-hour monthly retainer (roughly 10 hours per week) is a maintenance-only commitment. It covers:
- Adobe Commerce security patches when they release (typically Patch Tuesday in the second month of each quarter)
- Monthly security review and dependency scanning
- One or two small feature requests or bug fixes per month
- Reactive incident response within SLA hours
- Quarterly platform health checks
- Light advisory and Q&A
It does not cover:
- Sustained feature development
- Significant migrations or refactors
- 24/7 incident response
- Complex integrations or third-party debugging
The 40-hour tier is appropriate for stores that have a stable codebase, an in-house team handling most development, and a need for specialized Adobe Commerce expertise on retainer for the work in-house cannot handle. It is the wrong tier for stores that need active feature development.
Common failure mode: the merchant signs a 40-hour retainer expecting to “build features as they come up” and finds that two months in, the retainer is consumed by patch cycles and small fixes with no capacity left for the roadmap.
The 80-Hour Tier: Maintenance Plus Light Development
An 80-hour monthly retainer (roughly 20 hours per week) supports maintenance plus light development. It covers everything in the 40-hour tier, plus:
- Sustained feature development at modest pace
- One or two integration projects per quarter
- More substantive performance work
- More active advisory and architecture consulting
- Faster response times for non-critical issues
It still does not cover:
- Major migrations or platform-level projects
- Around-the-clock incident response
- Heavy custom development on multiple parallel workstreams
The 80-hour tier is the most common retainer for mid-market Adobe Commerce stores in the $20-100M revenue range. It is large enough to make meaningful progress on the roadmap while small enough to remain efficient. Bemeir’s Adobe Commerce retainer practice sees the 80-hour tier as the typical entry point for stores that have moved beyond launch and are settling into operational rhythm.
The 160-Hour Tier: Active Engineering Partnership
A 160-hour monthly retainer (roughly 40 hours per week, or one full FTE-equivalent) represents an active engineering partnership. It covers everything in the smaller tiers, plus:
- A named primary engineer who is effectively dedicated to the account
- Active roadmap execution at significant pace
- Multiple parallel workstreams
- Direct integration with the merchant’s product and engineering teams
- Sprint-cadence delivery
- Faster incident response and broader after-hours coverage
The 160-hour tier is appropriate for stores in the $50-200M range that have ongoing platform investment and want a partner doing the work rather than just standing by to support. It is also common for stores in the middle of a migration, a platform expansion, or a significant integration program.
The cost is meaningful, typically $25-40k per month depending on the agency’s blended rate, but it represents a real engineering capacity, not just availability.
| Tier | Hours / month | Typical use | Best for | Common mismatch |
|---|---|---|---|---|
| 40 hr | ~10/week | Maintenance only | Stores with in-house dev team needing specialist coverage | Underestimates feature work, overruns by month two |
| 80 hr | ~20/week | Maintenance + light development | Mid-market $20-100M with active but moderate roadmap | Right-sized when scoped honestly |
| 160 hr | ~40/week | Active engineering partnership | $50-200M with ongoing investment, migration, or expansion | Often the floor for stores doing serious work |
| 240+ hr | ~60+/week | Embedded team | Stores effectively outsourcing eCommerce engineering | Should be structured as named team, not raw hours |
Above 160: The Embedded Team Pattern
For stores beyond 160 hours, the pricing model usually shifts from retainer-hours to a named embedded team. The conversation becomes “you have this team of three engineers working full-time on your account” rather than “you have this many hours per month.” The team is named, the seniority is specified, and the agency is committed to keeping that team consistent rather than rotating people.
This pattern is appropriate for stores that effectively outsource their Adobe Commerce engineering. It is not a maintenance retainer at this scale, it is a build relationship.
What Drives Tier Selection
A few factors drive which tier is right for a given store:
- In-house engineering capacity: stores with strong in-house Magento expertise need less retainer; stores without in-house expertise need more.
- Catalog and platform complexity: high-SKU stores, B2B stores with ERP integration, multi-storefront installations all need more retainer than simple DTC catalogs.
- Roadmap intensity: stores actively shipping features need more; stores in maintenance mode need less.
- Adobe Commerce version and patch posture: stores behind on patches need catch-up work, which consumes retainer hours that would otherwise be feature work.
- Integration density: stores with many third-party integrations spend more retainer on integration maintenance.
- Traffic and incident frequency: high-traffic stores have more production incidents, which consumes retainer hours.
A reasonable diagnostic: track the previous twelve months of work done against the store, in hours, by category. The total tells you what the actual demand has been. The category breakdown tells you what kind of retainer fits the demand.
What’s Outside Every Retainer
Some categories of work should be outside every retainer tier and priced separately:
- Major migrations (Magento 1 to Adobe Commerce, Luma to Hyvä, headless transitions)
- Platform replatforms (to or from Shopify Plus, Shopware, BigCommerce)
- New storefront launches
- M&A-driven brand integrations
- Compliance-driven projects (PCI scope reduction, accessibility remediation)
These projects are too large to absorb into a maintenance retainer without breaking the retainer’s economics. They should be scoped, priced, and contracted separately, with the retainer continuing in parallel.
Bemeir’s Hyvä migration practice and Shopify Plus practice both treat migrations as separate scoped projects rather than retainer absorptions, because the economics of migrations and the economics of maintenance are different and bundling them produces unhealthy retainer dynamics.
The Honest Tier Conversation
The conversation about retainer sizing should happen at the start of every engagement and should be revisited every quarter. The right tier today may not be the right tier in six months. Stores that go through a migration usually need more retainer immediately afterward as they stabilize and then can step down. Stores entering a heavy investment cycle need more for the duration of the cycle and can return to baseline once the work ships.
Both sides benefit from the conversation being explicit. The agency that quietly burns through hours on scope creep is providing bad service. The merchant who quietly accumulates unused hours is wasting money. The relationship that thrives is the one where the conversation about whether the tier fits is held openly and adjusted when needed.
For broader benchmarks on agency retainer pricing in eCommerce services, Clutch’s eCommerce agency rate surveys and Digital Commerce 360’s vendor reports provide market data. Use these to calibrate against the local agency proposal you’re evaluating. The right tier is the one where the work that needs to happen fits inside the hours the merchant is willing to commit, with both sides comfortable with the answer.
