System: MWMS
Document Type: Standard
Authority Level: MCR Source Of Truth
Status: Draft For MCR
Primary Location: MCR
Future Operational Destination: AI Business Systems Brain, Offer Brain, Content Brain, Sales Brain, Conversion Brain, Creative Brain, Customer Brain, Research Brain, Affiliate Brain, Future AIBS Client Systems
Parent Page: Offer Brain
Owner: Martyn
Developer Boundary: No Development Action Authorized By This Page
Source Of Truth: MCR
Purpose
The purpose of this document is to define the MWMS Right-Fit Client And Offer Profile Standard.
This standard establishes how MWMS captures, structures, governs, reviews, and applies the two core context files that sit at the centre of any offer-specific or client-specific AI system:
Right-Fit Client Profile
Offer Profile
MWMS must not allow AI Employees to create business assets for a vague audience or unclear offer.
Most generic AI output starts with one of two problems:
the buyer is unclear
the offer is unclear
If MWMS does not define who the offer is for and what the offer actually does, AI outputs will drift into generic marketing language, weak positioning, broad content, shallow ads, unclear funnels, and poor sales assets.
This standard exists to ensure every serious MWMS offer, client system, affiliate campaign, AI Business System package, lead magnet, webinar, sales asset, content plan, or ad campaign is grounded in:
the right buyer
the right problem
the right offer
the right transformation
the right promise
the right objections
the right proof
the right next step
The Right-Fit Client And Offer Profile Standard creates the buyer-offer foundation for context-driven AI work.
Scope
This standard applies to all MWMS work where AI creates, evaluates, reviews, or supports offer-specific business output.
This includes:
AI Business Systems Brain
Offer Brain
Content Brain
Sales Brain
Conversion Brain
Creative Brain
Customer Brain
Research Brain
Affiliate Brain
Ads Brain
HeadOffice Brain
AI Manager
AI Employee Router
future AIBS client systems
This standard applies before creating:
offer context libraries
client context libraries
lead magnets
webinars
landing pages
sales pages
email sequences
content plans
VEO3 scripts
ad angles
sales scripts
client reports
affiliate offer pages
AI Employee workflows
AIBS client packages
This standard does not authorize development work, plugin changes, Supabase changes, WordPress changes, automation wiring, publishing, client implementation, or M developer action.
Core Definition
A Right-Fit Client Profile defines the specific buyer, client, customer, user, audience, or market segment the offer is designed to serve.
An Offer Profile defines the product, service, system, package, transformation, delivery model, promise, mechanism, and next step being offered to that buyer.
Together, these two files answer:
Who is this for?
What are they dealing with?
What do they want?
What do they believe?
What are they afraid of?
What do they need to understand?
What does the offer do?
What does the offer not do?
How does the offer create transformation?
Why is the offer different?
What proof supports it?
What should the buyer do next?
Core Principle
The core principle of this standard is:
No serious MWMS output should be created until the buyer and offer are clear.
AI cannot write useful copy, content, ads, sales scripts, funnels, or client reports if the buyer and offer are vague.
The Right-Fit Client Profile gives AI the buyer reality.
The Offer Profile gives AI the offer truth.
Together, they create the minimum viable foundation for business-relevant AI output.
Right-Fit Client Profile
Purpose
The Right-Fit Client Profile defines the specific person, business, buyer, or audience segment the offer is meant to serve.
It prevents MWMS from writing for “everyone.”
The profile should make clear:
who the buyer is
what situation they are in
what problem they are aware of
what problem they may not yet understand
what outcome they want
what objections they have
what language they use
what makes them a good fit
what makes someone a bad fit
This file should be specific enough that AI Employees can create relevant messaging without inventing buyer reality.
Right-Fit Client Profile Fields
The profile should include the following fields where relevant.
Buyer Name Or Segment
Defines the buyer category.
Examples:
AI-curious business owner
affiliate marketer testing paid traffic
coach needing client content systems
agency owner needing operational reporting
service provider needing repeatable AI workflows
Current Situation
Defines where the buyer is now.
Examples:
overwhelmed by AI tools
getting generic AI output
struggling to create consistent content
running ads without strong creative strategy
trying to build systems without clear context
Current Problem
Defines the problem the buyer knows they have.
Examples:
AI content sounds generic
ads are not converting
content ideas are inconsistent
business knowledge is trapped in the founder’s head
client systems are messy
Hidden Problem
Defines the deeper problem the buyer may not yet understand.
Examples:
they do not have a context library
they are trying to fix strategy with prompts
they are building assets before offer clarity
they are missing buyer language
they are using tools before process
Desired Outcome
Defines what the buyer wants.
Examples:
better AI output
more consistent content
clearer sales assets
less repeated explanation
more useful client systems
more leads
more sales
less operational chaos
Emotional State
Defines what the buyer feels.
Examples:
frustrated
overwhelmed
skeptical
curious
burned by tools
excited but confused
ready to systemize
tired of random outputs
Practical Constraints
Defines real-world limits.
Examples:
low budget
small team
limited time
messy files
weak documentation
unclear offer
no technical skill
platform restrictions
compliance concerns
Buying Trigger
Defines what makes the buyer act now.
Examples:
AI output is wasting time
team needs repeatable process
launch is approaching
content is inconsistent
ads need better hooks
business owner wants to stop repeating themselves
client wants scalable systems
False Beliefs
Defines what the buyer currently believes that may block progress.
Examples:
better prompts will fix everything
one AI tool will solve the problem
content volume matters more than context
automation should come before process
AI should know the business automatically
Trust Barriers
Defines what makes the buyer hesitate.
Examples:
does this really work?
will it sound like me?
is this too technical?
will this be expensive?
will AI make mistakes?
will this create more work?
is this just another tool?
Decision Criteria
Defines what the buyer needs before saying yes.
Examples:
clear process
proof of usefulness
low complexity
human review
specific examples
risk reduction
realistic implementation path
Who This Is Not For
Defines poor-fit buyers.
Examples:
people wanting instant automation without clarity
people unwilling to review outputs
people with no offer direction
people expecting AI to replace all judgment
people unwilling to provide source material
Buyer Language
Captures real phrases or likely phrases the buyer uses.
Examples:
AI sounds too generic
I keep explaining the same thing
I do not know what to give the AI
we have too many tools and no system
I need this to sound like us
I want this to save time, not create more work
Right-Fit Client Profile Rules
Rule 1: Be Specific
The buyer should not be described as “business owners” unless the offer truly serves all business owners.
Rule 2: Separate Known Buyer From Assumed Buyer
If buyer information is based on evidence, mark it as known.
If buyer information is inferred, mark it as assumption.
Rule 3: Include Bad-Fit Buyers
Knowing who the offer is not for helps prevent weak leads and wrong messaging.
Rule 4: Preserve Buyer Language
Use real buyer wording where available.
Rule 5: Do Not Invent Customer Evidence
If no buyer language is available, mark it as missing rather than fabricating it.
Rule 6: Update After Research
Buyer profiles should update after new sales calls, surveys, support messages, campaign data, or client feedback.
Offer Profile
Purpose
The Offer Profile defines what the offer is, what it does, who it serves, how it works, what it includes, what it promises, what proof supports it, and what next step the buyer should take.
It prevents MWMS from misrepresenting or oversimplifying the offer.
The Offer Profile is one of the most important files in the Offer Context Library.
Offer Profile Fields
The profile should include the following fields where relevant.
Offer Name
Defines the name of the offer.
Offer Type
Examples:
course
service
consulting package
AI Business System
affiliate offer
software
membership
audit
done-with-you package
done-for-you package
lead magnet
webinar
client report
Primary Buyer
Links to the Right-Fit Client Profile.
Core Problem Solved
Defines the main problem the offer addresses.
Main Promise
Defines the promise the offer can safely make.
The promise must be accurate and not exaggerated.
Core Transformation
Defines the before-and-after change.
Examples:
from scattered AI prompts to structured context library
from generic content to buyer-grounded content system
from unclear offer to structured offer context
from repeated manual explanation to reusable AI Employee context
Offer Mechanism
Defines how the offer works.
Examples:
context library build
IP excavation
workflow mapping
skill creation
AI Employee setup
lead magnet funnel
buyer-intent landing page system
Delivery Model
Defines how the offer is delivered.
Examples:
self-paced
done-for-you
done-with-you
consulting
template
workshop
software-assisted
AI-assisted
manual process
Included Components
Lists what is included.
Examples:
intake session
context library
voice file
offer profile
content plan
lead magnet
webinar outline
AI skill
audit checklist
Not Included
Defines what the offer does not include.
Examples:
no live technical development
no guaranteed income
no platform management
no legal advice
no full automation unless separately scoped
no client implementation without review
Ideal Use Case
Defines when the offer is most useful.
Poor Fit Use Case
Defines when the offer should not be used.
Proof Available
Defines approved proof.
Examples:
case studies
testimonials
examples
internal builds
process demonstration
performance data
client feedback
Proof Limits
Defines what proof cannot be claimed.
Examples:
no income guarantee
no universal results claim
no unverified testimonials
no unapproved vendor claims
Objections
Summarizes main objections.
Examples:
too complex
too expensive
not enough source material
will AI sound generic?
will this work in my niche?
how long will it take?
Risk Notes
Defines risk areas.
Examples:
compliance-sensitive claims
paid traffic restrictions
affiliate claim limits
client data privacy
technical implementation risk
Next Step
Defines the action the buyer should take.
Examples:
watch VSL
book call
download guide
complete assessment
start intake
join waitlist
view offer page
Offer Profile Rules
Rule 1: The Offer Profile Must Preserve Offer Truth
AI must not change the offer promise, inclusions, limitations, or delivery model.
Rule 2: Promise Must Be Safe
The offer promise must not become exaggerated for marketing effect.
Rule 3: Proof Must Be Approved
AI must use only approved proof.
Rule 4: Limits Must Be Clear
What the offer does not include should be stated clearly where relevant.
Rule 5: Offer Must Link To A Buyer
An offer without a buyer profile is incomplete.
Rule 6: Offer Profile Must Update When Offer Changes
If the offer changes, the Offer Profile must be updated before new outputs are created.
Buyer-Offer Fit
The Right-Fit Client Profile and Offer Profile must work together.
Buyer-offer fit asks:
Does this buyer have the problem the offer solves?
Does the offer create the transformation this buyer wants?
Does the buyer believe the problem matters?
Does the buyer trust this kind of solution?
Does the offer match the buyer’s sophistication level?
Does the offer match the buyer’s budget, urgency, and readiness?
Does the offer create a logical next step?
If buyer-offer fit is weak, do not force the asset.
Revise the buyer, offer, or strategy.
Buyer-Offer Fit Checks
Problem Fit
The buyer’s problem should match the offer’s core problem.
Outcome Fit
The buyer’s desired outcome should match the offer transformation.
Readiness Fit
The buyer should be ready for the next step the offer requires.
Belief Fit
The buyer should be able to accept the offer mechanism after the correct belief shift.
Proof Fit
The proof should support what the buyer needs to trust.
Language Fit
The offer should use language the buyer understands.
Constraint Fit
The offer should respect buyer constraints such as budget, time, complexity, and risk.
Usage Rules For AI Employees
AI Employees must use the Right-Fit Client Profile and Offer Profile before creating:
content plans
ad scripts
VEO3 scripts
lead magnets
webinars
landing pages
sales pages
emails
sales scripts
client reports
offer evaluations
affiliate bridge pages
AI Business Systems client assets
AI Employees must not rely on vague audience descriptions.
AI Employees must not invent offer details.
AI Employees must not assume buyer motivations without source.
AI Employees must flag missing buyer or offer context before producing high-value outputs.
Minimum Viable Buyer-Offer Profile
For early-stage work, MWMS may use a minimum viable version.
Minimum Right-Fit Client Profile:
buyer segment
current problem
desired outcome
main objection
buyer language
who this is not for
Minimum Offer Profile:
offer name
offer type
core problem solved
main promise
core transformation
included components
proof available
next step
Minimum profiles are acceptable for draft work.
They are not enough for:
client deployment
paid traffic
public-facing sales assets
automation
MCR canon promotion
Full Buyer-Offer Profile Requirement
Full profiles are required for:
client-facing systems
paid ad campaigns
affiliate offer pages
sales pages
evergreen webinars
major lead magnets
AIBS package builds
AI Employee workflows
public-facing campaign assets
high-risk compliance-sensitive offers
Profile Review Workflow
MWMS uses the following review workflow.
Step 1: Gather Source Material
Use sales pages, client notes, calls, customer language, support messages, testimonials, offer docs, and existing content.
Step 2: Draft Profiles
Create draft Right-Fit Client Profile and Offer Profile.
Step 3: Mark Missing Evidence
Flag missing buyer language, proof, offer details, or unclear promises.
Step 4: Review With Human Operator
Martyn, the founder, or the client reviews the profiles.
Step 5: Correct And Approve
Update unclear areas.
Step 6: Activate For Use
Once approved, profiles become active context files.
Step 7: Audit Over Time
Update when buyer, offer, proof, or positioning changes.
Profile Update Triggers
Update profiles when:
offer changes
price changes
new buyer segment appears
old buyer segment no longer fits
new objections appear
new proof appears
delivery model changes
campaign data reveals mismatch
sales calls reveal different objections
customer language changes
compliance rules change
client changes positioning
AI output repeatedly targets wrong buyer
Profile Quality Standards
Strong profiles are:
specific
current
source-grounded
buyer-aware
offer-accurate
clear about limitations
usable by AI Employees
reviewed by human operator
Weak profiles are:
generic
unsupported
too broad
filled with assumptions
missing buyer language
missing offer limits
missing proof boundaries
unclear about who is not a fit
outdated
Common Failure Modes
MWMS must prevent:
writing for vague audiences
changing the offer promise
inventing buyer pain
inventing proof
ignoring bad-fit buyers
using old offer details
using unsupported claims
mixing multiple offers
mixing multiple buyer segments
creating content before buyer-offer fit is clear
using generic customer avatars
assuming one buyer fits all assets
Governance Role
Offer Brain owns the MWMS Right-Fit Client And Offer Profile Standard.
HeadOffice governs cross-Brain alignment and source-of-truth discipline.
Content Brain uses the profiles for content planning.
Creative Brain uses the profiles for creative angles and VEO3 scripts.
Sales Brain uses the profiles for sales assets.
Conversion Brain uses the profiles for landing pages and funnel flow.
Customer Brain supports buyer reality and customer language.
Research Brain supports market and VOC evidence.
Affiliate Brain governs affiliate offer adaptation.
AI Business Systems Brain governs future client-system application.
Relationship To Other MWMS Standards
This standard supports and must align with:
MWMS Document Structure Standard
MWMS Client IP Excavation Framework
MWMS Offer Context Library Standard
MWMS Context Library Governance And Folder Map Standard
MWMS AI Context Activation And Usage Protocol
MWMS AI Context Pack Template Standard
MWMS Context-Driven Asset Builder Framework
MWMS Context-Grounded Lead Magnet Funnel Framework
MWMS Context-Grounded Evergreen Webinar Framework
MWMS Voice Architecture And Brand Language Standard
MWMS Content Intelligence Scanner Framework
MWMS AI Brain Readiness Review Checklist
MWMS AI Brain Audit And Decay Prevention Framework
Content Brain VOC Grounded AI Copy Framework
Research Brain Voice Of Customer Extraction Framework
Offer Brain Offer Structure Framework
Sales Brain Objection Resolution Framework
Conversion Brain Landing Page Structure Framework
Creative Brain Belief Shift Framework
Compliance Brain Claims Risk Framework
AI Business Systems Brain Canon
This standard defines the buyer-offer foundation that many MWMS asset and context systems depend on.
Drift Protection
This standard protects MWMS from:
vague audience targeting
generic offer messaging
wrong buyer assumptions
wrong offer promise
unsupported claims
AI-invented buyer language
AI-invented offer details
bad-fit buyers entering funnels
content disconnected from offer
ads disconnected from buyer readiness
client systems built around unclear offers
Any major output created without a clear Right-Fit Client Profile and Offer Profile should be treated as a buyer-offer drift risk.
Architectural Intent
The architectural intent of the MWMS Right-Fit Client And Offer Profile Standard is to create a stable buyer-offer foundation for AI-driven business output.
MWMS cannot build strong content, ads, funnels, sales systems, or client Brains without knowing who the offer is for and what the offer truly does.
The long-term goal is that every serious MWMS or client offer can answer:
Who is this for?
What are they dealing with?
What do they want?
What do they believe?
What do they resist?
What does the offer do?
What does it not do?
How does it create transformation?
What proof supports it?
What next step makes sense?
When MWMS can answer these questions consistently, AI output becomes more specific, more accurate, more persuasive, and safer to scale.
Change Log
v1.0 — Initial Draft
Created the MWMS Right-Fit Client And Offer Profile Standard as the buyer-offer foundation standard for MWMS context libraries, offer systems, content systems, sales systems, creative systems, affiliate systems, and future AIBS client systems.
This standard defines the Right-Fit Client Profile, Offer Profile, buyer-offer fit, profile fields, usage rules, minimum viable profiles, full profile requirements, review workflow, update triggers, quality standards, failure modes, governance role, drift protection, and architectural intent.
Change Impact Declaration
Pages Created:
MWMS Right-Fit Client And Offer Profile Standard
Pages Updated:
None
Pages Deprecated:
None
Registries Requiring Update:
MWMS Architecture Registry
Offer Brain Page Registry
Content Brain Page Registry
Sales Brain Page Registry
Creative Brain Page Registry
Conversion Brain Page Registry
AI Business Systems Brain Page Registry
Affiliate Brain Page Registry
Canon Version Update Required:
No
Change Log Entry Required:
Yes
Employee Impact Check
Employees impacted:
Offer Strategist Employee
Content Planner Employee
Creative Strategist Employee
Sales Strategist Employee
Conversion Strategist Employee
Customer Research Employee
Affiliate Offer Evaluator Employee
Context Library Builder
Client IP Excavator
AI Business Systems Architect Employee
Required behaviour updates:
AI Employees must use a clear Right-Fit Client Profile and Offer Profile before producing high-value offer, content, sales, creative, conversion, affiliate, or client-facing outputs.
AI Employees must not create major business assets for vague buyers or unclear offers.
AI Employees must not invent buyer language, buyer pain, offer details, proof, claims, pricing, inclusions, exclusions, or next steps.
AI Employees must flag missing buyer-offer context before producing public-facing, client-facing, paid traffic, or high-risk outputs.
AI Employees must update or request review of buyer-offer profiles when offer details, buyer segments, proof, objections, positioning, or compliance constraints change.
END MWMS RIGHT-FIT CLIENT AND OFFER PROFILE STANDARD v1.0