Customer Value Assessment

Why this node matters

Most Mittelstand portcos manage product experience by feature count and uptime. They track release velocity, ticket volume, and an annual NPS number. These are the variables that fit on an engineering dashboard. They are also the variables that describe what the firm built, not what the customer experienced, and not what the customer was willing to pay for.

The economically meaningful construct is perceived value: the customer's own judgement of benefits received against sacrifices made, formed in use, not at the point of sale. Product experience is the input; perceived value is the output that actually moves retention, expansion, and price.

The unexamined assumption underneath in both the engineering-led and the marketing-led views is that a better-built product is, by definition, a more valuable one. The assumption is rarely tested against the customer's own value judgement. The real differentiator is the gap between what the product can do and what the customer perceives it does for them. That gap is what this node has to find and close.

Perceived value as the trade-off, not the feature set. Product experience converts to commercial outcome through perceived value, defined by Zeithaml (1988) in the Journal of Marketing as the customer's overall assessment of utility based on what is received versus what is given. The mechanism is a ratio, not a sum: more features raise the "received" side only if the customer perceives and uses them, while every feature added raises the "given" side through complexity and learning cost. Blut, Chaney, Lunardo, Mencarelli, and Grewal's meta-analysis (2024, Journal of Retailing) confirms the construct's force and finds that in B2B contexts overall perceived value has a stronger positive effect on satisfaction, word-of-mouth, and repurchase than in B2C. Product experience that is not measured as a perceived-value ratio is being measured on the wrong axis.

Value-in-use, not value-in-the-box. The service-dominant logic literature (Vargo and Lusch, 2004; 2008, Journal of Marketing) established that value is not embedded in the product at the point of sale; it is co-created and realised by the customer in use. For a Mittelstand portco this reframes the node entirely: the product as shipped is a value proposition, and the value is only realised through the customer's actual usage pattern. A product with high theoretical capability and low realised usage has, economically, delivered nothing. The node's job is to manage realised value-in-use, not catalogue capability.

The experience-satisfaction-profit chain. Lemon and Verhoef (2016, Journal of Marketing) consolidated three decades of research showing customer experience is a cumulative, multi-touchpoint construct that drives the downstream financial outcomes, and that the post-purchase, in-use phase is a distinct, designable stage, not an afterthought. The chain is empirically established, not assumed: experience drives satisfaction, satisfaction drives retention, retention drives profitability (Gupta and Zeithaml, 2006, Marketing Science, synthesising the satisfaction-to-financial-performance links). A portco that cannot describe its product experience as a managed stage of the customer lifecycle has no instrument on the largest single driver of its retention curve.

Effort is the hidden tax on perceived value. The customer-effort research stream demonstrates that the sacrifice side of the value ratio is dominated less by price than by effort: the friction of getting the product to do what it promised. High-effort product experiences depress loyalty and word-of-mouth more reliably than low satisfaction does. For Mittelstand portcos this is the most frequently mismeasured variable. A product can score adequately on satisfaction surveys while quietly accumulating an effort tax that erodes expansion readiness and raises churn risk months before it shows up in a renewal conversation.

Usage depth is the leading indicator; sentiment is the lagging one. Product engagement research consistently finds that depth of feature adoption (the integration of the product into the customer's actual workflow) predicts retention and expansion earlier and more reliably than sentiment metrics like NPS. Sentiment confirms a judgement the customer has already formed; usage depth reveals the judgement while it is still forming, and intervention is cheap only while it is forming. A node built on NPS alone is reading the verdict, not the trial. A node built on instrumented usage depth can intervene while intervention is still cheap.

Complexity is the failure mode, not richness. Steinhoff, Kim, Kanuri, and Palmatier (2025, Journal of the Academy of Marketing Science) showed across a three-study B2B SaaS design that adding more to the offering raises perceived complexity, which impedes value realisation and increases churn. This is the product-experience analogue of the segmentation "one-size-fits-none" failure: a product loaded with capability that no single customer fully realises serves no customer's perceived value. Richness without realisation is not a stronger product. It is a heavier one.

The reputation substitute when value is hard to read. In B2B, where much of a product's value can only be assessed after purchase and extended use, customers fall back on corporate reputation as a proxy for value (consistent with Zeithaml's signalling logic and confirmed in B2B perceived-value studies). This cuts both ways for a portco: a strong reputation buys time for value to be realised, but it also means a product-experience gap is masked by reputation until it is large enough to override it, at which point the correction is sharp. The node's job is to make realised value visible before reputation stops covering for it.

When a portco cannot show the gap between its product's delivered capability and its customers' perceived value (segment by segment, in realised usage data, not in an annual sentiment score) then it is managing the product it built rather than the value its customers experience, and the retention and expansion lines of the EBITDA bridge are resting on an assumed value that has never been measured.

The thesis: a product experience that cannot be expressed as perceived value is not an experience. It is a feature inventory.

Margin and retention drivers

• Perceived-value ratio, not feature count. Value is benefits-over-sacrifices (Zeithaml, 1988). Features raise the numerator only if perceived and used; every feature also raises the denominator. The B2B perceived-value effect is stronger than the B2C one (Blut et al., 2024).
• Value-in-use realisation. Value is co-created in use, not shipped in the box (Vargo and Lusch, 2004). A high-capability, low-usage product has economically delivered nothing. Realised usage is the metric, not capability.
• Effort as the hidden sacrifice. The dominant term on the sacrifice side is effort, not price. High-effort experiences erode loyalty and expansion readiness before they surface in renewal conversations.
• Usage depth as leading indicator. Feature-adoption depth predicts retention and expansion earlier than NPS. Sentiment confirms the verdict; usage depth reveals it forming, and intervention is cheap only while it is forming.
• Complexity, not richness, is the failure mode. Added capability raises perceived complexity, which impedes realisation and raises churn (Steinhoff et al., 2025). Richness without realisation is a heavier product, not a stronger one.
• Reputation masking. In B2B, reputation substitutes for hard-to-read value, buying time for realisation but also concealing experience gaps until the correction is sharp.