4.3 KiB
Before/After Content Examples
Concrete examples showing how brand voice enforcement transforms generic content into on-brand output. Each example shows the generic version, the enforced version, and annotations explaining what changed and why.
These examples use a fictional B2B SaaS company for illustration. During enforcement, replace all specifics with data from the user's actual brand guidelines and context.
Cold Outreach Email
Before (Generic)
Subject: Quick question about your sales process
Hi [Name], I wanted to reach out because I think our product could be a great fit for your team. Would you be open to a quick 15-minute call?
After (Brand Voice Enforced)
Subject: [Company] is leaving pipeline on the table
Hi [Name], Your team closed $12M last quarter — impressive. But our data shows mid-market teams like yours typically lose 23% of qualified pipeline to slow follow-ups. [Product] fixes that. [Customer X] saw their win rate jump 18% in the first quarter. Worth 15 minutes?
What Changed
- Voice: Confident — leads with bold claim and specific data
- Voice: Data-driven — concrete numbers replace vague "more productive"
- Voice: Direct — no "I wanted to reach out"
- Tone: Energy HIGH — active language, short sentences
- Tone: Formality MEDIUM — professional but conversational
- Tone: Technical depth LOW — outcomes, not features
Follow-Up Email
Before
Just following up on my previous email. I'd love to schedule a call.
After
Quick update: we just published our Q4 benchmark report. Three insights relevant to [Company]: (1) Teams using real-time signals close 31% faster. (2) The #1 pipeline killer is response time, not competition. (3) Mid-market wins are 15% larger when reps personalize within 2 hours. Happy to walk through how these compare to your numbers — report attached if you'd rather dig in first.
What Changed
- Voice: Data-driven — new value in every touch, not just "following up"
- Voice: Approachable — offers two paths without pressure
- Key principle: Add new value each touch — no empty follow-ups
Enterprise Proposal Executive Summary
Before
We are pleased to submit this proposal. We believe our platform is the best choice for organizations looking to modernize their sales operations.
After
[Company] processes 2,400 leads per quarter with a 12-person team. Pipeline-to-close sits at 18% — below the 24% benchmark for your ARR stage. This proposal outlines how [Product] closes that gap. Typical results: +31% win rate, -40% time to close. Implementation: 3 weeks. ROI breakeven: week 6.
What Changed
- Voice: Data-driven — opens with client's own metrics
- Voice: Direct — no filler, every sentence carries information
- Tone: Formality HIGH — structured, precise
- Tone: Technical depth HIGH — specific features and ROI math
LinkedIn Post
Before
Excited to announce our new feature! We think it's going to change the way sales teams work! #sales #AI #innovation
After
The average sales rep spends 4.2 hours/day on tasks that don't close deals. We analyzed 50,000 sales activities across 200 teams: top performers aren't working harder — they're responding faster. Today we're launching Signal Score: real-time prioritization that tells your reps exactly which deal to work next, and why. Early results: 23% fewer lost deals from delayed follow-up.
What Changed
- Voice: Data-driven — opens with stat, not "excited to announce"
- Voice: NOT hype-driven — measurable outcomes replace "change the way"
- Tone: Energy HIGH — short sentences, bold opening
- Terminology: No "revolutionary" or "game-changing"
Internal Slack Message
Before
Hey team, just a reminder to use the approved messaging. Please refer to the brand guidelines for more information.
After
Heads up — we updated the competitive positioning section. Two changes: (1) Against [Competitor]: lead with implementation speed (3 weeks vs. their 3 months). (2) Against Status Quo: new stat — manual processes lose 23% of pipeline to timing. Updated doc pinned in #sales-enablement. Questions? Tag me.
What Changed
- Voice: Direct — specific changes, not vague "please refer to"
- Tone: Formality LOW — appropriate for Slack
- Key principle: Internal comms can be less polished, but voice attributes still apply