#135 — The 7-step messaging framework

Plan for 2-4 weeks from kickoff to final approval. Week 1 involves customer research (surveys, review analysis, sales team interviews). Week 2 is the collaborative workshop with founders, product leads, and PR/marketing (budget 4-8 hours). Weeks 3-4 focus on testing with advisors and customers, then iterating. Slack famously spent months refining their messaging before their 2014 launch, testing with early users until they identified their magic number: 2,000 messages exchanged = 93% retention. Rush this process and you'll spend months fixing bad messaging in market.

Positioning is your strategic foundation (internal, rarely changes): what you replace in the market and why you matter now. Messaging is the communication layer (external, adaptable): how you talk about that position across channels. Stripe's positioning was 'payments infrastructure for developers' while their messaging evolved from '7 lines of code' in 2010 to emphasizing embedded finance by 2024. Get positioning wrong and no amount of clever messaging will save you—you're just polishing a confused strategy.

Track message pull-through: Are customers and press repeating your exact phrases back to you? Quantitative signals include: (1) Media coverage using your key messages, (2) Win rate changes in sales cycles, (3) Inbound demo request quality, (4) Time-to-close reduction. Twilio's Toyota Connected case study showed messaging alignment reduced after-call work by 13% and monthly handle time by 18%. The ultimate signal: competitors start repositioning to sound like you.

Hire externally if: (1) Internal stakeholders can't agree on who you serve, (2) Your founding team lacks go-to-market experience, (3) You're pre-launch with no customer feedback loop, or (4) A rebrand/pivot requires fresh perspective. Cost ranges: $6,000-$12,000 for positioning + messaging audit; $12,000-$25,000 for full framework with distribution materials. Do it in-house if you have strong product marketing leadership and can commit your founders + product lead for 2-4 weeks. Bessemer (104-year-old firm) hired external help for their brand audit despite deep internal expertise—sometimes outside perspective is worth the investment.

No—you need distinct message tracks for each persona, anchored to a single positioning foundation. Twilio demonstrates this perfectly: they message 'ease of integration' to developers but emphasize 'scalability and deliverability' to enterprise IT buyers. Stripe positioned as 'payments infrastructure' but messaged '7 lines of code' to developers and 'embedded finance platform' to enterprise CFOs. Create one core positioning doc, then build 3-message frameworks tailored to each persona's specific problems and evaluation criteria.

Minimum once per year, or when: (1) Launching a major new product, (2) Competitors are winning deals you should close, (3) Internal teams describe your company differently, or (4) You've raised a new funding round and expanded TAM. Stripe evolved from 'online payments API' (2010) to 'embedded finance and data infrastructure' (2024) as their product expanded. Warning signs you're overdue: sales cycles lengthening, press coverage missing your key points, or leadership debating positioning in every pitch deck review.

Your value proposition is one sentence: the single biggest benefit you deliver to your target customer. Your messaging framework is the complete structure: 3 main messages, 9 supporting points (3 per message), proof points, and distribution materials. Think of it as: value prop = headline, messaging framework = the entire playbook. Slack's value prop was 'make work simpler, more pleasant, and more productive'—their messaging framework expanded that into developer benefits, enterprise security, and integration ecosystem across different channels.

Lead with the problem you solve, not the category you're creating. Compare to something familiar, then differentiate. Slack didn't say 'team collaboration platform'—they said 'email killer' and 'searchable log of all conversation and knowledge'. Stripe didn't invent 'embedded finance'—they solved 'accepting payments on the web in 7 lines of code vs weeks of integration'. Only after customers understand the problem-solution fit should you introduce category language. Create analogies ('it's like X meets Y for Z audience') to accelerate comprehension.

Five fatal errors: (1) Feature-first messaging—customers care about their problems, not your roadmap. (2) Too broad targeting—'everyone' messaging converts no one. (3) Skipping customer research—founders guess at pain points instead of surveying actual users. (4) No internal alignment—sales says one thing, marketing says another, founder pitches a third version. (5) Leading with 'we're better'—instead of 'here's your problem and proof we solve it.' Stripe succeeded because developers evangelized the '7 lines of code' message—not because Stripe had the cheapest pricing.

Stick to the 3-3-30 rule: 3 main messages, 3 supporting points each, 30 words maximum per point. This comes from cognitive science research on crisis communications—it's how stressed, busy buyers retain information under pressure. Going beyond 3 main messages dilutes focus and kills retention. Twilio's messaging doc had detailed 25-word and 50-word descriptions, but always laddered to 3 core messages. If you think you need 5-7 messages, you either: (1) don't understand your positioning, (2) are trying to serve too many personas with one framework, or (3) are confusing features with benefits.

Follow this 4-step process: (1) Involve top sellers early in messaging development—they'll be your internal champions. (2) Train sales leadership first, then have them train their teams (not marketing). (3) Bake it into onboarding—new hires should see messaging in their first week via slide decks and live demo observations. (4) Hold quarterly refreshers where product marketing reviews updates and clarifies confusion. Create internal collateral (battle cards, one-pagers, use cases) and host regular feedback sessions. One SaaS company saw a 28% increase in C-level meetings after implementing structured sales messaging training.

Messaging is what you say (the strategic ideas and key points). Copywriting is how you say it (the exact words, tone, and format). Messaging defines your value proposition and supporting proof points—this stays consistent across channels. Copywriting adapts that messaging for specific contexts: homepage vs pitch deck vs LinkedIn ad. Example: Notion's messaging is 'all-in-one workspace for notes, tasks, and collaboration.' Their homepage copy makes it conversational: 'Write, plan, organize. With AI at your side'. Create your messaging framework first, then hire copywriters to bring it to life across touchpoints.

Lead with outcomes, not features. Non-technical buyers don't care about your stack—they care about time saved, revenue increased, or errors reduced. Follow this formula: (1) Convert technical features to business benefits ('256-bit encryption' becomes 'your customer data stays secure and compliant'). (2) Use analogies to simplify complex concepts ('think of it as autopilot for your finances'). (3) Start with impact metrics (30% faster deployment) before explaining how it works. (4) Test with the 'mom rule': if someone outside your industry can't explain it after one pitch, simplify further.

Always messaging framework first. Launching a website without messaging leads to delays, reworks, and confusion about what you're trying to communicate. Your messaging framework becomes the strategic foundation for: website copy, design hierarchy, CTAs, and page structure. One agency reported helping a client launch an effective lead-generating website in just 2 weeks because they started with a solid messaging doc. Without it, website projects drag for months as stakeholders debate positioning on every page. Create your messaging framework, share it with your web team in a strategy session, then turn them loose to design.

Your launch messaging checklist must include: (1) Master messaging document with value prop, key talking points, audience personas, and pain points solved. (2) 25-word and 50-word descriptions for different contexts. (3) Channel-specific content matrix mapping core messages to email, ads, PR, and social. (4) Sales enablement materials: one-pagers, battle cards, demo scripts, objection handlers. (5) Stakeholder alignment ensuring product, marketing, sales, and support use identical language. (6) Consistent CTAs across touchpoints. Most launches fail because messaging isn't aligned across every customer interaction—fix this before launch day.

They must be identical at the core—investors should hear the same problem/solution narrative your customers experience. Your pitch deck messaging isn't just for fundraising; it cascades to customer acquisition, team alignment, and press coverage. Follow this structure: (1) One-line mission that works in both contexts ('We exist to [solve what] for [who], by [how]'). (2) Problem slide = customer pain points from your messaging framework. (3) Solution slide = your 3 core messages with proof points. Figma's 'Design for everyone' worked for both investors (TAM story) and users (accessibility promise). If your investor pitch sounds different than your website, you have a consistency problem that kills credibility.

Use this 7-section template: (1) Target audience—specific persona with psychographic details and daily pressures. (2) Problems they face—3-5 pain points from customer research. (3) 3 main messages—how you solve each problem (outcome-focused, not feature-focused). (4) 9 supporting points—3 sub-points per message, max 30 words each. (5) Proof points—customer names, case studies, metrics, testimonials. (6) Boilerplate descriptions—25-word and 50-word versions. (7) Competitive differentiators—what makes you unique. Multiple B2B agencies offer free downloadable templates, but the structure should always follow the cognitive science-backed 3-3-30 rule.

Dual-track messaging is essential: one for developer/community adoption, another for commercial/enterprise buyers. For open source: (1) Lead with developer benefits first—ease of integration, extensibility, community support. (2) Emphasize transparency and control ('no vendor lock-in, full data ownership'). (3) Show scale proof points ('500 million messages sent, battle-tested') to build trust. (4) Position commercial offering as 'enterprise edition' with additional security, support, and features—not as the 'real' product. Laudspeaker positions as 'Open Source alternative to Braze/OneSignal' for developers, then sells enterprise licenses to companies needing SLAs and compliance. Don't force developers through a sales process—let the product message itself.

Four pitch-killing errors: (1) Complexity over clarity—founders think dense explanations sound smarter, but investors skim 50 decks weekly. If you're still explaining your product by slide 3, you've lost them. (2) Inconsistent narrative—different executives describe the company differently, signaling poor internal alignment. (3) Industry jargon—if someone can't explain your startup after one pitch, it's not ready. Dropbox's rule: 'If my mom can explain it, we're good'. (4) No emotional hook—great pitches like Notion's 'all-in-one workspace' are simple but memorable. Your messaging should work across investors, customers, and press—clarity cascades into growth.

Developer messaging requires technical credibility first, business value second. Follow this structure: (1) Lead with the problem in code—show the painful 'before' (weeks of integration, brittle APIs). (2) Prove your solution with code examples—Stripe's '7 lines of code' became legendary because it was tangible. (3) Message 'developer experience' benefits—speed, simplicity, documentation quality, not just features. (4) Build social proof through community—OSS contributions, GitHub stars, Stack Overflow presence. (5) Separate dev messaging from buyer messaging—developers want technical specs, but their bosses want ROI and security. Twilio excels at this: developer docs focus on API ease, enterprise pages emphasize scalability and compliance.

Use a one-page master doc with these sections: (1) One-line positioning (who you serve + what you replace + why now). (2) Target ICP—specific persona, not 'all developers'. (3) 3 problems you solve (validated by customer research). (4) 3 core messages connecting your product to those problems. (5) Proof points—early customer wins, even if small. (6) Value proposition (one sentence). (7) POV/Sales story—why customers should care now. Early-stage founders should prioritize clarity over sophistication. Your messaging will evolve as you get customer feedback—nail the basics first, then add complexity as you scale.