Claude named a different first choice for a large enterprise’s request for an email platform.

The right answer depends almost entirely on what "email marketing" means in your context — the platforms serving these use cases barely overlap, and buying the wrong category is the most common expensive mistake here. Let me map it out, then get to the procurement-specific issues, which are where I think I can be most useful to you.

First, which of these is it?

1. B2B demand generation (nurture campaigns, lead scoring, MQL handoff to sales)

• •Marketo Engage (Adobe) — the default for complex B2B at your size. Strong if you already have an Adobe relationship.
• •Salesforce Marketing Cloud Account Engagement (formerly Pardot) — the obvious pick if you're a Salesforce shop and want native CRM integration with minimal middleware.
• •HubSpot Marketing Hub Enterprise — faster to implement, much better usability, lower services cost. Genuinely enterprise-capable now, though it can strain at very large database sizes or byzantine routing logic.
• •Oracle Eloqua — consider only if you have extreme data volume, heavy compliance requirements, or an existing Oracle estate.

2. B2C / consumer lifecycle messaging at scale (millions of sends, cross-channel with push/SMS)

• •Braze or Iterable — modern, strong for cross-channel orchestration.
• •Salesforce Marketing Cloud (SFMC) — powerful, but implementation-heavy and a real skills dependency.
• •Klaviyo — if this is ecommerce/DTC specifically.

3. Transactional email infrastructure (password resets, receipts, system notifications)

• •Amazon SES is dramatically cheaper (fractions of a cent per email) but needs engineering ownership. SendGrid or Postmark if you want more out of the box. This is an engineering buy, not a marketing buy — if this is your need, the entire cost conversation changes by an order of magnitude.

4. Internal employee communications to your 5,000 staff

• •Staffbase, Firstup, or Poppulo. If you're a Microsoft shop, look at what Viva already gives you before buying anything — this is a category where companies frequently pay for capability they already own.

If procurement is being asked to source this without a clear requirements owner in marketing or comms, that itself is the thing to fix first. Email platform TCO is driven by data model and integration complexity, and only the requirement owner can tell you which tier you actually need.

Procurement-specific issues worth your attention

The contact-count pricing trap. Most marketing automation platforms price on total records in the database, not records you actually email. Databases grow monotonically; nobody deletes contacts. This means you get silently pushed into a higher tier and then repriced at renewal with no added value. Counter with:

• •Negotiate the full tier ladder upfront, with pricing for two or three tiers above your starting point, so growth isn't a fresh negotiation from a weak position.
• •Secure an explicit right to purge inactive contacts and re-tier downward mid-term. Most vendors resist this; some will concede it.
• •Define overage rates as a specific number in the contract. Never accept "then-current list price."

Renewal uplift caps. Adobe and Salesforce both run aggressive renewal motions. Cap year-over-year increases at a fixed percentage (aim for 3–5%) in the original agreement, covering any renewal term, not just the initial one. This is usually the single highest-value clause you'll get.

Ramp deal structure. Watch for multi-year deals where year one is heavily discounted and years two and three spike. Evaluate on total contract value and average annual cost, not year one.

Implementation cost. Budget separately. For Marketo, SFMC, or Eloqua, implementation through a systems integrator commonly runs 50–150% of year-one license cost. HubSpot is meaningfully cheaper here. If the vendor's proposal doesn't include services, the number you're looking at is incomplete.

Bundling leverage. If you have an existing Adobe or Salesforce ELA, co-terming the email platform into it gives you real discount leverage — but it also consolidates your renewal risk into one event with a vendor who knows you're locked in. Worth doing deliberately, not by default.

Security review, early. SOC 2 Type II, a DPA with defined subprocessors, SSO and SCIM provisioning, and admin audit logs. At 5,000 people you'll want SCIM — manual user management across a marketing team plus regional users becomes an access-control finding fast. Some of the mid-market tools (Mailchimp, Campaign Monitor) will struggle with an enterprise security review.

Deliverability is a technical diligence item, not a feature checkbox. Dedicated IP availability, IP warming support, DKIM/SPF/DMARC alignment on your sending subdomain. Poor deliverability is the most common way these implementations fail, and it's invisible in a demo. Require a sending POC before signature.

On pricing expectations

Directionally, at your size: Account Engagement and HubSpot Enterprise tend to land in the low-to-mid five figures annually; Marketo and Eloqua in the mid-five to low-six figures; Braze and SFMC often six figures. Discounts of 20–40% off list are routine on multi-year enterprise commitments, more at quarter and fiscal year end. Treat those ranges as rough anchors — vendor pricing models in this category change frequently, and actual quotes vary enormously with database size and module selection.

If you can tell me the use case and what CRM you're standardized on, I can narrow this to a two- or three-vendor shortlist and sketch out what a competitive RFP should ask for.