Adobe Commerce Agency: How to Hire One and How Engagements Work

An Adobe Commerce agency is a services firm that plans, builds, connects and runs online stores on Adobe Commerce, the platform many teams still call Magento. The right one has delivered your kind of project before, on the same deployment model. It will also put its plan in a proposal you can hold it to. This guide covers what agencies do, engagement models, shortlisting and vetting, red flags, proposal contents and cost drivers.

What does an Adobe Commerce agency do?

An Adobe Commerce agency usually sells six kinds of work: new builds, replatforming, business-to-business (B2B) programs, integrations, performance work and ongoing support. Very few firms are equally strong at all six. So before you talk to anyone, decide which one sits at the center of your project.

Integrations usually mean connecting the store to an enterprise resource planning (ERP) system and a product information management (PIM) tool. Order management, payments and tax come next. Here's how the six services break down, and the proof worth asking for in each.

Most agency marketing focuses on the first two rows. The last row is where most of the long-term relationship happens. Adobe's shared responsibility model for Adobe Commerce on cloud infrastructure puts this on the merchant. The merchant applies "security and other patches to all custom extensions and code" as soon as vendors release them. In practice that work lands with your agency, so its support offer matters as much as its portfolio.

If B2B is the core of your project, read our guide to hiring an Adobe Commerce B2B development agency. The evidence you need from a B2B specialist is different.

Do you need an agency, a freelancer or your own team?

You need an agency when a project calls for several roles at once for a set period. That usually means an architect, backend and frontend developers, quality assurance (QA), a project manager and someone who owns the hosting setup. Hiring all of those yourself takes months, and you'd still carry them after launch.

If you already run an in-house team and only lack one skill, an agency may be the wrong tool. A single contractor or a staff augmentation deal can fill the gap for less. Our guide to Adobe Commerce experts covers the roles, certifications and vetting for individual hires.

Some merchants mix the two. The agency builds and hands over, then an internal team takes on day-to-day changes. The agency stays on a small retainer for upgrades and escalations. That works well when the handover is planned from the start, not bolted on at the end.

How does an Adobe Commerce agency engagement work?

Most engagements run through the same stages: discovery, solution design, build, testing, launch and then ongoing support. Adobe's own implementation playbook follows a similar arc, from project scoping through development, integrations and deployment to ongoing support. What changes between agencies is how much they write down at each stage.

Here's what each stage should give you:

• Discovery. Workshops with your business, IT and operations teams. You should come away with a requirements list, an integration map, a risk list and a revised estimate.
• Solution design. The architecture, data model, extension list and storefront approach. The agency should say what will be native, what will be configured and what will be custom code.
• Build. Usually two-week sprints with a demo at the end of each. You should have access to the code repository and the ticket board from day one.
• Testing. Functional tests, user acceptance testing by your own team, performance and load tests, and checks on payment and tax flows.
• Launch and hypercare. A cutover plan with a rollback option, then a few weeks of closer support while real orders flow.
• Run. Patches, upgrades, monitoring and a backlog of small improvements.

The handoffs between stages are where projects slip. If discovery ends without a revised estimate, or design ends without a written list of customizations, expect surprises later.

Here's a pattern buyers run into often. A retailer signs a fixed price based on a short brief and skips discovery. Six weeks into the build, the team learns the ERP only sends stock updates once a night, and the business wants live stock on product pages. That gap turns into a change request, a new integration design and a later launch date. A two-week discovery would have found it before anyone signed.

Fixed scope, time and materials or retainer: which model fits?

The right engagement model depends on how certain your scope is. Fixed scope suits work you can describe in detail. Time and materials suits work where you'll learn as you go. A retainer suits ongoing support and a steady stream of improvements.

Buyers commonly see the hybrid pattern on larger builds. A paid discovery at a fixed fee produces the detailed scope. The build then runs on time and materials with a cap, or on a fixed price based on that scope. Support moves to a retainer after launch.

Two details matter more than the model's name. First, how change requests are priced and approved. Second, what happens to retainer hours you don't use in a month. Ask both questions before you compare totals.

How do you shortlist Adobe Commerce agencies?

Start with firms that have done your type of project on your deployment model, then narrow by team fit. Three to five serious candidates is enough. With more than that, you won't have time to vet each one properly.

Good starting points are our directory of Adobe Commerce partners, Adobe's own Partner Directory and peers who run similar stores. Then filter on these points:

• Project type. A firm that mostly builds new direct-to-consumer stores may struggle with a complex replatform.
• Deployment model. Adobe Commerce on cloud infrastructure, Adobe Commerce as a Cloud Service and self-hosted installs need different skills. Our guide to choosing an Adobe Commerce cloud development company explains the split.
• Industry and region. Tax rules, payment methods and languages differ by market. Overlap with your working hours matters for support.
• Size fit. You want to be a meaningful client. A small store can get lost in a very large firm, and a huge program can stretch a small one.

When you read any directory, ours included, keep two kinds of information apart. One is what the public record shows, such as an Adobe partner level. The other is what the firm says about itself, such as headcount or certification totals. Both are useful, but only the first has been checked by someone else.

Partner status in Adobe's program is a useful filter, not a verdict. Our guide to Adobe Commerce partners explains how to check a firm's level and Commerce specialization in Adobe's directory.

How should you vet an Adobe Commerce agency before you sign?

Vet the people who will do the work, not the pitch team. The most useful checks are reference calls, a working session with the proposed technical lead and a small paid task. Do all three before the main contract.

Ask references specific questions. What went wrong, and how did the agency handle it? Did the named team stay on the project? How did the store hold up at its first big sales peak? Were launch dates met, and if not, why not?

Then spend an hour with the technical lead. Ask them to walk through their last checkout customization and how it was tested. Ask how they keep custom code safe through upgrades. Adobe's implementation guidance recommends "out-of-process extensibility wherever possible to ease maintenance and upgradability". A good lead knows when to build outside the core and when that's overkill.

Ask about extensions too. Adobe warns that third-party extensions "have the potential to cause various issues that can negatively impact storefront performance". A careful agency has a written policy for vetting, updating and removing them. Ask to see it.

If you can, pay for a short discovery or a technical audit of your current store first. It shows you how the team thinks and writes before you commit to the large contract.

What red flags should you watch for?

The biggest red flags are vague staffing, a price far below the field and a proposal that skips the hard parts. Any one of them deserves a direct question. Two or more is usually a reason to walk away.

• No named team. The proposal lists roles but no people, or the people in the pitch won't work on the project.
• A fixed price for a vague scope. If they haven't asked about your integrations and data, the price can't be real.
• A bid far below the others for the same scope. The gap usually comes out of testing, performance work or seniority.
• An extension for everything. Leaning on third-party modules for core needs adds upgrade and security work later.
• No testing plan. No mention of performance targets, load tests or user acceptance testing.
• Unclear code ownership. You should own the code and have repository access throughout.
• Silent subcontracting. Ask who does the work and where. Offshore delivery is fine. Hiding it isn't.
• Certifications you can't check. Claims should map to named people with credentials you can verify.

What should an Adobe Commerce agency proposal contain?

A good proposal tells you what will be built, by whom, how it will be tested and what happens after launch. It also lists its assumptions, because that's where most later disputes start.

The redirect plan protects your search engine optimization (SEO) during a replatform, so don't let it slip to the last week. Ask every agency to answer the same written brief, so the proposals line up section by section. Our Adobe Commerce request for proposal (RFP) template gives you a ready structure for that brief.

What drives the cost of an Adobe Commerce agency?

Agency cost is driven by scope, complexity and team mix, not by a standard price list. Adobe doesn't publish Adobe Commerce prices on its product pages, and the license is a separate cost from the agency's fees. So be wary of any "typical cost" you read online, and compare proposals only against the same brief.

These factors move the number most:

• Custom code versus configuration. Every custom feature has to be built, tested and kept working through future upgrades.
• Integrations. Each ERP, PIM, order or payment connection adds design, build and test work, plus error handling.
• Storefront approach. A theme-based storefront, a headless build and an Edge Delivery Services storefront need different skills and effort.
• Stores, countries and languages. Each one adds configuration, content, tax rules and testing.
• Data migration. Volume, years of order history and data quality all add time.
• B2B rules. Company hierarchies, approval flows and negotiated pricing add depth.
• Deployment model. For Adobe Commerce on cloud infrastructure, Adobe's feature comparison says upgrades and patching are manual, with "six patch releases and one minor release per year". On Adobe Commerce as a Cloud Service, Adobe upgrades the platform. That changes the size of a support retainer.
• Team location and seniority. Rates differ by region and level. A cheaper blended rate can cost more if it leads to rework.
• Support terms. Round-the-clock cover with short response times costs more than business-hours support.

If an agency can't explain which of these drives its estimate, ask it to break the price down by phase and role. That breakdown is also what lets you compare bids fairly.

What to do next

Here's a short checklist to get from research to a signed agency:

• Write down your project type, your deployment model and the systems the store must connect to.
• Build a longlist from our directory and Adobe's Partner Directory, then cut it to three to five firms.
• Send every firm the same written brief and ask for named teams.
• Hold reference calls and a working session with each proposed technical lead.
• Pay for a short discovery or audit with your preferred firm before the main contract.
• Agree support terms, code ownership and exit terms before you sign, not after launch.

When you're ready, build a shortlist with our Adobe Commerce partner finder and line up finalists in the partner comparison tool.