MWMS AI Audit Diagnostic And Paid Roadmap Framework

System: MWMS
Document Type: Operating Framework
Authority Level: MCR Source Of Truth
Status: Draft For MCR
Version: v1.0
Primary Location: MCR
Future Operational Destination: AIBS Brain, HeadOffice Brain, Sales Brain, Research Brain, Experimentation Brain, Finance Brain, Content Brain, Risk Brain, Compliance Brain, Data Brain, Operations Brain
Parent Page: AIBS Brain
Owner: Martyn
Developer Boundary: Do Not Touch M’s Active Build Areas Unless Specifically Assigned
Source Of Truth: MCR
Last Reviewed: 2026-06-03
Source / Origin: AI Automations by Jack — AI Audit Starter Pack / When To Pivot / Lessons From Alex Hormozi / Lessons From Alex Hormozi #2
MWMS Classification: AIBS Commercial Entry Offer Framework / Paid Diagnostic Framework / AIOS Roadmap Sales Bridge / Client Opportunity Assessment System
Primary Brain: AIBS Brain
Supporting Brains: HeadOffice Brain, Sales Brain, Research Brain, Experimentation Brain, Finance Brain, Content Brain, Risk Brain, Compliance Brain, Data Brain, Operations Brain, Automation Brain
Related Pages: MWMS Commercial Constraint And Client Acquisition Operating Framework, MWMS Offer And Niche Selection Framework, MWMS Avatar Hypothesis And Market Definition Framework, MWMS Plus Drift Control And Human Challenge Protocol, MWMS Client Intelligence Report Automation Framework, MWMS Lead Intake Qualification And Follow-Up Automation Framework, MWMS Outbound Lead Enrichment And Cold Outreach Governance Framework, MWMS AI Tool Permission And Access Framework, MWMS AI Automation Security And Risk Checklist, AIBS Brain Canon, Research Brain Canon, Experimentation Brain Canon, HeadOffice Kaizen Continuous Improvement Loop

Source Evidence: This framework is derived primarily from the AI Audit Starter Pack, which positions the AI audit as a paid opportunity assessment that can lead into larger transformation projects and recurring revenue. It also draws supporting principles from the pivoting and Hormozi lessons around focus, value-first acquisition, simple funnels, proof-led selling, direct conversations, feature deletion, and retention value.

Purpose

The purpose of the MWMS AI Audit Diagnostic And Paid Roadmap Framework is to define how MWMS uses a paid AI audit as a low-risk diagnostic entry offer that identifies client business opportunities, quantifies cost of inaction, prioritises AI system improvements, and creates a logical bridge into larger AI Business Systems projects.

This framework exists because AIBS Brain should not try to sell large AIOS builds before understanding the client’s business, workflows, data, constraints, tools, goals, bottlenecks, and commercial opportunity.

A business owner often does not know what AI system they actually need.

They may think they need:

a chatbot
a CRM automation
a content system
a lead follow-up system
a support bot
a proposal generator
an AI agent
an internal knowledge assistant
an AI receptionist
a reporting dashboard
a full AIOS

But the business may actually need something different.

The audit protects MWMS from guessing.

The audit protects the client from buying the wrong solution.

The audit gives MWMS a paid way to learn the business, diagnose the real opportunity, create trust, and sell the correct transformation project.

The core purpose is:

Use the paid AI audit to move from vague AI interest to quantified business opportunity, prioritised roadmap, and paid implementation pathway.

Core Doctrine

The MWMS doctrine is:

Do not sell the big AI build before diagnosing the business.

The audit comes before the transformation project.

The roadmap comes before the build.

The cost of inaction comes before the price.

The client’s business context comes before the AI solution.

AIBS Brain should not ask first:

What AI automation can we sell?

AIBS Brain should ask:

What business constraint is costing this client money, time, conversion, delivery quality, or growth — and what AI-enabled system would create the clearest ROI?

Strategic Importance

This framework is strategically important because it gives AIBS Brain a practical commercial pathway.

The pathway is:

Free value / outreach
Diagnostic lead magnet
Paid AI audit
Paid transformation project
Monthly recurring revenue

This is stronger than going straight from cold prospect to expensive AIOS build.

The audit creates a bridge.

It allows MWMS to:

start smaller
lower client risk
get paid for discovery
understand the business deeply
identify high-ROI opportunities
build trust
create a roadmap
sell the next project naturally
avoid wrong builds
reduce failed projects
create proof
create recurring support pathways

The audit also strengthens the MWMS commercial model because it can be sold as a standalone product while also functioning as a sales mechanism for larger work.

Definition

An AI audit is a structured diagnostic assessment of a business that identifies where AI, automation, workflow redesign, reporting, data systems, or AIOS components can create measurable value.

A paid roadmap is the audit output that explains the client’s current state, highest-value opportunities, cost of inaction, recommended projects, ROI logic, risk level, implementation priority, and next-step transformation options.

A quick strike audit is a smaller paid audit designed to create clarity quickly, usually focused on the highest-leverage opportunities rather than a full enterprise assessment.

MWMS Definition

An MWMS AI Audit is:

A paid diagnostic and roadmap process that analyses a client’s business goals, constraints, customer journey, workflows, tools, data, pain points, and opportunities, then converts that analysis into a quantified AIOS roadmap with clear ROI, risk, priority, and implementation options.

Scope

This framework applies to:

AIBS client acquisition
AIOS discovery offers
paid diagnostic products
client workflow audits
lead qualification system audits
client communication audits
content system audits
proposal/sales workflow audits
competitor intelligence audits
customer support audits
reporting/dashboard audits
internal knowledge workflow audits
automation opportunity assessments
AI readiness assessments
business constraint audits
pre-project discovery
transformation project selling
MRR support pathways

This framework applies before MWMS offers a major client AIOS build, automation project, or recurring AIBS implementation package.

Core Principle

The core principle is:

AIBS should diagnose before prescribing.

Just as a mechanic should not sell an engine before inspecting the car, and a professional should not recommend a major solution before assessment, MWMS should not recommend expensive AI systems without understanding the business.

The audit earns the right to prescribe.

The MWMS AI Audit Commercial Pathway

The default pathway is:

Free value / outreach
Diagnostic lead magnet
Paid AI audit
Paid transformation project
Monthly recurring revenue

Stage 1: Free Value / Outreach

The first stage is getting the client’s attention through value.

This can happen through:

helpful content
LinkedIn posts
YouTube content
email
direct outreach
Upwork proposal
community value
Loom audit
free checklist
short diagnostic
public teardown
referral conversation
webinar
local business conversation
personal network message

The goal is not to immediately sell a large project.

The goal is to start a value-led relationship.

Free Value Questions

Ask:

Who is the target client?
What business pain do they have?
What valuable insight can MWMS provide before asking for money?
What small diagnostic can reveal the problem?
What content or message would make the client feel understood?
What proof can be shown?
What next step is natural?

Rule

The first touch should create trust, not pressure.

Stage 2: Diagnostic Lead Magnet

The second stage is a free or low-friction diagnostic lead magnet.

This sits between free content/outreach and the paid audit.

It reduces the jump from stranger to paid diagnostic.

Examples:

AI readiness scorecard
missed lead follow-up calculator
workflow bottleneck checklist
customer journey gap checklist
AIOS opportunity self-assessment
lead response loss calculator
email list revenue leak calculator
competitor intelligence sample report
client communication gap assessment
proposal workflow scorecard
support automation opportunity checklist

The lead magnet should solve a smaller version of the bigger problem.

It should also help qualify the prospect.

Diagnostic Lead Magnet Questions

Ask:

What problem does this lead magnet reveal?
What data does it collect?
Does it naturally lead to the paid audit?
Is it specific to the desired client avatar?
Does it show the client what they are losing?
Does it create curiosity about the roadmap?
Does it lead to a call or paid audit offer?

Rule

The diagnostic lead magnet should make the paid audit feel like the obvious next step.

Stage 3: Paid AI Audit

The paid AI audit is the entry offer.

It should be positioned as:

opportunity assessment
AIOS roadmap
business bottleneck diagnosis
automation opportunity assessment
workflow and ROI audit
client intelligence audit
AI readiness and implementation roadmap

It should not be positioned as:

random AI ideas
generic automation suggestions
tool recommendations only
vague consultation
free discovery
“let’s see what happens”

Audit Positioning

The strongest positioning is:

We will assess your business, identify the highest-value AI and automation opportunities, quantify what inaction is costing you, and give you a clear roadmap for what to fix first.

Rule

The paid audit sells clarity, quantified opportunity, and a roadmap.

Stage 4: Paid Transformation Project

After the audit, MWMS presents the larger implementation offer.

This may include:

AIOS build
lead qualification system
customer communication system
client intelligence report system
proposal automation system
content production system
internal knowledge assistant
workflow automation package
CRM integration
data/reporting dashboard
support automation
sales follow-up system
competitor intelligence system

The transformation project should be based on audit findings, not pre-decided.

Rule

The transformation project should feel like the natural continuation of the audit roadmap.

Stage 5: Monthly Recurring Revenue

After the transformation project, MWMS should identify recurring value opportunities.

MRR may include:

system monitoring
monthly optimisation
reporting
AIOS maintenance
prompt/workflow updates
tool management
content/report production
client intelligence updates
competitor tracking
lead quality monitoring
support and improvement
training
strategy retainer
quarterly roadmap review

Rule

AIBS should prefer systems that create recurring value, not one-off novelty.

Audit Pricing Rule

The quick strike audit can be priced as a paid diagnostic entry product.

The source material uses a rough example of $1,000 to $3,000 for a smaller quick strike audit, with higher audit prices possible for larger or more complex organisations.

MWMS should not treat that price as fixed.

Pricing should depend on:

client size
business complexity
number of workflows
data complexity
number of calls required
reporting depth
ROI potential
urgency
industry
decision-maker level
expected transformation value
amount of research required

MWMS Audit Pricing Bands

Starter Audit

Use for:

small business
simple workflow
single core bottleneck
one call
basic roadmap

Growth Audit

Use for:

more complex business
multiple workflows
deeper ROI modelling
stronger roadmap
more detailed presentation

Strategic Audit

Use for:

larger business
multiple departments
higher risk
multiple stakeholders
deeper data review
broader AIOS roadmap

Rule

Audit price should be low enough to be an easier first yes, but high enough to command seriousness.

Pre-Audit Intake Requirement

Before the audit call, MWMS should collect key information from the client.

This makes the call more professional and allows MWMS to use time better.

Pre-Audit Intake Fields

Collect:

Client Name:
Business Name:
Website:
Industry:
Business Type:
Current Monthly Revenue / Turnover:
Team Size:
Primary Offer / Service:
Target Customer:
Customer Journey From Click-To-Close:
Main Lead Sources:
Sales Process:
Current Conversion Rate:
Average Customer Value:
Customer Lifetime Value:
Customer Acquisition Cost:
Current Tools / Software Stack:
Critical Workflows:
Where Data Is Stored:
Biggest Problem Right Now:
Dream Outcome:
Quick Win Desired:
What They Have Tried Before:
Current AI / Automation Usage:
AI Expectations:
Main Risk / Concern:

Rule

The quality of the audit depends on the quality of the intake.

Click-To-Close Mapping Rule

MWMS must understand the client’s customer journey from first attention to sale.

This is the click-to-close map.

It should show:

how the client gets attention
where leads come from
what happens after lead capture
how prospects are nurtured
how sales conversations happen
how proposals are sent
how payment happens
how onboarding begins
how delivery happens
how retention or repeat purchase happens

Click-To-Close Questions

Ask:

Where does the customer first hear about the business?
What action do they take first?
What form, call, message, or booking happens?
Who responds?
How fast is response?
What system stores the lead?
What follow-up happens?
What is the sales conversation?
What is the proposal process?
Where do prospects drop off?
Where are leads lost?
Where is money leaking?
Where could AI improve the journey?

Rule

No serious AI audit is complete without understanding the customer journey.

Discovery Call Structure

The audit discovery call should usually run 60 to 90 minutes depending on complexity.

The call should collect enough information to diagnose opportunities and quantify value.

Discovery Call Sections

Rapport
Business overview
Goals
Pain points
Quantification
Workflows
Tools
Data
AI expectations
Constraints
Quick wins
Next steps

1. Rapport

The call should begin naturally and professionally.

Purpose:

build trust
set tone
explain process
confirm time available
explain that many questions will be asked

Rule

The client should understand that MWMS is diagnosing, not guessing.

2. Business Overview

Ask the client to explain the business in their own words.

This should include:

what they sell
who they sell to
how customers find them
how customers buy
how delivery works
what the business model is

Rule

Always hear the business from the client, not only from the form.

3. Goals

Understand short-term and longer-term goals.

Ask:

What do you want to achieve in the next 6 to 12 months?
What would make this year a success?
What are you trying to become known for?
What part of the business matters most right now?
What growth target matters?
What operational improvement matters?
What do you not want to happen?

Rule

Do not recommend an AI system that moves the client away from their actual goal.

4. Pain Points

Identify what feels sluggish, broken, expensive, slow, repetitive, manual, risky, or frustrating.

Ask:

What is not working right now?
What keeps slowing the business down?
Where do leads or customers get lost?
Where is staff time wasted?
What do customers complain about?
What task do you hate doing?
What have you tried before?
Why did it not work?
What problem keeps repeating?

Rule

Pain creates the audit opportunity.

5. Quantification

This is one of the most important audit stages.

Quantification turns vague pain into financial meaning.

The key metric is Cost Of Inaction.

Cost Of Inaction

Cost Of Inaction asks:

What is this problem costing the business if nothing changes?

COI may include:

lost revenue
lost leads
missed conversions
wasted staff time
delayed follow-up
refund risk
churn
poor retention
lost upsells
manual labour cost
opportunity cost
slow response cost
lost customer lifetime value

Quantification Questions

Ask:

How many leads are lost each month?
What is one customer worth?
What is the current conversion rate?
What would a small improvement be worth?
How many hours are spent manually?
What is the hourly cost of that work?
What revenue is delayed or missed?
What is the cost of slow response?
What is the cost of poor follow-up?
What would this be worth if fixed?
What is the monthly or annual cost of doing nothing?

Rule

If the audit cannot quantify value, the transformation project becomes harder to sell.

6. Workflows

Identify the client’s key workflows.

For a quick strike audit, focus on the highest-value workflows.

Possible workflows:

lead intake
lead qualification
customer follow-up
sales call booking
proposal creation
onboarding
customer support
content production
reporting
review/testimonial collection
billing/payment
internal handoffs
data entry
appointment reminders
CRM updates
client reporting
competitor monitoring

Workflow Questions

Ask:

What are the 3 to 5 core workflows that run the business?
Who performs each workflow?
What tools are used?
What data is required?
Where does the workflow break?
What is manual?
What is repetitive?
What is high-value?
What is low-value?
What causes errors?
What could be automated, improved, or removed?

Rule

AI opportunities live inside workflows, not abstract ideas.

7. Tools

Map the client’s current software stack.

Tools may include:

CRM
email
calendar
website
forms
payment platform
project management
spreadsheets
support inbox
social platforms
analytics
ads platforms
automation tools
AI tools
document tools
cloud storage
communication tools

Tool Questions

Ask:

What tools are used?
Who owns them?
What data is stored where?
Which tools are essential?
Which tools are underused?
Which tools do not connect?
Which tool causes friction?
Which tool is unnecessary?
What API/access is available?
What permissions would be needed?

Rule

Tool mapping is required before feasibility decisions.

8. Data

Data is critical for any AIOS system.

MWMS must understand:

where the data lives
who owns it
who can access it
how clean it is
how sensitive it is
how often it updates
whether it can be exported
whether it can be integrated
whether it can be used safely

Data Questions

Ask:

Where is customer data stored?
Where are leads stored?
Where are sales notes stored?
Where are support messages stored?
Where are documents stored?
Where are reports stored?
Who has access?
Is the data structured?
Is there sensitive information?
What permissions are needed?
What compliance risks exist?

Rule

No AIOS roadmap should ignore data location, ownership, or risk.

9. AI Expectations

Understand what the client thinks AI should do.

Ask:

What do you want AI to do?
What have you seen that made you interested?
What are you worried about?
What would feel like a win?
What should AI not do?
Where do you still want human review?
What level of automation feels safe?
What would make you trust the system?

Rule

AI expectations must be clarified before implementation.

Enhance → Eliminate → Expand Prioritisation

This is a core MWMS audit prioritisation rule.

When identifying opportunities, prioritise:

Enhance
Eliminate
Expand

1. Enhance

Enhance means improving what already works.

Examples:

improve lead follow-up
improve conversion
improve reporting
improve proposal process
improve client communication
improve onboarding
improve content production
improve customer retention
improve sales workflow
improve response speed

Enhancing existing profit centres is usually the highest-value opportunity.

Rule

First look for what already makes money and can be improved.

2. Eliminate

Eliminate means removing repetitive, low-value, manual, boring, or error-prone work.

Examples:

manual data entry
copy-paste reporting
repetitive follow-up
appointment reminders
manual CRM updates
manual document processing
repeated support questions
internal status chasing

Rule

Eliminate work that drains time without creating strategic value.

3. Expand

Expand means creating new revenue opportunities.

Examples:

new lead magnet
new report product
new AIOS offer
new retention system
new upsell
new client intelligence service
new content distribution path
new automated sales assist system

Expansion can be valuable, but it should not come before enhancing what already works unless the data supports it.

Rule

Expand after enhance and eliminate unless a major opportunity is obvious.

Impact Matrix

The audit should rank opportunities by value and difficulty.

Four Quadrants

1. High Value / Easy

Classification:

Quick Win

Action:

Prioritise early.

2. High Value / Hard

Classification:

Strategic Roadmap

Action:

Plan for later phase.

3. Low Value / Easy

Classification:

Nice To Have

Action:

Do only if it supports larger goal.

4. Low Value / Hard

Classification:

Ignore

Action:

Do not recommend.

Rule

The audit should lead with high-value, achievable opportunities.

ROI / Payback / Risk Scoring

Each recommended opportunity should include:

estimated annual value
time saved
revenue impact
cost saved
implementation cost
payback period
risk level
maintenance level
priority
recommended phase

ROI Questions

Ask:

What is the annual value?
What is the monthly value?
How much time is saved?
What revenue may increase?
What costs may reduce?
What is the expected implementation cost?
How quickly could this pay back?
What is the risk?
What maintenance is required?
Is this a quick win or strategic project?

Rule

AIBS recommendations should be decision-ready, not just interesting.

Audit Output Structure

The audit output should be a clear, visual, decision-ready presentation.

It should not be a vague document full of theory.

Recommended Audit Deck Structure

Cover / client brand
Audit objective
Business overview
Current goals
Current customer journey
Current workflow map
Current tool stack
Current impact / cost of inaction
Opportunity summary
Impact matrix
Opportunity cards
Recommended quick wins
Strategic roadmap
Three-month implementation plan
Package options
Next steps
Thank you / confirmation

Cover / Client Brand

Use the client’s branding where appropriate.

This increases perceived specificity and care.

Rule

The audit should feel built for the client, not templated for everyone.

Audit Objective

State what the audit was designed to answer.

Example:

Identify the highest-value AI and automation opportunities that can improve lead response, conversion, reporting, and operational efficiency over the next 90 days.

Rule

The client should know what the audit is solving.

Current Impact / Cost Of Inaction Slide

This is one of the most important slides.

It should show:

current leakage
lost revenue
time waste
missed conversions
cost of slow response
annualised cost
opportunity cost

Rule

The client must see the cost of doing nothing.

Opportunity Cards

Each opportunity card should include:

Opportunity Name:
Problem:
Solution:
Business Benefit:
Estimated Value:
Implementation Difficulty:
Payback Period:
Risk Level:
Maintenance Level:
Priority:
Recommended Phase:

Rule

Opportunity cards should make decision-making easy.

Three-Month Roadmap

Use a simple roadmap.

Example:

Month 1: Quick Wins

highest-value easy opportunities
immediate workflow improvements
basic system setup

Month 2: Foundations

core data/workflow systems
integration setup
process stabilisation

Month 3: Scale

advanced automation
reporting
optimisation
expansion opportunities

Rule

Three months is practical enough to understand and long enough to show strategy.

Audit Delivery Call Rule

The audit should usually be presented live.

Do not simply email the audit report unless the client relationship or context requires it.

The live call allows MWMS to:

explain context
answer questions
show understanding
handle objections
guide decision-making
present the roadmap
sell the next step

Rule

The audit delivery call is both value delivery and sales bridge.

Two-Option Close

After presenting the audit, MWMS should usually offer two implementation options.

Do not present too many options.

Option 1: Quick Win Package

Purpose:

Implement the highest-value quick win.

Useful for:

smaller client
lower budget
fast trust-building
first engagement
urgent bottleneck

Option 2: Growth / Full Roadmap Package

Purpose:

Implement multiple roadmap opportunities.

Useful for:

more serious client
stronger ROI
larger transformation
better long-term fit

Rule

The second option should look like the stronger value when the ROI supports it.

Next-Step Close

The audit presentation should end with clear next steps.

Possible next steps:

sign engagement letter
pay invoice/deposit
book onboarding call
provide required access
confirm implementation scope
begin quick-win deployment
schedule first milestone

Rule

Do not end the audit with vague “let me know.”

Objection Handling In Audit Close

Audit objections should be handled using the cost of inaction and ROI logic.

“I need more time”

Ask:

What information would help you make the decision?

“It is expensive”

Ask:

Compared to the cost of the problem, does the investment make sense?

“I am not sure it will work”

Respond with:

proof
process
pilot option
quick win
risk reduction
phased roadmap

“We can do this ourselves”

Ask:

who will own it?
when will it be done?
what is the cost of delay?
what expertise is missing?
what happens if it is not implemented?

Rule

Objections reveal missing clarity, missing proof, missing urgency, or poor fit.

Proof And Testimonial Capture

After delivering value, MWMS should capture proof.

Proof may include:

testimonial
before/after state
audit reaction
implementation result
client quote
ROI result
time saved
workflow improved
system launched
lead response improved
conversion improved
reporting improved

Testimonial Questions

Ask:

What was happening before the audit?
What became clearer?
What opportunity did you see?
What was most valuable?
What changed after implementation?
What would you say to another business considering this?

Rule

Proof should be captured when value is fresh.

Monthly Recurring Revenue Pathway

After audit and implementation, MWMS should look for recurring value.

Possible MRR offers:

AIOS maintenance
monthly optimisation
monthly reporting
competitor intelligence digest
content intelligence report
lead quality review
automation monitoring
prompt/workflow updates
staff training
quarterly roadmap
system improvement retainer
technical support
dashboard review
compliance/risk review

Rule

Recurring revenue should be attached to ongoing business value, not artificial dependency.

Pivot To Clarity Rule

From the pivoting lesson, MWMS should not pivot away from fear.

MWMS should pivot toward clarity.

A pivot may be needed when:

the avatar is wrong
the problem is weak
the market is not responding
the channel is wrong
the offer is not converting
the client segment cannot pay
the economics are poor
the constraint has changed
repeated tests disprove the hypothesis

A pivot is not needed just because:

work became hard
results are slower than hoped
a new idea seems exciting
another creator claims easier money
the current path requires boring work
Plus suggests a more exciting structure

Rule

Pivot to clarity, not away from discomfort.

Knowledge Problem Before Pivot Rule

Before pivoting, ask whether the issue is actually:

missing knowledge
weak execution
wrong offer
weak lead generation
poor follow-up
poor sales process
bad proof
poor avatar research
weak content
weak delivery
poor pricing

Rule

Most early pivots should be treated as diagnosis problems before direction changes.

Focus Compounds Rule

The pivoting and shiny object material reinforces that focus compounds.

When MWMS keeps switching:

learning resets
content momentum resets
market understanding resets
sales process resets
avatar knowledge resets
proof collection resets
system-building resets

Rule

Do not reset the clock without evidence.

Proof-Led VSL / Presentation Rule

The Hormozi lessons reinforce that proof matters.

For audit and AIBS selling, MWMS should lead with proof where possible.

Proof may include:

client results
audit examples
before/after workflow
revenue impact
time saved
testimonials
case studies
dashboard screenshots
implementation examples
sample roadmap
known problem patterns

Rule

Proof increases perceived likelihood of success.

Direct Conversation Rule

The Hormozi lessons reinforce that direct conversation in funnels can massively improve conversion, especially for higher-ticket offers.

For AIBS audits, direct conversation is usually required.

This may include:

discovery call
audit call
delivery call
roadmap call
implementation planning call
stakeholder call

Rule

High-value AIBS offers should include human conversation before major commitment.

Decision-Maker Rule

The audit must involve the correct decision-maker.

If the user and buyer are different, MWMS must know that early.

Examples:

students may want tutoring, but parents pay
staff may want automation, but owner approves
marketing manager may want reporting, but founder approves budget
receptionist may feel pain, but practice owner pays
operations manager may use system, but CEO signs off

Rule

Do not sell implementation to someone who cannot approve implementation.

Delete To Test Value Rule

The Hormozi lesson #2 includes a useful product/service principle:

You often learn whether something is core by removing it and seeing whether people demand it back.

For MWMS, this applies to:

client deliverables
reporting sections
content types
community features
service elements
dashboard widgets
audit sections
internal MCR pages
unnecessary workflows
overcomplicated offers

Rule

If removing something causes no pain, it may not be core value.

Monthly Value Bomb Rule

For ongoing AIBS retainers or communities, MWMS should consider a recurring value asset that justifies retention.

Examples:

monthly competitor intelligence digest
monthly automation opportunity report
monthly lead quality report
monthly content opportunity report
monthly AI tools watchlist
monthly campaign insight report
monthly workflow improvement report
monthly industry trend alert
monthly client dashboard review

Rule

A monthly recurring offer should have a recurring value moment.

Audit Data Capture Standard

Data Brain should eventually store audit intelligence.

Suggested fields:

Client Name:
Business Type:
Industry:
Website:
Audit Date:
Audit Type: Starter / Growth / Strategic
Monthly Revenue:
Primary Goal:
Biggest Pain:
Commercial Constraint: Leads / Conversion / Delivery / Profit / Focus
Customer Journey Summary:
Core Workflows:
Tool Stack:
Data Locations:
Top Opportunities:
Cost Of Inaction:
Quick Wins:
Strategic Projects:
ROI Estimate:
Payback Period:
Risk Level:
Recommended Package:
Next Step:
Closed: Yes / No
Objections:
Proof Captured:
MRR Opportunity:
Follow-Up Date:

Rule

Audit learning should improve the MWMS AIBS offer over time.

Compliance And Risk Requirements

AI audits may involve sensitive business information.

Risk and Compliance Brain should review:

client data access
API key handling
sensitive data
personal data
financial data
contracts
claims
ROI projections
guarantee language
testimonial permissions
data retention
tool permissions
client ownership
confidentiality
handover terms

Rule

Do not request or store more client data than needed for the audit.

Software Ownership And Access Boundary

During audit and implementation planning, software ownership should be clear.

Preferred rule:

client owns production accounts
client owns API keys
client owns core business data
MWMS may use controlled temporary access where required
MWMS should not rely on trapping clients through hidden technical dependency
handover should be clear
support should be sold through ongoing value, not access hostage

Rule

Trust is stronger than lock-in.

Developer Boundary

This framework does not authorize immediate changes to M’s active build areas.

This is a commercial and AIBS operating standard.

If this framework later becomes a build task, it must be converted into a controlled developer brief.

Any future implementation must specify:

exact site
exact page
exact data fields
exact form
exact dashboard
exact plugin/module
exact file path if code is involved
what not to touch
test steps
rollback/safety notes

Rule

This page is not a build instruction for M.

Application To AIBS Brain

AIBS Brain owns this framework operationally.

AIBS Brain should use this framework to:

sell paid diagnostics
identify client opportunities
create AIOS roadmaps
sell implementation projects
sell recurring support
avoid premature builds
improve client acquisition
increase close rate
improve delivery scope
create proof
create retained clients

AIBS Rule

AIBS should use audits to sell clarity first and transformation second.

Application To HeadOffice Brain

HeadOffice uses this framework to govern when AIBS should sell, build, pause, pivot, or focus.

HeadOffice should check:

is the client avatar clear?
is the audit offer defined?
is the commercial constraint known?
is this a good use of Martyn’s time?
does this require M?
is there a paid path?
is the next project realistic?
is MRR possible?
is this aligned with MWMS current priorities?

HeadOffice Rule

HeadOffice must prevent AIBS from building before diagnosis and payment.

Application To Sales Brain

Sales Brain uses this framework to structure:

audit positioning
discovery call
cost of inaction
roadmap presentation
two-option close
objection handling
payment next step
follow-up
proof capture

Sales Rule

The audit sale is a clarity sale.

The implementation sale is a transformation sale.

Application To Research Brain

Research Brain supports this framework by defining:

target client avatar
client pain
market language
competitor offers
industry workflows
pricing signals
decision-maker profile
resonance signals

Research Rule

Research Brain improves audit targeting and positioning.

Application To Experimentation Brain

Experimentation Brain tests the audit pathway.

Tests may include:

audit offer positioning
lead magnet conversion
outreach message
discovery call script
audit pricing
audit deck format
two-option close
MRR offer
follow-up sequence

Experimentation Rule

The audit system itself should be tested and improved.

Application To Finance Brain

Finance Brain supports:

audit pricing
transformation pricing
ROI modelling
payback calculation
margin review
support cost
MRR model
client profitability
delivery burden

Finance Rule

Audit and implementation pricing must support profit.

Application To Content Brain

Content Brain supports audit acquisition through:

educational content
case study content
problem-awareness content
AIOS opportunity content
diagnostic lead magnets
proof-led posts
founder authority content
objection-handling content

Content Rule

Content should make the paid audit feel obvious.

Application To Risk And Compliance Brain

Risk and Compliance Brain must check:

audit claims
ROI claims
guarantee wording
data access
client confidentiality
contract terms
testimonial permissions
AI usage disclosure
automation risk
regulated industry exposure

Risk Rule

The audit should create trust, not compliance exposure.

AI Audit Diagnostic Checklist

Before selling or delivering an audit, check:

Offer

Is the audit name clear?
Is the price clear?
Is the outcome clear?
Is the timeframe clear?
Is the deliverable clear?
Is the next step clear?

Avatar

Who is this audit for?
What problem do they have?
Can they pay?
Is the decision-maker involved?

Intake

Has pre-call data been collected?
Is click-to-close mapped?
Are goals clear?
Are metrics collected?
Are workflows known?
Are tools known?
Are data locations known?

Analysis

Is cost of inaction quantified?
Are opportunities ranked?
Is enhance/eliminate/expand applied?
Is the impact matrix used?
Is ROI estimated?
Is risk scored?
Is payback period estimated?

Delivery

Is the audit presented live?
Is the roadmap clear?
Are next steps defined?
Are two package options presented?
Is payment path clear?
Is onboarding path clear?

Follow-Up

Was proof captured?
Was objection data recorded?
Was MRR opportunity identified?
Was follow-up scheduled?

Drift Protection

This framework protects MWMS from:

selling AI before diagnosing business
building before payment
recommending tools without context
selling large projects too early
doing free discovery forever
failing to quantify value
ignoring cost of inaction
recommending low-value automations
missing quick wins
overbuilding strategic projects too early
sending reports without explanation
presenting too many options
weak follow-up
weak proof capture
no MRR pathway
pivoting from fear
chasing shiny offers
treating AI as the value instead of business transformation
letting M build without commercial validation

Strategic Summary

This framework gives AIBS Brain a practical paid-entry commercial model.

The strongest insight is:

The audit is not just analysis.
The audit is the bridge between interest and implementation.

The audit allows MWMS to:

get paid to understand the client
identify the real business opportunity
quantify cost of inaction
create a clear roadmap
reduce implementation failure
build trust
sell larger projects
create recurring revenue

This is highly valuable for AIBS because it prevents MWMS from trying to sell expensive AIOS builds too early.

The correct AIBS sequence is:

Value first → diagnostic lead magnet → paid audit → quantified roadmap → transformation project → recurring value.

This should become one of the main commercial pathways for AIBS Brain.

Final Standard

The MWMS final standard is:

AIBS should not sell major AIOS builds before diagnosing the client’s business.

Use the paid AI audit to understand the business, map click-to-close, identify goals and pains, quantify cost of inaction, rank opportunities, present quick wins and strategic roadmap, sell the correct transformation project, and create recurring value.

The audit sells clarity.

The roadmap sells confidence.

The transformation project sells implementation.

The MRR offer sells ongoing value.

That is the MWMS AI Audit Diagnostic And Paid Roadmap standard.

Change Log

Version: v1.0

Date: 2026-06-03
Author: MWMS HeadOffice

Change:

Created the MWMS AI Audit Diagnostic And Paid Roadmap Framework from the AI Automations by Jack block containing:

AI Audit Starter Pack
When To Pivot / SHO Syndrome
Lessons From Alex Hormozi
Lessons From Alex Hormozi #2

Captured the AI Audit Starter Pack as the main source because it provides the strongest practical AIBS commercial pathway.

Created the audit pathway:

Free value / outreach
Diagnostic lead magnet
Paid AI audit
Paid transformation project
Monthly recurring revenue

Added key audit operating sections:

Audit Pricing Rule
Pre-Audit Intake Requirement
Click-To-Close Mapping Rule
Discovery Call Structure
Cost Of Inaction
Enhance → Eliminate → Expand Prioritisation
Impact Matrix
ROI / Payback / Risk Scoring
Audit Output Structure
Audit Delivery Call Rule
Two-Option Close
Next-Step Close
Objection Handling In Audit Close
Proof And Testimonial Capture
Monthly Recurring Revenue Pathway
Pivot To Clarity Rule
Knowledge Problem Before Pivot Rule
Focus Compounds Rule
Proof-Led VSL / Presentation Rule
Direct Conversation Rule
Decision-Maker Rule
Delete To Test Value Rule
Monthly Value Bomb Rule
Audit Data Capture Standard
Compliance And Risk Requirements
Software Ownership And Access Boundary

Mapped the framework across:

AIBS Brain
HeadOffice Brain
Sales Brain
Research Brain
Experimentation Brain
Finance Brain
Content Brain
Risk Brain
Compliance Brain

Established AIBS Brain as the primary owner, with HeadOffice governing when the audit pathway should be used and ensuring it does not become unvalidated build work for M.

Purpose of creation:

To give AIBS Brain a practical paid diagnostic entry offer that allows MWMS to sell clarity before implementation, quantify business opportunity before proposing AIOS builds, reduce project failure risk, create trust through a roadmap, sell larger transformation projects from evidence, and attach recurring value after implementation.

END — MWMS AI AUDIT DIAGNOSTIC AND PAID ROADMAP FRAMEWORK v1.0