Document Type: Specification
Status: Strategic
Version: v1.2
Authority: Research Brain
Applies To: Customer insight extraction, customer-language analysis, objection mapping, and future persuasion-intelligence support
Parent: Research Brain Architecture
Last Reviewed: 2026-03-15
Purpose
The Customer Insight Engine defines the future system responsible for extracting structured intelligence from customer experiences.
This system converts customer signals into usable persuasion intelligence for MWMS.
Potential source inputs include:
• customer surveys
• customer interviews
• testimonials
• case studies
• third-party reviews
• community discussions
• support interactions
The goal is to convert raw customer feedback into structured strategic insight.
Scope
This specification applies to:
• future customer insight extraction systems
• structured capture of customer language and experience signals
• classification of problem, outcome, objection, and transformation insights
• support for future messaging, positioning, and persuasion systems
• manual-first customer insight collection before automation maturity
This document defines the intended structure and role of the Customer Insight Engine.
It does not govern:
• live ad creation
• direct copy generation
• campaign execution
• automated persuasion output
• capital allocation decisions
• final creative approval
Those remain governed by other MWMS systems even when they later consume insight outputs from this engine.
Definition / Rules
Strategic Role
The Customer Insight Engine operates as a cross-brain intelligence source.
It supports multiple MWMS systems including:
• Affiliate Brain
• Product Intelligence Systems
• Creative and Copy Systems
• Sales Systems
• future AI persuasion systems
The engine focuses on extracting:
• customer language
• problem awareness
• desired outcomes
• objections
• transformation narratives
These insights improve messaging accuracy and persuasion depth.
Core Insight Categories
Customer insights are categorised into the following intelligence groups.
Problem Signals
Problem signals are statements describing the problem customers experienced prior to purchasing a solution.
Examples include:
• pain points
• frustrations
• trigger events
• situational context
These signals help identify market demand and hook opportunities.
Outcome Signals
Outcome signals are statements describing the outcomes customers value most.
Examples include:
• benefits achieved
• emotional improvements
• time or cost savings
• lifestyle improvements
These signals help identify high-value marketing angles.
Language Signals
Language signals are the exact words customers use to describe their experiences.
These phrases provide valuable messaging assets for:
• ad hooks
• landing pages
• video scripts
• email marketing
Objection Signals
Objection signals are statements revealing hesitation or concerns before purchasing.
Examples include:
• price concerns
• skepticism
• fear of failure
• comparisons with alternatives
Understanding objections allows messaging systems to pre-empt resistance.
Transformation Signals
Transformation signals are customer stories describing the journey from problem to solution.
These narratives provide powerful storytelling frameworks for:
• case studies
• customer testimonials
• video advertising
• sales narratives
Data Sources
Customer insight data may be collected from:
• customer surveys
• customer interviews
• product reviews
• YouTube comments
• Reddit threads
• forum discussions
• support tickets
• community groups
Data collection methods may evolve over time.
Output Uses
Insights generated by this engine may be used for:
• ad creative development
• hook testing
• landing page messaging
• product positioning
• customer journey mapping
• case study creation
• testimonial development
Outputs are advisory signals only and do not trigger execution directly.
Execution Status
This system is currently defined as a strategic future system.
No automation is currently implemented.
Initial usage will be manual insight collection during research activities.
Automation may be introduced later once the MWMS research infrastructure matures.
Strategic Notes
Customer insight extraction significantly improves marketing effectiveness.
The most effective messaging often originates from the language customers use to describe their problems and outcomes.
The Customer Insight Engine exists to ensure this intelligence is captured and structured within the MWMS ecosystem.
Final Rule
Customer insight must be captured as structured intelligence, not left as scattered commentary.
Research value is lost when customer language, objections, and transformation signals are observed but not organised into reusable form.
Drift Protection
The system must prevent:
• treating raw customer commentary as finished marketing copy
• using unstructured feedback without categorisation
• confusing advisory insight output with execution authority
• automating persuasion output before research infrastructure maturity
• losing exact customer language through over-summarisation
Customer insight must remain structured, evidence-linked, and reusable.
Architectural Intent
The Customer Insight Engine exists to give MWMS a future-ready system for converting real customer experience signals into structured intelligence.
It creates the foundation for stronger positioning, better persuasion alignment, and more evidence-based messaging across multiple Brains without collapsing research into direct execution.
Change Log
Version: v1.2
Date: 2026-03-15
Author: MWMS HeadOffice / Research Brain
Change: Standardised the page fully to the locked cleanup format for this pass. Preserved the original future-system role, source inputs, core insight categories, data sources, output uses, execution-status logic, and advisory-output boundaries. Added a dedicated Final Rule section and updated the review date.
Version: v1.1
Date: 2026-03-14
Author: MWMS HeadOffice / Research Brain
Change: Rebuilt page to align with MWMS document standards. Added standardised document header, introduced Purpose / Scope / Definition / Rules structure, normalised section formatting, clarified future-system role and advisory output limits, and preserved the original customer insight engine concept and intelligence categories.
Version: v1.0
Date: 2026-03-05
Author: Research Brain
Change: Initial creation of Customer Insight Engine defining the future system for extracting structured intelligence from customer experiences and converting it into usable persuasion insight for MWMS.
END – CUSTOMER INSIGHT ENGINE v1.2