Document Type: Framework
Status: Active
Version: v1.1
Authority: HeadOffice
Applies To: Strategy Brain, Affiliate Brain, Ads Brain, Conversion Brain, Product Brain, Sales Brain, Content Brain
Parent: Strategy Brain
Last Reviewed: 2026-05-03
Purpose
The Strategy Brain Customer In Strategy Framework defines how MWMS builds all strategic direction starting from the customer rather than internal assumptions, preferences, or capabilities.
Most systems operate:
→ inside-out (internal-first)
MWMS must operate:
→ outside-in (customer-first)
This framework ensures strategy is driven by:
- customer problems
- customer priorities
- customer perception
- customer behaviour
Scope
This framework applies to:
- strategy development
- offer selection
- campaign planning
- messaging creation
- product development
- funnel optimisation
It governs how MWMS:
- gathers customer insight
- prioritises signals
- validates assumptions
- aligns strategy to real behaviour
Core Principle
The customer defines value.
If the system does not align with the customer:
→ strategy fails
Definition
Customer In Strategy
A strategic approach where all decisions are based on what is best for the customer rather than what is easiest, preferred, or assumed internally.
Customer Context Rule
Customers are not static.
Strategy must consider where the customer is in the journey:
- unaware
- problem aware
- solution aware
- ready to act
Without this:
→ strategy becomes generic and ineffective
Role Within MWMS
This framework supports:
- Strategy Brain direction
- Affiliate Brain offer selection
- Ads Brain targeting and messaging
- Conversion Brain optimisation
- Product Brain development
- Sales Brain positioning
It directly influences:
- offer success
- campaign performance
- conversion rate
- retention
- market relevance
Inside Out vs Customer In
Inside Out Strategy (Incorrect)
Starts with:
- product features
- internal capabilities
- team assumptions
- company priorities
Leads to:
- weak positioning
- irrelevant messaging
- low conversion
Customer In Strategy (Correct)
Starts with:
- customer problems
- customer desires
- customer behaviour
- market reality
Leads to:
- strong positioning
- relevant messaging
- higher conversion
Customer In Input Sources
Strategy must be built from:
- behavioural data
- customer research
- market signals
- competitor landscape
- purchase behaviour
- feedback loops
Signal Hierarchy Rule
Not all inputs are equal.
Priority order:
Behavioural Data → Purchase Behaviour → Market Signals → Feedback → Research
Rule:
Observed behaviour overrides stated opinion
Core Questions
Every strategy must answer:
- What problem does the customer actually care about?
- What is the customer trying to achieve?
- What is blocking the customer?
- What alternatives exist?
- Why would the customer switch?
- What does success look like for the customer?
If these are unclear:
→ strategy is invalid
Stated vs Real Behaviour Rule
Customers often:
- say one thing
- do another
Strategy must prioritise:
→ observed behaviour
Not:
→ claimed intent
Customer Reality Rule
Strategy must reflect real customer behaviour.
Not:
- assumed behaviour
- desired behaviour
- idealised behaviour
Reality overrides internal belief
Problem First Rule
Strategy must start with:
→ the problem
Not:
→ the solution
Solutions without clear problems fail
Value Perception Rule
Value is defined by the customer.
Not by:
- features
- internal effort
- product complexity
If the customer does not perceive value:
→ value does not exist
Alternative Awareness Rule
Customers always compare against alternatives:
- competitors
- doing nothing
- existing solutions
- manual work
Strategy must account for this
Switching Barrier Rule
Customers resist change.
Strategy must address:
- risk
- effort
- cost
- uncertainty
If switching friction is high:
→ conversion drops
Priority Alignment Rule
Strategy must align with:
→ current customer priorities
Not future priorities
If the problem is not urgent:
→ action will not occur
Customer Language Rule
Strategy must use language the customer understands.
Avoid:
- internal jargon
- technical complexity
- unclear messaging
Customer language improves clarity and trust
Customer Understanding Depth Model
Shallow Understanding
- assumptions
- generic personas
- surface insights
Moderate Understanding
- segmentation
- behavioural insights
- partial data
Deep Understanding
- real behaviour
- real decision triggers
- real objections
- real switching barriers
Rule
MWMS must aim for:
→ deep customer understanding
Segmentation Integration
Customer In Strategy must align with:
→ Customer Brain Segmentation And Personalization Framework
Different segments require:
- different problems
- different priorities
- different messaging
Three Why Integration
Customer In Strategy feeds:
- Why Buy Anything
- Why Buy Now
- Why Buy You
Without customer insight:
→ Three Why becomes weak
Feedback Loop Rule
Strategy must evolve based on:
- campaign results
- conversion data
- customer behaviour
- support interactions
Strategy is not static
Strategy Failure Detection Rule
Strategy is failing if:
- low conversion despite traffic
- high bounce rates
- poor engagement
- high drop-off
- low switching behaviour
- poor campaign performance
Action
→ re-evaluate customer understanding
Testing Rule
Customer assumptions must be tested.
Examples:
- problem importance
- messaging relevance
- offer attractiveness
- switching motivation
Results must be recorded in:
→ Experimentation Brain systems
Cross Brain Integration
Strategy Brain
→ defines direction
Customer Brain
→ provides segmentation and behaviour
Data Brain
→ provides signals
Affiliate Brain
→ selects offers
Ads Brain
→ applies messaging
Conversion Brain
→ optimises experience
Product Brain
→ aligns solution
Sales Brain
→ executes persuasion
Experimentation Brain
→ validates strategy
HeadOffice
→ governs strategic integrity
Failure Modes Prevented
- internal bias
- irrelevant offers
- weak messaging
- poor conversion
- market disconnect
- wasted budget
- shallow customer understanding
Drift Protection
The system must prevent:
- strategy based on internal preference
- ignoring behavioural data
- relying on stated opinions
- solution-first thinking
- outdated assumptions
- lack of testing
- ignoring feedback loops
Architectural Intent
This framework ensures MWMS builds strategy based on:
→ customer reality
rather than:
→ internal assumption
It keeps the system aligned with the market at all times
Final Rule
If the strategy does not start with the customer:
→ it will not succeed
Change Log
Version: v1.1
Date: 2026-05-03
Author: HeadOffice
Change:
Enhanced Customer In Strategy Framework with customer journey context, signal hierarchy, stated vs real behaviour rule, understanding depth model, and strategy failure detection logic based on CXL principles.
Change Impact Declaration
Pages Created:
None
Pages Updated:
Strategy Brain Customer In Strategy Framework
Pages Deprecated:
None
Registries Requiring Update:
Strategy Brain Page Registry
Canon Version Update Required:
No
Change Log Entry Required:
Yes