System: MWMS
Document Type: Framework
Authority Level: MCR Source Of Truth
Status: Draft For MCR
Version: v1.1
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-28
Source / Origin: AI Automations by Jack Client Reporting / Competitor Intelligence / WhatsApp Report / Proposal Automation / Company Researcher Block
MWMS Classification: Client Intelligence Reporting Framework / Recurring Value Automation / Competitive Monitoring System / Company Research And Enrichment System / Strategic Account Intelligence Support / 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, MWMS External Knowledge Engine And Reasoning Agent Separation Framework, MWMS Research Planning And Query Rewriting Standard, MWMS Research Synthesis Documentation And Distribution Framework, MWMS Source Visibility And Evidence Display Standard, MWMS High-Ticket AIOS Client Acquisition And Trophy Client Framework, MWMS Outbound Lead Enrichment And Cold Outreach Governance Framework
Source Evidence: The absorbed course block includes competitor monitoring workflows that scrape and compare website changes, gather review data, perform sentiment analysis, store findings, generate reports, and deliver results to clients. It also includes community intelligence reporting, transcript-to-proposal automation, recurring report generation, and a company-research workflow that first extracts a company’s own website claims before enriching the record through recent external sources, evidence checks, source diversity, recency, and concise executive synthesis.
Purpose
The purpose of the MWMS Client Intelligence Report Automation Framework is to define how MWMS designs, governs, automates, packages, validates, stores, and delivers client intelligence reports.
This framework exists because one of the strongest commercial opportunities in AIBS is not automation by itself.
It is automated intelligence delivery.
A client does not care that n8n, scraping tools, transcript tools, messaging platforms, PDF tools, databases, APIs, and language models are connected in the background.
A client cares about receiving useful intelligence that helps them:
understand competitors
understand a target company
improve offers
improve sales conversations
identify customer complaints
see market changes
track review sentiment
summarise internal discussions
create better proposals
improve follow-up
evaluate strategic accounts
make faster decisions
see value every week or month
This framework turns raw workflow ideas into a governed MWMS client intelligence capability.
The core purpose is:
Convert scattered company, client, market, competitor, conversation, review, community, and operational data into source-aware, evidence-classified, decision-ready intelligence reports.
This is a major AIBS recurring-value and client-acquisition opportunity.
Core Doctrine
The MWMS doctrine is:
Clients pay longer when value is visible, repeated, traceable, and decision-ready.
A one-time automation may impress a client once.
A recurring intelligence report can prove value every week or every month.
A company intelligence brief can improve outreach, qualification, proposals, audits, and strategic-account decisions before the first conversation.
Client intelligence reports should answer:
What changed?
What does the company say about itself?
What is externally supported?
What is uncertain?
What is contradicted?
What should I care about?
What opportunity exists?
What risk exists?
What should happen next?
What did the AIOS find?
Why should the client keep paying?
The strongest AIBS products will not only perform invisible backend tasks.
They will produce visible business intelligence.
Strategic Importance
This framework sits at the intersection of:
recurring revenue
client value proof
company research
strategic-account pursuit
lead enrichment
sales enablement
client qualification
AIOS dashboard and reporting layers
AIBS package design
competitor intelligence
customer intelligence
market research
automation delivery
client retention
proposal quality
The framework converts isolated workflow examples into 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 AI, creates a decision-ready report, validates the output where required, and delivers it to a client, business owner, sales operator, or internal Brain.
MWMS Definition
An MWMS Client Intelligence Report Automation is:
A governed reporting workflow that collects client-relevant information from approved sources, separates source evidence from interpretation, transforms the information into structured intelligence, validates the output where needed, and delivers it as a report, dashboard item, proposal, PDF, email, company brief, or action record.
Client Intelligence Is Not Generic Reporting
Generic reporting says:
Here is some data.
Client intelligence says:
Here is what was found, where it came from, what is supported, what remains uncertain, why it matters, what risk or opportunity it creates, and what action should be considered.
MWMS should not sell clients raw automation output.
MWMS should sell intelligence systems that produce useful business understanding.
MWMS Rule
A client intelligence report is not complete until it explains:
source
evidence status
meaning
limitation
recommended next action
Core Report Types
MWMS recognises the following client intelligence report types.
- Company Intelligence Snapshot
A concise company research report generated from a company’s own website and approved external sources.
May include:
company summary
core message
target audience
products
services
features
capabilities
positioning
commercial model
proof claims
pricing signals
technology signals
recent developments
external facts
contradictions
uncertainty
sales relevance
strategic-account relevance
recommended next research action
Use Case
Lead research, strategic-account preparation, discovery preparation, proposal preparation, audit preparation, partner research, client onboarding, and competitor analysis.
Rule
A Company Intelligence Snapshot must distinguish company-stated claims from externally supported facts.
- 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, ecommerce brands, affiliate campaigns, and AIBS clients.
Rule
Competitor intelligence must separate observed change from AI interpretation.
- 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, marketplaces, and service business reviews.
Rule
Review sentiment must preserve real customer language as evidence.
- Community Intelligence Report
A report that summarises approved 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
Use Case
Client groups, sales teams, support groups, communities, course groups, agency-client groups, and approved messaging environments.
Rule
Community intelligence reports must respect privacy, consent, access boundaries, and group ownership.
- 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
Use Case
AIBS sales calls, client discovery calls, consultant proposals, agency proposals, and onboarding summaries.
Rule
Sales call reports must not invent commitments, pricing, scope, or approvals.
- Proposal Intelligence Report
A report or proposal generated from conversation, intake, and approved research data.
May include:
executive summary
client problem
recommended solution
project scope
deliverables
timeline
pricing placeholder
assumptions
exclusions
supporting company intelligence
next steps
Use Case
AIBS proposal generation, automation packages, consulting, agency services, and onboarding.
Rule
AI may draft proposals, but commercial terms require human approval.
- Market Opportunity Report
A report that analyses market data for opportunities.
May include:
emerging trends
competitor gaps
customer language
underserved needs
offer opportunities
content angles
lead magnet ideas
campaign angles
product positioning ideas
Use Case
Research Brain, Content Brain, Affiliate Brain, Strategy Brain, and AIBS client strategy.
Rule
Opportunity reports must distinguish evidence from speculation.
- AIOS Value Proof Report
A report showing what a client’s AIOS 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
Value proof reports should make renewal easier by making value visible.
Evidence Classification Model
Every material finding should be classified as one of the following:
First-Party Claim
A statement made by the company on its own website or approved company material.
Externally Supported Fact
A finding supported by a credible external source.
Observed Fact
A directly observable website, product, review, pricing, or operational condition.
Historical Fact
A fact tied to a previous date or version.
Inference
A reasoned interpretation based on available evidence.
Recommendation
A proposed action or decision.
Unknown
Information that could not be confirmed.
Contradicted
A claim or finding challenged by credible contrary evidence.
Retired
A finding no longer considered current or usable.
MWMS Evidence Rule
A first-party company claim is not automatically an independently verified fact.
An inference is not a fact.
A recommendation is not evidence.
Unknown information must remain visible as unknown.
Contradictions must not be hidden.
First-Party Extraction And External Enrichment Model
The standard company research sequence is:
- Capture approved company URL.
- Extract visible first-party website content.
- Identify the company’s own statements.
- Summarise the core company message.
- Extract products, services, capabilities, audience, proof, pricing signals, and positioning.
- Identify claims requiring external verification.
- Search approved external sources.
- Collect recent, credible, relevant, and non-duplicative evidence.
- Compare first-party claims with external findings.
- Flag support, gaps, contradictions, and uncertainty.
- Generate a concise executive company brief.
- Preserve sources, timestamps, and evidence classification.
- Route the output into sales, proposals, outreach, audits, client reports, or strategic-account review.
Stage 1: Approved URL And Research Objective
Every company research workflow must define:
company name
approved URL
research purpose
intended recipient
required depth
report type
freshness requirement
decision being supported
Possible purposes include:
strategic-account research
lead qualification
competitor analysis
proposal preparation
audit preparation
client onboarding
market mapping
partnership assessment
Rule
Do not collect broad company data without a defined decision use.
Stage 2: First-Party Website Extraction
The workflow may extract:
homepage content
about content
product pages
service pages
pricing pages
feature pages
case studies
testimonials
FAQ content
contact information
legal and policy pages
publicly visible technical information
The extraction should identify:
core message
primary audience
problem addressed
promised outcomes
products and services
features and capabilities
proof claims
differentiation claims
pricing signals
calls to action
commercial model
Rule
The company website records what the company presents publicly.
It does not independently prove every claim.
Stage 3: Concise Company Summary
The first-pass company summary should explain:
what the company does
who it appears to serve
what it offers
its main positioning
its most important differentiators
The summary should remain concise.
Default executive summary limit:
35 to 75 words unless a longer format is required.
Rule
A concise summary should prioritise the most decision-relevant information.
It should not attempt to reproduce the website.
Stage 4: Core Feature And Capability Extraction
The workflow may extract five to ten core features or capabilities.
Each item should state:
feature or capability
business purpose
source location
evidence status
Avoid:
generic marketing language
duplicated features
unsupported interpretation
irrelevant detail
Rule
Feature extraction must remain tied to visible source content.
Stage 5: External Enrichment
External enrichment may examine:
recent news
press releases
credible industry publications
official registries
public product directories
reputable technology databases
public company profiles
review platforms
marketplaces
public social channels
public interviews
approved datasets
External enrichment should prioritise:
accuracy
recency
source quality
source diversity
relevance
non-redundancy
traceability
Rule
External enrichment should add information, not merely repeat the company website.
Stage 6: Claim Verification And Contradiction Check
The workflow should compare:
company claims
external evidence
current public conditions
historical records where relevant
Possible outcomes:
supported
partially supported
unsupported
outdated
contradicted
unable to verify
Rule
The system must not convert an unverified claim into a factual statement.
Stage 7: Uncertainty And Evidence Gap Handling
Evidence gaps may include:
missing pricing
unclear ownership
unclear customer size
unverified usage numbers
unclear product status
unclear geographic coverage
unclear implementation model
outdated claims
conflicting external information
The report should state:
what is unknown
why it matters
what source could resolve it
whether human research is required
Rule
Missing information must not be silently filled by AI.
Stage 8: Executive Company Brief
A Company Intelligence Snapshot may include:
Company Summary
Primary Audience
Core Offers
Core Features Or Capabilities
Positioning
Commercial Model
First-Party Claims
Externally Supported Facts
Recent Developments
Proof Signals
Risk Signals
Contradictions
Unknowns
Strategic Relevance
Recommended Next Action
Source Notes
Data Limitations
Rule
The brief must be concise enough for practical use before a sales call or decision.
Strategic-Account Research Support
Company intelligence may support the MWMS High-Ticket AIOS Client Acquisition And Trophy Client Framework.
The handoff may include:
company summary
target account identity
decision-maker context
observed business model
identified commercial opportunity
likely pain
relevant technology
current customer path
public proof
recent change
possible AIOS fit
evidence status
unknowns
recommended personalised value artifact
outreach relevance
research confidence
Rule
Research Brain and AIBS must not convert public company research into unsupported internal assumptions.
Core Workflow Pattern
The standard MWMS Client Intelligence Report workflow is:
- Purpose defined
- Source identified
- Permission checked
- Data collected
- Data cleaned
- Data stored
- Evidence classified
- Data analysed
- Intelligence extracted
- Contradictions and gaps checked
- Report generated
- Report validated
- Report delivered
- Action logged
- Learning captured
Stage 1: Purpose Defined
Ask:
What does the client or operator need to know?
What decision will this support?
How often is it needed?
What sources are required?
Who receives it?
What output format is appropriate?
Rule
No report should exist without a decision purpose.
Stage 2: Source Identified
Possible sources include:
company website
competitor website
Google Reviews
approved community or group
sales call transcript
CRM data
form intake
support tickets
email thread
Google Sheet
Airtable base
Supabase table
dashboard record
social comments
YouTube comments
scraped public pages
client documents
recent news
official registry
public product database
Rule
No report should begin without a clear source definition.
Stage 3: Permission Checked
Confirm:
source access
client consent
scraping risk
privacy rules
storage permission
report recipient
permitted output use
Rule
Data access must be permissioned before automation.
Stage 4: Data Collected
Data may be collected through:
n8n
webhooks
APIs
scrapers
RSS feeds
forms
Google Drive triggers
manual uploads
transcript APIs
approved messaging connections
review scrapers
CRM exports
database queries
Rule
Collection method must match source permissions, compliance, and client agreement.
Stage 5: Data Cleaned
Cleaning may include:
removing HTML
combining transcript sentences
splitting arrays
merging items
filtering irrelevant fields
removing duplicates
extracting message text
removing system noise
normalising dates
cleaning names and emails
separating source records
converting data into structured JSON
Rule
Clean data before analysis.
Messy input creates weak intelligence.
Stage 6: Data Stored
Possible storage includes:
Supabase
Airtable
Google Sheets
PostgreSQL
client CRM
report archive
event log
task table
dashboard table
Rule
Recurring reports require history.
Without history, the system cannot reliably detect change.
Stage 7: Evidence Classified
Each material finding should receive:
source type
source location
source date
evidence class
confidence level
validation status
Rule
Evidence classification must occur before client-facing synthesis.
Stage 8: 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
company positioning analysis
claim comparison
proposal section extraction
content idea extraction
action recommendation
Rule
Analysis must be tied to business meaning, not generic AI commentary.
Stage 9: Intelligence Extracted
Good intelligence answers:
What changed?
What is repeated?
What is unusual?
What is positive?
What is negative?
What is missing?
What is supported?
What is uncertain?
What is contradicted?
What opportunity appears?
What risk appears?
What should the client do?
What should MWMS do?
Rule
Extract insight, not only summary.
Stage 10: Contradictions And Gaps Checked
Check for:
claim conflict
date conflict
source conflict
missing evidence
stale source
duplicate evidence
unsupported numerical claim
unsupported recommendation
Rule
Material contradictions must be surfaced before report delivery.
Stage 11: Report Generated
Reports may be generated as:
dashboard card
Google Doc
HTML report
proposal
client brief
company snapshot
action list
Supabase record
MCR internal note
Rule
Format should match the use case.
Do not generate PDFs merely because the workflow can.
Stage 12: Report Validated
Validation may be required when reports involve:
competitor claims
company claims
client recommendations
proposal content
pricing
compliance-sensitive claims
scraped data
sentiment interpretation
public or customer data
personal data
strategic recommendations
Rule
Client-facing intelligence needs validation before trust.
Stage 13: Report Delivered
Delivery methods may include:
dashboard
client portal
Google Drive
Slack
approved messaging platform
CRM note
task assignment
HeadOffice Dashboard
Brain Room
AIBS client dashboard
Rule
Delivery must be logged.
Stage 14: Action Logged
Possible outcomes include:
client review
task creation
follow-up
proposal
issue escalation
idea parking
competitor watch
content brief
sales action
support update
strategic-account pursuit
further research
Rule
Reports should create decisions or actions, not dead documents.
Stage 15: Learning Captured
Learning may include:
better source selection
recurring client concerns
stronger recommendation patterns
weak data sources
false positives
sections clients ignore
sections clients value
new upsell opportunities
automation failures
source access issues
research gaps
contradiction patterns
Rule
Client intelligence reporting should feed Kaizen.
Competitor Intelligence Report Pattern
A mature competitor intelligence workflow may include:
- Client competitor list
- Website scrape
- Current copy extraction
- Previous version lookup
- Change comparison
- Review collection
- Review sentiment analysis
- Opportunity extraction
- Risk extraction
- Report generation
- PDF or dashboard generation
- Delivery
- Historical storage
Report Sections
Executive Summary
Competitors Monitored
Website Changes Detected
Offer And Positioning Changes
Review Sentiment Summary
Customer Complaint Themes
Customer Praise Themes
Competitor Weaknesses
Client Opportunities
Recommended Actions
Source Notes
Data Limitations
Rule
Competitor reports should focus on what changed and what the client can do about it.
Review Sentiment Report Pattern
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 data may support:
ad copy
landing page copy
offer improvement
service improvement
FAQ updates
content ideas
competitor weakness angles
sales objections
customer language mining
Rule
Do not over-polish review language before its meaning has been extracted.
Community Intelligence Pattern
Workflow:
- Identify approved group
- Confirm access and consent
- Pull approved messages
- Filter timeframe
- Combine and clean text
- Classify topics
- Extract issues and opportunities
- Generate report
- Validate sensitive information
- Deliver
Rule
Private communication data must remain isolated and permissioned.
Sales Call To Proposal Pattern
Workflow:
- Receive transcript
- Confirm participants and client
- Clean transcript
- Extract pain, goals, objections, decision-makers, and urgency
- Combine with approved company intelligence
- Draft proposal sections
- Add assumptions and exclusions
- Validate scope and claims
- Human approval
- Deliver and log
Rule
External company research may support a proposal but must not override what was actually agreed in the conversation.
Client Report Design Standard
A good report includes:
title
date
client name
reporting period
source summary
evidence classification
key findings
business meaning
recommended actions
risk notes
uncertainty
limitations
next steps
source traceability
Avoid:
vague AI summaries
unsupported claims
too much raw data
technical backend language
overconfident recommendations
hidden uncertainty
unattributed claims
unreviewed pricing or scope
bloated executive summaries
duplicated facts
Rule
Reports should be decision-ready and client-readable.
Concise Output Rule
Not every report should be long.
A concise company intelligence output may use:
35 to 75 word executive summary
five to ten core findings
three to five externally supported facts
three material unknowns or risks
one recommended next action
Use longer reports only when complexity requires it.
Rule
Brevity must come from prioritisation, not omission of material uncertainty.
PDF Report Rule
Before PDF generation:
confirm source data
validate AI summary
check client name
check dates
check recommendations
check sensitive data
check evidence status
check branding
check delivery recipient
check human approval requirement
Rule
PDF generation is not report approval.
A polished PDF can make wrong information appear official.
Dashboard Report Rule
Use dashboard reporting when:
data changes frequently
users need filters
users need approval controls
report findings become tasks
trends require monitoring
multiple reports require history
Use PDF reporting when:
a polished snapshot matters
the report is periodic
the report is sent by email
the report supports sales or proposals
a fixed historical record is needed
Rule
Choose dashboard or PDF based on use, not workflow convenience.
Email Delivery Rule
Before automated report email:
confirm recipient
confirm client
confirm attachment
confirm subject
confirm report version
confirm no wrong-client data
confirm human review where required
log send event
Rule
Automated client-facing delivery requires stronger review.
Source Traceability Rule
Reports should preserve:
source URL
source title
source type
source date
access date
review source
transcript ID
group source
scrape date
company or competitor name
source document name
database record ID
internal source log
Rule
MWMS should be able to answer:
Where did this come from?
Source Quality Rule
External sources should be evaluated for:
authority
directness
recency
relevance
independence
specificity
consistency
traceability
Promotional repetition across multiple websites does not necessarily equal independent confirmation.
Rule
Source quantity must not be confused with source quality.
Recency Rule
Time-sensitive findings must include:
source date
retrieval date
relevant period
staleness status
A current company brief should not rely on old evidence without clearly stating that it is historical.
Source Diversity Rule
Where material claims require verification, use diverse source types where possible.
Examples:
official company source
independent publication
public registry
review or user source
industry source
Rule
Multiple copies of the same original claim do not create genuine source diversity.
Non-Redundancy Rule
Research workflows should remove repeated information unless repetition itself is meaningful evidence.
The report should prioritise distinct findings.
Rule
A long list of duplicated facts creates false confidence and report bloat.
Contradiction Handling
When sources conflict:
preserve both positions
identify the source and date
state which source appears stronger
explain uncertainty
avoid false resolution
route material conflict for human review
Rule
The AI must not silently choose the most convenient version.
Data Freshness Rule
Every report should display freshness where relevant.
Freshness may include:
collection date
reporting period
last updated date
source publication date
historical comparison period
Rule
A source-aware report must also be time-aware.
Client Data Isolation
Each client must have isolated:
source records
report history
delivery records
access controls
report templates where required
client identifiers
Rule
Client data must never be mixed across reports.
Scraping Governance
Scraping workflows should define:
source
allowed pages
frequency
data collected
data excluded
storage rule
client visibility
fallback path
terms and risk review
source timestamp
Rule
Scraping is monitored data collection, not guaranteed infrastructure.
AI Analysis Governance
AI may analyse:
company websites
competitor changes
reviews
transcripts
messages
proposals
market signals
content themes
support issues
AI must not:
invent facts
exaggerate claims
imply certainty without evidence
create legal or compliance claims without review
make unsupported recommendations
treat sentiment as absolute truth
ignore source limitations
convert first-party claims into independent facts
Rule
AI interpretation must remain tied to evidence and limitation notes.
Report Storage And History
Store reports and source summaries so MWMS can track:
what changed
what was sent
what sources were used
what recommendations were made
whether the client acted
whether quality improved
whether patterns repeated
which claims changed
which contradictions were resolved
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
Package 1: Company Intelligence Snapshot
Client receives:
company summary
offer and capability summary
first-party claims
externally supported facts
recent developments
risk and uncertainty notes
strategic relevance
recommended next action
Package 2: Competitor Watch Report
Client receives:
competitor changes
review sentiment
customer complaint themes
opportunity gaps
recommended actions
Package 3: Reputation Intelligence Report
Client receives:
sentiment summary
common praise
common complaints
response opportunities
operational suggestions
content and ad language
Package 4: Community Digest
Client receives:
key topics
support issues
buying signals
unanswered questions
suggested follow-ups
Package 5: Sales Call Proposal Generator
Client receives:
call summary
extracted needs
company intelligence
proposal draft
follow-up email
PDF proposal
next action list
Package 6: AIOS Monthly Value Report
Client receives:
workflows run
tasks handled
reports created
leads processed
support questions answered
time saved estimate
improvement recommendations
Minimum Viable Client Intelligence Product
The highest-value recurring first product remains:
Competitor Watch plus Review Sentiment Report.
The highest-value pre-sales intelligence product is:
Company Intelligence Snapshot.
Rule
Start with the smallest report that proves useful value.
Client Intelligence Workflow Build Path
Stage 1: Define Report Purpose
Stage 2: Define Data Sources
Stage 3: Define Permission
Stage 4: Build Data Collection
Stage 5: Clean And Store
Stage 6: Classify Evidence
Stage 7: Analyse
Stage 8: Compare And Verify
Stage 9: Generate Report
Stage 10: Validate
Stage 11: Deliver
Stage 12: Log And Improve
Launch Readiness Checklist
Before launch, confirm:
client or internal use case is clear
report type is defined
research objective is defined
report frequency is defined
source data is approved
source access is permissioned
scraping risk reviewed
client data is isolated
data cleaning works
evidence classification works
first-party and external facts are separated
contradiction handling exists
unknowns remain visible
AI analysis prompt is tested
report format is approved
concise output limits are appropriate
human review requirement is defined
PDF or 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 Only A Summary
Correction:
Add evidence status, business meaning, and recommended action.
Failure Mode 2: AI Invents Competitor Or Company Facts
Correction:
Tie findings to source records and evidence classification.
Failure Mode 3: First-Party Claims Are Presented As Verified Facts
Correction:
Label company claims separately and externally verify material claims.
Failure Mode 4: External Research Repeats The Website
Correction:
Require non-redundant external enrichment.
Failure Mode 5: Contradictory Sources Are Hidden
Correction:
Surface the conflict and route it for review.
Failure Mode 6: Old Information Appears Current
Correction:
Display publication date, retrieval date, and freshness status.
Failure Mode 7: Report Is Too Long To Use
Correction:
Prioritise findings and apply concise output limits.
Failure Mode 8: Report Looks Official But Is Draft
Correction:
Add Draft, Reviewed, or Approved status.
Failure Mode 9: No Historical Storage
Correction:
Store source snapshots and prior reports.
Failure Mode 10: Client Does Not Know What To Do
Correction:
Add next actions and ownership recommendations.
Failure Mode 11: Report Becomes Noise
Correction:
Shorten, prioritise, and focus on material action.
Failure Mode 12: Company Research Creates Unsupported Sales Claims
Correction:
Separate research evidence from Sales Brain messaging and require claim review.
Application To AIBS Brain
AIBS Brain owns this framework because client intelligence reports can become recurring revenue, sales-enablement, and strategic-account products.
AIBS may package:
company intelligence snapshots
monthly intelligence subscriptions
AIOS value reports
competitor monitoring
reputation intelligence
sales proposal systems
community digest systems
customer insight systems
Rule
AIBS should sell decision-ready intelligence, not workflow diagrams.
Application To Automation Brain
Automation Brain owns:
triggers
APIs
webhooks
data collection
cleaning
evidence metadata handling
report generation
email delivery
storage
error handling
logs
maintenance
Rule
Every recurring report workflow must have failure handling and delivery logging.
Application To Research Brain
Research Brain owns:
research objective
source planning
source quality
source diversity
recency
competitor selection
company research
evidence interpretation
trend extraction
opportunity framing
source limitations
contradiction handling
Rule
Research-backed reports must separate evidence, inference, and recommendation.
Application To Data Brain
Data Brain should define:
report tables
source tables
company records
client IDs
source timestamps
evidence classifications
confidence fields
report history
metadata
storage schema
dashboard compatibility
export formats
Rule
Recurring intelligence requires structured historical data.
Application To Sales Brain
Sales Brain may use:
company intelligence snapshots
strategic-account research
lead intelligence reports
sales call reports
proposal sections
objection extraction
follow-up actions
client-ready recommendations
Rule
AI-generated sales material must be reviewed before delivery.
Sales Brain must not convert uncertain research into confident outreach claims.
Application To Content Brain
Content Brain may use approved intelligence for:
company-specific Loom scripts
executive opportunity briefs
proposal support
account-specific content
competitor analysis
customer-language assets
thought-leadership content
Rule
Content must preserve the evidence and claim boundaries supplied by Research Brain and AIBS.
Application To Customer Brain
Customer Brain may use reports to identify:
customer friction
support patterns
retention risk
value proof
renewal opportunities
service improvement
Rule
Client intelligence should improve the relationship, not merely increase report volume.
Application To Finance Brain
Finance Brain should review:
package economics
data and tool costs
research time
delivery effort
report margins
subscription viability
manual review burden
Rule
An intelligence product is only commercially useful if its recurring delivery remains profitable.
Application To Risk And Compliance Brain
Risk and Compliance review may be required for:
personal data
private messages
scraping
regulated claims
competitor allegations
confidential client information
automated external delivery
physical or strategic-account targeting data
Rule
Publicly accessible does not always mean unrestricted use.
Application To SIT Brain
SIT should test:
correct client data
correct company identity
correct sources
failed scrape handling
missing content
no external evidence found
contradictory evidence
wrong recipient
PDF generation failure
duplicate sends
sensitive data exposure
AI output quality
evidence labels
report formatting
delivery logging
Rule
A report workflow is not ready until it has been tested for wrong data, missing data, contradictory data, and failed delivery.
Related AI Employee Capabilities
Client Intelligence Report Architect
Company Research And Enrichment Agent
Competitor Monitoring Agent
Review Sentiment Analyst
Community Intelligence Analyst
Sales Proposal Drafting Agent
Strategic Account Research Agent
Report Validation Agent
Client Value Proof Agent
Report Delivery Agent
Evidence Classification Agent
Contradiction Review Agent
Future Expansion
This framework may later produce:
MWMS Company Intelligence Snapshot Template
MWMS Strategic Account Research Record
MWMS Competitor Intelligence Report Product Framework
MWMS Review Sentiment Intelligence Framework
MWMS Community 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
Recurring value comes from reporting and intelligence, not hidden automation alone.
The core pattern is:
Collect approved data
Clean it
Classify it
Compare it
Verify it
Analyse it
Create a report
Validate it
Deliver it
Create action
Repeat
This pattern supports:
company research
strategic-account intelligence
competitor intelligence
review sentiment
community digests
sales call proposals
client AIOS value proof
market opportunity reports
For recurring AIBS value, the strongest early product remains:
Competitor Watch plus Review Sentiment Monthly Report.
For client acquisition and pre-sales, the strongest supporting product is:
Company Intelligence Snapshot.
Final Standard
Client intelligence reports must turn raw data into decision-ready business insight.
They must be:
source-aware
time-aware
evidence-classified
client-specific
concise where appropriate
validated where required
connected to action
First-party claims must remain separate from externally supported facts.
Contradictions and unknowns must remain visible.
Reports should prove value, improve decisions, support strategic-account work, and preserve trustworthy historical intelligence.
Client reporting is not a side feature.
For AIBS, client intelligence reporting is a retention engine, sales-enablement system, and strategic-account research capability.
Change Log
Version: v1.1
Date: 2026-06-28
Author: MWMS HeadOffice
Change:
Expanded the framework with the Company Researcher course material.
Added:
Company Intelligence Snapshot report type
First-Party Extraction And External Enrichment Model
Concise Company Summary Standard
Core Feature And Capability Extraction
External Source Enrichment
Source Quality Rule
Source Diversity Rule
Recency Rule
Non-Redundancy Rule
Evidence Classification Model
Claim Verification
Contradiction Handling
Uncertainty And Evidence Gap Handling
Strategic-Account Research Support
Company Research To Sales Handoff
Concise Output Rule
Company Intelligence Product Package
Company Research And Enrichment Agent capability
Strategic Account Research Agent capability
Evidence Classification Agent capability
Contradiction Review Agent capability
Expanded the core workflow to include purpose definition, evidence classification, external verification, contradiction checking, and uncertainty preservation.
Added protection against first-party company claims being presented as independently verified facts.
Aligned the framework with the MWMS External Knowledge Engine And Reasoning Agent Separation Framework, MWMS Source Visibility And Evidence Display Standard, MWMS High-Ticket AIOS Client Acquisition And Trophy Client Framework, and MWMS Outbound Lead Enrichment And Cold Outreach Governance Framework.
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, community report, and proposal automation block.
Captured competitor website monitoring, review sentiment analysis, community intelligence reporting, transcript-to-proposal automation, PDF 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 report types, workflow stages, package ideas, launch readiness, governance, Brain applications, AI Employee capabilities, and future expansion.
END MWMS CLIENT INTELLIGENCE REPORT AUTOMATION FRAMEWORK v1.1
END OF FULL FILE OUTPUT