MWMS Client Intelligence Report Automation Framework

System: MWMS
Document Type: Framework
Authority Level: MCR Source Of Truth
Status: Draft For MCR
Version: v1.0
Primary Location: MCR
Future Operational Destination: AIBS Brain, HeadOffice Brain, Automation Brain, Research Brain, Data Brain, Sales Brain, Customer Brain, Content Brain, Client AIOS Systems
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-01
Source / Origin: AI Automations by Jack — Client Reporting / Competitor Intelligence / WhatsApp Report / Proposal Automation Block
MWMS Classification: Client Intelligence Reporting Framework / Recurring Value Automation / Competitive Monitoring System / AIOS Client Report Layer
Primary Brain: AIBS Brain
Supporting Brains: HeadOffice Brain, Automation Brain, Research Brain, Data Brain, Sales Brain, Customer Brain, Content Brain, Risk Brain, Compliance Brain, SIT Brain, Finance Brain
Related Pages: MWMS n8n Operating And Deployment Standard, MWMS AI Dashboard Capability Framework, MWMS Supabase RAG And Vector Memory Framework, MWMS Client AI Interface Selection Framework, MWMS Advanced AI Capability Stack Framework, MWMS Advanced AI Capability Activation Registry, MWMS AI Agent Operations Core, MWMS AI Agent Memory And Context Framework, MWMS AI Tool Permission And Access Framework, MWMS AI Automation Security And Risk Checklist, MWMS Automation Build Planning Framework, MWMS Automation Client Demo And Handover Framework
Source Evidence: The absorbed block includes competitor monitoring workflows that scrape and compare website changes, gather Google review data, perform sentiment analysis, store findings, generate PDF reports, and email results to clients. It also includes WhatsApp group intelligence reporting, Fireflies transcript-to-proposal automation, and recurring report generation patterns using n8n, APIs, databases, PDFs, and email delivery.

Purpose

The purpose of the MWMS Client Intelligence Report Automation Framework is to define how MWMS should design, govern, automate, package, and deliver recurring client intelligence reports.

This framework exists because one of the strongest commercial opportunities from this course block is not “automation” by itself.

It is automated intelligence delivery.

A client does not care that n8n, Appify, Fireflies, WhatsApp, Google Reviews, Placid, PDF tools, Gmail, or databases are connected in the background.

A client cares about receiving useful intelligence that helps them:

understand competitors
improve offers
improve sales conversations
identify customer complaints
see market changes
track review sentiment
summarize internal group discussions
create better proposals
improve follow-up
make faster decisions
see value every week or month

This framework turns raw workflow ideas into a governed MWMS client-reporting capability.

The core purpose is:

Convert scattered client, market, competitor, conversation, review, and community data into recurring, source-aware, decision-ready intelligence reports.

This is a major AIBS recurring-value opportunity.

Core Doctrine

The MWMS doctrine is:

Clients pay longer when value is visible, repeated, and decision-ready.

A one-time automation may impress a client once.

A recurring intelligence report can prove value every week or every month.

Client intelligence reports create retention because they answer:

What changed?
What should I care about?
What is the opportunity?
What is the risk?
What should I do next?
What did the AI system find for me?
Why should I keep paying for this system?

The strongest AIBS products will not just perform invisible backend tasks.

They will produce visible business intelligence.

Strategic Importance

This framework is strategically important because it sits at the intersection of several MWMS priorities:

recurring revenue
client value proof
AIOS dashboard/reporting layer
AIBS package design
competitor intelligence
customer intelligence
sales enablement
market research
automation delivery
client retention

The course block shows multiple reporting patterns:

competitor website monitoring
review sentiment reporting
WhatsApp group digest/reporting
sales call transcript to proposal
recurring PDF reports
email delivery
database-backed report history
AI analysis of scraped content
client-ready summaries

These patterns should not remain as isolated workflow examples.

They should become a formal client intelligence layer inside MWMS.

Definition

A Client Intelligence Report Automation is an automated or semi-automated workflow that collects relevant business data, processes it through structured logic and/or AI, creates a decision-ready report, and delivers it to a client, business owner, or internal operator.

MWMS Definition

An MWMS Client Intelligence Report Automation is:

A governed reporting workflow that collects client-relevant data from approved sources, transforms it into structured intelligence, validates the output where needed, and delivers it as a recurring report, dashboard item, proposal, PDF, email, or action brief.

Client Intelligence Is Not Generic Reporting

Generic reporting says:

Here is some data.

Client intelligence says:

Here is what changed, why it matters, what risk or opportunity it creates, and what action should be considered.

MWMS should not sell clients raw automation outputs.

MWMS should sell client intelligence systems that produce useful business understanding.

MWMS Rule

A client report is not complete until it explains meaning and next action.

Core Report Types

MWMS recognises the following client intelligence report types.

1. Competitor Intelligence Report

A report that monitors competitors and identifies meaningful changes.

May include:

website copy changes
offer changes
pricing changes
new pages
new positioning
new services
review changes
customer complaints
customer praise
competitor weaknesses
opportunity gaps
action recommendations

Use Case

Monthly or weekly competitor intelligence for local businesses, agencies, consultants, e-commerce brands, affiliate campaigns, or AIBS clients.

Rule

Competitor intelligence must separate observed changes from AI interpretation.

2. Review Sentiment Report

A report that analyses customer reviews.

May include:

positive themes
negative themes
recurring complaints
recurring praise
service gaps
competitor weaknesses
customer language
content angles
offer improvement ideas
reputation risks

Use Case

Google Reviews, Trustpilot, app reviews, product reviews, marketplace reviews, service business reviews.

Rule

Review sentiment should use real customer language as evidence.

3. WhatsApp / Community Intelligence Report

A report that summarises group or community conversations.

May include:

common questions
complaints
requests
buying signals
support issues
internal team problems
repeated topics
customer confusion
sales opportunities
content ideas
follow-up tasks

The absorbed WhatsApp group workflow shows retrieving messages from a chosen WhatsApp chat, combining message text, generating a report, converting it to PDF, and emailing the result.

Use Case

Client WhatsApp groups, sales teams, support groups, communities, course groups, agency-client groups.

Rule

Group intelligence reports must respect privacy, consent, access boundaries, and group ownership.

4. Sales Call Intelligence Report

A report generated from a sales or discovery call transcript.

May include:

client pain points
stated goals
objections
budget signals
decision-makers
urgency
required deliverables
proposal sections
follow-up tasks
offer fit
next action

The absorbed proposal workflow uses Fireflies transcript data, extracts client needs, creates proposal sections, generates HTML/PDF, and sends the result by email.

Use Case

AIBS sales calls, client discovery calls, consultant proposals, agency proposals, onboarding summaries.

Rule

Sales call reports must not invent commitments, pricing, or scope not stated or approved.

5. Proposal Intelligence Report

A report or proposal generated from conversation, intake, or discovery data.

May include:

executive summary
client problem
recommended solution
project scope
deliverables
timeline
pricing placeholder
assumptions
exclusions
next steps

Use Case

AIBS proposal generation, agency services, automation packages, client onboarding.

Rule

AI may draft proposals, but commercial terms require human approval.

6. Market Opportunity Report

A report that analyses market data for opportunities.

May include:

emerging trends
competitor gaps
customer language
under-served needs
offer opportunities
content angles
lead magnet ideas
campaign angles
product positioning ideas

Use Case

Research Brain, Content Brain, Affiliate Brain, AIBS client strategy.

Rule

Opportunity reports must distinguish evidence from speculation.

7. AIOS Value Proof Report

A report showing what a client’s AI Operating System achieved.

May include:

workflows run
leads processed
tasks created
reports generated
questions answered
calls handled
content produced
support items resolved
time saved estimate
issues caught
recommended improvements

Use Case

AIBS retention reporting.

Rule

AIBS value proof reports should make renewal easier by making value visible.

Core Workflow Pattern

The standard MWMS Client Intelligence Report workflow is:

Source identified
Data collected
Data cleaned
Data stored
Data analysed
Intelligence extracted
Report generated
Report validated
Report delivered
Action logged
Learning captured

Stage 1: Source Identified

Every report must define source.

Possible sources:

competitor website
Google Reviews
WhatsApp group
Fireflies transcript
sales call transcript
CRM data
form intake
support tickets
email thread
Google Sheet
Airtable base
Supabase table
dashboard record
social media comments
YouTube comments
scraped public pages
client documents

Rule

No report should begin without a clear source definition.

Stage 2: Data Collected

Data may be collected through:

n8n workflow
webhook
API call
scraper
RSS feed
form trigger
Google Drive trigger
manual upload
Fireflies API
WhatsApp/Unipile connection
Appify actor
Google Reviews scraper
CRM export
database query

Rule

Collection method must match source permissions, compliance, and client agreement.

Stage 3: Data Cleaned

Raw data is rarely ready for AI.

Cleaning may include:

removing HTML
combining transcript sentences
splitting arrays
merging items
filtering irrelevant fields
removing duplicates
extracting message text
removing system noise
normalizing dates
cleaning names/emails
separating source records
converting data into structured JSON

Rule

Clean data before analysis.

Messy input creates weak intelligence.

Stage 4: Data Stored

Useful report workflows should store source data or processed findings.

Possible storage:

Supabase
Airtable
Google Sheets
PostgreSQL
client CRM
report archive
event log
task table
dashboard table

Rule

Recurring reports need history.

Without history, the system cannot detect change.

Stage 5: Data Analysed

Analysis may include:

comparison with prior version
sentiment analysis
theme extraction
trend detection
pain point extraction
opportunity extraction
risk detection
competitor positioning analysis
proposal section extraction
content idea extraction
action recommendation

Rule

Analysis must be tied to business meaning, not generic AI commentary.

Stage 6: Intelligence Extracted

Intelligence is the useful interpretation of the data.

Good intelligence answers:

What changed?
What is repeated?
What is unusual?
What is positive?
What is negative?
What is missing?
What opportunity appears?
What risk appears?
What should the client do?
What should MWMS do?

Rule

Extract insight, not just summary.

Stage 7: Report Generated

Reports may be generated as:

PDF
email
dashboard card
Google Doc
HTML report
proposal
client brief
action list
Notion-style page
Supabase record
MCR internal note

Rule

Format should match the client’s use case.

Do not generate PDFs just because the workflow can.

Stage 8: Report Validated

Validation may be required when reports involve:

competitor claims
client recommendations
proposal content
pricing
compliance-sensitive claims
scraped data
sentiment interpretation
public/customer data
personal data
strategic recommendations

Rule

Client-facing intelligence needs validation before trust.

Stage 9: Report Delivered

Delivery methods may include:

email
dashboard
client portal
Google Drive link
Slack
WhatsApp
CRM note
task assignment
HeadOffice Dashboard
Brain Room
AIBS client dashboard

Rule

Delivery should be logged.

A report that disappears into email only is weak operationally.

Stage 10: Action Logged

A report should create an action path.

Possible action outcomes:

client reviews
task created
follow-up scheduled
proposal sent
issue escalated
idea parked
competitor watched
content brief created
sales action assigned
support update triggered

Rule

Reports should create decisions or actions, not dead documents.

Stage 11: Learning Captured

Recurring reports should improve over time.

Learning may include:

better source selection
recurring client concerns
stronger recommendation patterns
bad data sources
repeated false positives
report sections clients ignore
report sections clients value
new upsell opportunities
automation failures
source access issues

Rule

Client intelligence reports should feed Kaizen.

Competitor Intelligence Report Pattern

The competitor intelligence workflow is one of the strongest commercial patterns from this block.

A mature MWMS competitor intelligence workflow may include:

Client competitor list
Website scrape
Current copy extraction
Previous version lookup
Change comparison
Google review scrape
Review sentiment analysis
Opportunity extraction
Risk extraction
Report generation
PDF creation
Email or dashboard delivery
Historical storage

Report Sections

A strong competitor report may include:

Executive Summary
Competitors Monitored
Website Changes Detected
Offer / Positioning Changes
Review Sentiment Summary
Customer Complaint Themes
Customer Praise Themes
Competitor Weaknesses
Client Opportunities
Recommended Actions
Source Notes
Data Limitations

MWMS Rule

Competitor reports should focus on what changed and what the client can do about it.

Review Sentiment Report Pattern

Review sentiment reports turn public customer language into business intelligence.

Workflow:

Select business or competitor
Collect reviews
Clean review text
Identify sentiment
Extract repeated themes
Group complaints
Group praise
Identify business opportunities
Create summary
Recommend action

Review Intelligence Uses

Review data can support:

ad copy
landing page copy
offer improvement
service improvement
FAQ updates
content ideas
competitor weakness angles
sales objections
customer language mining

MWMS Rule

Review sentiment is valuable because it captures real customer language.

Do not over-polish it until the raw language has been mined.

WhatsApp Group Intelligence Pattern

WhatsApp group reporting is useful when a client or internal team has a busy group where useful signals are buried in messages.

Workflow:

Identify approved chat/group
Retrieve chat ID
Store chat name and ID
Pull messages
Filter timeframe
Combine message text
Classify topics
Extract issues/opportunities
Generate report
Convert to PDF
Email or dashboard delivery

Possible Report Sections

Group Activity Summary
Main Topics
Common Questions
Customer Complaints
Buying Signals
Support Issues
Team Actions Needed
Content Ideas
Follow-Up Recommendations

Risk

WhatsApp group data can be private and sensitive.

MWMS Rule

Do not process WhatsApp group data without clear permission, scope, and privacy controls.

Sales Call To Proposal Pattern

The proposal workflow is commercially strong because it turns a sales call into a structured business document.

Workflow:

Sales call recorded
Transcript generated
Transcript retrieved
Client email matched
Needs extracted
Pain points extracted
Solution sections drafted
Proposal generated
PDF or designed document created
Human review
Email sent

Proposal Sections

A proposal may include:

Client Background
Problems Discussed
Desired Outcome
Recommended Solution
Scope
Deliverables
Timeline
Assumptions
Exclusions
Pricing Placeholder
Next Steps

MWMS Rule

AI may draft proposals from call transcripts, but a human must approve scope, pricing, commitments, and legal/commercial terms.

Client Report Design Standard

Client reports should be clear, useful, and professional.

A good report includes:

title
date
client name
reporting period
source summary
key findings
business meaning
recommended actions
risk notes
limitations
next steps
source traceability where appropriate

Avoid

vague AI summaries
unsupported claims
too much raw data
technical backend language
overconfident recommendations
hidden uncertainty
unattributed competitor claims
unreviewed pricing or scope

MWMS Rule

Client reports should be decision-ready and client-readable.

PDF Report Rule

PDF reports can feel polished and valuable.

But PDFs can also create risk if wrong information is sent.

Before PDF generation:

confirm source data
validate AI summary
check client name
check dates
check recommendations
check sensitive data
check branding
check delivery recipient
check whether human approval is required

MWMS Rule

PDF generation is not the same as report approval.

A PDF can make wrong information look official.

Dashboard Report Rule

Some intelligence should appear in dashboards instead of PDFs.

Use dashboard reporting when:

data updates frequently
user needs to filter
user needs to approve actions
report items become tasks
trends need monitoring
client wants ongoing visibility
multiple reports need history

Use PDF reporting when:

client needs a polished deliverable
report is periodic
report is sent by email
report is used in sales/proposal context
snapshot record matters

MWMS Rule

Choose dashboard or PDF based on client use, not workflow convenience.

Email Delivery Rule

Email delivery is useful but must be controlled.

Before sending automated reports:

confirm recipient
confirm client
confirm attachment
confirm subject
confirm report version
confirm no sensitive wrong-client data
confirm human review where required
log send event

MWMS Rule

Automated report emails require stronger review when client-facing.

Source Traceability Rule

Client reports should preserve source traceability.

This may include:

source URL
review source
transcript ID
chat source
scrape date
competitor name
source document name
data timestamp
database record ID
internal source log

Rule

If the client asks, “Where did this come from?” MWMS should be able to answer.

Data Freshness Rule

Client intelligence reports must show the reporting period or source date.

Freshness matters especially for:

competitor website changes
review monitoring
support issues
WhatsApp groups
sales calls
proposal drafts
market opportunities
pricing comparisons

Rule

Old data should not look current.

Human Review Rules

Human review is required before sending reports that include:

proposal terms
pricing
legal claims
compliance-sensitive claims
public accusations
competitor criticism
customer personal data
sensitive WhatsApp messages
sales recommendations
cold outreach recommendations
strategic decisions
client-facing performance claims

Rule

The more the report can affect money, reputation, customer relationships, or legal/compliance risk, the stronger the review required.

Client Permission And Data Access Rule

Before building a client intelligence report system, confirm:

client owns the source data
client has permission to process it
access method is allowed
scraping is permitted or acceptable
data retention is agreed
private messages are handled correctly
users are informed where required
third-party terms are considered
client-specific data is isolated

MWMS Rule

Client data access must be permissioned before automation.

Scraping Governance

Competitor intelligence and review monitoring may involve scraping.

Scraping can be valuable, but it creates risk.

Risks include:

platform terms breach
data accuracy issues
IP blocking
stale cached data
personal data collection
scraping private areas
relying on unofficial APIs
broken workflows when websites change

Required Controls

Scraping workflows should define:

source
allowed pages
frequency
data collected
data excluded
storage rule
client visibility
fallback path
terms/risk review
source timestamp

MWMS Rule

Scraping should be treated as monitored data collection, not guaranteed infrastructure.

AI Analysis Governance

AI may analyse:

competitor changes
reviews
transcripts
messages
proposals
market signals
content themes
support issues

AI must not:

invent facts
exaggerate competitor claims
imply certainty without evidence
create legal/compliance claims without review
make unsupported recommendations
treat sentiment as absolute truth
ignore source limitations

Rule

AI interpretation must remain tied to evidence and limitation notes.

Report Storage And History

Recurring intelligence needs history.

Store reports and source summaries so MWMS can track:

what changed over time
what was sent
what sources were used
what recommendations were made
whether client acted
whether report quality improved
whether patterns repeated

Possible storage:

Supabase
Airtable
Google Drive
CRM
client portal
dashboard table
report archive

Rule

Recurring reports should create a historical intelligence asset.

Client Intelligence Product Packages

This framework can support several future AIBS packages.

Package 1: Competitor Watch Report

Weekly/monthly competitor website and review intelligence.

Client receives:

competitor changes
review sentiment
customer complaint themes
opportunity gaps
recommended actions

Package 2: Reputation Intelligence Report

Google review and customer feedback analysis.

Client receives:

sentiment summary
common praise
common complaints
review response opportunities
operational improvement suggestions
content/ad copy language

Package 3: WhatsApp / Community Digest

Weekly group intelligence report.

Client receives:

key topics
support issues
buying signals
unanswered questions
suggested follow-ups

Package 4: Sales Call Proposal Generator

After a discovery call, client or MWMS receives:

call summary
extracted needs
proposal draft
follow-up email
PDF proposal
next action list

Package 5: AIOS Monthly Value Report

AIBS client receives monthly proof of AIOS activity.

Report includes:

workflows run
tasks handled
reports created
leads processed
support questions answered
time saved estimate
improvement recommendations

Minimum Viable Client Intelligence Product

The first sellable version should be simple.

Recommended MVP:

Competitor Watch + Review Sentiment Report

Inputs:

client business name
3–5 competitors
competitor website URLs
Google review sources
reporting frequency
client email

Outputs:

monthly PDF report
key competitor changes
review sentiment summary
customer complaint themes
action recommendations

Why this is strong:

easy for clients to understand
recurring
visible value
not too operationally invasive
creates strategic conversations
can later connect to dashboards

MWMS Rule

Start with the smallest report that proves recurring value.

Client Intelligence Workflow Build Path

Stage 1: Define Report Purpose

Ask:

What does the client need to know?
What decision will this support?
How often is it needed?
What source data is required?
Who receives it?

Stage 2: Define Data Sources

Select sources:

competitor websites
reviews
WhatsApp group
sales calls
CRM records
support tickets
forms
dashboards

Stage 3: Define Permission

Confirm:

source access
client consent
scraping risk
privacy rules
storage permission
report recipient

Stage 4: Build Data Collection

Use:

n8n
APIs
webhooks
scraper tools
Google Drive
Fireflies
Unipile
Appify
database queries

Stage 5: Clean And Store

Normalize:

text
dates
source names
message groups
review content
transcript content
competitor records

Stage 6: Analyse

Use AI and logic to extract:

changes
sentiment
themes
opportunities
risks
recommendations

Stage 7: Generate Report

Create:

PDF
email
dashboard card
proposal
client brief

Stage 8: Validate

Check:

facts
sources
client identity
dates
claims
recommendations
sensitive data

Stage 9: Deliver

Send through:

email
dashboard
client portal
Google Drive
CRM

Stage 10: Log And Improve

Record:

delivery
source data
report version
client feedback
actions created
errors
Kaizen improvements

Launch Readiness Checklist

Before launching a client intelligence report automation, confirm:

Client use case is clear
Report type is defined
Reporting frequency is defined
Source data is approved
Source access is permissioned
Scraping risk reviewed if relevant
Client data is isolated
Data cleaning works
AI analysis prompt is tested
Report format is approved
Human review requirement is defined
PDF/email delivery tested
Recipient is correct
Source traceability exists
Data freshness is visible
Sensitive data is protected
Error handling exists
Logs are captured
Client feedback path exists
Maintenance owner is assigned
Kaizen review is planned

Failure Modes

Failure Mode 1: Report Is Just A Summary

The report repeats data without insight.

Correction:

Add business meaning and recommended action.

Failure Mode 2: AI Invents Competitor Changes

AI claims a competitor changed something without evidence.

Correction:

Use stored previous/current source comparison.

Failure Mode 3: Scraped Data Is Wrong Or Stale

Report uses outdated or failed scrape data.

Correction:

Add source timestamp and scrape failure handling.

Failure Mode 4: Wrong Client Data In Report

Report includes data from another client.

Correction:

Add client isolation and recipient validation.

Failure Mode 5: Sensitive Group Messages Exposed

WhatsApp/community report reveals private or unnecessary details.

Correction:

Use permission, minimization, and human review.

Failure Mode 6: Proposal Sent Without Review

AI sends proposal with wrong scope or pricing.

Correction:

Require human approval before proposal delivery.

Failure Mode 7: Report Looks Official But Is Draft

PDF makes unreviewed AI output look final.

Correction:

Add status: Draft / Reviewed / Approved.

Failure Mode 8: No Historical Storage

Every report starts from zero.

Correction:

Store source snapshots and prior reports.

Failure Mode 9: Client Does Not Know What To Do

Report has insights but no action path.

Correction:

Add next actions and owner recommendations.

Failure Mode 10: Report Becomes Noise

Reports are too long or frequent and client ignores them.

Correction:

Shorten, prioritize, and focus on top actions.

Application To AIBS Brain

AIBS Brain owns this framework because client intelligence reports can become recurring revenue products.

AIBS should package report automations as:

monthly intelligence subscriptions
AIOS value reports
competitor monitoring packages
reputation intelligence packages
sales proposal systems
community digest systems
customer insight systems

AIBS Rule

AIBS should sell decision-ready intelligence, not workflow diagrams.

Application To Automation Brain

Automation Brain should design and maintain the workflows.

Automation Brain owns:

triggers
APIs
webhooks
data cleaning
PDF generation
email delivery
storage
error handling
logs
workflow maintenance

Automation Rule

Every recurring client report workflow must have failure handling and delivery logging.

Application To Research Brain

Research Brain should guide competitor, review, and market analysis quality.

Research Brain owns:

source quality
competitor selection
evidence interpretation
trend extraction
opportunity framing
source limitations

Research Rule

Research-backed reports must separate source evidence from AI interpretation.

Application To Data Brain

Data Brain owns report data structure.

Data Brain should define:

report tables
source tables
client IDs
source timestamps
report history
metadata
storage schema
dashboard compatibility
export formats

Data Rule

Recurring intelligence requires structured historical data.

Application To Sales Brain

Sales Brain uses reports to improve sales outcomes.

Sales Brain may use:

sales call proposal generator
lead intelligence report
proposal sections
objection extraction
follow-up action lists
client-ready recommendations

Sales Rule

AI-generated sales material must be reviewed before client delivery.

Application To Customer Brain

Customer Brain uses reports to improve support and customer experience.

Customer Brain may use:

review sentiment reports
WhatsApp group issue reports
customer complaint themes
FAQ improvement reports
support trend summaries

Customer Rule

Customer intelligence must feed service improvement, not just reporting.

Application To Content Brain

Content Brain can use intelligence reports to create better content.

Reports may provide:

customer language
competitor gaps
objection themes
content angles
FAQ ideas
case study ideas
social post themes

Content Rule

Market and customer intelligence should feed content strategy.

Application To Risk And Compliance Brain

Risk and Compliance Brain must review reports involving:

scraping
personal data
customer reviews
private messages
cold outreach recommendations
competitor claims
legal/commercial claims
financial implications
client-sensitive findings
automated email delivery

Risk Rule

Client reports must not create reputation, privacy, legal, or compliance risk.

Application To SIT Brain

SIT Brain should test report automations.

SIT should test:

correct client data
correct sources
failed scrape handling
missing transcript
no reviews found
wrong email recipient
PDF generation failure
duplicate report sends
sensitive data exposure
AI output quality
report formatting
delivery logging

SIT Rule

A report workflow is not ready until it has been tested for wrong data, missing data, and failed delivery.

Related AI Employee Capabilities

Client Intelligence Report Architect

Designs client report structure, source inputs, report sections, and delivery path.

Competitor Monitoring Agent

Tracks competitor website and offer changes.

Review Sentiment Analyst

Extracts customer praise, complaints, themes, and opportunities from reviews.

WhatsApp Intelligence Analyst

Summarizes approved group conversations into business insights.

Sales Proposal Drafting Agent

Turns call transcripts into proposal drafts.

Report Validation Agent

Checks report facts, source traceability, sensitive data, and client identity.

Client Value Proof Agent

Turns AIOS activity into client-readable value proof.

Report Delivery Agent

Handles PDF/email/dashboard delivery and logs send status.

Future Expansion

This framework may later produce:

MWMS Competitor Intelligence Report Product Framework
MWMS Review Sentiment Intelligence Framework
MWMS WhatsApp Group Intelligence Report Standard
MWMS Sales Call To Proposal Automation Standard
MWMS AIOS Monthly Value Report Template
MWMS Client Report Validation Checklist
MWMS Client Report PDF And Email Delivery Standard

These should be created only when the related product moves into active build or client offer design.

Strategic Summary

This block is one of the strongest commercial automation blocks in the course because it shows that recurring value comes from reporting and intelligence, not from hidden automation alone.

The most powerful pattern is:

Collect useful data → clean it → compare it → analyse it → create a report → deliver it → create action → repeat.

That pattern can support:

competitor intelligence
review sentiment analysis
WhatsApp group digests
sales call proposals
client AIOS value proof
market opportunity reports

This is especially strong for AIBS because recurring intelligence reports can become recurring revenue products.

The highest-value first product candidate is:

Competitor Watch + Review Sentiment Monthly Report.

It is simple to understand, commercially useful, and easier to sell than vague “AI automation.”

Final Standard

The MWMS standard is:

Client intelligence reports must turn raw data into decision-ready business insight.
They must be source-aware, fresh, client-specific, validated where needed, and connected to action.
Reports should prove recurring value, not just display automation output.

Client reporting is not a side feature.

For AIBS, client intelligence reporting is a retention engine.

Change Log

Version: v1.0
Date: 2026-06-01
Author: MWMS HeadOffice

Change:

Created the MWMS Client Intelligence Report Automation Framework from the AI Automations by Jack client reporting, competitor intelligence, WhatsApp report, and proposal automation block.

Captured key workflow patterns including competitor website monitoring, website copy comparison, Google review scraping, review sentiment analysis, WhatsApp group intelligence reporting, Fireflies transcript-to-proposal automation, PDF report generation, email delivery, database-backed report history, and recurring client reporting.

Defined client intelligence reporting as a governed workflow that collects client-relevant data from approved sources, transforms it into structured intelligence, validates the output where needed, and delivers it as a recurring report, dashboard item, proposal, PDF, email, or action brief.

Added core report types: Competitor Intelligence Report, Review Sentiment Report, WhatsApp / Community Intelligence Report, Sales Call Intelligence Report, Proposal Intelligence Report, Market Opportunity Report, and AIOS Value Proof Report.

Added standard client intelligence workflow stages: Source Identified, Data Collected, Data Cleaned, Data Stored, Data Analysed, Intelligence Extracted, Report Generated, Report Validated, Report Delivered, Action Logged, and Learning Captured.

Added dedicated patterns for competitor intelligence, review sentiment, WhatsApp group intelligence, and sales call to proposal automation.

Added client report design standards, PDF report rule, dashboard report rule, email delivery rule, source traceability rule, data freshness rule, human review rules, client permission and data access rule, scraping governance, AI analysis governance, and report storage/history guidance.

Added future AIBS product package ideas including Competitor Watch Report, Reputation Intelligence Report, WhatsApp / Community Digest, Sales Call Proposal Generator, and AIOS Monthly Value Report.

Added Minimum Viable Client Intelligence Product recommendation: Competitor Watch + Review Sentiment Report.

Added Client Intelligence Workflow Build Path and Launch Readiness Checklist.

Added failure modes covering reports that are only summaries, invented competitor changes, stale scraped data, wrong-client data, sensitive group message exposure, unreviewed proposal sending, draft reports looking official, missing historical storage, unclear action paths, and report noise.

Mapped responsibilities across AIBS Brain, Automation Brain, Research Brain, Data Brain, Sales Brain, Customer Brain, Content Brain, Risk Brain, Compliance Brain, and SIT Brain.

Added related AI Employee capabilities: Client Intelligence Report Architect, Competitor Monitoring Agent, Review Sentiment Analyst, WhatsApp Intelligence Analyst, Sales Proposal Drafting Agent, Report Validation Agent, Client Value Proof Agent, and Report Delivery Agent.

Purpose of creation:

To establish client intelligence reporting as a governed AIBS capability and recurring-value automation layer, turning competitor data, review data, WhatsApp/community data, call transcripts, proposals, and AIOS activity into source-aware, decision-ready client reports that support trust, retention, and recurring revenue.