The ongoing maintenance contract structure is one of the few decisions a Magento merchant makes that locks in operational reality for a year at a time. Hourly billing optimizes for control and flexibility. Retainer billing optimizes for predictability and responsiveness. Time-and-materials billing sits somewhere between. Each works for the right merchant; each fails for the wrong one. The patterns are clear enough that the decision should be deliberate rather than defaulted.
Bemeir’s Magento team works with clients across all three structures and the operational shape of each is meaningfully different. Here is the honest comparison.
What each model actually means
The terms get used loosely in agency contracts. The specifics that matter:
Hourly billing. The agency bills for actual hours worked at a defined hourly rate. The merchant pre-approves work in batches, the agency tracks hours against approved work, and invoices reflect actual time spent. There is no minimum commitment beyond the approved work. Rates typically run $175-$250 per hour for senior Magento developers at mid-market agencies.
Retainer. The merchant pays a fixed monthly fee in exchange for a defined amount of capacity (e.g., 100 hours per month) and a defined SLA on response time. Work within the capacity is included in the retainer. Work beyond the capacity bills at an overage rate. Unused capacity typically does not carry forward, though some retainers allow partial rollover.
Time and materials (T&M). A hybrid pattern: an hourly rate applies to actual work, but a minimum monthly commitment (typically 40-80 hours) is contracted in advance. The merchant gets some predictability through the minimum, the agency gets revenue predictability, and overage above the minimum bills at the hourly rate.
The three models look similar in pitch decks. They produce very different operational dynamics.
How each model actually operates
Hourly billing in practice. Every piece of work requires a scope, an estimate, and merchant approval before it starts. Maintenance work, bug fixes, and small enhancements all go through this approval cycle. The cycle adds operational friction: a small bug fix that should take 4 hours might involve 1 hour of scoping, an email approval cycle, and then the actual work. For ongoing maintenance, the friction can dominate.
The benefit: the merchant has explicit control over every billable hour. There are no surprises. The merchant pays only for what they explicitly approve.
Retainer in practice. The merchant has a named team available for the contracted capacity, with response time SLAs that match the retainer level. Routine work happens without per-task approval cycles. The agency has authority to handle defined maintenance categories (patches, monitoring, bug fixes under a certain size) without explicit sign-off on each one.
The benefit: dramatically lower operational friction for routine work, predictable monthly cost, and a partnership relationship rather than a transactional one. The cost: the merchant pays the full retainer even in months when the work volume is low.
T&M in practice. The minimum commitment establishes a baseline relationship and predictable agency revenue. Work happens at hourly rates against that minimum, with merchant approval for larger pieces but typically lighter approval cycles for smaller maintenance items. Overage above the minimum bills hourly with notification but typically without separate approval.
The benefit: more flexibility than pure retainer, less friction than pure hourly. The cost: the operational dynamics are less clear than either pure model, and merchant-agency alignment can drift if the structure is not actively managed.
The cost comparison at typical work volumes
A useful way to compare: what does each model cost for the same actual work output?
Assume a mid-market Adobe Commerce store with monthly work volume averaging 80-120 hours (security patches, bug fixes, small enhancements, performance tuning, support). Realistic monthly costs:
| Engagement model | Typical monthly cost | What you get |
|---|---|---|
| Pure hourly ($200/hr blended) | $16,000-$24,000 | Bills only for approved work, no minimums |
| Retainer (100 hours/month at $185/hr) | $18,500 | Fixed monthly fee, includes SLA, includes proactive maintenance |
| T&M (40-hour minimum at $195/hr, plus hourly overage) | $17,500-$22,500 | Mix of fixed minimum and variable work |
At consistent work volumes, the three models cost similar amounts. The pure hourly model is cheapest when work volume is genuinely low and most expensive when work volume is high (because every hour bills without volume discount). The retainer is most cost-efficient at the design capacity. T&M is in between.
Where the models diverge meaningfully is in months with unusual work volume. A pure hourly relationship in a quiet month might bill $4K. A retainer in the same month bills the full $18.5K. A retainer in an unusually busy month bills the same $18.5K plus overage.
When each model fits
Pure hourly is the right choice when: the work volume is genuinely variable and the merchant wants the flexibility to scale to near-zero in quiet months, the merchant has internal engineering capacity to evaluate and approve scoped work efficiently, the merchant prefers transactional vendor relationships to partnerships, and the work is mostly project-shaped (defined deliverables with clear endings) rather than ongoing maintenance.
It fits poorly when: the work is mostly ongoing maintenance with frequent small tasks, the merchant doesn’t have internal capacity to manage approval cycles, or the merchant needs guaranteed response times on incidents.
Retainer is the right choice when: the work volume is reasonably consistent month-to-month, the merchant values response time SLAs and proactive maintenance over per-task control, the relationship is partnership-oriented and expected to run for years, and the merchant wants the agency to take ownership of routine work without daily merchant involvement.
It fits poorly when: the work volume is genuinely variable, the merchant wants explicit control over every billable hour, or the merchant is in cost-cutting mode and willing to defer non-urgent work to save money.
T&M is the right choice when: the work volume has a predictable baseline but variable surge, the merchant wants the security of a committed minimum without the full cost of a retainer, the relationship is mid-term (year or two) rather than long-term partnership, or the merchant wants to test the agency relationship before committing to a full retainer.
It fits poorly when: the merchant is decisively cost-sensitive (pure hourly is cheaper), the merchant wants strong partnership dynamics (retainer is better), or the operational structure needs to be especially clear.
The non-cost factors that determine fit
Beyond the financials, several operational factors push the decision.
Response time expectations. If the merchant expects same-day or next-business-day response on incidents, a retainer with a documented SLA is the only model that genuinely delivers this. Hourly and T&M relationships can offer “best effort” response but cannot guarantee it without unusual contract terms.
Proactive vs reactive maintenance. Proactive maintenance (patches, monitoring, optimization, dependency updates) is structurally better fit to retainers because the agency has standing authority to do the work without per-task approval. Reactive maintenance (responding to issues as they arise) fits hourly or T&M models more naturally.
Internal engineering capacity. Merchants with strong internal engineering can manage the approval cycle of pure hourly efficiently. Merchants with limited internal engineering benefit from the agency taking ownership through a retainer.
Strategic vs tactical relationship. A retainer signals strategic partnership and produces deeper agency investment in the merchant’s business. Pure hourly signals transactional relationship and produces correspondingly shallower agency engagement.
Predictability requirements. Public companies, PE-backed companies, and merchants with strict budget governance often need predictable monthly costs. Retainers provide this; hourly does not.
The hidden costs of each model
Each model has costs that don’t show up in the per-hour rate.
Pure hourly hidden costs. The approval cycle has real cost: merchant time scoping each piece of work, agency time estimating each piece, communication overhead, and slower response to small issues. Stores that bill $15K/month in hourly work often spend another $3K-$5K of internal time managing the relationship.
Retainer hidden costs. Months when work volume is below the retainer capacity feel expensive. Merchants may push to “use the retainer” with work that doesn’t actually deserve the priority. The agency may struggle to deliver value in low-volume months, which can affect the long-term relationship dynamic.
T&M hidden costs. The structure can produce both the worst of hourly (approval friction on overage work) and the worst of retainer (committed minimum even in quiet months). Without active management, T&M can drift in ways that satisfy neither side.
The hidden costs make the model decision more nuanced than the headline math suggests. The right model is the one whose hidden costs are tolerable for the specific merchant.
What contracts should specify
Whichever model the merchant chooses, the contract should specify:
The exact hourly rate, with any role-based variations (developer vs architect vs project management). The capacity included in a retainer or T&M minimum, and the overage rate for work beyond it. The response time SLA by severity tier, with specific definitions of what “severity” means. The escalation path for issues the standard process cannot handle. The reporting cadence: monthly hours, monthly status, quarterly review. The renewal terms and the notice period for ending the engagement. The scope of work included: which categories of work are covered by the standard rates, which require separate scoping.
Vague contract terms produce friction the entire year of the engagement. Specific contracts produce clean operational relationships.
The pattern that works for most mid-market merchants
For most mid-market Adobe Commerce merchants we work with, the pattern that fits best is a retainer covering ongoing maintenance and routine enhancements, with project-based engagements layered on top for larger forward work (Hyvä migration, B2B implementation, replatforms).
The retainer ensures the store is well-maintained, patches stay current, performance stays tuned, and incidents get responded to predictably. The project engagements deliver the larger strategic initiatives without absorbing the retainer capacity.
This combination gives the merchant predictable ongoing cost, strong response times on operational issues, and a partner relationship that earns trust over years. It also gives the agency stable revenue that supports continued investment in the relationship.
Bemeir’s team runs retainers for many of our long-term clients alongside project engagements when forward initiatives come up. The merchants who land in this pattern often stay for many years; the merchants who try to operate purely on hourly billing often switch to retainer within 18 months once the operational friction becomes visible.
How to evaluate which model fits your situation
The deliberate decision-making sequence:
First, assess your actual monthly work volume from the last 12 months. The agency should be able to produce this from their billing records; if you haven’t been tracking it, this is the moment to start.
Second, assess the variance in that volume. Stable monthly volume fits retainer well. Highly variable volume fits hourly or T&M better.
Third, assess your internal engineering capacity and your tolerance for managing approval cycles. Higher capacity supports pure hourly; lower capacity supports retainer.
Fourth, assess your response time requirements. If incidents need guaranteed response, retainer is the only model that delivers it cleanly.
Fifth, assess your relationship preference. Partnership orientation supports retainer; transactional orientation supports hourly.
The result of this assessment usually points clearly at one of the three models. If it doesn’t, the merchant is in an ambiguous spot and T&M is often the right interim choice while the situation clarifies.
The contract structure decision is not glamorous, but it determines the operational shape of the agency relationship for the year ahead. Spend the time to pick deliberately, write the specifics into the contract, and revisit the choice annually. The merchants who do this have agency relationships that work. The merchants who default to whatever the agency proposes often find themselves in contract structures that fight their operational needs. Our team is happy to talk through what the right structure looks like for your specific situation, whether that ends up being us or another agency.
