A CDP RFP (request for proposal) template is a structured document that organizations use to solicit, compare, and score customer data platform vendor proposals against standardized requirements. A well-structured RFP eliminates the guesswork from vendor evaluation and ensures every platform is assessed on the same criteria.
The RFP is the most important document in a CDP buying process, yet most organizations write them from scratch every time — leading to gaps, inconsistencies, and wasted effort. Worse, many RFPs focus on feature lists rather than the architectural and operational requirements that determine whether a CDP will actually deliver business value.
This guide provides a complete RFP structure with over 40 ready-to-use questions organized by category. Whether you are evaluating hybrid CDPs, composable CDP architectures, or enterprise marketing suites, these questions will surface the differences that matter. For a broader evaluation framework, see How to Choose the Right CDP.
Why a Structured RFP Matters
Without a standardized RFP, CDP evaluations devolve into comparing marketing materials. Each vendor highlights different strengths, uses different terminology, and structures proposals differently — making apples-to-apples comparison nearly impossible.
A structured RFP solves three problems:
- Consistency. Every vendor answers the same questions in the same format, enabling direct comparison across capabilities.
- Completeness. A comprehensive template ensures you do not forget to ask about critical areas like data governance, AI architecture, or total cost of ownership until it is too late.
- Accountability. Written RFP responses become contractual reference points. Capabilities claimed during sales demos but omitted from RFP responses are a red flag.
RFP Structure: Seven Essential Sections
Section 1: Company and Use Case Overview
This section provides vendors with the context they need to propose a relevant solution. Be specific — vague requirements produce vague proposals.
Include:
- Your organization’s industry, size, and geographic footprint
- Number of customers and data volume (profiles, events per day)
- Current technology stack (CRM, marketing automation, data warehouse, ESP)
- Top three to five use cases the CDP must support (ranked by priority)
- Timeline expectations for implementation and first value delivery
- Budget range (optional but recommended — it filters vendors who cannot compete at your price point)
Section 2: Data Ingestion and Integration Requirements
This section evaluates the platform’s ability to connect with your existing systems and ingest your data at the required volume and speed.
RFP questions:
- List all pre-built connectors available for data ingestion. Indicate which are maintained by your team versus third-party partners.
- Describe your real-time streaming ingestion capabilities. What is the maximum sustained event throughput you have demonstrated in production?
- How does your platform handle schema evolution in source systems without requiring manual intervention?
- Describe your approach to ingesting unstructured data (call transcripts, support tickets, images).
- What data integration options exist for connecting to cloud data warehouses (Snowflake, BigQuery, Databricks, Redshift)?
- Describe your custom connector framework. Can our engineering team build and maintain proprietary connectors?
Section 3: Identity Resolution and Profile Unification
Identity resolution quality determines the accuracy of every downstream use case. This section should surface both the technical approach and the practical outcomes.
RFP questions:
- Describe your identity resolution methodology (deterministic, probabilistic, ML-based, or hybrid). How do you handle cross-device and cross-channel matching?
- What is your average match rate for enterprise customers with 10 million or more profiles? Provide three customer references we can validate this with.
- How does your platform handle identity conflicts, such as shared devices or merged accounts?
- Can identity resolution rules be customized by region or business unit to comply with local regulations?
- Describe your identity graph persistence. How does the identity graph update when new data arrives, and how are merge/unmerge operations handled?
- Will you perform a proof-of-concept identity resolution test using our data? What data do you need from us?
Section 4: AI and Analytics Capabilities
AI capabilities have become central to CDP value delivery. This section distinguishes platforms with genuinely integrated AI from those that offer AI as an add-on module.
RFP questions:
- Describe your native AI decisioning capabilities. Are these included in the base platform, or do they require additional licensing?
- What predictive analytics models are available out of the box (churn prediction, lifetime value, purchase propensity, next-best-action)?
- Can AI models access the full unified customer profile in real time, or do they operate on a delayed copy of the data?
- Describe your platform’s ability to support AI agents that autonomously read profiles, take actions, and learn from outcomes within closed feedback loops.
- Does your platform support custom model deployment (bring-your-own-model)? What frameworks are supported?
- How do you handle AI model explainability, bias detection, and auditability?
For a deeper exploration of AI architecture questions, see How to Evaluate a CDP in the AI Era.
Section 5: Activation and Channel Support
Data activation determines whether unified profiles translate into business outcomes. Evaluate both the breadth of activation channels and the latency of data delivery.
RFP questions:
- List all native activation channels (email, SMS, push, in-app, web personalization, paid media). For each, indicate whether it is native or requires a third-party integration.
- What is the typical latency from profile update to activation in each channel?
- Does activation require copying PII to external systems? If so, describe the data flows and security controls.
- Describe your audience syndication capabilities for paid media platforms (Meta, Google, TikTok, The Trade Desk).
- Does the platform support reverse ETL for pushing enriched profiles and segments back to a data warehouse?
- Can the platform activate individual profile attributes to destination systems, or only segment membership?
Section 6: Privacy, Security, and Compliance
This section is critical for legal, security, and compliance teams. Ensure their requirements are represented in the RFP.
RFP questions:
- What security certifications do you hold (SOC 2 Type II, ISO 27001, HIPAA, FedRAMP)?
- Describe your consent management enforcement. How does the platform ensure profiles with revoked consent are excluded from activation in real time?
- How does your platform handle GDPR right-to-erasure requests? What is the guaranteed deletion timeline, and does it include downstream copies?
- Describe your data residency options. Can customer data be stored exclusively in specific regions (EU, US, APAC)?
- Provide your data processing agreement (DPA) and describe your sub-processor management process.
- Describe your approach to data privacy during cross-border data transfers. Do you rely on Standard Contractual Clauses, adequacy decisions, or other mechanisms?
- Provide audit log capabilities: who accessed what data, when, and what actions were taken.
Section 7: Pricing, Implementation, and Support
This section eliminates pricing surprises and sets realistic implementation expectations.
RFP questions:
- Provide a detailed pricing breakdown for our stated data volume and use cases. Include all line items (platform license, connectors, AI modules, professional services, training).
- What is your pricing model (per profile, per event, flat platform fee, consumption-based)? How does pricing scale as data volume doubles?
- What is the typical implementation timeline for an organization of our size and complexity? Provide three comparable customer references.
- Is a systems integrator required for implementation? If so, which partners do you certify?
- Describe your customer success model. Will we have a dedicated CSM and technical account manager?
- What are your SLAs for platform uptime, data freshness, and support response time?
- Describe your product roadmap process. How do customers influence prioritization?
- What training and certification programs are available for our team?
- What is your contract term structure? Are there exit provisions if the platform does not meet agreed-upon performance benchmarks?
Evaluation Scoring Methodology
Once vendor proposals are received, score them using a weighted matrix. Here is a recommended approach:
| Category | Suggested Weight | Rationale |
|---|---|---|
| Data ingestion and integration | 15% | Foundation — nothing works without clean data flowing in |
| Identity resolution | 20% | Determines profile accuracy for all downstream use cases |
| AI and analytics | 15% | Increasingly central to CDP value, but requires strong data foundation |
| Activation and channels | 15% | Measures whether unified data reaches customers |
| Privacy and compliance | 15% | Non-negotiable for regulated industries |
| Pricing and TCO | 10% | Important but should not override capability fit |
| Implementation and support | 10% | Affects time to value and ongoing operational burden |
Scoring scale:
- 5 — Exceeds requirements with demonstrated production evidence
- 4 — Fully meets requirements
- 3 — Meets requirements with minor gaps or workarounds
- 2 — Partially meets requirements; significant customization needed
- 1 — Does not meet requirements
Adjust category weights based on your organization’s priorities. For healthcare organizations, privacy and compliance may warrant 25 percent weight. For retail and e-commerce, activation speed and channel breadth may take priority.
Common RFP Mistakes to Avoid
Asking about features instead of outcomes. “Do you support email?” is less useful than “Describe how your platform orchestrates a triggered email campaign from profile event to delivery, including the end-to-end latency.”
Omitting the proof-of-concept requirement. State in the RFP that finalists will be required to complete a two-to-four-week POC using your data. This filters vendors who cannot deliver on their claims.
Ignoring total cost of ownership. Platform license cost is often 40-60 percent of the three-year TCO. Implementation, training, internal staffing, and integration maintenance account for the rest. Require vendors to itemize all costs.
Skipping the reference check section. Require three customer references in your industry, with comparable data volumes and use cases. References from different industries or dramatically different scales are not meaningful comparisons.
Writing the RFP alone. The best CDPs serve marketing, IT, data engineering, and legal. Include stakeholders from each function in the RFP drafting process to ensure their requirements are captured. See our CDP implementation guide for recommended team structures.
For a tactical capability checklist to use alongside this RFP, see CDP Evaluation Criteria. For the broader process of running an RFP, see An 8-Step Approach to a Successful CDP RFP Process.
FAQ
How long should a CDP RFP response window be?
Give vendors three to four weeks to respond to a comprehensive CDP RFP. Less than two weeks signals that the decision is already made, which discourages serious vendors from investing effort in a thorough response. More than five weeks risks losing momentum and stakeholder engagement. State the deadline clearly and hold to it — vendors who cannot deliver a quality response on time are signaling something about their operational discipline.
Should the RFP include budget information?
Yes. Including a budget range (even a broad one) filters vendors who cannot compete at your price point, saving time for both sides. It also helps vendors propose solutions that fit your investment level rather than defaulting to their most expensive offering. If sharing exact budget is not possible, indicate whether you are in the under 250,000 dollars, 250,000 to 500,000 dollars, or over 500,000 dollar annual range.
How many vendors should receive the RFP?
Send the RFP to five to eight vendors. Fewer than four limits competitive comparison. More than ten creates evaluation burden that delays the decision by weeks or months. Start with a long list informed by analyst reports (Forrester Wave, Gartner Magic Quadrant), narrow to five to eight based on must-have criteria, then shortlist three for POC after RFP scoring. This approach typically produces a final decision within 10 to 14 weeks from RFP distribution.
Download the complete CDP RFP Template → treasure.ai/rfp