Marketing Core Conflict Cloud

Concept: Vocabulary that names a phenomenon.

A pricing conflict cloud that separates the customer’s perceived-value basis from the supplier’s cost-floor need, then resolves the clash through a TVC floor and isolated market segmentation.

Also known as: pricing cloud; market-pricing conflict.

Pricing is where TOC finance and market strategy meet. A supplier can’t ignore its cost structure, but customers don’t buy because a supplier has costs to recover. They buy when the offer is worth the price in their own system. The Marketing Core Conflict Cloud gives that tension a precise shape: one side wants price based on customer perceived value so volume will hold; the other wants price based on supplier economics so the company remains profitable.

Understand This First

• Market Constraint — why demand can become the active system limit.

• Throughput Accounting — why operating expense is not allocated into product cost.

• Evaporating Cloud — the necessity-logic form this pricing conflict uses.

Context

The Marketing Core Conflict Cloud belongs in Strategy, Marketing, and Sales because a market-constrained system is usually tempted to treat price as the easiest exploitation move. Sales asks for a lower price to win volume. Finance protects margin. Marketing tries to position the offer around value. Each actor has a legitimate requirement, and the conflict recurs because the organization keeps arguing over the price number instead of the basis for setting it.

The TOCICO Dictionary treats this as one of marketing’s core problems. The cloud’s shared objective is profitable sales growth. One requirement is enough volume, which pulls the price toward the customer’s perceived value. The other is a reasonable profit result, which pulls the price toward the supplier’s cost basis. In ordinary cost-world language, those two bases collide.

The TOC solution does not say “price low” or “price high.” It changes the cost-side requirement. The company does not need each product’s price to cover an allocated share of operating expense. It needs the whole system to cover operating expense and investment while every sale clears its truly variable cost. That correction opens the door to market segmentation: different segments can pay different prices when the price and quantity offered in one segment do not affect the price and quantity in another.

What It Is

The Marketing Core Conflict Cloud is a domain-specific Evaporating Cloud for pricing. It names the apparent contradiction between two pricing bases:

• Customer perceived value. To sell enough volume, the price has to make sense against the customer’s alternative, pain, risk, urgency, and value of the outcome.

• Supplier economics. To remain profitable, the supplier has to recover operating expense and investment, and each sale has to contribute positive throughput.

The cloud can be drawn compactly:

flowchart LR
    D["D: Base price on customer perceived value"] --> B["B: Sell enough volume"]
    E["D-prime: Base price on supplier cost"] --> C["C: Cover OE and investment"]
    B --> A["A: Grow profitably"]
    C --> A
    D -. "appears to conflict with" .- E

Diagram: Flowchart. The diagram contains these connections:

• D: Base price on customer perceived value leads to B: Sell enough volume.

• D-prime: Base price on supplier cost leads to C: Cover OE and investment.

• B: Sell enough volume leads to A: Grow profitably.

• C: Cover OE and investment leads to A: Grow profitably.

• D: Base price on customer perceived value leads to D-prime: Base price on supplier cost: appears to conflict with.

The invalid assumption usually sits under D-prime. Cost-based pricing treats supplier cost as if every unit has to carry an allocated share of labor, overhead, and fixed expense. Throughput Accounting rejects that allocation. The minimum price for a clean incremental sale is truly variable cost, not fully absorbed unit cost. Operating expense is recovered by the system’s total throughput over the period, not by forcing every unit to carry an accounting burden.

That does not make every above-TVC sale good. The segment has to be isolated. If a lower price leaks into the main market, displaces higher-throughput demand, consumes constraint time, or trains regular customers to wait for discounts, the cloud has not been broken. It has been dodged.

How It Is Measured or Recognized

The conflict is visible when pricing meetings oscillate between volume and margin. Sales says the price is too high for the buyer’s perceived value. Finance says the price is too low against cost. Both sides can be right inside their local frame, which is why the same argument returns product after product.

A second signal is misuse of Throughput per Constraint Unit. T/CU ranks demand after price and TVC are known. It doesn’t decide the market price. When a team tries to set price by T/CU alone, it has moved a product-mix tool into a market-basis problem.

A third signal is an untested segmentation claim. Market segmentation in this cloud is not demographic grouping or buyer-persona language. It is an economic isolation test: can one segment receive a different price and quantity without changing what another segment sees, expects, or can arbitrage? Government contracts, emergency capacity, rush orders, educational pricing, regional offers, or special channels may pass that test. A public discount on the same product usually doesn’t.

The strongest recognition test is the T-I-OE check. A proposed price should raise or protect total throughput, avoid unnecessary investment, and avoid operating-expense growth that wipes out the gain. If the recommendation can’t be stated in those terms, the conversation has probably slipped back into cost-world pricing or generic value-pricing advice.

Why It Matters

The cloud keeps TOC pricing from collapsing into two weaker slogans: “charge what the market will bear” and “never sell below cost.” TOC accepts the customer’s perceived-value basis, but only when the segment is real and the offer’s value is specific. It accepts the need to cover cost, but not the fiction that allocated operating expense belongs inside every unit’s price.

That distinction matters for Mafia Offer work. Lang’s label-printer example shows the point. The customer-valued offer was not a lower sticker price; it was a changed deal that reduced label inventory, protected availability, removed forecast pressure, and shifted stockout risk back to the supplier. Because the offer changed the customer’s economics, price could be held at the current competitive level while customer value rose. If a supplier instead cuts price without changing the customer’s damage, it has not built a Mafia Offer. It has joined a margin contest.

For certification-track readers, the entry also marks the boundary between Finance and Measures and Business Strategy. The finance side supplies the TVC floor and T-I-OE discipline. The strategy side supplies target-market choice, perceived-value analysis, segmentation, and the offer that makes a price defensible. A practitioner who can move across that boundary can explain why an above-TVC special price may be acceptable in one isolated segment and destructive in another.

Common Misunderstanding

“TOC pricing means price at truly variable cost.” It doesn’t. TVC is the floor for a clean incremental sale, not the target price. A sale above TVC still has to be tested against constraint use, segment leakage, customer expectations, and the total move in T, I, and OE.

“Customer perceived value means ignore supplier economics.” It doesn’t. The cloud preserves both requirements. The customer-value side helps sell enough volume; the supplier-economics side protects the system’s ability to cover operating expense and investment. The solution changes the accounting assumption, not the need for profit.

“Segmentation is just charging different groups different prices.” Not in this context. The TOC requirement is isolation. A segment exists when the price and quantity offered there do not affect the price and quantity offered elsewhere. Without isolation, a segment price can cannibalize the main market.

“A Mafia Offer is a pricing tactic.” It isn’t. Price may be part of the offer, but the offer’s force comes from changed customer economics backed by a Decisive Competitive Edge. If the supplier can only change price, competitors can usually match the move faster than the supplier can build advantage.

“T/CU ranks prices.” It doesn’t. T/CU ranks products or orders against scarce constraint capacity after price has been chosen. The Marketing Core Conflict Cloud sits one step earlier: it asks which pricing basis is legitimate for the market segment being served.

Complements: Throughput-Accounting Decision Cases — Throughput-Accounting Decision Cases gives the broader price-floor and T-I-OE decision frame that the marketing cloud applies to market segments.

Contrasts with: Product Mix Decision Under Constraints — Product Mix Decision ranks demand by T/CU after a price exists; the Marketing Core Conflict Cloud asks what basis should set the price in the first place.

Depends on: Market Constraint — The pricing cloud is most useful when the market is the active constraint and the firm has to exploit demand without retreating into discounting.

Depends on: Throughput Accounting — The cloud's cost-side correction depends on Throughput Accounting: the price floor is truly variable cost, while operating expense is recovered at the system level.

Informed by: Decisive Competitive Edge (DCE) — The customer's perceived-value side is credible only when the supplier has a real DCE rather than a slogan or discount.

Informs: Mafia Offer (Unrefusable Offer) — A Mafia Offer can protect or raise price only when the offer changes customer value; the pricing cloud keeps that value-side logic explicit.

Specializes: Evaporating Cloud (Conflict Resolution Diagram) — The Marketing Core Conflict Cloud is a domain-specific Evaporating Cloud applied to pricing.

Uses: Assumption — Breaking the cloud depends on exposing the assumptions behind cost-based pricing, perceived-value pricing, and market segmentation.

Sources

• Cox, TOCICO Dictionary of Theory of Constraints Terms (2nd ed., 2012), entries “marketing core conflict cloud,” “throughput per constraint unit (T/CU),” “throughput accounting (TA),” “market constraint,” “unrefusable offer,” and “sales core conflict cloud.” The certification-grade vocabulary for the pricing cloud, the TVC floor, and the boundary between marketing, finance, and offer design. Distributed through TOCICO membership; no Open Library record.

• Lang, “Mafia Offers: Dealing with a Market Constraint,” in Cox and Schleier, Theory of Constraints Handbook (2010), Ch. 22. The main source for the market-constraint pricing context, the price-per-quantity curve in the label-printer example, segmentation by target market, and the claim that a strong offer rests on changed customer economics rather than a price cut.

• Budd, “Traditional Measures in Finance and Accounting, Problems, Literature Review, and TOC Measures,” in Cox and Schleier, Theory of Constraints Handbook (2010), Ch. 13. The source for the Throughput Accounting decision frame that separates TVC from allocated operating expense.

• Ricketts, “Theory of Constraints for Professional, Scientific, and Technical Services,” in Cox and Schleier, Theory of Constraints Handbook (2010), Ch. 29. The service-side source for applying T, I, and OE without a product-cost construct and for treating offers as customer-core-problem solutions rather than price concessions.