Overview
An Amplience retainer is an ongoing Care engagement for a prioritized backlog of Amplience development and maintenance. AmpliFabrik supports commerce brands and integrators in the US and Canada, including teams taking over an implementation after support stalls. We review your setup, identify gaps, and agree the work, capacity, and responsibilities. The backlog can cover Amplience CMS (Dynamic Content), Amplience DAM (Content Hub), Dynamic Media, integrations, and editorial tools. A health check can help establish priorities before a retainer starts. We plan changes with your team and agree acceptance criteria and release dependencies. The role mix, working overlap, planning cadence, and fees are set in the engagement agreement. Your team retains business priorities and production approvals. For white-label work, the integrator owns the client relationship and controls introductions; AmpliFabrik stays unnamed unless invited, with ongoing support routed through the partner. We are an Amplience Partner Program member, operated by Senior Maple Marketing Ltd. in Saint John, New Brunswick. The retainer places continuing work in your delivery calendar, with progress and open decisions recorded for review.
Key facts
How an Amplience retainer supports ongoing development and maintenance
A planned backlog connects ongoing work with your platform context
Match Amplience expertise to the work your team needs next
Keep post-launch improvements tied to changing business priorities
Clear responsibilities connect feature delivery with support and production decisions
What an AmpliFabrik Amplience managed retainer engagement covers
Continuous feature delivery
Content model evolution
Integration extension and maintenance
Performance optimization and Core Web Vitals tuning
CMS extensions and editorial productivity improvements
Multi-brand and multi-market expansion work
What AmpliFabrik delivers
01 - Agreed Amplience capacity and role mix
02 - Clear sprint and program progress reports
03 - Backlog planning as priorities change
04 - Maintained context and handovers
Frequently asked questions
An Amplience managed retainer is an ongoing Care engagement for agreed development and maintenance work. We review your implementation and backlog, then set the scope, capacity, role mix, and planning arrangements in the agreement. Your team prioritizes requests and approves completed work. Reports record progress, capacity use, risks, and decisions. It can support an inherited implementation after an integrator exits, with a health check used to identify the first priorities and access needs.
The minimum commitment is set in your proposal and agreement. We review workload, onboarding, and delivery responsibilities before proposing a term. Renewal, review points, notice periods, capacity changes, and exit arrangements are documented there. Your team can assess the commitment and handover requirements before the engagement begins.
Pricing follows the agreed workload, role mix, capacity, and working arrangements. Scoping considers your implementation, access, dependencies, and the maintenance or development needed. Your proposal records the charging basis, what is included, and how additional work is approved. Emergency coverage and its effect on fees or planned capacity require separate agreement.
Your team keeps business priorities, product decisions, and release approvals. We contribute to the agreed Amplience work, with planning, code review, and handover arrangements matched to your processes. Shared records show dependencies and open decisions. For white-label delivery, the integrator owns the client relationship and controls introductions. AmpliFabrik remains unnamed unless invited, and ongoing support stays through the partner.
Yes. We review priorities at each planning cycle within the agreed scope and capacity. We assess requests for effort, dependencies, and their effect on work already planned. A backlog adjustment may fit the allocation; a new market launch or integration may need a scope or capacity review. We document any effect on timing or fees and obtain the required approval before committing the change. Your team remains responsible for business priorities.
Emergency Support can be scoped alongside a managed retainer, subject to confirmed availability and agreement. Coverage hours, response terms, escalation, approvals, and charges are documented separately. The agreement also defines whether incident work affects retainer capacity. Round-the-clock coverage or the same staff for both services requires explicit agreement.
We review the changed workload and discuss the capacity or engagement format that fits it. A smaller allocation or a scoped Platform Support arrangement may fit. Any change follows the agreed notice, commercial, and transition terms. We identify work to finish or hand over, update responsibilities, and record access and support arrangements before the transition.
An implementation project has defined delivery goals, such as a launch, integration, or substantial platform change. A managed retainer supports a continuing backlog of maintenance and development in an existing implementation. It can begin after another integrator built the platform or when your internal team needs ongoing Amplience expertise. We review access, documentation, and open issues before agreeing how the retainer will work.