Questions to Ask CDP Vendors Before You Sign

Four tests do most of the work: run the vendor's identity resolution against a sample of your own data; have your own marketer build an audience in the product unaided; get the split of generally available, roadmap and third-party capability in writing; and model the cost at two and five times your current volume. The full evaluation is eleven questions across five stages, from before you shortlist to the week you sign — those four plus the ones buyers say they only thought to ask once the leverage was gone. For what happens when these go unasked, the companion read is what CDP buyers wish they'd known.

Where the real gate is

A formal RFP is not the constant — whether one happens tracks company size and deal size more than it tracks the category, and several buyers say plainly that they don't mandate one. What is closer to universal is hands-on validation before signature, with separate demo rounds for business and technical stakeholders. The form varies more than the word suggests — a full production-style proof-of-concept is not always practical for a platform this heavy to stand up, and some buyers run one only after the shortlist exists or substitute a controlled demo on a small segment. Treat the questions below as a script you run in whichever format you get, not a document you send.

Stage 01 Before you shortlist

Decides whether you should be buying this class of tool at all. No later stage can recover a wrong answer here.

Data foundation sequencing

Ask What has to be true about our data before this platform works? Walk me through the sequencing, not the capability.

Require A phased answer that names your prerequisites — governance owner, source of truth, resolution of known duplicates — before it names a feature.

Red flag The answer pivots to platform capability. Buyers at the RFI stage report having to send a second round of questions because vendors jumped to a CDP discussion instead of engaging with sequencing.

Verify Take the prerequisites they name to your own data owner and have them confirm which are already satisfied, which are not, and what each gap costs in work before implementation can start.

Data residency and portability

Ask Does our data have to live in your environment, or can it stay in our warehouse? What replication is mandatory?

Require A written answer covering mandatory replication, export format, and exit notice period — before pricing, not after.

Red flag Full replication into the vendor's environment presented as an architectural given rather than a choice.

Verify Ask what a departing customer receives, in what format, over what period — then require the same terms in the agreement.

Fit, stated honestly

Ask Name the use cases you would not recommend we buy you for.

Require A specific answer, plus which of their customers resemble you in data shape and industry — and what those customers had to build themselves.

Red flag No limits offered, or feature breadth pitched before your mission is understood.

Verify Write down what the platform is for before the first demo, and score every vendor against that rather than against each other.

Stage 02 In hands-on validation

The real gate, whatever form it takes — a full proof-of-concept, a shortlist trial, or a controlled demo on a small segment. Two capabilities, both testable in an afternoon, and both routinely taken on faith instead.

Identity resolution

Ask Run your identity resolution against this sample of our data.

Require A match rate on your file, plus an explanation of every discrepancy against your own internal identity numbers. Your number is the bar, not theirs.

Red flag Only benchmark figures or customer averages offered. Also worth surfacing: whether the identity graph is theirs or licensed from a third party you could buy directly.

Verify Compare their output against your internal resolution on the same records. Buyers with unusual data shapes — B2B contacts who move between companies, post-merger duplicates — report off-the-shelf resolution failing on exactly this test.

Marketer self-service

Ask Build the audience we just described, here, in the product — and let our marketer drive.

Require A working segment built and activated by your least technical marketer, unassisted. Time it, and note every point they need help.

Red flag The sales engineer keeps the keyboard, or the answer routes to "our professional services team can set that up."

Verify Have the same person repeat it a week later without notes. If they can't, marketer self-service isn't proven — whatever the demo showed.

This is the average buyer's picture. Which parts apply to your stack?A 15-minute interview returns the read specific to you — and what peers with your setup chose.

Get my personalized read →

Stage 03 Technical diligence

Where the demo gets separated from the product. Both questions here are about getting something in writing while you still have leverage.

Available today vs. roadmap vs. partner

Ask Which capabilities in this demo are generally available today, which are roadmap, and which are delivered by a third party?

Require The split in writing, with dates on anything roadmap and the partner named on anything third-party.

Red flag "Out of the box" with no configuration estimate attached — the most consistently falsified claim in the corpus.

Verify Ask for the last three roadmap commitments made to customers like you — what shipped, what slipped, and by how long.

Implementation reality

Ask Of your last five implementations at our size, how long did each take from signature to first production use case — and what caused the longest one?

Require Five actual durations, not an average, plus what is in the statement of work, what is explicitly out, and who pays when scope changes.

Red flag A range quoted in quarters with no worst case, or professional services scoped "later."

Verify Ask what the longest one had in common with you. For what these timelines look like in practice, see real CDP implementation timelines.

Stage 04 Commercial diligence

Buyers who like the product still leave over price. The quote fits today's volume; the contract has to fit year two.

The cost curve

Ask Model our cost at two and five times our current event volume, profile count, and destination count.

Require Three quotes, not one — and the shape of the curve between them.

Red flag Only today's number offered, or growth pricing described as "we'll work with you."

Verify Model it against your own growth plan, not theirs. The cost picture in full is on what buyers actually pay for a CDP.

What meters, and what doesn't

Ask What is billed separately from the licence — API connections, additional destinations, backend queries, sandbox environments, professional services?

Require Every metered line named in the contract, not in an email.

Red flag Per-connection or per-query charges that surface only in the redlines.

Verify Count the destinations and queries you actually plan to run, and price those specifically.

Stage 05 Before signature

Two questions that cost nothing to ask now and are expensive to raise later.

Who you actually get

Ask Who from your team is on this account after signature — and are they the people in this room?

Require Named roles and the handover point from sales to delivery.

Red flag The people who learned your requirements during the POC disappear at signature, with no named implementation owner and no structured handoff.

Verify Ask to meet them before you sign, not after.

The exit

Ask If we leave, what do we get back, in what format, over what period?

Require Export scope and format for profiles, events and identity mappings — in the agreement.

Red flag Export described as a professional-services engagement.

Verify Read it against the renewal terms. The two together are your real switching cost.

Telling a real answer from a rehearsed one

Buyers rarely describe a vendor as dishonest. What they describe is a vendor answering a different question than the one asked. These are the signals they name.

Reads as credible

Engages with the phase you are in, rather than pitching the platform
Category depth — talks about your industry's data shape unprompted
An AI roadmap described as what ships when, not what is possible
Will name what it is not good at, and which customers resemble you
Responds to a non-standard requirement instead of routing around it

Worth a second round

Pivots to capability when you asked about sequencing
Feature breadth pitched before your mission is understood
Upsells a new module rather than closing the gap you raised
"Out of the box" with no configuration estimate
The team in the room is not the team on the account

Want this read against your own stack?

Get my read →

Who is in the room changes what gets asked

Two shapes recur, and they fail differently. A named committee scoring against a written framework tests broadly and still misses usability — the people scoring rarely operate the tool daily. A lean team of two tests deeply on what it cares about and is exposed on whatever nobody owns, usually portability and the cost curve. Watch also for procurement run on a cost threshold rather than by category: it sets diligence by price tag rather than by consequence.

Worth settling internally before you ask a vendor anything: which of the eleven questions above has an owner, and which currently has none.

The honest caveat

Buyers almost never attribute their outcome to their own evaluation process — the unhappy ones describe the product, not the diligence. So treat this as a pattern rather than a promise: the buyers reporting the fewest surprises are disproportionately the ones who tested rather than accepted, and who wrote down what the platform was for before seeing what it could do. That is a correlation drawn from how they describe their processes, not a claim that good evaluation guarantees a good outcome.

Common questions

What should I ask a CDP vendor before signing?

Four tests do most of the work: run their identity resolution against a sample of your own data and require an explanation of any gap against your internal numbers; have your own marketer build and activate an audience unaided; get the split of generally available, roadmap and third-party capability in writing; and model the cost at two and five times your current volume with every metered line named. The buyers reporting the fewest surprises are the ones who tested rather than took answers on faith.

Do I need a formal RFP to buy a CDP?

Not necessarily — many buyers in our interviews don't run one. Whether an RFP happens tracks company size and deal size more than the category. What is closer to universal is hands-on validation before signature, plus separate demo rounds for business and technical stakeholders — though the form varies, and buyers report that a full production-style proof-of-concept is not always practical for a CDP. In practice the validation is the real gate, not the paperwork.

What should a CDP proof-of-concept actually test?

Identity resolution and usability, whether you get a full proof-of-concept or a controlled demo on a small segment. On identity, the vendor should run against your file, and your own internal match rate is the bar — not their benchmark. On usability, the test that separates a marketing platform from an engineering one is whether a non-technical marketer can build and activate an audience unaided, and repeat it a week later without notes.

What questions do CDP buyers wish they had asked?

Two recur. What has to be true about your own data before the platform works — buyers report vendors steering to capability when the honest answer was sequencing. And data portability: only a minority raise lock-in during evaluation, and the rest meet it afterwards in mandatory replication or multi-year agreements they would leave if they could.

Get this research made for your stack

Every one of these questions matters more or less depending on your architecture, your team, and what you're replacing. Do a 15-minute interview about your stack and get the shortlist that applies to you — plus what buyers running your setup asked, and what they wish they'd asked.

Get my personalized read — 15-min interview

No password · your interview is anonymized before it ever informs a page like this one.

Methodology. Alium conducts verified interviews with software buyers — the marketing, data, and IT leaders who select and operate these platforms. This page draws on the customer-data-platform interviews in that corpus, conducted through August 2026, focusing on how buyers ran their evaluations and what they learned from them. Individual ratings quoted here are one buyer's score of their own platform, not a vendor average. Buyer identities are verified at interview time and anonymized before publication; vendor names are reported as given. No vendor paid to appear or was able to edit this page.

Questions to ask CDP vendors before you sign