Claude on Question 33, Sep 14

Short answer: it depends heavily on whether this is B2B demand gen, B2C lifecycle messaging, or ecommerce — those lead to three different shortlists. Here's how I'd frame it, plus the procurement angles that usually matter more than the feature checklist.

First, which problem are you buying for?

That last row is worth flagging: if the actual need is HR/internal announcements, marketing automation platforms are a poor and expensive fit.

The pre-work that determines the outcome

Before you run a process, get answers from the business owner on:

• 1.Contact/record count and annual send volume — this drives pricing on nearly every platform, and it's where overage clauses bite.
• 2.CRM of record — Salesforce, Dynamics, or HubSpot. Bidirectional sync quality varies a lot, and native beats iPaaS.
• 3.Where does customer data live? — If you have a Snowflake/Databricks warehouse, platforms with warehouse-native activation (Braze, Iterable, Klaviyo, or a CDP layer like Hightouch/Census) will save you a lot of integration spend.
• 4.Compliance scope — SOC 2 Type II is table stakes. Ask specifically about: GDPR/DPA if you have any EU data subjects, a HIPAA BAA if healthcare-adjacent, US data residency commitments, and subprocessor lists. Also confirm CAN-SPAM and CASL handling (suppression lists, unsubscribe SLAs).
• 5.Who will actually operate it? — Marketo and Eloqua realistically need 1–2 dedicated marketing ops FTEs or an agency retainer. That's a real TCO line item people forget.

Procurement levers worth pushing on

These are where I'd focus your leverage:

• •Implementation cost is the hidden number. For Eloqua, Marketo, and especially Salesforce Marketing Cloud, SI fees commonly run 0.5–2x first-year license. Get the SI quote in the same evaluation, not after you've signed.
• •Pricing model. Contact-based (Marketo, HubSpot) punishes database growth; send/MAU-based (Braze, Klaviyo) punishes campaign frequency. Model both against your 3-year growth forecast.
• •Cap renewal uplift in the original contract. Ask for 3–5% max. Without a cap, 15–25% renewal increases are common in this category.
• •Overage terms. Negotiate a grace band (e.g., 10% over contract tier without penalty) and pre-agreed tier pricing rather than punitive per-unit overage rates.
• •Get a mid-term downgrade right or at minimum a true-down at renewal. Vendors resist this; it's often winnable in a competitive deal.
• •Ramped multi-year beats flat multi-year if adoption is phased — but only commit multi-year if the discount is real (typically 10–20%) and you have an out for material breach or sustained SLA failure.
• •Time your negotiation to the vendor's fiscal year-end. Salesforce is Jan 31, Adobe is late Nov/early Dec, Oracle is May 31, HubSpot is Dec 31.

Directional list prices for enterprise tiers run roughly $40k–$150k+/year depending on database size and modules, but real deals vary enough that I wouldn't anchor on published numbers — these change frequently, so verify current pricing directly.

Red flags in the RFP responses

• •Vague answers on API rate limits — this kills real-time use cases later.
• •"Deliverability is your responsibility" with no dedicated IP option or warm-up support.
• •Modules priced separately that the demo presented as one product (very common with SFMC's SKU structure).
• •No sandbox environment included at your tier.

If you tell me the use case, contact volume, and current CRM, I can narrow this to two or three vendors and sketch out what a scoring matrix should weight.