Growth that compounds

A segment is real when a decision changes

A segment is operational only when its boundary changes a promise, service, price, owner, route, or retention action, then leaves an observable trace.

1,155 words 5 min read 2 references  readers

Management summary

A customer segment can be statistically neat and commercially empty. Stein, Smith, and Lancioni describe how CRM records are often kept deal by deal, which makes cross-segment and relationship-form analysis harder. Palmatier, Scheer, and Steenkamp show that relationship paths can connect differently to financial risk and selling effectiveness in triadic industrial data. Neither source validates a universal segmentation taxonomy. The useful operating test is narrower: a segment earns its place when its boundary changes a promise, service level, price or terms, owner or route, or retention action, and the change leaves an observable cost, constraint, or outcome.

Keywords: Customer segmentation · Customer intelligence · Service design · Growth operations

On this page

A segment can be statistically neat and commercially empty.

The labels may be consistent. The dashboard may show a different colour for each tier. The account team may still make the same promise, provide the same service, charge the same price, use the same owner, and run the same retention motion for everyone.

The useful question is not how many segments do we have? It is: what decision changes at the boundary, and what observable trace should that change leave?

Why is CRM data categorization distinct from true market segmentation?

Stein, Smith, and Lancioni describe a problem in B2B CRM intelligence. Records are often treated as deal-specific rather than reconstructed for analysis across market segments, customer categories, and relationship forms. Their paper is conceptual and managerial. It does not provide a validated segmentation score or an effect size. Its value is diagnostic: a CRM can contain many fields and still make the customer system hard to compare.

Their proposed classification asks three useful questions. Which way does the informing process run? Which way does decision-making run? Which criteria describe customer value? These questions are more productive than adding a new tier label because they ask how information, authority, and value move through the relationship.

A segment becomes operational only when the answer changes an action. If the same owner reads the same record, offers the same service, and uses the same price rule, the classification may be descriptive but has not yet become a commercial boundary.

How do distinct buyer relationship paths reshape operational resource allocation?

Palmatier, Scheer, and Steenkamp studied 362 buyer-salesperson triads in industrial markets. They model salesperson-owned loyalty, firm-owned loyalty, value received, financial risk, selling effectiveness, growth, and willingness to pay as different paths. Salesperson-owned loyalty predicted latent financial risk at 0.62, with R2 of 0.38. In the same study, salesperson-owned loyalty predicted selling effectiveness at 0.26, while value received was 0.05 and not statistically significant.

Those coefficients are not segment thresholds. They are a reason not to collapse every account into one customer-health or value label. A relationship can have a different owner path, a different risk path, and a different value path. A segmentation decision should state which path it is trying to change or protect.

The study also reports that buyers stated they would try to shift an average 26% of purchases to a departing salesperson’s new firm over three years. That is stated intention, not realized churn. The boundary matters. A segment that changes owner or retention action may be operationally real before an outcome is visible, but the outcome must not be claimed until it is measured.

Which six operational boundaries define an actionable customer segment?

BoundaryDecision that changesEvidence objectExpected traceFailure mode
PromiseWhich problem, use case, or value proposition is statedBuyer need, use case, requirement, or outcome definitionDifferent promise or qualification ruleDifferent label, same promise
ServiceWhich onboarding, support, or response level is offeredWork type, urgency, capacity, or contractual requirementDifferent service path or capacity useTier name with identical service
Price and termsWhich price, discount, credit, or contract rule appliesCost, value, risk, regulation, or negotiation objectDifferent terms and realized economicsTiering without a price decision
OwnerWho manages the relationship and decisionAuthority, knowledge, risk, and continuity requirementAccount owner or decision path changesField ownership changes only in CRM
RouteWhich direct, partner, or marketplace path is usedAccess, margin, service, and relationship dataDifferent route economics or accessChannel label with same work
RetentionWhich intervention or renewal path is triggeredRisk signal, cohort, contract, or observed behaviourDifferent action and outcome windowHealth colour with no intervention
MeasurementWhich denominator and period define successUnit, baseline, time window, and counterfactualComparable result or explicit unresolved statusSegment result cannot be compared

Table 1The segment-to-decision map

A segment earns an operating role only when its boundary changes work and leaves a measurable trace.

Source: Stein, Smith, and Lancioni (2013) and Palmatier, Scheer, and Steenkamp (2007). Framework rows are the author's synthesis.

View exhibit page

Why does behavioral distinctiveness fail to guarantee segment profitability?

Some boundaries are constraints. A regulatory category can require a different contract before revenue changes. A service-level agreement can require a different response path before retention is observed. An enterprise owner can be necessary because decision authority is distributed, not because the account has already produced higher margin.

That is why the framework separates operational reality from outcome proof. The first question is whether the boundary changes a decision or obligation. The second is whether the change produces a measured cost, constraint, or outcome. The third is whether that outcome is comparable to a stated baseline.

The order prevents a common mistake: using an outcome label to hide the decision that produced it. A “high-value segment” may mean high revenue, high margin, high strategic access, high service cost, or high expansion potential. Those are different objects and require different actions.

How should commercial leadership run a one-period segment validation test?

To test a segment without building a permanent taxonomy, choose one decision and one period. Record the boundary, the changed action, the work or cost that should move, the outcome window, and the comparison. If the action does not change, the segment has not earned an operating role. If the action changes but the outcome remains unresolved, record the segment as an intervention or constraint, not as a proven profit pool.

The minimum record is:

  • segment boundary and inclusion rule;
  • changed promise, service, price, owner, route, retention action, or measurement;
  • evidence object and data owner;
  • time window and comparison unit;
  • cost, constraint, or outcome expected to move; and
  • failure mode if the boundary is wrong.

Where are the empirical limits of customer segmentation models?

Stein, Smith, and Lancioni do not validate a segmentation model. Palmatier, Scheer, and Steenkamp do not show that their relationship paths define profitable segments. Neither source says that more tiers create more precision.

They support a disciplined boundary: a segment is commercially real when it changes a decision, and its claim becomes stronger only when the resulting cost, constraint, or outcome is observed against a defined comparison. A label can start the conversation. It cannot finish the operating design.

The boundary connects to net revenue retention as a cohort definition and the retention number measured from your side, which keep the population and relationship object explicit before an outcome is named.

References

  1. Stein, A. D., Smith, M. F., & Lancioni, R. A. (2013). The development and diffusion of customer relationship management (CRM) intelligence in business-to-business environments. Industrial Marketing Management, 42, 855–861. https://doi.org/10.1016/j.indmarman.2013.06.004
  2. Palmatier, R. W., Scheer, L. K., & Steenkamp, J.-B. E. M. (2007). Customer loyalty to whom? Managing the benefits and risks of salesperson-owned loyalty. Journal of Marketing Research, 44(2), 185–199. https://doi.org/10.1509/jmkr.44.2.185

Pass it on

Share this essay

If it was useful to you, it is probably useful to someone on your team.

Download as PDF

A complete document: title page, contents, sources, and the citation on the last page.

Sinan Isoglu

About the author

Sinan Isoglu, MBA (Quantic)

Commercial growth leader, lecturer and doctoral researcher

Sinan Isoglu is a commercial growth leader, lecturer and doctoral researcher. His work spans go-to-market, pricing and revenue operations; his doctoral research at EM Normandie examines sales and marketing integration after cross-border M&A. He lectures on marketing and growth at IU International University of Applied Sciences.

Credentials

  • Doctoral researcher, EM Normandie Business School
  • MBA, Quantic School of Business and Technology
  • Lecturer, IU International University of Applied Sciences

Writes on

  • Go-to-market
  • Pricing
  • Revenue operations
  • AI in commerce
  • Cross-border growth

The track

The work behind this question.

This piece sits in the commercial track: the operating problems behind growth, pricing and revenue systems.

Comments

Join the thinking.

Comment on the piece, or select a passage above to quote it directly.

Leave a comment

Comments are read and approved personally before they appear. Your name and comment are stored for publication. See the Privacy note.