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, Sales Brain, Automation Brain, Compliance Brain, Risk Brain, Data 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 — Apollo / Appify / Anymailfinder / Cold Email Personalization Block
MWMS Classification: Outbound Lead Enrichment Framework / Cold Outreach Governance Standard / Prospect Research Automation / Sales AI Compliance Layer
Primary Brain: AIBS Brain
Supporting Brains: Sales Brain, Automation Brain, Data Brain, Research Brain, Compliance Brain, Risk Brain, Content Brain, SIT Brain, HeadOffice Brain
Related Pages: MWMS n8n Operating And Deployment Standard, MWMS Lead Intake Qualification And Follow-Up Automation Framework, MWMS Client Communication Automation Framework, MWMS Client Intelligence Report Automation Framework, MWMS AI Tool Permission And Access Framework, MWMS AI Automation Security And Risk Checklist, MWMS AI Agent Operations Core, MWMS AI Agent Memory And Context Framework, MWMS Supabase RAG And Vector Memory Framework, MWMS Automation Build Planning Framework, MWMS Automation Client Demo And Handover Framework
Purpose
The purpose of the MWMS Outbound Lead Enrichment And Cold Outreach Governance Framework is to define how MWMS should evaluate, govern, automate, and safely use outbound lead enrichment and cold outreach workflows.
This framework exists because outbound automation can be commercially powerful but also risky.
The absorbed course block shows workflows using tools and patterns such as:
- Apollo prospect filtering
- Appify scraping or lead extraction
- Google Sheets lead handling
- AI-personalized cold email generation
- company and job-title personalization
- case-study-based outreach
- missing email enrichment
- Anymailfinder email discovery
- LinkedIn/domain-based routing
- automated lead data cleanup
These workflows can help businesses find prospects and create personalized outreach faster.
But outbound automation touches sensitive areas:
- personal data
- scraped data
- email deliverability
- spam law
- platform terms
- cold email compliance
- brand reputation
- inaccurate enrichment
- false personalization
- mass outreach risk
Therefore, MWMS must treat outbound automation as a governed sales system, not a growth hack.
Core Doctrine
The MWMS doctrine is:
Outbound automation must improve relevance, research quality, and follow-up discipline without becoming spam, scraping abuse, or uncontrolled personal-data processing.
Outbound systems should never be built around the idea of blasting as many people as possible.
The MWMS standard is:
- better targeting
- better fit
- better data quality
- better relevance
- better personalization
- better compliance
- better human review
- better deliverability control
- better logging
- better learning from outcomes
Cold outreach should be treated as a precision system, not a volume weapon.
Strategic Importance
This framework is strategically important because outbound lead generation may become useful for:
- AIBS client acquisition
- MWMS partner outreach
- consultant outreach
- B2B service offers
- competitor-based prospecting
- niche market validation
- lead research
- sales campaign testing
- client lead generation packages
However, this area must be handled carefully.
Outbound can create fast opportunities, but it can also damage trust if done badly.
AIBS should not position itself as a spam automation business.
AIBS should position outbound systems as:
- research-backed prospecting
- carefully filtered outreach
- permission-aware follow-up
- evidence-based personalization
- controlled test campaigns
- human-reviewed messaging
- compliant lead handling
Definition
Outbound Lead Enrichment is the process of collecting, cleaning, completing, and improving prospect records so they can be evaluated and contacted appropriately.
Cold Outreach Automation is the process of generating and sending outreach messages to prospects who have not directly requested contact.
MWMS Definition
An MWMS Outbound Lead Enrichment And Cold Outreach System is:
A governed B2B prospecting workflow that collects approved prospect data, enriches missing fields where appropriate, evaluates prospect fit, generates compliant personalized outreach, requires review where needed, logs activity, and learns from responses and outcomes.
Scope
This framework applies to workflows involving:
- Apollo prospect data
- Appify scraping or extraction
- Anymailfinder email enrichment
- LinkedIn profile references
- company domain lookup
- website scraping
- Google Sheets lead lists
- CRM lead imports
- AI-generated cold email
- personalized outbound messages
- case-study-based outreach
- decision-maker discovery
- prospect scoring
- lead enrichment routing
- outbound follow-up sequences
- sales prospecting automation
- AIBS client lead-generation packages
This framework applies before MWMS or a client uses automation to contact prospects.
Core Workflow Pattern
The standard MWMS outbound workflow is:
- Target market defined
- Prospect source selected
- Lead data collected
- Data cleaned
- Missing fields enriched
- Prospect fit evaluated
- Compliance reviewed
- Message personalized
- Human review applied where required
- Outreach sent or queued
- Response tracked
- Learning captured
Stage 1: Target Market Defined
Outbound begins with defining the target.
Possible criteria:
- industry
- location
- business size
- job title
- revenue range
- technology used
- pain point
- service need
- competitor used
- recent trigger
- hiring signal
- website weakness
- review weakness
- offer fit
Rule
Do not collect leads before defining who should and should not be contacted.
Stage 2: Prospect Source Selected
Possible sources include:
- Apollo
- company websites
- Google Maps
- review platforms
- public directories
- CRM exports
- purchased/permissioned lists
- event attendee lists where permitted
- Appify actors
- search results
- public business databases
Rule
Prospect source must be reviewed for legality, platform terms, data quality, and business fit.
Stage 3: Lead Data Collected
Lead records may include:
- name
- role/title
- company
- website
- LinkedIn URL
- company domain
- phone if appropriate
- location
- industry
- source
- source URL
- company context
- trigger reason
- data collection date
Rule
Collect only what is needed for legitimate prospecting.
Stage 4: Data Cleaned
Outbound data is often messy.
Cleaning may include:
- removing duplicates
- standardizing names
- standardizing company names
- extracting domains
- validating URLs
- removing invalid rows
- removing irrelevant titles
- removing missing companies
- separating personal and company fields
- normalizing job titles
- filtering by geography
- filtering by company type
Rule
Dirty lead data creates bad personalization, poor deliverability, and compliance risk.
Clean before outreach.
Stage 5: Missing Fields Enriched
The absorbed block shows email enrichment using tools like Anymailfinder, with routing depending on whether LinkedIn URL, domain, or other identifiers are available.
Missing enrichment may include:
- finding company domain
- finding business email
- verifying email
- identifying decision maker
- adding company website
- adding role context
- adding LinkedIn URL
- adding company description
Rule
Enrichment should complete useful business fields, not create invasive profiles.
Stage 6: Prospect Fit Evaluated
Not every lead should be contacted.
Prospect fit may be evaluated using:
- role fit
- company fit
- niche fit
- service fit
- location fit
- trigger fit
- budget likelihood
- pain relevance
- decision-maker likelihood
- compliance risk
- deliverability risk
Rule
Outbound quality improves when weak-fit leads are removed before messaging.
Stage 7: Compliance Reviewed
Compliance review is required before outreach.
Review should consider:
- jurisdiction
- business-to-business context
- consent requirements
- legitimate interest where applicable
- unsubscribe requirements
- sender identity
- truthful subject lines
- personal data handling
- opt-out storage
- suppression lists
- platform terms
- scraping risk
- third-party enrichment terms
- email deliverability rules
Rule
No outbound system should be launched without compliance review.
Stage 8: Message Personalized
AI may generate personalized cold emails based on:
- company context
- prospect role
- website observation
- industry pain point
- relevant case study
- public business information
- service fit
- trigger event
- review pattern
- competitor gap
Personalization must be truthful.
Avoid fake familiarity.
Avoid pretending to know something that is not verified.
Rule
Personalization must be evidence-based, not invented.
Stage 9: Human Review Applied
Human review is required when:
- campaign is new
- message uses scraped data
- message references personal details
- message makes performance claims
- case study claims are used
- compliance risk is unclear
- sending volume is high
- sender reputation matters
- client brand is involved
- legal jurisdiction is uncertain
Rule
Human review protects brand trust before automation scales.
Stage 10: Outreach Sent Or Queued
Outreach may be:
- manually reviewed and sent
- queued in CRM
- sent through email platform
- sent through approved outreach system
- assigned to sales rep
- scheduled in sequence
Rule
Sending should be controlled, rate-limited, logged, and opt-out compliant.
Stage 11: Response Tracked
Track:
- sent
- opened if available and permitted
- replied
- bounced
- unsubscribed
- positive response
- negative response
- meeting booked
- not interested
- complaint
- spam issue
Rule
Outbound systems must learn from replies, bounces, and complaints.
Stage 12: Learning Captured
Use outcomes to improve:
- targeting
- lead source quality
- subject lines
- personalization
- offer angle
- message length
- case study choice
- follow-up timing
- compliance controls
- suppression lists
Rule
Outbound is an experiment system.
Do not scale without learning.
Standard Prospect Schema
MWMS should use a standard prospect schema.
Prospect ID:
Source:
Source URL:
Collection Date:
First Name:
Last Name:
Job Title:
Company:
Company Domain:
Company Website:
LinkedIn URL:
Email:
Email Status: Unknown / Found / Verified / Invalid / Bounced
Location:
Industry:
Company Size:
Trigger Reason:
Personalization Evidence:
Fit Score:
Fit Reason:
Compliance Status:
Outreach Status:
Opt-Out Status:
Suppression Status:
Message Draft:
Human Review Status:
Sent Date:
Response Status:
Notes:
Rule
Prospect records must include source, fit reason, and outreach status.
Lead Source Governance
Different lead sources carry different risk.
Apollo
Useful for:
- B2B prospect filtering
- job title targeting
- company search
- decision-maker discovery
Risks:
- data accuracy
- platform terms
- over-exporting
- compliance
- cold outreach misuse
Rule
Apollo data should be filtered tightly and used responsibly.
Appify / Scraping Tools
Useful for:
- extracting public business data
- scraping review sources
- pulling website data
- exporting structured records
Risks:
- platform terms
- scraping restrictions
- broken actors
- stale data
- IP/blocking
- personal data capture
- overcollection
Rule
Scraping tools require source review and collection limits.
Anymailfinder / Email Enrichment
Useful for:
- finding missing B2B emails
- verifying likely email addresses
- completing prospect records
Risks:
- inaccurate emails
- personal data concerns
- deliverability risk
- overuse
- non-business email capture
Rule
Email enrichment must prioritize business relevance and verification.
LinkedIn / Profile Data
Useful for:
- role confirmation
- decision-maker fit
- personalization context
Risks:
- platform terms
- scraping restrictions
- personal data sensitivity
- fake personalization
Rule
Use LinkedIn/profile data carefully and avoid pretending personal familiarity.
Company Website
Useful for:
- business context
- service fit
- personalization evidence
- offer relevance
- trigger identification
Risks:
- stale pages
- AI misinterpretation
- unsupported assumptions
Rule
Website-based personalization must be based on observable evidence.
Personalization Governance
AI-personalized outreach can be useful.
It can also become creepy, inaccurate, or fake.
Good Personalization
Good personalization references:
- company type
- public website observation
- relevant business problem
- role-relevant pain point
- industry-specific issue
- public case study relevance
- clear reason for outreach
Bad Personalization
Bad personalization includes:
- pretending to know the person
- overusing personal details
- making assumptions about problems
- referencing scraped private data
- false compliments
- fake urgency
- false scarcity
- unsupported claims
- overly long AI-written messages
Rule
Personalization should show relevance, not surveillance.
Cold Email Message Standard
A good cold email should be:
- short
- clear
- relevant
- truthful
- specific
- low-pressure
- compliant
- easy to opt out of
- aligned to recipient role
- based on evidence
- focused on one next step
Suggested Structure
Subject: Clear and non-deceptive
Opening: Relevant reason for contact
Problem / Observation: Short and evidence-based
Value Proposition: What can help
Proof / Case Study: Only if real and approved
Call To Action: Simple next step
Opt-Out: Clear where required
Rule
Cold email should create a conversation, not force a sale.
Case Study Use Rule
The absorbed workflow references case-study-style personalization.
Case studies are powerful, but they must be true.
Before using a case study, confirm:
- client/result is real
- permission to mention exists
- result is not exaggerated
- claim is specific
- context is not misleading
- no guaranteed result is implied
- industry relevance is clear
Rule
Case studies must be approved before automated use.
Compliance Requirements
Outbound compliance depends on jurisdiction and channel.
MWMS must consider:
- Australia Spam Act
- CAN-SPAM for US
- GDPR / PECR where EU/UK data is involved
- CASL for Canada
- platform terms
- data protection rules
- unsubscribe handling
- sender identification
- suppression lists
- privacy policy
- lawful basis where relevant
- client responsibility
- recordkeeping
Rule
Outbound systems must be designed to comply with the strictest relevant jurisdiction where practical.
Consent And Opt-Out Rules
Cold outreach must include opt-out handling.
MWMS should define:
- how opt-outs are captured
- where suppression is stored
- how future sends are blocked
- how client sees opt-out status
- who manages suppression lists
- how manual sends are checked
- how unsubscribe wording appears
- what happens after a complaint
Rule
An opt-out must stop future outreach.
Deliverability Governance
Cold outreach can damage domain reputation.
Deliverability governance should consider:
- sending domain
- warm-up
- volume limits
- bounce rate
- spam complaints
- verified emails
- sequencing speed
- content quality
- subject line truthfulness
- unsubscribe handling
- domain authentication
- sender reputation
Rule
Do not scale outbound before deliverability is stable.
Human Review Gates
Human review is required before:
- first campaign launch
- using new data source
- using new email template
- sending to large batch
- using case study claims
- referencing scraped observations
- sending from client domain
- using enriched personal data
- operating in unfamiliar jurisdiction
- increasing volume
Rule
Cold outreach should begin in reviewed mode.
Outreach Experimentation Rule
Outbound should be treated as an experiment.
Each campaign should define:
- target segment
- hypothesis
- offer angle
- message version
- sample size
- send limit
- success metric
- stop condition
- complaint threshold
- learning capture
Rule
Do not scale an outbound campaign without response data and risk review.
Outreach Metrics
Track:
- leads collected
- leads enriched
- valid emails found
- invalid emails
- bounce rate
- open rate where appropriate
- reply rate
- positive reply rate
- negative reply rate
- opt-out rate
- complaint rate
- booked calls
- conversion rate
- cost per qualified response
- source quality
- enrichment success rate
Rule
Outreach metrics should measure quality, not just volume.
Data Storage Rules
Prospect data should be stored with:
- source
- date collected
- consent/legitimate-interest notes where relevant
- outreach status
- opt-out status
- suppression status
- enrichment status
- review status
- deletion rules
Rule
Outbound lead data should not be stored forever without reason.
Suppression List Rule
Every outbound system needs suppression logic.
Suppression should include:
- unsubscribed contacts
- bounced emails
- complained contacts
- do-not-contact domains
- existing clients where inappropriate
- competitors where inappropriate
- internal team addresses
- previously rejected prospects
Rule
Suppression lists must be checked before sending.
Client Package Models
This framework can support several AIBS packages.
Package 1: B2B Prospect Research System
Collects and enriches prospects without automatically sending outreach.
Lower risk.
Good first step.
Package 2: AI Personalized Outreach Drafting System
Creates reviewed drafts for sales teams.
Medium risk.
Human sends or approves.
Package 3: Cold Outreach Campaign Assistant
Builds segmented campaigns, drafts messages, tracks responses, and manages suppression.
Higher risk.
Needs compliance review.
Package 4: Decision-Maker Discovery System
Finds likely decision-makers and missing email data for approved target accounts.
Medium risk.
Package 5: Outbound Experimentation Dashboard
Tracks campaign hypotheses, outreach metrics, responses, and stop conditions.
Medium risk.
Minimum Viable Outbound Product
Recommended MVP:
B2B Prospect Research And Reviewed Outreach Draft System
Inputs:
- target niche
- location
- job titles
- approved source
- offer angle
- case study if approved
Outputs:
- cleaned prospect sheet
- enriched fields where permitted
- fit score
- personalization evidence
- AI-drafted email
- human review status
- no automatic sending
Why this is the safest MVP:
- creates value
- avoids immediate spam risk
- allows human judgment
- builds prospect intelligence
- can later add controlled sending
MWMS Rule
Start with research and reviewed drafts before automated sending.
Build Path
Stage 1: Define Target
Define ideal prospect, excluded prospects, and reason for outreach.
Stage 2: Select Source
Choose approved lead source.
Review compliance and platform risk.
Stage 3: Collect Data
Gather only necessary business fields.
Stage 4: Clean And Normalize
Deduplicate and standardize records.
Stage 5: Enrich Missing Fields
Use enrichment only where appropriate.
Stage 6: Score Fit
Determine whether the prospect matches the offer.
Stage 7: Generate Draft
Create evidence-based personalized email.
Stage 8: Human Review
Review claims, tone, source, and compliance.
Stage 9: Send Or Queue
Only send if approval and suppression checks pass.
Stage 10: Track Results
Log responses, opt-outs, bounces, and learnings.
Launch Readiness Checklist
Before launching outbound automation, confirm:
- target segment defined
- excluded segment defined
- source approved
- platform terms considered
- jurisdiction considered
- prospect schema defined
- data cleaned
- duplicates removed
- email verification considered
- suppression list exists
- opt-out process exists
- compliance review completed
- personalization evidence stored
- case studies approved
- message template reviewed
- human review gate active
- sending volume limited
- bounce threshold defined
- complaint threshold defined
- metrics tracked
- stop condition defined
- data retention rule defined
- client approval obtained if client-facing
- no automatic high-volume sending without test
Failure Modes
Failure Mode 1: Scrape First, Think Later
Large prospect list is scraped without target clarity.
Correction:
Define target and exclusions first.
Failure Mode 2: Personalization Is Fake
AI invents or exaggerates relevance.
Correction:
Require personalization evidence field.
Failure Mode 3: Enriched Email Is Wrong
Email discovery finds inaccurate contact.
Correction:
Verify where possible and track bounce rate.
Failure Mode 4: No Suppression List
Opted-out contacts are contacted again.
Correction:
Create suppression logic before sending.
Failure Mode 5: Cold Email Violates Rules
Campaign ignores jurisdiction or unsubscribe requirements.
Correction:
Compliance review before launch.
Failure Mode 6: Too Much Volume Too Soon
Domain reputation is damaged.
Correction:
Start small and monitor bounce/complaint rates.
Failure Mode 7: Case Study Claims Unsupported
AI uses fake or unapproved proof.
Correction:
Use only approved case studies.
Failure Mode 8: Client Brand Damaged
Poor outreach sent from client domain.
Correction:
Human review and controlled pilot required.
Failure Mode 9: Data Stored Indefinitely
Prospect data kept without reason.
Correction:
Define retention and deletion rules.
Failure Mode 10: Metrics Focus On Volume
Campaign celebrates sends instead of replies or conversions.
Correction:
Track quality metrics and business outcomes.
Application To AIBS Brain
AIBS Brain owns this framework because outbound systems may become client packages.
AIBS should package outbound carefully as:
- prospect research
- lead enrichment
- reviewed outreach drafting
- outbound experimentation
- sales intelligence
AIBS should not sell spam systems.
AIBS Rule
Outbound automation must be positioned as quality prospecting, not mass blasting.
Application To Sales Brain
Sales Brain owns targeting, offer angle, message quality, and follow-up logic.
Sales Brain should define:
- ideal prospect
- exclusions
- offer angle
- case study use
- call-to-action
- qualification path
- response handling
- sales task routing
Sales Rule
Outbound should create qualified conversations, not vanity send volume.
Application To Automation Brain
Automation Brain owns workflow design.
Automation Brain should govern:
- data extraction
- enrichment routing
- Google Sheets/Supabase storage
- message drafting
- sending controls
- suppression checks
- response tracking
- error handling
- logs
Automation Rule
Sending automation must be more tightly governed than research automation.
Application To Data Brain
Data Brain owns prospect data structure and retention.
Data Brain should define:
- prospect schema
- source metadata
- enrichment status
- suppression status
- consent/legitimate interest notes
- opt-out data
- retention period
- deletion rules
Data Rule
Prospect data is sensitive business data and must be governed.
Application To Research Brain
Research Brain supports source quality and prospect fit.
Research Brain should check:
- source reliability
- market fit
- niche relevance
- trigger signals
- company context
- competitor references
- public evidence
Research Rule
Research quality determines outreach relevance.
Application To Content Brain
Content Brain may help with:
- email templates
- outreach angles
- subject lines
- case study copy
- follow-up sequences
- objection handling
- tone guidelines
Content Rule
Outbound copy should be concise, truthful, and role-relevant.
Application To Compliance And Risk Brain
Compliance and Risk Brain must review:
- lead sources
- scraping
- enrichment
- cold email rules
- opt-out
- data storage
- jurisdiction
- platform terms
- case study claims
- sending volume
- client brand risk
Compliance Rule
Outbound workflows require compliance review before sending.
Application To SIT Brain
SIT Brain should test:
- duplicate removal
- missing email
- bad domain
- invalid LinkedIn URL
- enrichment failure
- suppression match
- opt-out handling
- email draft quality
- wrong personalization
- case study claim use
- batch limit
- error path
- client data isolation
SIT Rule
Outbound workflows need quality and compliance tests before launch.
Related AI Employee Capabilities
Prospect Research Agent
Identifies and structures potential target prospects.
Lead Enrichment Agent
Finds missing business fields where permitted.
Prospect Fit Scoring Agent
Evaluates whether prospects match the offer and target market.
Personalization Evidence Agent
Finds safe, public, relevant personalization evidence.
Cold Email Drafting Agent
Creates concise, compliant, evidence-based outreach drafts.
Outreach Compliance Reviewer
Checks message, data source, opt-out, jurisdiction, and claims.
Suppression List Guard Agent
Blocks outreach to unsubscribed, bounced, complained, or excluded prospects.
Outbound Experiment Analyst
Tracks results and recommends whether to continue, adjust, or stop.
Future Expansion
This framework may later produce:
- MWMS Cold Email Compliance Checklist
- MWMS Prospect Data Schema Standard
- MWMS Outbound Experimentation Framework
- MWMS AI Personalized Outreach Drafting Standard
- MWMS Lead Enrichment Tool Permission Standard
- MWMS Suppression List Governance Standard
- MWMS B2B Prospect Research Product Framework
These should only be created when outbound systems become active build or client-package priorities.
Strategic Summary
This block is valuable because it shows how AI and automation can improve outbound prospecting.
However, MWMS must not copy the “scrape and blast” mindset.
The real value is:
targeted prospecting, cleaner data, better fit scoring, safer enrichment, evidence-based personalization, reviewed outreach, and learning from outcomes.
The best starting product is not automatic cold email blasting.
The best starting product is:
B2B Prospect Research And Reviewed Outreach Draft System.
This gives clients useful sales intelligence while keeping compliance and reputation risk under control.
Final Standard
The MWMS standard is:
Outbound automation must be targeted, evidence-based, compliant, reviewed, logged, and measured by quality outcomes.
Prospect data must be sourced responsibly, enriched carefully, personalized truthfully, and suppressed immediately when opt-out or exclusion applies.
Start with research and reviewed drafts before automated sending.
Outbound is not a volume game.
For MWMS, outbound is a governed sales intelligence system.
Change Log
Version: v1.0
Date: 2026-06-01
Author: MWMS HeadOffice
Change:
Created the MWMS Outbound Lead Enrichment And Cold Outreach Governance Framework from the AI Automations by Jack Apollo, Appify, Anymailfinder, decision-maker discovery, email enrichment, and cold email personalization block.
Captured the core outbound workflow pattern: target market defined → prospect source selected → lead data collected → data cleaned → missing fields enriched → prospect fit evaluated → compliance reviewed → message personalized → human review applied → outreach sent or queued → response tracked → learning captured.
Defined outbound lead enrichment and cold outreach as a governed B2B prospecting workflow that collects approved prospect data, enriches missing fields where appropriate, evaluates prospect fit, generates compliant personalized outreach, requires review where needed, logs activity, and learns from responses and outcomes.
Added Standard Prospect Schema covering source, collection date, person/company fields, LinkedIn URL, company domain, email status, trigger reason, personalization evidence, fit score, compliance status, outreach status, opt-out status, suppression status, message draft, human review status, response status, and notes.
Added governance sections for lead sources including Apollo, Appify/scraping tools, Anymailfinder/email enrichment, LinkedIn/profile data, and company websites.
Added Personalization Governance, Cold Email Message Standard, Case Study Use Rule, Compliance Requirements, Consent And Opt-Out Rules, Deliverability Governance, Human Review Gates, Outreach Experimentation Rule, Outreach Metrics, Data Storage Rules, and Suppression List Rule.
Added client package models including B2B Prospect Research System, AI Personalized Outreach Drafting System, Cold Outreach Campaign Assistant, Decision-Maker Discovery System, and Outbound Experimentation Dashboard.
Added Minimum Viable Outbound Product recommendation: B2B Prospect Research And Reviewed Outreach Draft System.
Added Build Path, Launch Readiness Checklist, and failure modes covering scraping before strategy, fake personalization, wrong enriched email, missing suppression list, compliance violations, too much sending volume, unsupported case study claims, client brand damage, indefinite data storage, and volume-focused metrics.
Mapped responsibilities across AIBS Brain, Sales Brain, Automation Brain, Data Brain, Research Brain, Content Brain, Compliance Brain, Risk Brain, and SIT Brain.
Added related AI Employee capabilities: Prospect Research Agent, Lead Enrichment Agent, Prospect Fit Scoring Agent, Personalization Evidence Agent, Cold Email Drafting Agent, Outreach Compliance Reviewer, Suppression List Guard Agent, and Outbound Experiment Analyst.
Purpose of creation:
To establish outbound lead enrichment and cold outreach as a governed, compliance-aware AIBS capability focused on quality prospecting, safe data enrichment, truthful personalization, reviewed messaging, opt-out control, deliverability protection, and measurable sales outcomes.