MWMS Value Based Pricing Framework

Document Type: Framework
Status: Structural
Version: v1.0
Authority: HeadOffice
Applies To: AIBS Brain, Ecommerce Brain, HeadOffice, future MWMS service offers
Parent: HeadOffice
Last Reviewed: 2026-04-12


Purpose

This framework defines how MWMS determines pricing for services based on business value rather than time spent.

It exists to prevent:

• underpricing expertise
• hourly pricing traps
• margin erosion
• weak commercial positioning
• inconsistent pricing logic
• client expectations misalignment
• commoditization of expertise

Value based pricing ensures that pricing reflects:

expected business impact
economic leverage
strategic importance
decision value
performance upside

rather than internal effort estimation.

This strengthens both positioning and profitability.


Scope

This framework applies to:

• AI service offers
• ecommerce optimization services
• experimentation strategy services
• consulting engagements
• diagnostic engagements
• advisory retainers
• performance-focused service models

It governs how MWMS determines price ranges for services.

It does not define:

service scope structure
client qualification criteria
contract language
invoice structure
payment schedules

Those are governed by:

MWMS Productized Service Design Framework
MWMS Service Offer Qualification Framework
MWMS Proposal Structure Framework
Finance Brain standards


Definition or Rules

Core Principle

Price reflects value created.

Not hours consumed.

Clients do not purchase time.

Clients purchase improvement.

Value based pricing aligns incentives:

MWMS is rewarded for meaningful business impact.

The source material strongly emphasizes avoiding hourly billing structures because they anchor pricing to effort rather than value.


Rule 1 — Anchor Price to Business Impact

Price should relate to the magnitude of the problem being solved.

Key impact dimensions:

revenue improvement potential
profit improvement potential
cost reduction potential
risk reduction
decision clarity
operational leverage

If the potential improvement is large, the price may justifiably be higher.

Low-impact projects should not be priced as premium services.

Pricing should reflect commercial upside rather than effort estimation.


Rule 2 — Larger Companies Support Higher Fees

Larger companies:

have more at stake
have higher upside potential
have larger inefficiencies
have larger opportunity surfaces
have larger budgets

Therefore pricing can reasonably scale with company size.

Indicators of higher pricing tolerance:

high revenue
high order volume
significant paid acquisition spend
large customer base
complex funnel structure

The course material highlights that companies with higher revenue and larger traffic volumes typically justify higher service pricing because the economic upside is larger.


Rule 3 — Avoid Hourly Pricing

Hourly pricing creates:

price sensitivity
comparison pressure
scope micromanagement
reduced perceived expertise value
pressure to justify time usage

Hourly pricing frames expertise as labor.

Value pricing frames expertise as strategic leverage.

The course strongly discourages hourly billing because it caps upside and weakens positioning.


Rule 4 — Retainers Provide Stability

Retainers create:

predictable revenue
predictable collaboration structure
sustained improvement opportunity
ongoing experimentation capacity
long-term relationship growth

Retainers are especially appropriate when:

continuous experimentation is required
optimization is ongoing
research is iterative
implementation cycles repeat

Structured retainers provide more stable commercial structure than one-off engagements.

The source material emphasizes retainers as a strong model for continuous optimization work.


Rule 5 — Revenue Share Models Require Caution

Revenue share models appear attractive but introduce risks:

measurement complexity
attribution disputes
dependency risk
revenue variability
legal complexity

Revenue share structures may distort incentives or introduce friction if performance measurement is unclear.

They should be used selectively and cautiously.

The course notes that revenue-share pricing can create complications and should not be the default structure.


Rule 6 — Pricing Communicates Positioning

Pricing signals expertise level.

Very low pricing communicates:

low confidence
commoditized capability
lack of specialization
low differentiation

Premium pricing communicates:

confidence
specialization
expertise
expected impact

Pricing influences perception of value.

The course material highlights the importance of pricing as a positioning mechanism rather than purely a financial decision.


Rule 7 — Align Pricing With Qualification

Pricing should reflect client qualification strength.

Stronger clients:

have stronger economic leverage
have stronger implementation capability
have higher expected ROI

Therefore stronger clients justify stronger pricing.

Weak-fit clients often produce pricing pressure and reduced margins.

Pricing discipline reinforces qualification discipline.

This logic aligns with the course emphasis on selecting clients who can realistically benefit from the work.


Rule 8 — Price Should Support Delivery Quality

Pricing must support:

time for research
time for analysis
time for iteration
time for communication
time for documentation

Underpricing forces rushed delivery.

Rushed delivery reduces performance impact.

Reduced impact weakens reputation and results.

Pricing must enable proper execution quality.

The source material highlights that sustainable pricing ensures ability to deliver high-quality work consistently.


Rule 9 — Avoid Custom Pricing Chaos

Pricing logic should follow consistent structure.

Avoid:

inventing new pricing logic for each client
pricing purely emotionally
heavy discounting pressure
inconsistent justification logic

Consistency increases clarity and confidence in pricing decisions.

The course encourages standardized pricing logic to improve scalability.


Practical Pricing Anchors

Pricing decisions should consider:

client scale
business impact potential
complexity of work
level of strategic importance
duration of engagement
expected ROI magnitude

Pricing should feel proportional to expected improvement.


Governance Role

This framework ensures:

pricing discipline across MWMS service offers
consistent commercial positioning
protection against underpricing
alignment between value and compensation
sustainable margin structure

HeadOffice maintains authority over pricing philosophy.

Finance Brain maintains authority over financial performance validation.


Relationship to Other MWMS Standards

This framework works alongside:

MWMS Service Offer Qualification Framework
MWMS Productized Service Design Framework
MWMS Proposal Structure Framework
MWMS Client Expectation Setting Protocol
MWMS CLV CAC and Payback Framework

Qualification determines client viability.

Productization determines scope structure.

Pricing determines commercial structure.

Together these frameworks form the MWMS service commercialization layer.


Drift Protection

The system must prevent:

defaulting to hourly billing
pricing based purely on effort estimation
pricing driven only by client pressure
discounting without strategic reason
pricing inconsistency across similar services
underpricing due to uncertainty
pricing disconnected from economic impact

Pricing drift weakens positioning and margin stability.


Architectural Intent

MWMS Value Based Pricing Framework ensures that pricing reflects the strategic and economic importance of the work performed.

It protects expertise from commoditization.

It aligns commercial reward with business impact.

It ensures MWMS services remain sustainable as the ecosystem expands.

Strong pricing discipline strengthens long-term positioning.


Change Log

Version: v1.0
Date: 2026-04-12
Author: HeadOffice
Change: Initial creation.


Change Impact Declaration

Pages Created:

MWMS Value Based Pricing Framework

Pages Updated:

none

Pages Deprecated:

none

Registries Requiring Update:

MWMS Architecture Registry
MWMS Document Registry

Canon Version Update Required:

No

Change Log Entry Required:

No