A pricing improvement that has evaporated 18 months later is not an improvement. It is an expensive reminder that you asked the wrong question.

Pricing initiatives in industrial B2B follow a recognizable pattern. External consultants, internal task forces, software implementations, value-pricing workshops. The first twelve months show a margin lift of 1 to 3 percentage points. The next twelve months see that lift recede to zero. And after three years, the organization sits exactly where it started — with an expensive lesson and little to show for it.

The problem is not in the analyses. They are usually correct. The problem is in the framing: pricing is treated as a project. With a start, an end, a final report, and a celebration. But pricing is not a project. Pricing is a discipline — an ongoing organizational practice, like financial planning or operational excellence.

This article explains why that distinction is fundamental, and how the Pricetainability™ framework makes the shift from project thinking to disciplinary thinking.

Key takeaways

• Pricing projects evaporate within 18 to 24 months because they do not change organizational cadence — they only temporarily override it.
• Pricing as a discipline requires four ongoing layers: Truth (facts), Policy (rules), Execution (implementation), Governance (review).
• The sequence is not negotiable. Starting at Execution (software) without Truth (diagnostic) automates your existing leakage.
• Sustainable margin does not result from a one-off correction. It results from a rhythm the organization sustains on its own.
• Pricetainability™ is the framework that operationalizes that rhythm in industrial B2B — for both mid-market and SME.

Why pricing projects fail

Pricing projects do not fail because of weak analyses. They fail because of a wrong organizational assumption: that a one-off correction is sustainable in a system that does not address the causes.

Three patterns shared by every failing pricing initiative:

1. The analysis is correct, but the organization has not changed. An external consultancy delivers an 80-page report. The CEO nods. Sales reorganizes briefly. Twelve months later, the discount policy has reverted to a list of exceptions. Not because sales ignores the report — because the report left no rhythm behind.

2. The software is installed, but the discipline is not embedded. This is the variant with pricing software (Vendavo, PROS, Pricefx). The tool works. Adoption is low. When 30% of deals run through the tool and 70% run via "the way we always do it," you do not have a pricing system — you have a dashboard.

3. The pricing manager is hired, but their mandate is unclear. Many businesses hire a pricing manager in response to a crisis. The manager starts with energy. After a year, it is clear: they report to commerce while finance controls the tools and operations determines cost-to-serve. They have responsibility without leverage. They leave.

"Pricing is the only discipline where we accept that an improvement evaporates within two years. Imagine treating cybersecurity that way — a one-off audit, a report, and no follow-up review. We would call it madness. With pricing, we have done it for years."

The common factor: a project has an end. A discipline has a rhythm. Margin you recover without rhythm, you will lose again.

The four layers of pricing discipline

The Pricetainability™ framework defines pricing as a four-layer system that runs continuously:

Layer 1 — Truth (facts) What is actually true about our pricing? Not what we think is true, but what the data shows. Pocket price waterfall, customer profitability, discount distribution, gross-to-net erosion. This is not reporting — this is diagnosis. And diagnosis repeats every quarter or half-year, not just once.

Layer 2 — Policy (rules) What rules turn the facts into behavior? Discount mandates, discount structure, customer segmentation, indexation clauses, minimum viable margin. Policy must align with the facts — policy built on assumption undermines the entire cycle.

Layer 3 — Execution (implementation) How does policy become visible in daily operations? Quoting tools, CPQ systems, ERP configuration, sales incentives, contract templates. This is where tools play a role — but not for strategy. Tools serve the discipline; they do not replace it.

Layer 4 — Governance (review) How do we ensure the first three layers keep working? Periodic reviews where Truth is re-verified, Policy is adjusted where needed, and Execution issues are resolved. Without governance, the cycle decays within 18 months.

The four layers do not work sequentially — they work simultaneously. But they have a starting sequence, and that sequence is absolute.

Why the sequence is absolute

The sequencing principle is non-negotiable: diagnosis before design, design before execution, execution before governance.

Truth → Policy → Execution → Governance.

It sounds obvious. It is reversed in practice everywhere. Three common mistakes:

Mistake 1 — Starting at Execution: "We need pricing software." This is the most common error. An organization experiences margin erosion and jumps to a software selection. But without Truth, you do not know which problem you are solving. Without Policy, you do not know what the software should enforce. The result: a tool that automates your existing leakage, only faster and with more dashboards.

Mistake 2 — Starting at Policy: "We need a new discount policy." An external consultant or new pricing manager writes a policy. The document is logical. It does not match the actual patterns in your customer base, because no one mapped those patterns first. Result: a policy that is correct on paper and ignored in practice.

Mistake 3 — Starting at Governance: "We are setting up a pricing committee." Sounds sophisticated. Does not work. A review cycle without underlying Truth and Policy is a meeting of opinions. After three sessions, the participants ask why they are wasting time.

"The sequence is not a methodological preference. It is a logical necessity. You cannot make policy on facts you do not know. You cannot automate execution on policy that does not exist. You cannot install governance on execution that does not work."

No software implementation or policy redesign before the Truth phase. That is not a marketing position. It is the practical condition for sustainability.

Pricetainability™ in practice

What does pricing as a discipline concretely look like for an industrial mid-market business of €50 million revenue?

Truth — twice a year A diagnostic cycle that rebuilds the pocket price waterfall on the most recent twelve months of data. Whale curve update. Analysis of discount distribution. Gross-to-net erosion tracking. Output: a 15-page diagnostic deck that the leadership team can use directly.

Policy — annually reviewed The discount policy is reviewed at least once a year based on the Truth cycle. Discount mandates by role, segment definitions, indexation clauses in standard contracts, minimum viable margin per segment. Policy is owned by an internal pricing owner (CFO, commercial director, or dedicated pricing manager).

Execution — continuous CRM flows that show margin data before a quote goes out. ERP configuration that allocates rebates correctly to transactions. Contract templates that include indexation by default. Sales incentives that weigh net revenue, not just gross.

Governance — quarterly A margin governance review per quarter: pocket price status, discount exceptions, exception tracking, progress on improvement zones. Not a new meeting — preferably a fixed component of the existing commercial review.

This is not a project. This is an operating model. And that is exactly the difference between pricing as an optimization topic and pricing as a sustainable discipline.

When have you become a discipline rather than a project?

Five checks that identify mature pricing discipline:

1. For every new deal above €X, margin data is available before the quote goes out — not after.

2. Someone in your organization can show last quarter's pocket price waterfall, without ad hoc analysis.

3. Discount exceptions are not just approved; they are measured afterward on actual outcome and the learnings flow back into policy.

4. Your sales team can name not just gross but also net per customer for their top-10 accounts.

5. Pricing is a structural item on the leadership team agenda — at least quarterly, not only when there is a crisis.

Anyone who can say "yes" to all five has pricing as a discipline. Anyone who must say "no" to three or more still has pricing as a project — or none at all.

Bottom line

Pricing projects are not pointless. They are not sufficient. A good diagnostic, strong policy, and solid execution are all needed — but without governance, the effect evaporates within two years.

Pricetainability™ is not a marketing name. It is a working principle: pricing as ongoing organizational system, not as incidental correction. For mid-market and SME, this is within reach — not through large investments, but through discipline and the right cadence.

The question is not whether you can run a pricing project. The question is: can you sustain the effect? That distinction determines whether the margin you recover is still on your P&L three years from now.