---
title: "Who Sits on the CX Buying Committee (and What Each Member Kills a Deal For)"
date: "2026-08-21"
description: "The CX buying committee is the group of seven roles — CX lead, insights owner, IT, security, procurement, finance, and legal/privacy — that must collectively approve a customer experience platform purchase, and each one can stop the deal for a completely different reason."
keywords: ["cx buying committee", "customer experience buying committee", "cx software buyers"]
author: "Perspective AI Team"
category: "AI Conversations at Scale"
slug: "cx-buying-committee-who-sits-on-it"
excerpt: "The CX buying committee is the group of seven roles — CX lead, insights owner, IT, security, procurement, finance, and legal/privacy — that must collectively…"
image: "https://getperspective.agency/assets/e2998eb2-82d7-48c1-a618-55e1599faf55"
tags: ["customer research", "cx buying committee", "guides", "product management", "how-to"]
lastModified: "2026-08-21"
definition: "The CX buying committee is the group of seven roles — CX lead, insights owner, IT, security, procurement, finance, and legal/privacy — that must collectively approve a customer experience platform purchase, and each one can stop the deal for a completely different reason. Harvard Business Review documented the average B2B purchase group growing from 5.4 to 6.8 people between 2015 and 2017, and Gartner now puts a complex B2B buying group at six to ten decision makers, each arriving with four or five pieces of information they gathered independently. Gartner also reports that 77% of B2B buyers describe their most recent purchase as very complex or difficult, with consensus-building the single most-cited friction point. In CX software specifically, the failure mode is predictable: the CX lead gets excited about insight quality, then security asks for a SOC 2 Type II report, legal asks where verbatim customer transcripts are stored and for how long, finance discovers implementation services were never in the model, and the deal slips two quarters. The fix is not better selling — it is sequencing. Gather each seat's decision evidence before that seat is asked to approve, and run security, privacy, and finance review in parallel with evaluation rather than after it. This guide maps all seven seats, what each optimizes for, the specific objection each raises, and the artifact that pre-empts it."
faqs: [{"question": "Who owns the CX platform purchase decision?", "answer": "The CX or customer experience lead usually owns the CX platform purchase decision, but rarely holds unilateral authority. In most mid-market and enterprise organizations the CX lead is the champion and budget nominee, while security, legal, and finance hold independent veto rights. Where CX reports — to marketing, operations, support, or the COO — determines how much political capital the champion brings to the committee."}, {"question": "How many people are on a CX buying committee?", "answer": "A CX buying committee typically involves six to ten people across seven functional seats. Gartner's research puts complex B2B buying groups at six to ten decision makers, and CX platform deals sit at the higher end because they combine customer personal data, stack integration, and multi-year contracts. Smaller companies compress the seven seats into three or four people rather than eliminating any of the seven concerns."}, {"question": "What kills most CX platform deals?", "answer": "Most CX platform deals die on retention and residency questions raised by legal late in the process, or on costs finance discovers after the quote. Both are pre-emptable. Requesting the retention configuration, data processing agreement, and full three-year cost model in the first vendor conversation removes the two most common late-stage vetoes before they can reset the timeline."}, {"question": "When should security review start in a CX purchase?", "answer": "Security review should start in week one, in parallel with pricing conversations, not after a vendor is selected. Security evaluates artifacts — audit reports, subprocessor lists, penetration test summaries, questionnaires — none of which require a final decision to collect. Running review in parallel across all shortlisted vendors typically saves three to six weeks compared to serial review after selection."}, {"question": "Do I need procurement involved for a small CX purchase?", "answer": "Involve procurement even for small CX purchases, because thresholds are lower than most champions assume and retroactive involvement is expensive. Purchases touching customer personal data frequently trigger review regardless of dollar value, and Zip's 2025 procurement research found roughly 79% of software purchases now require CFO approval irrespective of who owns the budget line."}, {"question": "How do I get IT to support a new CX tool?", "answer": "Get IT support by removing work from IT rather than adding it. Confirm SSO and provisioning support, name the vendor-side owner of integration work, show a clean export path, and bring the build-versus-buy conversation up yourself before IT does. IT blocks tools that create unowned maintenance load, not tools that are unfamiliar."}]
---

## TL;DR

The CX buying committee is the group of seven roles — CX lead, insights owner, IT, security, procurement, finance, and legal/privacy — that must collectively approve a customer experience platform purchase, and each one can stop the deal for a completely different reason. Harvard Business Review documented the average B2B purchase group growing from 5.4 to 6.8 people between 2015 and 2017, and Gartner now puts a complex B2B buying group at six to ten decision makers, each arriving with four or five pieces of information they gathered independently. Gartner also reports that 77% of B2B buyers describe their most recent purchase as very complex or difficult, with consensus-building the single most-cited friction point. In CX software specifically, the failure mode is predictable: the CX lead gets excited about insight quality, then security asks for a SOC 2 Type II report, legal asks where verbatim customer transcripts are stored and for how long, finance discovers implementation services were never in the model, and the deal slips two quarters. The fix is not better selling — it is sequencing. Gather each seat's decision evidence before that seat is asked to approve, and run security, privacy, and finance review in parallel with evaluation rather than after it. This guide maps all seven seats, what each optimizes for, the specific objection each raises, and the artifact that pre-empts it.

## What Is the CX Buying Committee?

The CX buying committee is the cross-functional group inside a company that evaluates, approves, and signs off on a customer experience platform purchase — typically spanning the CX or insights function, IT, security, procurement, finance, and legal. Unlike a single-owner tool purchase, a CX platform touches customer personal data, integrates with the CRM and support stack, and carries a multi-year contract, which pulls in risk and spend reviewers who never attend the product demo.

Committee composition varies with deal size, but the seven functional seats are remarkably stable across mid-market and enterprise deals. What changes is whether one person holds two seats. In a 300-person company, the VP of Customer Experience may also carry the insights seat and the head of IT may also run the security review; in a 5,000-person company, all seven are separate people with separate approval queues. Either way, the same seven objections get raised — just by fewer or more mouths.

If you are still working out which function should own the program before you buy anything, start with the operating-model question rather than the vendor question. Our breakdown of [who owns customer experience across operating models and reporting lines](/blog/who-owns-customer-experience-operating-models-reporting-lines-and-first-hires) covers the ownership decision that determines who chairs this committee in the first place.

## Why CX Purchases Stall in Committee

CX purchases stall in committee because the seven approvers each optimize for a different variable, and the artifact that convinces one of them is irrelevant to the other six. A demo that thrills the CX lead does nothing for a security reviewer. A SOC 2 report does nothing for finance. The deal moves only when every seat has been handed the evidence it specifically needs.

Two structural forces make this worse in CX than in most software categories. First, buying is non-linear. [Gartner's research on the B2B buying journey](https://www.gartner.com/en/sales/insights/b2b-buying-journey) frames purchases as six recurring "buying jobs" — problem identification, solution exploration, requirements building, supplier selection, validation, and consensus creation — that buyers loop back through rather than complete in order. Every time a new seat joins, requirements building reopens. A security reviewer added in week six can send the whole group back to week two.

Second, more stakeholders means more risk aversion, not more decisiveness. [Harvard Business Review's analysis of the modern B2B purchase](https://hbr.org/2017/03/the-new-sales-imperative) found that as group size grows, buyers become measurably more likely to default to the safest available action — which is usually no purchase, or renewing the incumbent. Gartner's 2026 sales survey found 67% of B2B buyers now prefer a rep-free buying experience, which means most of this internal negotiation happens in documents and Slack threads you never see, using whatever evidence the champion has on hand.

The practical implication: your job as champion is not to sell the platform. It is to manufacture, in advance, the seven different pieces of evidence that seven different people will demand. Committees do not reject good tools. They reject incomplete packets.

## The 7 Seats at the CX Buying Committee Table

The seven seats on a customer experience buying committee, what each optimizes for, and the specific objection each raises are summarized below. Use this as the first page of your internal pre-read.

| Seat | What they optimize for | The deal-killer | Evidence that unblocks them |
|---|---|---|---|
| **CX lead / program owner** | A measurable outcome the exec team already tracks, plus real adoption | "This is another dashboard nobody opens" | Named outcome metric, baseline, and 90-day adoption plan |
| **Insights / research owner** | Methodological defensibility of the findings | Findings they cannot defend in a leadership meeting | Sample logic, question design, traceable verbatim quotes behind every claim |
| **IT / systems owner** | Fit with the existing stack, no new silo, no work IT inherits | No SSO, no API, or an integration IT has to build and maintain | SSO/SCIM support, documented API, integration owner named on the vendor side |
| **Security** | Reduced third-party risk and a clean questionnaire | Missing SOC 2 Type II, undisclosed subprocessors, no recent pen test | Current audit report, subprocessor list, pen-test summary, completed questionnaire |
| **Procurement** | A defensible competitive process and contract leverage | Single-source purchase with no comparison set or benchmark pricing | Scored comparison of 3+ vendors, reference pricing, redlined terms |
| **Finance / FP&A** | Total cost inside the current budget cycle | Costs discovered after signature — services, overages, seat sprawl | Three-year TCO model including implementation, support tiers, and growth |
| **Legal / privacy** | Defensible lawful processing of customer personal data | No retention schedule, no DPA, unclear cross-border transfer basis | DPA, retention and deletion schedule, transfer mechanism, consent language |

Two notes on reading the table. The seats are listed in the order they typically *enter* the deal, not in order of authority — legal and privacy arrive last and have the hardest veto. And the right-hand column is the actual deliverable list for your evaluation. If you are building that list from scratch, our [customer experience platform requirements checklist to write before you shortlist](/blog/customer-experience-platform-requirements-checklist-to-write-before-you-shortlist) is the artifact that feeds every row.

## Seat 1: The CX Lead — Outcomes and Adoption

The CX lead approves the purchase when they can name the metric it moves and the team that will use it weekly. This seat is usually the champion, which makes it the easiest to satisfy and the easiest to over-rely on — champion enthusiasm reads as bias to every other seat.

**Optimizes for:** an outcome already visible to the executive team (churn in a segment, resolution effort, onboarding completion, a specific journey's satisfaction) and evidence that the tool will still be used in month six.

**Kills the deal for:** any platform that looks like reporting infrastructure rather than a decision input. The historical pattern in CX buying is a suite purchase that generates dashboards, wins a launch announcement, and is abandoned by the second quarter because no decision ever changed because of it.

**Pre-empt it by:** picking one metric, writing down its current baseline before you buy, and committing to a named decision the data will inform. A CX lead who walks into the committee with "we will use this to decide whether to re-sequence onboarding for mid-market accounts in Q3" is unstoppable compared to one who walks in with "we need better visibility." If you need the executive-facing framing, the [CX scorecard for the board and its seven numbers](/blog/cx-scorecard-for-the-board-7-numbers) is the vocabulary the rest of the leadership team already uses, and the [customer experience maturity model](/blog/customer-experience-maturity-model-2026) tells you honestly which capabilities your organization can absorb this year.

Adoption is the part champions consistently under-plan. A CX platform used by three people is a failed purchase regardless of feature depth. The [customer experience roadmap that sequences CX work across four quarters](/blog/the-customer-experience-roadmap-sequencing-cx-work-across-four-quarters) is a useful pattern here: attach the platform to work already on the roadmap rather than creating new work that competes with it.

## Seat 2: The Insights Owner — Method and Defensibility

The insights or research owner approves the purchase when they believe they can defend the findings under challenge. This is the seat most CX software buyers forget exists, and the one that most often produces a quiet, late-stage veto.

**Optimizes for:** method integrity. Sample composition, question neutrality, whether follow-up is consistent, and — critically — whether every summarized insight can be traced back to what a customer actually said.

**Kills the deal for:** black-box synthesis. An AI feature that produces a confident theme with no path back to the underlying quotes is unusable in a leadership meeting, because the first question is always "who said that?" The same applies to survey instruments with leading questions or response rates too low to support a segment claim.

**Pre-empt it by:** demanding traceability as a hard requirement and testing it during evaluation. Ask the vendor to show you a summary claim, then click through to the specific responses behind it. Our teardown of [verbatim analysis across 40,000 open-ended responses](/blog/verbatim-analysis-40000-open-ended-responses) shows what defensible open-text analysis looks like at volume and where automated theming quietly breaks. For the underlying category question of what a modern platform should even be doing, see [what a customer experience platform is and why AI is replacing the survey suite](/blog/what-is-a-customer-experience-platform-cxp-and-why-ai-is-replacing-the-survey-suite).

This seat is also where the depth argument lands. Scores tell you a segment is unhappy; they never tell you why, and a committee cannot act on a number without a reason attached. Conversational research — an AI interviewer that asks a real follow-up when someone says "it depends" — produces the causal detail this seat needs to defend a recommendation. A [customer journey interview](/templates/customer-journey-interview) run against 200 accounts gives the insights owner named quotes, not a bar chart.

## Seat 3: IT — Integration and Identity

IT approves the purchase when the platform fits the existing stack and creates no work IT has to own indefinitely. IT rarely wants to block a CX purchase; it wants to avoid inheriting one.

**Optimizes for:** single sign-on and provisioning (SSO, ideally SCIM), a documented API, clean identity mapping to the CRM, and no new data silo that has to be reconciled with the warehouse later.

**Kills the deal for:** integration work with no owner. If the answer to "how does this write back to our CRM" is "we can build a custom integration," IT hears "IT builds it." Second-most-common IT veto: a platform that requires a data model IT has to maintain, or that cannot export its own data cleanly.

**Pre-empt it by:** getting the integration architecture in writing during evaluation, including who does the work and who supports it after go-live. Ask about exit before entry — an incumbent that makes data extraction painful is an argument for switching, and a candidate that makes it painful is a future trap. Our guide to [getting your data out of Qualtrics](/blog/getting-your-data-out-of-qualtrics) illustrates why IT asks the export question first, and the [CX platform migration checklist for 60 days](/blog/cx-platform-migration-checklist-60-days) gives IT a realistic picture of the cutover it is being asked to absorb.

IT will also, reliably, raise build-versus-buy. Someone on the team has assembled a feedback pipeline out of a form tool, a warehouse table, and a large language model API, and it half-works. That conversation deserves a real answer rather than a dismissal — our [build versus buy decision framework for a customer experience platform](/blog/build-vs-buy-a-customer-experience-platform-decision-framework) frames it in terms of maintenance load rather than initial build cost, which is the axis IT actually cares about.

## Seat 4: Security — Vendor Risk and the Questionnaire

Security approves the purchase when third-party risk is documented and within policy, not when it is zero. This seat operates on evidence artifacts, and it is almost entirely pre-emptable — which makes late security review the most avoidable delay in CX procurement.

**Optimizes for:** a current independent audit report, a disclosed subprocessor chain, recent penetration testing, encryption posture, and a completed security questionnaire with no material gaps.

**Kills the deal for:** a missing or expired SOC 2 Type II report, undisclosed sub-processors (especially model providers, in AI-based tools), or evasive answers on where data is processed. The relevant benchmark is the [AICPA's SOC 2 description and trust services criteria](https://www.aicpa-cima.com/resources/download/get-description-criteria-for-your-organizations-soc-2-r-report), which define five categories — security, availability, processing integrity, confidentiality, and privacy — of which only security is mandatory in every SOC 2 engagement. That distinction matters: a vendor can hold a valid SOC 2 that never examined privacy controls, and a good security reviewer will check the scope, not just the badge.

**Pre-empt it by:** requesting the security package in week one, not week six, and asking security what its questionnaire contains before you shortlist. For AI-based CX tools, add three questions security will ask anyway: which model providers process customer text, whether customer data is used for model training, and whether inference happens in a region you have approved. Getting those answers early converts a four-week review into a one-week one.

Security review length is the most commonly underestimated variable in a CX platform timeline. Treat it as a parallel workstream with its own owner and its own start date, and put the questionnaire in front of vendors during the shortlist stage rather than after the verbal commitment.

## Seat 5: Procurement — Process, Terms, and Leverage

Procurement approves the purchase when the process is defensible and the terms are competitive. Procurement is not evaluating whether the tool is good; its job is to make the vendor evaluation defensible — to prove the company compared real options and negotiated properly.

**Optimizes for:** a documented competitive process, comparable pricing benchmarks, and contract terms — renewal caps, exit rights, service levels, data return obligations.

**Kills the deal for:** single-source selection with nothing to compare it against. A champion who arrives with one vendor and a signature request will be sent back to build a comparison set, which typically costs four to eight weeks. Auto-renewal clauses with uncapped uplift are the second reliable red flag.

**Pre-empt it by:** running a scored, vendor-neutral evaluation you can hand over intact. That means a written scoring model, a real comparison set, and the same questions asked of every vendor. Three artifacts do most of this work: our [vendor-neutral scoring framework for evaluating a customer experience platform](/blog/how-to-evaluate-a-customer-experience-platform-vendor-neutral-scoring-framework), the [CX vendor scorecard weighted comparison model](/blog/cx-vendor-scorecard-weighted-comparison-model) for turning subjective preference into defensible weights, and a standard question set such as our [CX platform RFP questions for vendors](/blog/cx-platform-rfp-questions-for-vendors).

For the comparison set itself, procurement wants genuinely different options rather than three variations of the same architecture. Legacy suite, mid-market suite, and AI-first challenger is a credible spread. Our roundups of [Qualtrics alternatives for teams tired of enterprise CXM bloat](/blog/qualtrics-alternatives-in-2026-8-options-for-teams-tired-of-enterprise-cxm-bloat) and [the best Medallia alternatives beyond legacy CXM](/blog/best-medallia-alternatives-2026-8-platforms-beyond-legacy-cxm) are useful for building that spread quickly, and the [12 capabilities that separate a CXP from a survey tool](/blog/customer-experience-platform-features-12-capabilities-that-separate-a-cxp-from-a-survey-tool) gives you the feature axes to score against.

## Seat 6: Finance — TCO and the Budget Cycle

Finance approves the purchase when the full three-year cost is modeled and fits the budget cycle it has already committed to. Finance almost never kills a deal on price. It kills deals on surprises.

**Optimizes for:** total cost of ownership including implementation, professional services, support tier, overage and volume pricing, and the internal headcount hours the rollout consumes. It also optimizes for timing — a purchase that lands in the wrong quarter can be delayed purely on cash-flow sequencing.

**Kills the deal for:** costs that appear after the quote. Enterprise CXM deals are notorious for this: a license figure in the proposal, then implementation services, then a premium support tier, then per-response overages once volume grows. Zip's 2025 procurement survey found that roughly 79% of software purchases now require CFO approval regardless of who nominally owns the budget, so this seat has more reach than its formal authority suggests.

**Pre-empt it by:** building the TCO model yourself, before finance asks, and showing the incumbent's real cost next to the alternative's. Our [CX platform total cost of ownership breakdown](/blog/cx-platform-total-cost-of-ownership) lists the line items buyers forget, and the verified-buyer pricing teardowns — [what Qualtrics buyers actually pay](/blog/qualtrics-pricing-2026-what-verified-buyers-actually-pay) and [what Medallia costs and why buyers are rethinking the bill](/blog/medallia-pricing-2026-what-it-costs-why-buyers-rethinking-the-bill) — give you defensible benchmark ranges instead of vendor list prices.

One framing that consistently works with this seat: express the purchase as a share of existing CX spend rather than as net-new spend. Most companies are already paying for a survey tool, an analytics add-on, and some services hours. Our analysis of [how CX teams allocate their budget](/blog/customer-experience-budget-how-cx-teams-allocate-spend) helps you show the swap rather than the addition.

## Seat 7: Legal and Privacy — Retention, Consent, and Residency

Legal and privacy approve the purchase when processing customer personal data through the platform is lawful, documented, and reversible. This seat arrives last, moves slowest, and has the cleanest veto — which is exactly why it should be engaged first.

**Optimizes for:** a signed data processing agreement, a written retention and deletion schedule, a valid basis for any cross-border transfer, and consent or notice language that covers what the platform actually does.

**Kills the deal for:** indefinite retention. Under [Article 5(1)(e) of the General Data Protection Regulation](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32016R0679), personal data must be kept in identifiable form no longer than necessary for the purpose it was collected for, and Article 5(2)'s accountability principle means the controller has to be able to *demonstrate* that a deletion schedule exists and actually runs. A CX platform that stores customer verbatims and interview transcripts forever, with no configurable retention window, is a documented compliance gap rather than a feature.

Residency is the second flashpoint. For EU-to-US transfers, the mechanism matters: the [EU-U.S. Data Privacy Framework administered by the U.S. Department of Commerce](https://www.dataprivacyframework.gov/Program-Overview) has been available since 10 July 2023 and requires participating US organizations to self-certify annually, and legal will want to know whether your vendor is certified or relying on standard contractual clauses. If your CX program records voice, add consent capture to the list, since recording law varies by jurisdiction and the platform has to support the stricter case.

**Pre-empt it by:** asking three questions in the first vendor call — what is the configurable retention window, where is data processed, and is a DPA available without negotiation. Our companion guide to [customer feedback data retention and privacy](/blog/customer-feedback-data-retention-and-privacy) covers the specific schedules CX teams should be requesting and the traps in "we keep everything for analytics."

## How to Build Consensus in the Right Order

Build consensus by satisfying the seats with veto power *before* the seats with enthusiasm, and by running risk review in parallel with evaluation rather than after it. The sequence below reverses the default order most champions use, which is why most champions lose a quarter.

**Step 1: Write requirements before you look at vendors.** Requirements written after demos are just a transcript of the demo you liked most. Draft them with the insights owner and one skeptic from IT.

**Step 2: Start security and privacy review in week one.** Request the audit report, subprocessor list, DPA, and retention configuration options from every shortlisted vendor at the same time you request pricing. These reviews are long but almost entirely parallelizable.

**Step 3: Build the TCO model before finance asks for it.** Three years, all line items, incumbent cost shown alongside. A champion who brings finance a completed model earns the benefit of the doubt on everything else.

**Step 4: Give procurement a scored comparison set.** Three genuinely different architectures, the same question set asked of each, and written weights. This is the single highest-leverage artifact in CX procurement because it converts a preference into a process.

**Step 5: Run a scoped pilot that produces two proofs at once.** Design the pilot so it delivers the CX lead's outcome evidence *and* IT's integration proof in the same 30 days. Our guide to [running a CX platform pilot](/blog/how-to-run-a-cx-platform-pilot) covers scoping one that produces a decision rather than a demo extension.

**Step 6: Present one packet, not seven conversations.** Circulate a single pre-read containing every seat's evidence, then hold one meeting. Sequential one-on-ones let each seat raise objections the others have already resolved, which is how deals loop indefinitely.

## The Seven-Seat Pre-Read Checklist

A complete CX buying committee pre-read contains one section per seat, each answering that seat's question in a single page. Use this as your table of contents.

- **CX lead** — target metric, current baseline, the named decision this data will inform, 90-day adoption plan with owners.
- **Insights owner** — sample and segment logic, question design, a worked example tracing one summary claim back to source responses.
- **IT** — integration architecture diagram, SSO/SCIM confirmation, API documentation link, who builds and who supports, export format.
- **Security** — SOC 2 Type II (with scope noted), subprocessor list including model providers, pen-test summary, completed questionnaire.
- **Procurement** — scoring model with weights, three-vendor comparison, benchmark pricing, requested contract redlines.
- **Finance** — three-year TCO by line item, incumbent cost comparison, internal hours estimate, quarter of first invoice.
- **Legal / privacy** — DPA, retention and deletion schedule, transfer mechanism, consent and notice language, sub-processor change notification terms.

If a section is empty, that seat is your bottleneck. Fill it before the meeting.

## Common Pitfalls in CX Committee Navigation

The most common mistake CX software buyers make is treating the committee as an obstacle to route around rather than a set of requirements to satisfy. Four specific pitfalls account for most stalled deals.

Building the business case on survey scores alone is the first. A committee cannot approve spend against a number with no explanation attached, and "our NPS is 31" invites the question "compared to what, and why?" Our guide to [customer experience benchmarking without fooling yourself](/blog/customer-experience-benchmarking-without-fooling-yourself) covers why score-only cases collapse under finance questioning.

The second is champion-only evidence. If every claim in the packet traces back to the person who wants the tool, the committee discounts all of it. Bring one piece of evidence from a seat that has no stake in the outcome.

The third is late-stage scope creep, where the committee's questions expand the requirement list mid-evaluation and no one re-scores. The fourth is skipping the incumbent honestly — committees notice when the alternative to buying is described as "do nothing" rather than "keep paying for the current tool." For a fuller list of what goes wrong in CX programs before, during, and after purchase, see our roundup of [customer experience mistakes to avoid](/blog/customer-experience-mistakes-2026).

## Frequently Asked Questions

### Who owns the CX platform purchase decision?

The CX or customer experience lead usually owns the CX platform purchase decision, but rarely holds unilateral authority. In most mid-market and enterprise organizations the CX lead is the champion and budget nominee, while security, legal, and finance hold independent veto rights. Where CX reports — to marketing, operations, support, or the COO — determines how much political capital the champion brings to the committee.

### How many people are on a CX buying committee?

A CX buying committee typically involves six to ten people across seven functional seats. Gartner's research puts complex B2B buying groups at six to ten decision makers, and CX platform deals sit at the higher end because they combine customer personal data, stack integration, and multi-year contracts. Smaller companies compress the seven seats into three or four people rather than eliminating any of the seven concerns.

### What kills most CX platform deals?

Most CX platform deals die on retention and residency questions raised by legal late in the process, or on costs finance discovers after the quote. Both are pre-emptable. Requesting the retention configuration, data processing agreement, and full three-year cost model in the first vendor conversation removes the two most common late-stage vetoes before they can reset the timeline.

### When should security review start in a CX purchase?

Security review should start in week one, in parallel with pricing conversations, not after a vendor is selected. Security evaluates artifacts — audit reports, subprocessor lists, penetration test summaries, questionnaires — none of which require a final decision to collect. Running review in parallel across all shortlisted vendors typically saves three to six weeks compared to serial review after selection.

### Do I need procurement involved for a small CX purchase?

Involve procurement even for small CX purchases, because thresholds are lower than most champions assume and retroactive involvement is expensive. Purchases touching customer personal data frequently trigger review regardless of dollar value, and Zip's 2025 procurement research found roughly 79% of software purchases now require CFO approval irrespective of who owns the budget line.

### How do I get IT to support a new CX tool?

Get IT support by removing work from IT rather than adding it. Confirm SSO and provisioning support, name the vendor-side owner of integration work, show a clean export path, and bring the build-versus-buy conversation up yourself before IT does. IT blocks tools that create unowned maintenance load, not tools that are unfamiliar.

## Getting the CX Buying Committee to Yes

The CX buying committee is not seven obstacles — it is seven questions with seven answers, and the answers are all collectible before the first approval meeting. The CX lead needs an outcome and an adoption plan. The insights owner needs traceable evidence. IT needs an integration owner. Security needs current audit artifacts with the scope disclosed. Procurement needs a scored comparison set. Finance needs a three-year model with no surprises. Legal needs a retention schedule and a transfer basis. Champions who assemble all seven in advance close in one cycle; champions who discover them one at a time lose two quarters to looping.

The evidence problem underneath all of this is worth naming directly. Committees stall on CX purchases because scores cannot justify spend — a satisfaction number tells six of the seven seats nothing they can act on. Depth is what converts a committee, and depth comes from conversations rather than dropdowns. Perspective AI runs AI-moderated customer interviews at scale: the interviewer follows up when someone says "it depends," probes vague answers, and returns themes with the exact customer language behind each one, which is precisely the traceable evidence the insights owner has to defend and the CX lead has to present. Because it replaces the survey layer instead of adding another suite, the TCO and integration stories stay simple enough that finance and IT stop being blockers.

If you are assembling a committee packet now, the fastest path is real evidence from your own customers. [Start a customer interview study](/research/new) with the segment your business case depends on, and use the transcripts as the insight exhibit in your pre-read. If you are building the program rather than the purchase, our resources for [CX teams](/roles/cx-teams) and the guide to [building a customer experience strategy](/blog/how-to-build-a-customer-experience-strategy) cover what happens after the committee says yes.