Adobe Journey Optimizer sits at the sharp end of the Experience Platform stack: it is where unified profiles finally do something a customer notices. That position makes AJO implementations deceptively dependent — on profile quality, on identity design, on channel infrastructure — and the partners who deliver them well are the ones who manage those dependencies, not just the ones who can configure a journey canvas.
What you are actually buying
Strip the branding and an AJO engagement has five layers: profile and event readiness (is the data there to trigger and personalize journeys?), channel foundations (email authentication, push certificates, SMS provider integration, deliverability posture), journey architecture (the portfolio of lifecycle moments worth automating), content operations (who builds the messages, with what approval flow), and measurement (how journey impact is proven against holdouts). Weak proposals collapse all five into "implementation." Strong ones price and staff them separately, because they are different skills.
Screening criteria that separate the field
Platform-native depth. AJO runs on Experience Platform primitives — XDM events, profile attributes, audiences, decisioning. Ask candidates how a journey trigger differs from a segment qualification, and when they would use each. Fluency here predicts whether your journeys will fire correctly at scale.
Deliverability scar tissue. Moving email volume onto AJO means IP warming, authentication (SPF, DKIM, DMARC), and reputation management. Ask for the warming plan from a previous migration and what inbox-placement rates they achieved. Partners who subcontract this thinking will discover deliverability problems on your sending domains.
A journey portfolio, not a journey list. Good partners arrive with a prioritized map: welcome and onboarding sequences, abandonment recoveries, lifecycle milestones, service-to-marketing handoffs, win-back programs — each with expected impact and dependency notes. Ask which three they would ship first for your business and why; the reasoning matters more than the picks.
Holdout discipline. Journey value is provable only against control groups. Insist the measurement design — global holdouts, per-journey controls, incremental revenue readouts — appears in the proposal. 'We'll report opens and clicks' is not measurement; it is decoration.
Migration realism. Coming from Adobe Campaign or another ESP? The honest answer on timeline is phased coexistence — transactional and triggered programs move first, batch campaigns later — and partners who promise a clean cutover in a quarter are optimizing for signature, not success.
Cost bands
Foundation engagements — channel setup, profile readiness validation, first three to five journeys live — typically run $60,000–150,000 over three to five months, assuming Experience Platform and profile work is broadly in place. Programs that must also remediate identity or schema issues grow accordingly (and should be scoped honestly as CDP work plus AJO work). Managed journey operations — new journeys, content production, optimization — run $6,000–20,000 monthly. As always, delivery geography drives rate variance more than quality does.
Failure modes to screen against
Journeys launched on unready profiles, firing on stale or missing data. Content bottlenecks where every message queues behind one designer. Measurement debt — a year of journeys with no holdout evidence when the license renewal arrives. And the quiet one: journey sprawl, where dozens of overlapping automations message the same customers without global frequency governance. Ask every candidate how they prevent each; the specificity of the answers is your ranking.
Run the standard process — three to five firms with documented AJO delivery, one written scope, delivery-lead interviews, a reference call focused on what went wrong — and weight the partner whose plan reads like a program you will own, not a platform you will rent attention to.
Frequently Asked Questions
How much does an Adobe Journey Optimizer implementation cost?
Foundation engagements — channel setup, readiness validation and the first three to five live journeys — generally run $60,000–150,000 over three to five months. If profile or identity remediation is needed first, that is additional CDP-scoped work. Managed journey operations add $6,000–20,000 monthly.
What are the prerequisites for AJO?
A working Experience Platform foundation: profile-enabled data with sound identity design, event streams for triggers, and audiences worth journeying. Plus channel infrastructure — authenticated sending domains, push credentials, SMS provider. Partners should validate readiness in week one, not discover gaps in month three.
How is AJO different from Adobe Campaign?
Campaign is batch-and-blast campaign management on its own data model; AJO is real-time, profile-triggered journey orchestration on Experience Platform. Migrations typically run phased: triggered and transactional programs move to AJO first, complex batch programs later — plan for coexistence rather than a hard cutover.
How do we prove Journey Optimizer ROI?
Holdout groups. Keep a global control excluded from journeys and per-journey controls where volume allows, then read incremental conversion and revenue against them. Insist your partner builds this measurement design into the first journeys — retrofitting controls after launch is far harder.