The Measurement Matters
Why balancing customer needs and business priorities is often a measurement problem
How do you best balance customer needs and wants with the business's needs and priorities? Executives in complex-product B2B companies ask me this in many forms, and I understand why. Budgets are fixed, and every customer request lands on someone's P&L. My experience tells me the two sides aren't really competing. What matters is the lens used to make the decision, and that lens shifts when the culture is organized around the experience customers have with your brand. In that kind of company, decisions get made faster, and when the culture is built into how the company operates, they hold up longer, which protects long-term value. Two examples show the difference.
At one company I worked for, a large customer asked for weekly reporting on the status of their equipment through the company's online technology. The company didn't have the systems, procedures, or funding to deliver it. A short-term decision was made to pull money from other customer-facing initiatives and those projects sat on hold until the reports were finished. Two years later, that customer left anyway. Nothing the company learned building the reports helped any other product.
I want to be careful about the lesson. A customer leaving doesn't prove the decision was wrong. The real failures came earlier. The implementation of the equipment had caused conflict from the start of the relationship, and the customer wanted weekly reports to verify the solution was working as intended. Because this was a large, important customer, the company built the most expensive version of the need, as a one-off, and asked for nothing in return, to appease the customer. Other customers had been asking for reporting too. The company had no mechanism to prioritize customer requests beyond equipment enhancements. The request was framed as a customer-versus-business conflict. In reality, it was a recurring need that no one could see clearly or fund.
A business case for reporting had been made, and it lost on ROI. But the model counted only five years of direct revenue. It left out service costs and the value of retention and renewals, so it could never see what reporting protected. No one had decided who was accountable for the revenue, and that call belonged to the CFO.
At a different company I worked for, I saw the opposite. Customers disliked extended downtime for maintenance, and the service team disliked the hours it took them to perform the maintenance each year. Same pain, two sides. Using equipment data and better reporting, the service team, IT, and marketing built a service that removed it. As the service product marketing leader, I designed the program so that customers who used it paid less on their service contracts, and the team added services to make the offer worth taking. Sales, marketing, service, and IT were aligned. My business case was that the reduced service costs would cover the lost contract revenue.
It did better than that. More than 90% of customers adopted it, but adopting a discount proves little. What mattered was that the cost savings exceeded the revenue the company gave up, and they alone drove the success. The offer also became the base for additional services, branded together. Notice the difference between the two stories. One need was bolted on as an exception and returned nothing reusable. The other was built as a foundation and beat its own business case. The measurement was different too: the first model counted only direct revenue, and mine counted the service cost savings against the revenue the company gave up.
The truth is that executive buy-in for customer experience existed at that company before I built anything. The culture was steeped in customer success and innovation. For example, I once sat in a room where commercial and operational leaders debated a decision that would cost more than a million dollars to implement. After 45 minutes, the CEO walked in, listened to the options, and decided to spend the money because it was right for customers and the people they served. He could decide that quickly because he already knew the context. That's a strength, but it's also fragile. At the other company, the CX priorities didn't survive a change in leadership.
So what should an executive do? Customer focus becomes real when it's built into how the company operates and it stays intact when a leader moves on. These are the five mechanisms I'd put in place first.
1. One intake for every customer ask. Sales, service, support, and CX log requests in one place, tagged by account and need, and reviewed monthly so a pattern shows up as a pattern instead of as scattered one-offs. One named owner keeps the log current.
2. A triage test before funding anything. How many customers have asked, what pain sits behind the ask, what happens if you don't deliver, and could it be reused? If it truly is a one-off, scope it, price it, or trade it for a commitment such as renewal or term.
3. One business case standard, owned by finance. Count retention, renewals, service costs, and multi-year revenue, not only new revenue. Settle in advance who is accountable for the revenue. How to put a number on retention is a bigger topic than one essay.
4. A standing cross-functional decision forum. Commercial, operations, service, product, and finance leaders meet on a fixed cadence with the authority to decide, which drives decision speed and clarity.
5. Regular executive exposure to customers and the people who serve them. Leaders review top customer pain points and service team feedback on a routine schedule, and customer metrics sit on executive scorecards, so context isn't lost when leaders move positions or leave the company.
The tension between customer needs and business needs feels real because the measuring stick is wrong and leaders lack the context to see it. Build the mechanisms to fix both, and most of the "balance" disappears.
I help B2B complex-product organizations find where customer needs are going unfunded, and build the case and ownership to close the gap.
The first call is free: sixty minutes to look at where your customer experience is actually being owned today, and where it isn't.