Multiple stakeholder paths converging into a single approved business case.

How to get buy-in for a new customer feedback platform (in 6 steps)

Most feedback analytics purchases stall on internal approval, not on the product. This is the six-step process for winning buy-in from finance, procurement, IT, and your executive sponsor.

Insights
>
>
How to get buy-in for a new customer feedback platform (in 6 steps)
While you're here

TLDR

Getting buy-in for a customer feedback platform works better as an enterprise purchase than as a persuasion exercise. Map everyone who can say no, price what the status quo already costs, write the case in finance's units, and prove the numbers with a scoped pilot. Gartner found that organizational readiness raised the likelihood of hitting technology goals by 300%, against 50% for being effective at vendor evaluation.

You've run the evaluation and you know which platform you want. Now you need five or six other people to agree, and at least two of them have never read a customer verbatim. This is where most feedback analytics purchases stall, and it usually has nothing to do with the product.

The way through is to treat this as an enterprise purchase rather than a persuasion exercise. Map everyone who can say no, price what the status quo already costs, write the case in finance's units, give each gatekeeper the artifact they need, and prove the numbers with a scoped pilot. Thematic goes through this approval process with enterprise CX and insights teams constantly, and the programs that win buy-in are rarely the ones with the best deck. They're the ones where the buying group agreed on the problem before anyone argued about the vendor.

Gartner's research supports that ordering. In a 2025 survey of service and support leaders, being effective at organizational readiness raised the likelihood of hitting technology goals by 300%. Being effective at vendor evaluation raised it by only 50%.

The 6-step process

  • Map the buying group before you build anything, including procurement, IT, and finance.
  • Price the status quo so the comparison is against a real number, not against zero.
  • Write the business case in the CFO's units: hours, headcount, payback, and risk.
  • Give each gatekeeper their own artifact rather than one deck for everyone.
  • Run a scoped pilot with success criteria agreed in advance.
  • Pre-answer the three objections that kill these deals.

Step 1: Map the buying group before you build anything

The most common mistake is preparing for a conversation with one executive when the decision belongs to a committee. Forrester's State of Business Buying, 2026 found that the typical B2B buying decision includes 13 internal stakeholders and nine external influencers. Procurement professionals are decision-makers in 53% of business buying cycles, engaging from the start of the process.

Write the list down: executive sponsor, finance, procurement, IT or data engineering, information security, and the person who owns whatever tool you're augmenting. For each, note what they're accountable for and what would make them say no.

Do this first because consensus predicts a clean purchase. Gartner found that 74% of B2B buyer teams show unhealthy conflict during the decision process. Buying groups that reach consensus are 2.5 times more likely to report their deal was high quality.

Step 2: Price the status quo

A budget request compares your proposal against doing nothing, so doing nothing needs a price tag. Most CX teams have never calculated theirs, which means the platform gets evaluated against zero and loses.

Count the hours your team spends manually reading, coding, and tagging open-ended feedback each cycle. Multiply by loaded cost. Add the analyses nobody runs for lack of capacity.

The numbers are usually larger than people expect. At Atlassian, which serves over 250,000 customers, research teams had been spending six weeks in a Miro whiteboard bucketing and categorizing feedback. Community Health System is a not-for-profit healthcare network serving California's central San Joaquin Valley. Before it automated the work, the team spent more than 250 hours and roughly $15,000 in staff time per reporting cycle on open-ended employee survey responses.

Neither is a software cost. Both are already on the P&L, buried in salaries.

Step 3: Write the business case in the CFO's units

Finance doesn't evaluate insight quality. It evaluates hours, avoided headcount, payback, and downside risk. Translate accordingly, and be specific enough that the model can be audited.

The Forrester Total Economic Impact study commissioned by Thematic in 2023 is a useful template, because it prices both sides. Its composite organization is a $6 billion US e-commerce business receiving 150,000 open-ended survey responses per quarter. The study found a 543% three-year ROI and $2.9 million in total benefits on a present-value basis. The benefit lines are the ones worth copying: 4,250 hours of manual data preparation, reading, and tagging automated; avoided headcount of two full-time employees worth $652,000 in three-year risk-adjusted present value; $1.8 million in incremental income. Against that, $369,300 in software and professional services plus $74,400 in ongoing internal costs.

Capacity per analyst is often the cleanest single argument. At Mitre 10, a retail hardware cooperative across New Zealand, a three-person insights team handles 20,000 verbatim comments a month across 84 stores.

In 2022, Gartner found that organizations demonstrating the link between customer satisfaction and profitability were 29% more likely to secure additional CX budget.

Step 4: Give each gatekeeper their own artifact

One deck for six audiences satisfies none of them. Gartner's 2022 research found that 67% of technology-buying decision participants work outside the IT department, so the questions differ sharply from person to person.

GatekeeperWhat they are actually askingWhat to hand them
Executive sponsorDoes this move a number I am accountable for?One page linking feedback themes to the metric in their objectives
FinanceWhat is the return, and when?Three-year cost model with the status-quo baseline from Step 2
ProcurementIs this the right commercial structure and vendor?Total cost of ownership, contract term, and what happens at renewal
IT and data engineeringWhat will this cost my team to support?Integration list, data flow diagram, and implementation timeline
Information securityWhere does our customer data go?SOC 2 report, data processing agreement, and data residency answers
Incumbent tool ownerIs this replacing what I bought?An explicit statement of what stays and what this adds

That last row matters more than it looks. If you're adding a customer intelligence layer alongside an existing survey platform rather than replacing it, say so early and in writing. Left unaddressed, the ambiguity turns a colleague into an opponent.

Step 5: Run a scoped pilot with success criteria agreed in advance

A pilot isn't a hedge or a persuasion tactic. It's standard enterprise buying behavior, and procurement expects it. Forrester found that more than 60% of business buyers now use a trial before purchase, rising to 78% for purchases of $10 million or more.

Agree the success criteria in writing before the pilot starts, with the people from Step 1. Pick one dataset, one team, and one decision the output has to inform. Define what result converts the pilot into a contract and what result ends it.

Scope it to weeks, not quarters. Community Health System delivered 250 one-page department reports in a single three-day sprint. That saved more than 160 hours and about $10,000 per reporting cycle, and it put structured comment-based insight in front of leaders below VP level for the first time.

Vague open-ended evaluations produce the opposite. Gartner found in 2022 that 56% of organizations had high purchase regret over their largest recent technology purchase, and those organizations took seven to 10 months longer to complete it.

Step 6: Pre-answer the three objections that kill these deals

Every feedback analytics purchase meets the same three challenges. Answer them in the proposal, before someone raises them in a meeting where you can't respond with evidence.

  • "Why not build it in-house?" Answer with a five-year total cost that includes engineering time, model maintenance, and the opportunity cost of that team not working on the product.
  • "Can't we use the AI tools we already pay for?" A general-purpose model summarizes a batch of feedback. It won't produce a theme that means the same thing this quarter as last, which is what makes trend reporting and score attribution defensible.
  • "We already own a CX suite." Be precise about the layer. Survey platforms collect feedback well. Analyzing unstructured feedback consistently across every channel is a different job.

A worked example: how LendingTree funded a fix

LendingTree is an online marketplace for home lending, consumer lending, and insurance. Its story shows what a funded internal case looks like, because the case was built from the platform's own output.

Lee King, Head of Insights, was working through more than 20,000 customer comments every 90 days. Analysis surfaced a theme the team hadn't been looking for: a "Timing of Call" problem, where leads were being called outside business hours because of US time-zone differences. It was disproportionately driving detractors in net promoter score (NPS) surveys.

The insight alone wouldn't have funded a fix. King quantified the loan value affected by the problem. That converted a customer-experience complaint into a revenue figure, which is the unit the people approving the fix already used.

That sequence is the method in miniature: a theme nobody had time to find manually, a number attached to it, and that number expressed in the language of the person signing.

Common mistakes to avoid

  • Leading with the platform instead of the problem. If the buying group hasn't agreed the problem is real and expensive, every capability you demo reads as a nice-to-have.
  • Presenting ROI without a baseline. A projected return with no measured starting point is unauditable, and finance treats unauditable numbers as zero.
  • Citing statistics that don't survive scrutiny. The claim that it costs five times more to acquire a customer than to retain one has no traceable primary source. McKinsey's finding that compensating for one lost customer can require acquiring three new ones is sourced and does the same work.
  • Bringing security and procurement in at the end. They won't be rushed, and introducing them late converts a two-month process into a two-quarter one.
  • Treating a stalled decision as a "no." Research behind The JOLT Effect, based on 2.5 million recorded sales conversations, found that 40% to 60% of B2B deals are lost to customer indecision rather than to a competitor. Narrow the scope and reduce perceived risk instead of adding features.
1. Guide Analysis
Guides

Build, Buy or Partner? A Layered Guide to AI Feedback Analytics

Transforming customer feedback with AI holds immense potential, but many organizations stumble into unexpected challenges.