I have been in enough boardrooms to know how this conversation usually goes. Someone from the CX team presents the NPS scores. A few people nod. Someone asks about the loyalty program. Everyone agrees that trust matters. Then the meeting moves on to the revenue slide and nobody connects the two.

I built Customer Trust Infrastructure as a discipline because I got tired of watching that meeting happen over and over while the churn numbers kept moving in the wrong direction. The problem was diagnosis. Organizations were measuring experience and calling it trust, and the gap between those two things was costing them in ways they could not see because they were looking at the wrong data and asking the wrong questions.

What I want to do in this piece is make the business case as plainly as I can: trust is a revenue infrastructure problem, and until your C-suite understands that, the CX team will keep being handed responsibility for something they cannot fix with the tools they have been given.

Those are not brand health metrics. They are revenue metrics, and your finance team should have their own version of that slide. 

We Have Been Solving the Wrong Problem

For the better part of a decade, organizations have invested heavily in customer experience — journey mapping, personalization, omnichannel platforms, AI-driven support, an ever-expanding technology stack all aimed at improving how customers feel about their interactions. And by most measures, those investments have not moved the trust needle. The 2026 Edelman Trust Barometer, which surveyed nearly 34,000 respondents across 28 countries, describes a world where trust is becoming more insular, more conditional, and harder to earn, with only 32% of respondents globally believing the next generation will be better off. That collapse in optimism reaches into how people approach brand relationships too.

This is the thing I keep coming back to when I look at the data: we have been optimizing touchpoints while trust erodes at the system level. A touchpoint is a moment, and trust is a pattern built across many moments, and you cannot build that pattern if the systems connecting those moments are unreliable, inconsistent, or designed primarily for operational convenience rather than customer reliability.

We have been treating a systems problem like a moments problem, and until we shift that diagnosis we will keep pouring resources into solutions that address the symptom rather than the source.

What This Costs (in Numbers Your Board Actually Tracks)

I want to spend a moment on the financial case, because this is where the conversation often gets lost between the CX team and the C-suite. CX leaders know intuitively that trust drives retention. What they often struggle to do is express that in the language that gets resources allocated.

Churn is a valuation problem, not a customer success problem. SaaS businesses with churn rates above 10% see valuation multiples drop to 3 to 4 times revenue, while companies with low churn command 8 to 12 times revenue multiples. Reducing churn by just 1 to 2% can boost long-term enterprise value by 30 to 50%. When I sit across from a CFO and translate trust erosion into those terms, the conversation changes.

The acquisition side compounds everything. Every churned customer costs not only the revenue they took with them but the full cost of finding someone to replace them. When your systems are eroding trust and producing churn as a result, you are not just losing customers; you are funding your competitors' pipelines with your own revenue and then paying full acquisition price to try to fill the hole. 

True loyalty, the trust-based kind rather than the habit-or-switching-friction kind, fell to 29% in 2025, a five-point drop in a single year. 77% of consumers now retract their loyalty more quickly than they did three years ago. A better loyalty program will not fix that. It is the wrong solution for the actual problem.

Points and perks rent behavior, and the rent goes up every time a competitor offers a better deal. The organizations that will retain customers through the next decade are the ones building the underlying systems that make trust the natural output of how they operate, rather than a campaign running on top of a broken foundation.

What I Mean by Customer Trust Infrastructure

When I started developing Customer Trust Infrastructure as a formal discipline, I was trying to solve a specific problem: the gap between how much academic research existed on trust and how little of it ever made it into the actual decisions organizations make about their customer systems. Sociologists have been studying trust as a social mechanism for decades. Behavioral psychologists have mapped how trust forms and breaks at the individual level. Organizational theorists have written extensively about the conditions that produce or destroy trust inside institutions. And almost none of that scholarship was showing up in boardroom conversations about CX.

Customer Trust Infrastructure draws on all three of those bodies of knowledge to make a simple argument: trust is not a feeling that customers have about your brand. It is an outcome of the systems your brand operates. You can engineer it deliberately, or you can let it erode accidentally, but you cannot manage it through messaging alone. I published the founding document for this discipline in March 2026 through Zenodo (DOI: 10.5281/zenodo.19022147) because I wanted it to be citable, indexed, and available to anyone doing serious work in this space.

At the center of CTI is the Customer Trust Equation, which I developed as a way to make trust operationally legible:

What I like about the equation format is that it forces specificity. You cannot just say trust is important and then measure NPS. You have to ask which of these five variables is failing and why, which means you can actually do something about it. Each variable maps to a distinct organizational capability and a distinct category of business risk.

The reason I made Friction a subtractive variable is that it operates differently from the others. Loss aversion research tells us that losses register more powerfully than equivalent gains, which means friction destroys trust faster than any of the other variables can build it. Delight will not fix a friction problem.

This is why organizations that invest in customer delight initiatives while leaving systemic friction unaddressed keep losing customers they believe they have satisfied. The delight registers, then the friction registers louder, and the customer leaves anyway. Daniel Kahneman's research on loss aversion, along with decades of work on negativity bias, makes this entirely predictable. The customers know it even when the retention cohorts haven't shown it yet.

Why the CX Team Cannot Fix This Alone

I want to be careful here because I am not criticizing CX teams, many of whom are doing genuinely excellent work under genuinely impossible constraints. What I am saying is that the constraint itself is the problem, and it is structural rather than personal.

When a customer has to repeat their account information to four different support agents, that is not a CX failure. It is the downstream consequence of a technology architecture decision made by people who were not thinking about trust when they made it. When a customer receives contradictory information from sales and from customer success, that is not a communication breakdown. It is the consequence of misaligned incentive structures and the absence of a shared source of truth. When a customer encounters a cancellation policy that feels adversarial, they are not having a bad moment. They are experiencing the consequence of a legal or finance decision made by people who never had to sit across from a customer and explain it.

Once you see the current systems in action, the trust failures make sense. Of course your customers don’t trust you when this is the system working as is. Once you see it, you can’t unsee it.

I am sick of seeing it.

CTI locates accountability where control actually lives. Consistency belongs to operations and technology. Response belongs to customer success and product. Connection belongs to marketing, community, and frontline leadership. Value belongs to product and pricing. Friction belongs to whoever owns the process creating it, which is a different answer for every organization and often a different answer for every piece of friction you find when you actually look. The CX leader's job is to diagnose, advocate, and architect, but they cannot build the infrastructure if the rest of the organization does not own their piece of it.

That 60-point gap between executive self-assessment and customer reality is what happens when the people responsible for trust infrastructure have no instrument to measure it and no framework to identify where it is eroding. They are not lying when they say they believe customers trust them. They genuinely believe it because the data they are looking at does not show them otherwise until the churn moves, and by the time the churn moves, the trust problem is months old.

You can’t solve a problem you don’t measure for.

Three Places to Start

1. Replace what you measure

NPS, CSAT, and Customer Effort Score tell you how customers feel at a specific moment. They do not tell you whether the systems producing those moments are stable or deteriorating. An organization can have a healthy NPS score and a failing trust infrastructure, and the two data sets will not connect until a churn cohort turns or a retention rate drops. CTI asks you to measure the variables instead: consistency across channels, responsiveness at the system level rather than the interaction level, connection signals that go beyond survey scores, perceived value trends over time, and friction identified through journey analysis rather than complaint volume. Most of these data points already exist somewhere inside your organization. The gap is usually not data but assembly, someone needs to put it together into a trust diagnostic rather than a satisfaction dashboard.

2. Run a friction audit

I have never worked with an organization that knew the full extent of the friction in their customer journey before someone actually mapped it. Friction accumulates gradually and invisibly, one policy decision and one process shortcut at a time, until it is woven into how everything works and nobody remembers why it has to be that way. A friction audit maps every step a customer is required to take, identifies which steps are genuinely necessary, and calculates the trust cost of the ones that aren't — it is an operational exercise, and the ROI is among the most defensible in CX because you don't need new technology to remove friction. You need organizational will to stop protecting internal convenience at the customer's expense, which is a leadership decision the CX team cannot make unilaterally.

3. Name who owns each variable

The single most useful thing I see organizations do when they start working with CTI is name which function owns each variable, because that naming exercise forces a conversation that almost never happens otherwise. Every broken trust system has an owner. The reason it stays broken is usually invisibility — nobody has drawn the line between the policy or process and the trust outcome it produces. When you name it explicitly and assign it to the function that actually controls it, accountability becomes possible in a way it wasn't before. You are surfacing what was always true about where the problem lives, so the people who can fix it know it is theirs to fix.

The Window for This Is Not Permanently Open

The 2026 Edelman Trust Barometer describes a world where 70% of global respondents are unwilling or hesitant to trust someone with different values, backgrounds, or information sources, where institutional trust in government, media, and NGOs has reached historic lows, and where the trust customers extend to brands is more finite and more conditional than it has been in decades. Business is currently the only institution the data shows people still trust to be both ethical and competent, and I do not think that will remain true indefinitely without organizations actively doing the work to deserve it.

What I find genuinely compelling about this moment is that the organizations willing to build trust infrastructure deliberately are accumulating a structural advantage that will be very hard to close once it compounds. Lower acquisition costs because retention improves. Higher lifetime value because trusted customers spend more and stay longer. Stronger advocacy because connection converts satisfied customers into people who bring others in. Better valuations because investors are already pricing retention into multiples. The math is not subtle.

The question customers are actually asking is not whether their last experience was good. It is whether they can trust you to get it right every time. The organizations that can answer that question through their systems rather than their messaging are the ones building something durable.

What I Would Ask Your C-Suite to Do

I am not asking your leadership team to become trust scholars, though if they want to go deeper I would genuinely encourage it. The founding document for Customer Trust Infrastructure is publicly available at DOI: 10.5281/zenodo.19022147 and I published it specifically because I wanted this work to be accessible and citable rather than proprietary.

What I am asking is simpler: the next time the retention numbers are on the agenda, ask which of the five variables is failing and who owns it. The next time the loyalty program budget is up for renewal, ask whether you are renting behavior or building trust and whether you can tell the difference from the data you have. The next time a policy gets approved that makes an internal process easier but adds friction for the customer, ask someone to calculate what that friction costs in trust terms before the signature goes on it.

Customer Trust Infrastructure is a discipline grounded in sociology, behavioral psychology, and organizational theory that makes trust measurable, diagnosable, and actionable at the organizational level. The Customer Trust Equation gives you a practical instrument: Consistency drives retention, Response converts detractors, Connection builds advocacy, Value justifies price, and Friction, if you leave it unaddressed, erodes all four while your NPS score stays exactly where it was last quarter.

The data on trust erosion, churn costs, and valuation multiples is unambiguous. The question is whether your organization decides to treat trust as the infrastructure it actually is before the churn cohorts make the decision for you.

Christina Garnett is the founder of Pocket CCO, a CX consultancy and fractional CCO firm. She is the creator of the Customer Trust Equation and Customer Trust Infrastructure She is the award-winning author of Transforming Customer-Brand Relationships (Kogan Page, 2025).

CTI Founding Document: DOI 10.5281/zenodo.19022147  ·  customertrustequation.com