You bought Adobe Experience Cloud. Now someone has to run it.
That second sentence is where most enterprise Adobe programs quietly stall. The licensing decision gets a business case, an executive sponsor and a signature. The staffing decision usually gets made by default — whoever is available, whatever the last agency quoted, whatever headcount survived the budget cycle.
There are three realistic ways to resource an Adobe practice. This is an honest comparison of them, including where our own model is the wrong answer.
The three models
Build in-house. Hire AEM developers, an architect, and eventually AEP and Journey Optimizer specialists onto payroll. Maximum control and institutional knowledge; slowest to stand up and hardest to staff.
Agency on a statement of work. Scope a project, sign an SOW, get a team assigned. Fast to start and good for defined deliverables; expensive at the margins and structurally poor at continuous operations, because every change is a change order.
Managed service on a subscription. Senior specialists embedded in your team on a recurring monthly fee, with capacity rather than deliverables as the unit. Predictable and fast to start; it requires you to have enough steady-state work to justify it.
Most organizations end up with an accidental blend of all three and wonder why costs are unpredictable.
Start with the number nobody can agree on
Here is the first practical problem with building in-house: you cannot budget it from public salary data.
As of early 2026, the average U.S. salary for an AEM developer is reported as:
- $89,187 — Salary.com (February 1, 2026)
- $119,080 — ZipRecruiter (February 17, 2026)
- $132,025 — Glassdoor
That is a 48% spread between the low and high figure for the same job title, in the same market, in the same quarter. The spread isn’t sloppiness — it reflects genuinely different methodologies and samples. But it means a plan built on any single one of those numbers is a plan built on a coin flip.
The variance exists because “AEM developer” isn’t one job. A component developer maintaining an existing Sites implementation and an architect designing a Cloud Service migration share a title and almost nothing else. Public averages blend them.
And the salary is not the cost. Fully-loaded cost — benefits, payroll tax, equipment, software, recruiting fees, management overhead — is commonly planned at roughly 1.25–1.4× base as a rule of thumb. Then add the part nobody budgets: the months between “approved” and “productive.”
The three costs people forget
Time to productive. A senior Adobe hire is not a fast hire. Between search, notice periods and ramp on your specific implementation, the gap between approving headcount and getting real output is typically measured in months, not weeks. Every one of those months, your licensed platform is underused.
Coverage, not headcount. One AEM developer is not one AEM capability. They take vacation, they get sick, they leave. A single-threaded practice has a bus factor of one, and the day that person resigns is the day you discover how much of your implementation lived only in their head.
The specialization tax. Adobe Experience Cloud is not one skill. AEM Sites, AEM Assets, Real-Time CDP, Journey Optimizer, Workfront, GenStudio and Firefly integration are genuinely different disciplines. Hiring one generalist to cover all of them produces a person who is mediocre at each. Hiring a specialist for each produces a headcount request nobody will approve.
Don’t buy the badge, buy the bench
If you evaluate agencies or managed services, you’ll see Adobe partner badges. They’re worth something — a partner relationship means a firm has committed to the ecosystem and has a channel to Adobe when something goes wrong.
What a badge does not tell you is whether the specific people assigned to your account are any good. Partner status is held by the firm; the work is done by individuals. A large partner can staff your project with juniors, and a small one can put a genuine expert on it.
So ask about the bench, not the badge: Who specifically will do this work? How senior are they? Where are they located? Will they still be on my account in six months? A firm that answers those questions crisply is telling you more than any tier ever could.
When to build in-house
Build when Adobe is core to how your business operates, not a channel you maintain. Specifically:
- You have enough continuous Adobe work to keep specialists busy indefinitely
- Your implementation is deeply proprietary and institutional knowledge compounds
- You can genuinely compete for senior Adobe talent on compensation and interest
- You can afford the 6–12 month runway before the team is fully productive
If those are all true, in-house wins on long-run economics. Nothing beats a team that knows your platform cold.
When an agency SOW is right
Choose a scoped SOW when the work is genuinely a project with an end: a migration, a replatform, a site launch. Defined scope is what SOWs are good at.
The failure mode is using an SOW for continuous operations. Ongoing Adobe work is a stream of small changes, and a contract structure that requires a change order for each one converts your delivery team into an estimating team.
When a managed service makes sense
A subscription model fits when you have steady-state Adobe work but not enough — or not enough predictability — to justify permanent headcount for every discipline. It trades some control for speed, coverage and a fixed monthly number.
It is the wrong answer if your Adobe work is genuinely a one-off project, if you need someone physically on site, or if your volume is so high that permanent staff is simply cheaper. We’ll say that plainly, because a managed service sold into the wrong situation fails for both sides.
The questions to ask before you decide
Whichever direction you lean, these are the questions that actually separate the models:
- How many hours a month of Adobe work do we genuinely have — and how predictable is it?
- Which Adobe disciplines do we need, and are they the same ones every month?
- What happens to our roadmap if the one person who knows our implementation leaves?
- What is our real cost of a month of delay on the platform we already license?
- Are we buying deliverables, or buying capacity?
- Who specifically will do the work — named people, seniority, and location?
Question 6 is the one that gets skipped, and it’s the one that predicts whether the engagement works.
Where we land
We built Navigator as our answer to the third model: senior, U.S.-based Adobe specialists embedded in your team on a flat monthly subscription, without SOWs or headcount approvals. Focus GTS is an Adobe Silver Solution Partner, and pricing is published on the page — $5,600 to $10,400 a month depending on tier — because “call us for a quote” is how comparison shopping gets deliberately difficult.
We’re also clear that it isn’t the answer for everyone, which is why the sections above exist. If you’re weighing this decision and want a straight read on which model fits your situation, start here.