Adobe Campaign RFP Template

Before You Issue a Adobe Campaign RFP

Adobe Campaign engagements come in three shapes — new implementation, remediation of an instance that has accumulated years of workflow debt, or ongoing managed operations — and the RFP should declare which you are buying because the skill sets barely overlap. Remediation in particular rewards partners who can read someone else's data model without flinching; ask for evidence of that specifically.

Whatever the shape, insist on a view of the future. Adobe's roadmap energy is with Journey Optimizer, so any material investment in Campaign today should come with a written position on the migration path: what to build cleanly now so it moves later, and what to stop building at all.

What the Adobe Campaign Sections Cover

• v7, v8 or Standard, and the upgrade sitting in front of you
• Custom schema extensions and what they cost to carry
• Workflow inventory: rebuilt, retired or left alone
• Nightly job monitoring and the on-call arrangement
• Deliverability baseline taken before sending changes
• Exit route toward Journey Optimizer, costed now

Writing the Adobe Campaign Scope of Work

Start by stating which Campaign you have and the shape of the work. Classic, Standard and v8 differ enough in architecture and administration that experience with one is not experience with another, and hosting model matters too, since on-premise and managed instances give the vendor very different access. Then say whether this is a build, a remediation of an instance carrying years of accumulated workflows, or ongoing operations. If it is remediation, the scope should fund a discovery phase whose output is an inventory, because nobody can price fixing a data model they have not seen.

Scope the data model explicitly. Campaign implementations live or die on schema extensions: which custom tables exist, how recipients relate to contracts, subscriptions and transactions, and which fields are actually maintained. If this project adds entities, say so, and say who owns the extension design. Import and export workflows deserve a line each, with the source system, file format, frequency and error behavior, because in most instances the technical workflows moving data are far more numerous and more fragile than the marketing workflows anyone talks about.

Describe the delivery side in operational terms. Typology rules, pressure rules, blocklists, quarantine handling and the approval chain before a delivery leaves are the mechanisms that stop a mistake reaching a million people, and they should be specified rather than inherited. State your sending volumes, peaks and the number of sending domains. If the engagement includes deliverability work, define it as a measurable outcome with monitoring left running, rather than as a configuration checklist completed once during setup.

Put the boundaries in writing. Out-of-scope candidates worth naming: migration of historical campaign data, rebuilding reports outside Campaign, changes to source systems, and any Journey Optimizer transition work. For managed operations, define done per cycle rather than per project: campaigns delivered on schedule, a stated ceiling on production defects reaching customers, workflow failures resolved within an agreed window, and a monthly account of instance health covering workflow error rates, database growth and quarantine volumes rather than ticket counts alone.

Requirements That Actually Separate Adobe Campaign Proposals

• Instance health diagnosis — require the vendor to describe what they examine first in an inherited instance: failing technical workflows, unused schema extensions, table growth and purge configuration, and to explain what they would leave alone deliberately.
• Purge and retention configuration — ask how log and tracking table growth is controlled, since an instance whose purges were disabled years ago degrades in ways that look like application faults and get misdiagnosed as capacity problems.
• Typology and pressure rule design — require the fatigue, exclusion and priority rules to be written out, including how a high-priority transactional message bypasses them and who can authorise an exception.
• Workflow error handling — ask what happens when a nightly import fails at three in the morning: whether it retries, whether the dependent campaign still sends with stale data, and who is alerted before the delivery goes out.
• personalization block architecture — require reusable personalization blocks and delivery templates so that a legal footer or brand change is one edit, not a sweep through hundreds of deliveries.
• Approval and proof controls — ask how proofs are generated, who approves, and what technically prevents an unapproved delivery from reaching the full target, since the worst incidents in this product are operational rather than technical.
• Migration posture — require a written statement of which parts of the work would survive a later move to Journey Optimizer and which are deliberately temporary, so today's investment is made with open eyes.

Common Mistakes in Adobe Campaign RFPs

• ✕ Not declaring whether this is implementation, remediation or managed operations — proposals become incomparable.
• ✕ Ignoring data-model and workflow debt in an existing instance, then paying for it as change orders.
• ✕ Deliverability configuration assumed rather than specified, audited and monitored.
• ✕ No AJO migration position, building fresh technical debt on a platform in maintenance mode.
• ✕ Managed-operations SLAs defined by response time alone, with no campaign-quality measures.

• ✕ Scoping only the marketing workflows while ignoring the technical workflows that feed them, which are usually more numerous, less documented and the actual source of production incidents.
• ✕ Assuming the existing instance can absorb additional volume, without checking database sizing, purge settings and the delivery throughput the current infrastructure can sustain at peak.
• ✕ Treating a Classic to v8 move as an upgrade rather than a migration, so the effort of validating every custom workflow and schema extension against the new architecture is never priced.
• ✕ Writing managed-service requirements around response times only, leaving no obligation about the quality of what gets sent, so campaigns go out on time and wrong.

Questions Worth Asking Adobe Campaign Vendors

1. Describe a Campaign remediation you delivered: what you found, what you fixed, what you left alone and why.
2. Show your deliverability configuration checklist and the monitoring you leave running.
3. What is your recommended AJO migration posture for a client investing in Campaign today?
4. How do you structure ETL workflows and CRM sync to stay debuggable by the client's own team?
5. For managed operations: what does a monthly quality report look like, beyond ticket counts?

How to Weight the Adobe Campaign Evaluation

Weight diagnostic ability over build capacity, particularly for an existing instance. Most Campaign engagements are archaeology before they are engineering, and the difference between vendors is whether they can read an unfamiliar data model and a thousand workflows without either panicking or rebuilding everything. Evidence of having walked into someone else's instance and made it stable is more relevant here than a portfolio of greenfield implementations.

Score operational discipline at least as heavily as technical design. This is a product where a single mistake sends the wrong message to a very large audience, and the controls that prevent that are procedural: proof routines, typology rules, approval gates and the habit of checking targeting counts before release. A vendor who talks about these unprompted is describing how they actually run, and that is worth more weight than an elegant architectural proposal.

Give the succession question genuine weight rather than treating it as a footnote. Adobe's development energy has moved on, so a sensible engagement builds cleanly enough to migrate later and avoids deepening dependence on constructs that will not carry across. Weight vendors who can say plainly which of your requests they would decline to build in Campaign today, and why, above those who will build anything you ask for.