UitbreidenOS Messaging Architect
When to activate
After competitive analysis is complete and white-space opportunities identified. You have your core value prop and key differentiators. This skill designs 4–6 messaging pillars—each tied to a customer job and proof point—that will guide all subsequent content creation.
When NOT to use
Not for individual piece content — use Content Generator. Not for tone audits — use Tone Enforcer. Not without a defined competitive set and your core differentiators already clear.
Messaging Framework
Core Value Prop One sentence: what unique outcome do you enable that competitors don't?
Messaging Pillars (4–6) Each pillar connects:
- Customer Job: What is the customer trying to achieve?
- Your Claim: What does your product/service enable them to do?
- Proof Point: Data, case study, customer quote, or research backing the claim.
- Content Angles: 2–3 ways to tell this story (blog, social, email, video, case study).
Proof Hierarchy
- Customer quote (highest credibility)
- Case study with metrics (second)
- Research or industry data (third)
- Your testing or data (fourth)
Output Format
Return messaging architecture in this format:
# Messaging Architecture
**Date:** [ISO date]
**Company:** [Your company]
**Competitive Context:** [Brief: what white space you're owning]
---
## Core Value Proposition
[One sentence defining unique customer outcome]
---
## Messaging Pillars
### Pillar 1: [Name]
**Customer Job:** [What customer is trying to achieve]
**Our Claim:** [What we enable them to do]
**Proof Point:**
[Quote / Case study / Data / Research]
**Content Angles:**
- [Angle 1]: [Type of content to tell this story]
- [Angle 2]: [Type of content to tell this story]
- [Angle 3]: [Type of content to tell this story]
**Example Content Headline:**
[One strong headline showing how we'd position this]
---
### Pillar 2: [Name]
[Same structure]
---
### Pillar 3: [Name]
[Same structure]
---
### Pillar 4: [Name]
[Same structure]
---
## Messaging Hierarchy
**Always lead with:** [What customer values most]
**Then show:** [How we enable it]
**Finally proof:** [Why customers trust us]
---
## Anti-Messages
Do NOT emphasize:
- [What competitors own]
- [What doesn't differentiate us]
- [What customers don't care about]
---
## Channel-Specific Messaging Notes
**Website:** Lead with core value prop, then dive into pillars with proof
**Blog:** Deep-dive on one pillar; tell customer story
**LinkedIn:** Highlight trend + how we help; conversational tone
**Email:** One pillar per email series; build case over time
**Social:** Pillar headlines + customer quotes; debate-friendly takes
---
**Next Step:** Present messaging pillars to human. Human approves or requests messaging adjustments. All content creators use these pillars as north star.
Example
Messaging Architecture
Date: 2026-06-12 Company: Acme Developer Platform Competitive Context: Own "enterprise security without developer friction" (Competitor A = friction, Competitor B = no security)
Core Value Proposition
Ship faster with enterprise-grade security built in.
Messaging Pillars
Pillar 1: Ship Securely, Not Slowly
Customer Job: Move fast without worrying about security compliance becoming a bottleneck
Our Claim: Security-first architecture that doesn't slow down developers or delay releases
Proof Point: "We reduced our security review time from 2 weeks to 2 days. Build the feature, it's secure by default." — Sarah Chen, VP Engineering, Acme Inc.
Content Angles:
- Case study: how fast-growing companies ship without security debt
- Blog: "Security doesn't have to slow you down"
- LinkedIn: "Security review bottleneck? Here's how we eliminated ours"
Example Content Headline: "How We Went From 2-Week Security Reviews to Ship-Ready in 48 Hours"
Pillar 2: Grow Without Rip-and-Replace
Customer Job: Scale from startup to enterprise without rewriting infrastructure
Our Claim: Platform grows with you — what works at 10 engineers works at 500
Proof Point: "We started with [Competitor B]. When we hit 200 engineers, we thought rip-and-replace was inevitable. [Our platform] meant we scaled without rewiring." — CTO, TechCorp (Series B → Series C)
Content Angles:
- Comparison: "Startup tools vs. enterprise solutions: why not both?"
- Blog: "How to choose infrastructure that scales with your company"
- Webinar: "From Series A to Series C without a big rewrite"
Example Content Headline: "The Infrastructure That Scales From Series A to Enterprise (Without a Rewrite)"
Pillar 3: Transparent Pricing, No Enterprise Surprise Tax
Customer Job: Budget for growth without getting surprised by sudden pricing jumps
Our Claim: Pricing that scales predictably; no hidden features locked behind million-dollar enterprise plans
Proof Point: Research: 72% of companies cite "unexpected cost increases" as reason for platform abandonment. Our transparent, linear pricing model means $10M revenue company pays 10x what $1M company pays.
Content Angles:
- Blog: "The hidden cost of enterprise pricing"
- LinkedIn: "Why we made pricing transparent (and how it helps you)"
- Comparison tool: head-to-head pricing vs. competitors
Example Content Headline: "Your Pricing Model is Pushing Customers Away (Here's Why Ours Doesn't)"
Pillar 4: Developer Experience > Everything Else
Customer Job: Use tools that feel intuitive, well-documented, and maintained by people who code
Our Claim: developers, for developers. API design, docs, and DX are features, not afterthoughts
Proof Point: "Their API docs are incredible. Usually, when I have a question, the answer is already in the docs. Saves us hours per week." — Dev Lead, QuickStart Inc.
Content Angles:
- Developer guide: "How we design APIs that don't suck"
- Podcast/video: "Inside our API design process"
- Blog: "Why good docs are competitive advantage"
Example Content Headline: "We Spent 6 Months on Documentation. Here's What Changed."
Messaging Hierarchy
Always lead with: Developer velocity and peace of mind Then show: How our architecture and pricing enable that Finally proof: Customer quotes and metrics proving we deliver
Anti-Messages
Do NOT emphasize:
- "We have more features than [Competitor A]" — not true, not what customers want
- "We're cheaper than [Competitor B]" — we're not, and cost is secondary to value
- "AI-powered," "cutting-edge," "enterprise-grade" (buzzwords) — show, don't tell
Channel-Specific Messaging Notes
Website: Open with "Ship faster with enterprise security"; pillar breakdown shows how Blog: One pillar = one series of 3–4 posts (deep customer stories) LinkedIn: Rotate pillars weekly; use debate-friendly takes ("Why [Competitor] pricing doesn't work," not "we're better") Email: Build narrative over time: Pillar 1 → Pillar 2 → Social proof → CTA Social: Pillar headlines, customer quotes, industry data points. Never "we're awesome," always "here's what customers achieve"