Skip to content

ozwilder/Product-Messaging

Folders and files

NameName
Last commit message
Last commit date

Latest commit

Β 

History

1 Commit
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 

Repository files navigation

Product-Messaging: Clear Messaging Agent

An interactive coaching tool that enforces disciplined product messaging through the Vanilla Template structure. Built to challenge weak claims, demand evidence (RTB), and produce rigorous 1-page messaging frameworks.

🎯 What It Does

The Clear Messaging Agent is a non-negotiable messaging coach that:

βœ… Enforces the Vanilla Template β€” 8-section structure: Bottom Line β†’ Roadmap β†’ WIIFM β†’ Why You β†’ Disarm Concerns β†’ RTB β†’ Specifics β†’ CTA

βœ… Challenges Vague Claims β€” Detects weak language ("helps", "improves", "better") and demands specificity with numbers, personas, and timeframes

βœ… Validates Evidence β€” Refuses weak Reasons to Believe (RTB). Evidence must include sources, stats, or customer validation

βœ… Requires Deliberation β€” "Continue" enforcement forces one question at a time, preventing rushing through sections

βœ… Generates Actionable Output β€” Produces 1-page messaging framework + JSON export for stakeholder review

πŸš€ Quick Start

Installation

# Clone repository
git clone https://github.com/ozwilder/Product-Messaging.git
cd Product-Messaging

# No external dependencies required (Python 3.8+)

Run Interactive Session

python src/clear_messaging_agent.py interactive

What You'll Answer

  1. Key Message β€” What's the news you're announcing?
  2. Value Articulation β€” WIIFM, competitive advantage, customer concerns
  3. Evidence & RTB β€” Statistics, customer feedback, analyst validation
  4. Template Completion β€” Bottom line, roadmap, specifics, CTA
  5. Output β€” 1-page framework + JSON export

Example Session

🎯 CLEAR MESSAGING AGENT - Interactive Messaging Coach

Step 1: SETUP
❓ What is the key message?
β†’ Microsoft announces the world's first AI security scanner...

❓ Who is your target audience?
β†’ Security leaders, AppSec teams, developers

βœ“ Framework created. Let's build your messaging.

Step 2: ARTICULATE YOUR VALUE
❓ What's In It For Me (WIIFM)?
β†’ Advanced detection that catches zero-days other scanners miss

⚠️ FEEDBACK: Too vague. What's the actual data?...

Type 'continue' to move to the next section: continue

πŸ“‹ Template Structure (Vanilla Template)

1. Bottom Line (1-2 sentences)

The single most important thing to remember.

2. Roadmap

Evolution, timeline, what's next.

3. WIIFM (What's In It For Me)

Why should this specific audience care? Benefits per persona.

4. Why You (Competitive Advantage)

What makes this special? Why now? Unique differentiators.

5. Disarm Concerns (Objection Handlers)

What worries customers? How do you overcome them?

6. RTB (Reasons to Believe)

Evidence-backed proof:

  • Statistics (market data, benchmarks)
  • Customer Feedback (testimonials with org context)
  • Analyst Reports (Gartner, Forrester validation)
  • KPIs (measurable business metrics)

7. Specifics (Tactical Details)

Pricing, availability, timeline, deployment model.

8. CTA (Call To Action)

What should the audience do NOW? Registration link? Demo request? Sales contact?

πŸ” Claim Validation Rules

The agent automatically challenges answers containing vague language:

Vague Language Challenge Expected Fix
"Helps save time" What's the actual time saved? "Reduces scanning time by 70% (3 hrs β†’ 45 min)"
"Better accuracy" Better than what? By how much? "99.2% accuracy vs 92% industry average"
"Enterprise-grade" What does that mean operationally? "SOC 2 certified, 99.99% uptime SLA"
"First" or "Only" What proof backs this? "Verified by [analyst/source]" + evidence link
"Advanced AI" How is it different? Training data? "Trained on 20+ years of Windows security data"

πŸ“€ Output Formats

1-Page Summary (Console Output)

PRODUCT: MDASH
AUDIENCE: CISOs, AppSec Teams, Developers

## Bottom Line
Microsoft's AI security scanner detects zero-day vulnerabilities...

## WIIFM
Catch threats competitors miss with <1% false positives...

[... 6 more sections ...]

JSON Export

{
  "product": "MDASH",
  "audience": "Security leaders, AppSec teams, developers",
  "framework": {
    "Bottom Line": "...",
    "Roadmap": "...",
    "What's In It For Me": "...",
    ...
  },
  "created_at": "2026-05-31T09:30:00"
}

πŸŽ“ How to Use This Tool

For Product Managers

Create messaging that lands with confidence β€” no more weak claims that executives challenge. Each section is battle-tested before you present.

For Marketing Teams

Generate structured messaging frameworks that sales can inherit. JSON export makes it easy to distribute across tools.

For Sales Teams

Use the objection handlers (Disarm Concerns section) as battle cards. CTA section gives you a clear ask every time.

For Leadership Reviews

Share the 1-page output in your next meeting. Evidence section proves your claims aren't opinions.

πŸ’‘ Pro Tips

  1. Answer One Question at a Time β€” Don't rush. The agent enforces this deliberately.
  2. Use Real Data β€” "~1% false positive rate" vs "very low false positives". Numbers win.
  3. Know Your Personas β€” The RTB section should call out which persona cares about each claim.
  4. Anticipate Objections β€” The Disarm Concerns section is where you win or lose customer trust.
  5. Test Your CTA β€” Make sure it's a single, clear action. Not "learn more and sign up and download specs".

πŸ›  Customization

Extend Evidence Types

Edit EvidenceType enum to add custom validation types:

class EvidenceType(Enum):
    STATISTIC = "statistic"
    CUSTOMER_FEEDBACK = "customer_feedback"
    ANALYST = "analyst"
    KPI = "kpi"
    PATENT = "patent"  # Add custom type

Modify Vague Indicators

Update VAGUE_INDICATORS list in ClearMessagingAgent to match your industry:

VAGUE_INDICATORS = [
    "helps", "improves", "better", "advanced", 
    "blockchain-enabled",  # Add custom
    "synergistic"  # Add custom
]

πŸ“š Example Use Cases

Launch Announcement

Create messaging for a new product launch with consistent narrative across all stakeholders.

Competitive Positioning

Build a differentiation story that holds up under sales scrutiny.

Board Deck Narrative

Develop the "why this matters" story in your exec summary before building slides.

Customer Pitch

Generate talking points that objection-handle every concern upfront.

βš™οΈ Technical Details

  • Language: Python 3.8+
  • Dependencies: None (standard library only)
  • Output: JSON + Console
  • Session Persistence: Framework saved to JSON; re-import to resume

πŸ“– License

MIT License β€” use freely for product messaging work.

🀝 Contributing

This tool enforces messaging discipline, not creative expression. Contributions should:

  • Strengthen challenge logic (detect more vague claims)
  • Expand evidence validation (new RTB types)
  • Improve CTA recommendations (clearer asks)

πŸ“ž Questions?

This is a coaching tool β€” it will challenge you. That's the feature, not a bug.


Built with the philosophy: Great messaging is rigorous, evidence-backed, and customer-focused. Vague claims don't survive contact with this agent.

About

Interactive AI messaging coach. Help Product Managers and Engineering Leaders turn their new announcement to outbound facing message that is clear and powerful to be used by Marketing and any other teams

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors

Languages