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.
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
# Clone repository
git clone https://github.com/ozwilder/Product-Messaging.git
cd Product-Messaging
# No external dependencies required (Python 3.8+)python src/clear_messaging_agent.py interactive- Key Message β What's the news you're announcing?
- Value Articulation β WIIFM, competitive advantage, customer concerns
- Evidence & RTB β Statistics, customer feedback, analyst validation
- Template Completion β Bottom line, roadmap, specifics, CTA
- Output β 1-page framework + JSON export
π― 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
The single most important thing to remember.
Evolution, timeline, what's next.
Why should this specific audience care? Benefits per persona.
What makes this special? Why now? Unique differentiators.
What worries customers? How do you overcome them?
Evidence-backed proof:
- Statistics (market data, benchmarks)
- Customer Feedback (testimonials with org context)
- Analyst Reports (Gartner, Forrester validation)
- KPIs (measurable business metrics)
Pricing, availability, timeline, deployment model.
What should the audience do NOW? Registration link? Demo request? Sales contact?
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" |
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 ...]
{
"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"
}Create messaging that lands with confidence β no more weak claims that executives challenge. Each section is battle-tested before you present.
Generate structured messaging frameworks that sales can inherit. JSON export makes it easy to distribute across tools.
Use the objection handlers (Disarm Concerns section) as battle cards. CTA section gives you a clear ask every time.
Share the 1-page output in your next meeting. Evidence section proves your claims aren't opinions.
- Answer One Question at a Time β Don't rush. The agent enforces this deliberately.
- Use Real Data β "~1% false positive rate" vs "very low false positives". Numbers win.
- Know Your Personas β The RTB section should call out which persona cares about each claim.
- Anticipate Objections β The Disarm Concerns section is where you win or lose customer trust.
- Test Your CTA β Make sure it's a single, clear action. Not "learn more and sign up and download specs".
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 typeUpdate VAGUE_INDICATORS list in ClearMessagingAgent to match your industry:
VAGUE_INDICATORS = [
"helps", "improves", "better", "advanced",
"blockchain-enabled", # Add custom
"synergistic" # Add custom
]Create messaging for a new product launch with consistent narrative across all stakeholders.
Build a differentiation story that holds up under sales scrutiny.
Develop the "why this matters" story in your exec summary before building slides.
Generate talking points that objection-handle every concern upfront.
- Language: Python 3.8+
- Dependencies: None (standard library only)
- Output: JSON + Console
- Session Persistence: Framework saved to JSON; re-import to resume
MIT License β use freely for product messaging work.
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)
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.