---

title: "B2B Persona Messaging Playbook" description: "Comprehensive guide to cold email messaging for B2B personas across Executive, Engineering, Product, Customer Experience, Support, Developer Relations, Technical Writing, Community, Growth, and AI Transformation roles. Evidence-backed insights on responsibilities, metrics, pain points, buying behavior, content consumption, and messaging strategies." createdAt: 2026-02-10 updatedAt: 2026-02-12 subjects:

• B2B SaaS personas
• Cold email copywriting
• DevTool buyer personas
• Sales messaging topics:
• persona research
• cold outreach
• B2B sales
• buyer psychology
• email copywriting
• ICP segmentation

---

B2B Persona Messaging Playbook

Purpose: Provide actionable, evidence-backed guidance for crafting cold email messaging that resonates with specific B2B personas. This playbook maps target personas to 19 researched archetypes, with detailed insights on what each persona cares about and how to reach them effectively.

---

Executive Summary

This playbook provides deep research on 19 distinct B2B persona archetypes. Each archetype includes:

1. Role responsibilities — What they own and how success is defined
2. Key metrics/KPIs — What numbers determine their career trajectory
3. Day-to-day activities — How they spend their time
4. Pain points & priorities — What keeps them up at night
5. Buying behavior — How they evaluate vendors and make decisions
6. Content consumption — What they read, listen to, and trust
7. Messaging angle — Problem framing, proof points, and CTAs that work
8. Anti-patterns — What turns them off and kills response rates

Key Findings:

• Interest-based CTAs double response rates — "Would it be helpful to see..." outperforms "Book a demo" (30% vs 15% response rate)
• Narrow targeting wins — Targeting 1 person per company yields 7.8% reply rate vs 3.8% for 10+ people
• Budget authority varies dramatically by level — VPs have it; Managers influence but may need approval
• Content consumption is role-specific — Each persona has distinct trusted sources and formats
• Developer-adjacent personas are skeptical — They identify as practitioners first and detect sales tactics instantly
• ROI proof is the universal VP-level challenge — Connect every claim to measurable business outcomes

---

Inkeep Market Pain Points (CEO Framing)

When mapping personas to Inkeep's value proposition, anchor on these two core pain points:

Pain Point 1: Fragmented AI Solutions

"Technical B2B SaaS companies are aiming to adopt AI to accelerate and improve every step of the customer journey. To do so, they are adopting a mix of AI solutions to cover different company-specific workflows and use cases covering everything from product onboarding, support engineering, success, and content teams. The problem: system of record platforms like support platforms often have siloed "closed garden" AI functionality that just doesn't work that well or doesn't connect or interface with a company's knowledge sources, customer data, 1st party product APIs and apps, or the other 3rd party SaaS solutions that the customer may use. Companies find themselves purchasing piece-meal solutions from specialized vendors (often startups) that solve narrow scenarios (e.g. "support chatbot") or workflows ("turn support tickets into documentation updates"). These solutions don't talk to each other, are configured and behave differently, or just don't quite work well in the specific requirements, data sources, workflows, or use cases unique to a company (and every company has a unique combination of these). Any limitation turns into a feature request to 1 vendor which may or may not get prioritized, and you're bottlenecked by that vendor's ability to ship features or make their solution extensible (which is often not a priority). This piecemeal approach poses significant burden on vendor procurement, security and governance, and actual adoption across every CX-related function of the company." — Nick Mishra, CEO

Pain Point 2: Support Engineers Don't Get to Spend Time on Tough Problems

"In B2B SaaS companies, support is part of the product. B2B SaaS companies gravitate towards Enterprise sales motions, so providing a great customer experience and keeping individual customers happy is often a basic expectation of any of their Enterprise customers. Similarly, for product-led companies, support and a great user experience is imperative to promoting word of mouth and organic growth. Because of these dynamics, B2B SaaS companies invest heavily and see as a requirement to deliver timely, accurate, top-notch support. Delivering this support often relies on highly specialized talent including dedicated support engineers or engineering members of their product team. These engineers have to become always-up-to-date product experts (which has a ramp up period and is hard to hire for), but also need to spend significant amount of time performing workflows to help gather all the right context to resolve a problem. This often includes gathering additional context from the user, looking up customer information in downstream systems like error logs, CRMs, 1st party product-specific data sources or APIs, cross-referencing information with engineering and product backlogs, etc. All of these systems are often varied, and the workflows that stem from them are often custom to the company and how it operates. AI Support solutions today often don't cover anything beyond product knowledge chat Q&A, and even there, often don't handle the varied knowledge sources of a technical B2B SaaS company (knowledge base, docs, github, internal KBs like confluence, marketing site, etc.). The result: technical B2B SaaS companies struggle to adopt AI in a meaningful way beyond chat Q&A; keeping time-to-resolution stats high and support and product engineering teams swamped with the more manual and tedious parts of support." — Nick Mishra, CEO

---

Research Rubric

Dimension	Description
Role responsibilities	What they own, scope of authority, success definition
Key metrics/KPIs	Numbers they report on, what gets them promoted/fired
Day-to-day activities	Time allocation, meetings, tools used
Pain points & priorities	Top 3-5 challenges, what keeps them up at night
Buying behavior	Evaluation process, budget authority, purchase triggers
Content consumption	Newsletters, podcasts, communities, formats that resonate
Messaging angle	Problem framing, proof points, effective CTAs
Anti-patterns	What kills response rates, common mistakes

---

Persona Mapping: New Archetype Structure

Primary Archetypes (8)

#	Archetype	Original Personas Covered
1	VP of Customer Experience	VP of CX, DevTool Customer Experience VP
2	Customer Success Leaders (Manager+)	Customer Success Manager (Manager+), Onboarding Manager (Manager+), DevTool CX Manager/Lead, Onboarding and Success (leadership)
3	Support Leaders (Manager+)	Support VP Titles, VP & Head Support + Customer Care, Support Tools (Head/Manager), DevTool Head of Support Titles, DevTool Support Director Titles, DevTool Support Manager/Lead Titles, Support leader, Support low-level manager
4	Support Operations & CX Operations Leaders	CX Operations roles, Support Operations roles, Process/tooling-focused CX Directors
5	CEO, Founder, Chairman	Founder - CEO, Founder - CXO (all), Chairman
6	CTO, VP Engineering, Engineering Leaders	Founder - CTO, CTO (Non Founder), VP of Eng, Engineering Director/Head, Engineering Manager
7	Product Leaders, CPO	Product Manager - VP/CXO/Partner, DevTool Product Exec, Founder - Product, Product Manager - Head/Director, DevTool Product VP/Director titles, DevTool Product Manager/Lead titles, Product Manager - Senior/Manager
8	CIO, Head of AI, AI Transformation Leader	AI Transformation Leader, CIO, Head of AI, Chief AI Officer (CAIO)

Secondary Archetypes (11)

#	Archetype	Original Personas Covered
9	Mid-level / Junior PM	Product Manager - Junior, DevTool Product Titles (IC level)
10	Technical / Platform PM	Technical PM, Platform PM
11	Head of DevRel	Developer Relations Lead (VP/Head level)
12	Senior Developer Advocate	DevRel, Developer Relations Lead (Manager level)
13	Junior Developer Advocate	Developer Relations IC
14	Head of Technical Writing	Docs Leader, Technical Writing - Manager+
15	Technical Writer	IC-level docs roles
16	Head of Community	Head/VP/Manager of Community
17	VP/Head of Growth	Growth Titles (VP, Director, Head)
18	Growth Manager	Growth Titles (Manager, Lead, Specialist)
19	Content Creator (Recruiting)	Recruiting - Content Creator

Note on TAM Personas: These map directly to the functional archetypes above. Use the relevant archetype research and adjust for their specific TAM context.

---

Complete Persona Mapping: 44 Original Personas → 19 Archetypes

Executive & Leadership Personas

#	Original Persona	New Archetype	Archetype #
1	Founder - CEO	CEO, Founder, Chairman	5
2	Founder - CXO (all)	CEO, Founder, Chairman	5
3	Chairman	CEO, Founder, Chairman	5
4	Founder - CTO	CTO, VP Engineering, Engineering Leaders	6
5	CTO (Non Founder)	CTO, VP Engineering, Engineering Leaders	6
6	VP of Eng	CTO, VP Engineering, Engineering Leaders	6
7	Engineering Director/Head	CTO, VP Engineering, Engineering Leaders	6
8	Engineering Manager	CTO, VP Engineering, Engineering Leaders	6
9	CIO	CIO, Head of AI, AI Transformation Leader	8
10	Head of AI	CIO, Head of AI, AI Transformation Leader	8
11	AI Transformation Leader	CIO, Head of AI, AI Transformation Leader	8
12	Chief AI Officer (CAIO)	CIO, Head of AI, AI Transformation Leader	8

Product Personas

#	Original Persona	New Archetype	Archetype #
13	Product Manager - VP/CXO/Partner	Product Leaders, CPO	7
14	DevTool Product Exec	Product Leaders, CPO	7
15	Founder - Product	Product Leaders, CPO	7
16	Product Manager - Head/Director	Product Leaders, CPO	7
17	DevTool Product VP titles	Product Leaders, CPO	7
18	DevTool Product Director Titles	Product Leaders, CPO	7
19	DevTool Product Manager/Lead titles	Product Leaders, CPO	7
20	Product Manager - Senior/Manager	Product Leaders, CPO	7
21	Product Manager - Junior	Mid-level / Junior PM	9
22	DevTool Product Titles (IC level)	Mid-level / Junior PM	9
23	Technical PM	Technical / Platform PM	10
24	Platform PM	Technical / Platform PM	10

Customer Experience & Support Personas

#	Original Persona	New Archetype	Archetype #
25	VP of CX	VP of Customer Experience	1
26	DevTool Customer Experience VP	VP of Customer Experience	1
27	Customer Success Manager (Manager+)	Customer Success Leaders (Manager+)	2
28	Onboarding Manager (Manager+)	Customer Success Leaders (Manager+)	2
29	DevTool CX Manager/Lead	Customer Success Leaders (Manager+)	2
30	Onboarding and Success (leadership)	Customer Success Leaders (Manager+)	2
31	Support VP Titles	Support Leaders (Manager+)	3
32	VP & Head Support + Customer Care	Support Leaders (Manager+)	3
33	Support Tools (Head/Manager)	Support Leaders (Manager+)	3
34	DevTool Head of Support Titles	Support Leaders (Manager+)	3
35	DevTool Support Director Titles	Support Leaders (Manager+)	3
36	DevTool Support Manager/Lead Titles	Support Leaders (Manager+)	3
37	Support leader	Support Leaders (Manager+)	3
38	Support low-level manager	Support Leaders (Manager+)	3
39	Customer Experience (Director Level) - Ops focus	Support Operations & CX Operations Leaders	4
40	Support Operations roles	Support Operations & CX Operations Leaders	4
41	CX Operations roles	Support Operations & CX Operations Leaders	4

Developer Relations, Docs & Community Personas

#	Original Persona	New Archetype	Archetype #
42	Developer Relations Lead (VP/Head level)	Head of DevRel	11
43	DevRel (Manager level)	Senior Developer Advocate	12
44	Developer Relations Lead (Manager level)	Senior Developer Advocate	12
45	Developer Relations IC	Junior Developer Advocate	13
46	Docs Leader	Head of Technical Writing	14
47	Technical Writing - Manager+	Head of Technical Writing	14
48	Technical Writer (IC)	Technical Writer	15
49	Head/VP/Manager of Community	Head of Community	16

Growth & Content Personas

#	Original Persona	New Archetype	Archetype #
50	Growth Titles (VP, Director, Head)	VP/Head of Growth	17
51	Growth VP/Manager/Head	VP/Head of Growth	17
52	Growth Titles (Manager, Lead, Specialist)	Growth Manager	18
53	Recruiting - Content Creator	Content Creator (Recruiting)	19

TAM Personas (Map to Functional Archetypes)

#	Original Persona	Maps To	Notes
54	Sales/Solution Engineering - TAM	Engineering Leaders (6) or Product Leaders (7)	Adjust for sales engineering context
55	Content - TAM	Content Creator (19) or Growth (17/18)	Adjust for TAM context
56	Marketing - TAM	VP/Head of Growth (17) or Growth Manager (18)	Adjust for TAM context
57	Product - TAM	Product Leaders (7) or Mid-level PM (9)	Adjust for TAM context
58	Support team member - TAM	Support Leaders (3) or Support Ops (4)	Adjust for TAM context
59	Onboarding and Success team member - TAM	Customer Success Leaders (2)	Adjust for TAM context
60	Sales team member - TAM	VP/Head of Growth (17)	Adjust for TAM context

---

Archetype Summary Table

Archetype #	Archetype Name	Persona Count	Budget Authority
Primary Archetypes
1	VP of Customer Experience	2	Full (CX tools)
2	Customer Success Leaders (Manager+)	4	Growing; may need VP approval
3	Support Leaders (Manager+)	8	VP: Full / Manager: Influence
4	Support Operations & CX Operations Leaders	3	Yes for ops tools; larger needs approval
5	CEO, Founder, Chairman	3	Full (company-wide)
6	CTO, VP Engineering, Engineering Leaders	5	Full (engineering/dev tools)
7	Product Leaders, CPO	8	Yes (for product tools)
8	CIO, Head of AI, AI Transformation Leader	4	Very high (explicit mandate)
Secondary Archetypes
9	Mid-level / Junior PM	2	Rarely / No
10	Technical / Platform PM	2	Technical evaluation influence
11	Head of DevRel	1	Yes (<$10-50K)
12	Senior Developer Advocate	2	Moderate influence
13	Junior Developer Advocate	1	Limited influence
14	Head of Technical Writing	2	Yes (docs tools)
15	Technical Writer	1	Strong influencer
16	Head of Community	1	Yes; larger needs exec approval
17	VP/Head of Growth	2	Yes (dept budget control)
18	Growth Manager	1	Influence; may have P&L
19	Content Creator (Recruiting)	1	Limited (8% have dedicated budget)
	Total	53

Note: Count exceeds 44 due to TAM personas being counted separately and some roles appearing in multiple original persona lists.

---

Part 1: Executive & Company Leadership

1.1 CEO, Founder, Chairman

Role Responsibilities:

• Sets company vision, long-term strategy, and market positioning
• Owns GTM strategy and sales/marketing alignment
• Jack-of-all-trades in early stage; gradually delegates as company scales
• Maintains culture during hyper-growth
• Manages investor relations and fundraising
• Board management and shareholder communications

Key Metrics/KPIs:

• MRR / ARR
• CAC and CAC Payback Period
• Customer Lifetime Value (CLTV) and LTV:CAC ratio
• Net Revenue Retention (NRR)
• Customer Churn Rate
• Burn rate and runway
• Valuation multiples

Day-to-Day Activities:

• Customer conversations, demos, closing deals
• Deep work blocks (afternoon) with email/Slack off
• Support monitoring (many handle incoming queries personally)
• Content creation for thought leadership
• Leadership meetings (often stacked on Mondays)
• Investor updates and board preparation

Pain Points & Priorities:

1. Growth slowdown — pivot from "growth at any cost" to efficiency
2. CAC efficiency crisis — ratios trending wrong direction
3. Increased competition and customer portability
4. Real-time customer expectations
5. GTM clarity — which channels actually drive pipeline

Buying Behavior:

• 41% have preferred vendor before formal evaluation begins
• Complete 60%+ of buying process before engaging vendor
• 13 stakeholders involved on average (Forrester 2024)
• CFOs increasingly involved in software purchasing
• 80%+ opt for interactive demos
• Average SaaS vendor discount: 19%

Content Consumption:

• Podcasts: Nathan Latka's SaaS podcast, The SaaS Podcast (Omer Khan)
• Communities: SaaSBoomi, SaaS Open conferences, founder Slack groups
• Format: Email newsletters (4x higher engagement than social)

Messaging Angle:

• Problem framing: "Your CAC is rising but conversion is flat" / "You're leaving pipeline on the table"
• Proof points: ROI metrics, customer logos, revenue/growth results from similar-stage companies
• CTA: "Worth a quick chat?" / specific time suggestions / "Mind if I send a 2-min Loom?"

Anti-Patterns:

• Generic "fellow founder" appeals without specificity
• Long emails asking for 30+ minute meetings
• Pitching features rather than business outcomes
• Not understanding their stage (seed vs. Series B priorities differ)
• Spray-and-pray to multiple people (7.8% → 3.8% reply rate)

---

1.2 CTO, VP Engineering, Engineering Leaders

Role Responsibilities:

• Steers technological direction; final word on technology selection
• Develops tech product vision, strategy, and roadmap
• Provides technical leadership to engineering team
• Creates innovation culture; empowers experimentation
• Ensures security, compliance, and scalable architecture
• Translates business priorities into technical roadmaps
• Builds high-performing organization: recruiting, mentoring, best practices
• Owns SDLC processes, quality assurance, release management

Key Metrics/KPIs:

• System uptime and reliability (99.9%+ targets)
• Development velocity and deployment frequency
• DORA metrics: deployment frequency, lead time, change failure rate, MTTR
• Lead time for changes
• Time to market for new features
• Technical debt ratio
• Security posture and compliance certifications
• Engineering team productivity and retention
• Sprint velocity and on-time delivery rates
• Engineering cost per feature, ROI on engineering efforts

Day-to-Day Activities:

• Strategic planning and technology roadmap development
• Team meetings: architecture reviews, sprint planning
• Cross-functional collaboration on technical decisions
• Hands-on coding (especially early-stage or CTO)
• Hiring, talent management, technical interviews
• Security reviews and vendor evaluations
• Leadership meetings and cross-functional alignment
• Process improvement and tooling optimization
• Escalation handling and incident management
• 42% of time lost to "organizational overhead" at scale

Pain Points & Priorities:

1. Productivity crisis — developers spend only 32% of time writing code (McKinsey 2024)
2. Cybersecurity — increasing threats, robust posture needed
3. AI adoption pressure — racing to integrate but balancing practical value
4. Technical debt — quick fixes creating inefficient systems (67% cite as blocker)
5. Talent sourcing and retention
6. Budget constraints affecting development speed
7. Scalability challenges with rapid growth
8. Scaling complexity — at 50+ engineers, 1,225+ communication paths
9. Context switching — 78% cite "too many interruptions" as primary blocker
10. 78% struggle to align tech strategy with business objectives

Buying Behavior:

• Business alignment focus — every tool must tie to objectives
• Pilot-first approach — less than 2% of engineering budget for POC
• ROI-driven — need clear metrics on time saved, cost efficiency
• Security-first — require attestations, certifications, SBOM visibility
• Team buy-in required — evaluate based on developer experience
• 73% expected to adopt generative AI-enabled solutions by end of 2024
• 98% plan investments in analytics, automation, AI-driven optimization
• Integration with existing toolchain required
• Proof through pilots before company-wide rollout

Content Consumption:

• Newsletters: Amazing CTO, Lenny's Newsletter (825k+), The Pragmatic Engineer, Refactoring, LeadDev
• Podcasts: Modern CTO Podcast (Joel Beasley, 150k+ listeners), Engineering Enablement, Software Engineering Daily
• Communities: 7CTOs peer groups, Hacker News, LeadDev community, CTO Craft

Messaging Angle:

• Problem framing: "Your engineers are spending X% of time on Y instead of shipping" / "Security vulnerabilities are increasing compliance risk" / "Your engineers are only coding 32% of the time" / "Context switching is costing X hours per week"
• Proof points: Security certifications, integration capabilities, developer productivity metrics, time saved per engineer, deployment frequency improvements
• CTA: "Happy to share how [similar company] reduced deploy time by X%" / Technical deep-dive offer / "Worth a pilot with one team?"

Anti-Patterns:

• Marketing fluff without technical substance
• Not understanding their tech stack
• Overselling without addressing security/compliance
• Generic personalization lacking technical depth
• Pitching to CTOs when tool should go through engineering managers
• Ignoring integration requirements
• Asking for company-wide commitments before proving value

---

1.3 CIO, Head of AI, AI Transformation Leader

Role Responsibilities:

• Sets vision and roadmap for AI use cases and platform capabilities
• Manages teams across research, engineering, MLOps
• Helps executives understand where AI creates value vs. risk
• Shapes responsible AI practices, safety artifacts, compliance
• Reports to CTO or CDO; 26% of organizations now have CAIO (up from 11%)
• 48% of FTSE 100 companies have CAIO or equivalent
• Oversees enterprise IT strategy and infrastructure
• Manages vendor relationships and technology partnerships

Key Metrics/KPIs:

• ROI on AI spend (organizations with CAIOs report ~10% higher return)
• POC-to-production conversion rate (42% abandoned most AI initiatives in 2025)
• Business impact (80%+ haven't realized significant impact per McKinsey)
• MLOps metrics: reliability, latency, drift monitoring
• IT operational efficiency
• System availability and performance
• Security incident metrics
• Technology cost optimization

Pain Points & Priorities:

1. Data quality and readiness (43% cite as top obstacle)
2. POC abandonment — Gartner predicts 50%+ gen AI pilots will be abandoned
3. Strategic alignment — 74% haven't seen tangible value
4. Integration complexity — 42% need 8+ data sources for AI agents
5. User adoption — fear of replacement, rigid workflows
6. Security and governance requirements
7. Vendor consolidation pressure
8. Legacy system modernization

Buying Behavior:

• Explicit mandate to shape strategy, make investment decisions, enforce governance
• Evaluation: AI maturity, provider track record, security certifications, documentation
• Decline suppliers without technical documentation, safety artifacts, training data transparency
• Stakeholders: CIO, CDO, CISO, Procurement, Finance, Legal
• Long evaluation cycles with multiple proof points required
• Preference for established vendors with enterprise support

Content Consumption:

• Newsletters: The AI Optimist, Ben's Bites (140k+), TAAFT (1.7M)
• Reports: McKinsey, Gartner AI, MIT CISR
• Format: Executive summaries, ROI frameworks, governance frameworks

Messaging Angle:

• Problem framing: "74% of AI projects never make it past pilot — we help you be in the 26%"
• Proof points: POC-to-production conversion, deployment time reduction, security certifications
• CTA: Multi-channel (email + LinkedIn yields ~30% reply rates)

Anti-Patterns:

• Technical jargon overload without business value
• Ignoring governance and security concerns
• Generic AI claims without specific capabilities
• Overpromising ROI — 74% haven't seen value
• Not addressing compliance requirements
• Underestimating evaluation timeline

---

Part 2: Product Leadership

2.1 Product Leaders, CPO

Role Responsibilities:

• Crafts coherent long-term product strategy aligned with company goals
• Defines and communicates product vision
• Manages product management, UX, product analytics, product marketing teams
• Owns entire product lifecycle from concept to market
• Partners with engineering, design, marketing, sales
• Sets and executes product vision and strategy
• Develops product roadmaps for entire product team
• Manages product budget including development, marketing, resources
• Strategic oversight and leadership of product teams
• Exercises strategic leverage across all product lines
• Handles larger, more complex products or feature suites (Senior PM/GPM)
• Primary communication link between product teams and leadership

Key Metrics/KPIs:

• Revenue and profitability (product revenue targets)
• Roadmap delivery (on-time, on-spec)
• Customer satisfaction: NPS, customer feedback metrics
• User engagement: product usage, feature adoption
• Retention and churn rates
• Revenue metrics: MRR, ARR, revenue growth, CLV
• Business metrics: CAC, ARPU, market share, time to market
• Team metrics: velocity, product team efficiency
• 70-20-10 time allocation: 70% core product, 20% opportunities, 10% exploratory

Day-to-Day Activities:

• Creating clarity and alignment across product org
• Strategic planning and roadmap development
• Executive business reviews and board reporting
• Cross-functional partnership meetings
• Customer communication and feedback collection
• Strategic planning with executive leadership
• Cross-functional alignment with engineering, design, marketing, sales
• Roadmap reviews and prioritization
• Budget and resource allocation decisions
• Mentoring product managers

Pain Points & Priorities:

1. Managing competing stakeholder priorities (#1 challenge in 2024)
2. AI integration challenges — not every AI feature solves real problems
3. Cross-team alignment and delivery — roadmaps derailed by missed deadlines
4. Customer knowledge gaps
5. Becoming business strategists — boundaries with "business strategy" disappearing
6. Demonstrating ROI on product investments
7. Stakeholders proposing solutions rather than problems

Buying Behavior:

• Evaluation framework: functionality (25%), features (25%), usability (10%), onboarding (10%), value (10%), reviews (10%)
• Primary concern: understanding user engagement and friction points
• Need tools that convert user data into actionable insights
• Have direct budget authority for product tools
• 83% prefer self-serve during discovery and evaluation
• Trust software comparison sites (55%) and product review sites (46%)
• 81% factor in vendor's security breach history
• 57% expect positive ROI within 3 months
• Peer recommendations carry significant weight

Content Consumption:

• Newsletters: Lenny's Newsletter (300k+), ProductLed Newsletter, Mind the Product (Prioritised), ProductHQ
• Podcasts: The Product Podcast (300+ episodes), Lenny's Podcast, The Product Experience
• Communities: CPO Club, Product School alumni, Mind the Product Slack (60k+), Product School Slack (30k), Launch Awesome Slack, Creators of Products Slack (500+ active weekly)
• Best practice: Pick 3-4 newsletters max, 2-3 podcasts

Messaging Angle:

• Problem framing: "Your product decisions are based on incomplete user data" / "Stakeholder conflicts are slowing releases" / Cross-functional alignment, proving product ROI, time-to-insight bottlenecks / "How do you ensure every feature drives measurable business impact?"
• Proof points: User engagement improvements, feature adoption rates, impact on NPS/retention, case studies showing revenue impact and time savings, testimonials from peer companies
• CTA: "Want to see how [similar company] increased feature adoption by X%?" / Interest-based CTAs achieve 30% response rate vs 15% for direct booking / "Happy to share how [Company] cut prioritization debates by 60%"

Anti-Patterns:

• Feature-dumping without connecting to user/business outcomes
• Ignoring cross-functional nature of their role
• Generic "product tool" positioning without specific use case
• Generic templates without context-specific personalization
• Aggressive sales pitches — relationship-building outperforms selling
• Monday outreach — only 5.29% reply rate
• Mixing marketing and sales benchmarks
• Treating Senior PMs like individual contributors — they think strategically
• Overselling budget authority they may not have

---

Part 3: Customer Experience & Support Leadership

3.1 VP of Customer Experience

Role Responsibilities:

• Defines and executes customer experience strategy across the organization
• Leads, manages, and scales high-performing CX team
• Works with sales, marketing, product for consistent customer experience
• Develops strategies to reduce churn, increase satisfaction, identify upsell
• Owns and reports on NRR, churn, customer health to executives
• Champions customer-centric culture across departments
• Drives cross-functional initiatives to improve customer journey

Key Metrics/KPIs:

• Net Revenue Retention (NRR) — target 120%+ for fastest-growing B2B SaaS
• Churn Rate / Logo Retention Rate
• Customer Lifetime Value (CLV)
• NPS and CSAT
• Expansion Revenue
• Renewal Rate
• Customer Health Score
• Time to Value (TTV)

Pain Points & Priorities:

1. Proving ROI — must connect programs to business outcomes
2. Cross-functional collaboration (top challenge per CMSWire)
3. AI adoption concerns — privacy, bias, IP infringement
4. Data fragmentation across platforms
5. Underfunded teams with minimal headcount
6. Aligning CX initiatives with revenue goals
7. Breaking down silos between departments

Buying Behavior:

• Full budget ownership for CX technology stack
• Final say on platforms (Gainsight, ChurnZero, Totango)
• Evaluation criteria: integration, vendor references, support quality
• Team-based decisions result in better outcomes
• Long-term partnership mindset
• Requires executive-level business case

Content Consumption:

• Podcasts: Scale Tale, The Customer Success Pro Podcast, CX Nexus
• Communities: Gain Grow Retain ("most impactful CS community for B2B SaaS leaders")
• Newsletters: Customer Experience Works, EI Evolution
• Reports: Forrester CX Index, Gartner Customer Experience research

Messaging Angle:

• Problem framing: "Your CX team is running on instinct, not data. How do you prove value to the board?" / "Customer data is siloed across 5+ tools — how do you get a unified view?"
• Proof points: Express ROI in dollars: "Delivered 300% ROI, turning $10K into $40K" / NRR improvements, churn reduction percentages
• CTA: Specific date/time CTAs double meeting bookings (15% → 37%)

Anti-Patterns:

• Generic personalization with no relevance
• Emailing 10+ people at same company drops replies from 7.8% to 3.8%
• Manipulative subject lines invoking CEO's name
• Guilt-tripping follow-ups
• Focusing on features instead of business outcomes
• Not understanding their cross-functional challenges

---

3.2 Customer Success Leaders (Manager+)

Role Responsibilities:

• Nurtures customer relationships, drives satisfaction and loyalty
• Guides customers toward their goals and desired outcomes
• Manages and mentors CS team members
• Designs and implements onboarding processes
• Creates tutorials, guides, and drip campaigns
• Tracks customer progress and health metrics
• Identifies expansion and upsell opportunities
• Handles escalations and at-risk accounts

Key Metrics/KPIs:

• Renewals and renewal rate
• Expansion revenue and upsell rate
• Customer health scores
• Product adoption metrics
• Time-to-Value (TTV)
• Feature adoption rates
• Milestone completion rates
• CSAT and NPS at account level
• Churn prevention metrics

Day-to-Day Activities:

• Customer check-ins and business reviews
• Onboarding new customers
• Monitoring health scores and engagement
• Coordinating with product and support
• Training and enablement sessions
• Escalation management
• Team coaching and development
• Reporting on portfolio health

Pain Points & Priorities:

1. Burnout and stress (core issues facing CS professionals)
2. Lack of strategic seat — limited visibility and growth opportunities
3. Outdated success metrics that don't predict retention
4. Tool limitations from underfunding
5. Haphazard AI adoption without compromising human connection
6. Scaling personalized engagement
7. Balancing reactive and proactive work
8. Getting product to prioritize customer feedback

Buying Behavior:

• Influence role with growing authority — may have budget for CS tools
• Champions for tools that solve daily pain points
• Practical evaluation: "Will this help my team retain customers?"
• Trial-focused — wants to see tool in action
• Peer recommendations carry significant weight
• ROI-focused for budget justification

Content Consumption:

• Podcasts: The Customer Onboarding Podcast, Onboarding Therapy, Gain Grow Retain podcast
• Communities: Gain Grow Retain, CS in Focus, Customer Success Network
• Newsletters: CS-focused Substacks, vendor newsletters
• Format: Templates, playbooks, tactical how-tos

Messaging Angle:

• Problem framing: "You're spending hours on manual tasks instead of building customer relationships" / "Your team is reactive instead of proactive — how do you get ahead of churn?"
• Proof points: Time savings: "CSMs save 10 hours/week on manual reporting" / Churn reduction metrics, health score improvements
• CTA: Free template or checklist offer / "See how [similar company] improved TTV by 40%"

Anti-Patterns:

• Treating them as decision-makers when they need VP approval
• Enterprise-only language when they're practitioners
• Not providing immediately actionable value
• Ignoring their burnout reality
• Overly strategic messaging — they want tactical help

---

3.3 Support Leaders (Manager+) including VP of Support

Role Responsibilities:

• Leads, manages, and mentors technical support team
• Ensures delivery of high-quality support services; establishes SLAs
• Point of escalation for complex or critical issues
• Continuously evaluates and improves support processes
• Develops metrics and KPIs for optimal productivity
• Supports, coaches, develops, and supervises support agents
• Monitors daily activities: punctuality, backlog management
• Helps recruit, train, and mentor support reps
• Owns support technology stack and tooling decisions

Key Metrics/KPIs:

• First Response Time (FRT) and First Contact Resolution (FCR)
• Average Resolution Time
• SLA Compliance
• Ticket Volume and trends
• Team Productivity (tickets per agent, utilization)
• CSAT per agent and team-wide
• Backlog management and aging tickets
• Employee engagement: target 70-80%
• Escalation rates
• Agent retention and satisfaction

Day-to-Day Activities:

• Queue management and ticket triage
• Agent coaching and 1:1s
• Escalation handling
• Process improvement initiatives
• Cross-functional meetings with product/engineering
• Hiring and onboarding new agents
• Performance reviews and feedback
• Reporting to leadership
• Tool evaluation and optimization

Pain Points & Priorities:

1. Knowledge/skill gaps (51% cite as top pain point)
2. Scaling challenges — lack of processes, unclear escalation paths
3. Tool sprawl creating inefficiency
4. Team burnout from high-pressure environments
5. Automation needs for lower-level activities
6. Agent turnover and retention
7. Balancing quality with speed
8. Getting engineering to prioritize bug fixes
9. Documentation gaps

Buying Behavior:

• VP level has budget authority; Manager level is strong influencer
• Practical focus: "Will this make my team's life easier?"
• Proof-of-concept focused — wants to see tool in action
• Integration with existing stack is critical
• Peer-influenced — trusts other support leaders
• ROI must be demonstrable quickly

Content Consumption:

• Communities: Support Driven, Help Scout community
• Podcasts: Support-focused episodes on CS podcasts
• Format: Case studies, ROI calculators, benchmark reports
• Events: Support Driven Expo, vendor conferences

Messaging Angle:

• Problem framing: "Your support engineers are buried in repetitive tickets while complex issues pile up" / "You're spending time fighting fires instead of coaching your team" / "Knowledge gaps are extending resolution times by X%"
• Proof points: Agent productivity improvements, escalation reduction, time-to-competency for new hires, FCR improvements
• CTA: ROI calculator or assessment tool / "See the 5-minute demo" / offer template they can use immediately

Anti-Patterns:

• Ignoring technical depth — these are sophisticated buyers
• Pure marketing speak without substance
• Assuming Manager level has budget authority (they influence, VP decides)
• Executive-level language and strategic framing for Managers
• Long emails requiring significant time investment
• Not respecting their operational time constraints

---

3.4 Support Operations & CX Operations Leaders

Role Responsibilities:

• Architects the operational environment — designs how work flows through escalation paths, triage rules, and handover protocols; turns ad-hoc actions into structured, repeatable processes
• Owns support and CX technology stack optimization and vendor relationships
• Creates and maintains workflows, automations, and routing rules
• Defines meaningful KPIs and builds dashboards — ensures data supports decisions; helps leaders see capacity bottlenecks, volume spikes, and performance outliers
• Analyzes data to identify improvement opportunities and cost reduction
• Bridges Support, Product, Development, and Services — ensures shared ownership of issues, clean escalation paths, and meaningful feedback loops
• Oversees how knowledge is captured, organized, and accessed (internal for agents, external for customers)
• Partners with Support Leads to translate tribal knowledge into clear SOPs
• Leads process documentation and knowledge management initiatives
• Procures, implements, maintains, streamlines, and retires technology as needed
• Capacity planning, forecasting, and resource optimization

Key Metrics/KPIs:

• Operational efficiency: Cost per ticket, cost per resolution, cost per contact
• Automation metrics: Deflection rate, self-service success rate, bot containment rate
• System health: Uptime, reliability, integration success rates
• Process metrics: SLA compliance, process adherence rates, escalation accuracy
• Tool performance: Adoption rate, utilization, time-to-value for new tools
• Data quality: Accuracy, completeness, freshness across systems
• Time savings: Hours saved through automation, manual task reduction
• Throughput: Tickets per agent, queue velocity, backlog aging
• Unit costs: Fully loaded cost per interaction by channel

Compensation (US Market 2025):

• CX Operations Manager: $118,307 total (base: $87,293 + $31,013 variable); range: $94K-$151K
• Senior CX Operations Manager: $144,485 average; range: $110K-$192K
• Customer Service Operations Manager: $98,721 average; range: $78K-$127K
• Operations Support Manager: $110,383-$119,975 average; range: $57K-$113K

Day-to-Day Activities:

• System administration, configuration, and troubleshooting
• Workflow optimization and automation building (Zapier, native platform automations)
• Data analysis, reporting, and dashboard maintenance
• Vendor evaluation, contract management, and relationship management
• Process documentation and SOP creation
• Training teams on tools, processes, and best practices
• Cross-functional coordination on operational initiatives
• Capacity planning, forecasting, and staffing models
• Migration planning and execution for platform changes
• QA on data flows and integration health checks

Pain Points & Priorities:

1. Tool sprawl and integration challenges — CX teams juggle 6+ different tools; 81% believe consolidating to a single system would significantly improve CX
2. Fragmented data and systems — disconnected CRMs, helpdesks, and AI chatbots disrupt communication and create data silos
3. Three stubborn enterprise challenges: customer drop-off, slow time-to-resolution, and fragmented journeys that drive up support costs
4. Automation ROI uncertainty — "Sometimes you automate, but you're not sure if it's actually saving time or improving satisfaction"
5. Legacy system integration — adding new tools to existing CRM/ERP is technically challenging, time-consuming, and expensive
6. Data quality dependency — AI and automation effectiveness relies on data quality; poor data leads to inaccurate responses and flawed insights
7. Balancing automation with human touch — biggest challenge is losing personal touch; customers feel unheard when over-automated
8. Change management — getting teams to adopt new processes and tools
9. Limited budget — justifying operational investments without clear ROI metrics
10. Cross-departmental silos — 73% say breaking barriers is top challenge

Buying Behavior:

• Often has budget for operational tools ($10K-$50K); larger purchases need VP/Director approval
• Highly technical evaluation criteria:
  • API capabilities, webhooks, integration depth
  • Native integrations with existing stack (Zendesk, Salesforce, Intercom, Freshdesk)
  • Customization flexibility vs. out-of-box functionality
  • Data migration and implementation support
• Total cost of ownership focus — licenses, implementation, ongoing administration, training
  • Example: Zendesk is 43% cheaper TCO than Salesforce Service Cloud (Nucleus Research)
  • Salesforce recommends 2+ dedicated admins for teams over 150 seats
• Proof-of-concept required — needs to test in their actual environment with real data
• Time-to-value critical — prefer solutions that work out-of-box vs. heavy customization
• Peer recommendations from ops communities carry significant weight
• Long-term scalability is key criterion — will this grow with us?
• Security and compliance — 81% factor vendor's breach history into decisions

Tech Stack Context:

• Help desk/Ticketing: Zendesk, Salesforce Service Cloud, Freshdesk, Intercom, Help Scout
• Automation: Zapier, Workato, native platform automations, custom integrations
• Analytics: Looker, Tableau, Metabase, platform-native dashboards
• Knowledge management: Guru, Confluence, Notion, platform-native KB
• Quality assurance: MaestroQA, Klaus, Scorebuddy
• Workforce management: Assembled, Tymeshift, NICE

Content Consumption:

• Communities:
  • Support Driven (primary community for support ops)
  • RevOps Co-op (for broader ops perspective)
  • ON Community (operations professionals across industries)
  • Digital Project Manager Membership (delivery operations, tooling, capacity planning)
  • Tool-specific communities (Zendesk Community, Salesforce Trailblazer)
• Podcasts:
  • Beyond the Queue (operational aspects of support — workflows, toolsets, team dynamics)
  • Support Ops Podcast (weekly episodes with show notes newsletter)
  • The Supportive (Help Scout — customer-centric operations)
• Newsletters:
  • Operations Council (COOs and operations executives)
  • The Supportive (weekly text-based content for customer-centric folks)
  • Support Ops weekly digest
• Format preferences: Technical documentation, API guides, implementation case studies, ROI calculators, migration guides
• Reports: Operational benchmark reports, technology landscape analyses, vendor comparison guides

Messaging Angle:

• Problem framing:
  • "Your support data lives in 5 different systems — how do you get a single source of truth?"
  • "Manual processes are eating up 20+ hours per week that could be automated"
  • "Your team is juggling 6+ tools to manage CX — what if you could consolidate?"
  • "Integration gaps mean agents are copy-pasting between systems instead of helping customers"
  • "You've automated, but can you prove it's actually saving time or improving CSAT?"
• Proof points:
  • Integration success stories with specific tool combinations
  • Automation ROI with concrete time savings ("Reduced manual routing by 15 hours/week")
  • Implementation timelines ("Live in 2 weeks, not 6 months")
  • TCO comparisons with their current stack
  • Data quality improvements and their downstream impact
• CTA:
  • "See how [similar company] automated X and saved Y hours/week"
  • Technical demo or sandbox access
  • "Here's our API documentation — take a look before we talk"
  • Integration architecture review offer
  • "Want to see how this connects to your Zendesk/Salesforce?"

Anti-Patterns:

• Non-technical messaging — they'll dismiss you immediately
• Ignoring integration requirements — if you don't mention their stack, you're irrelevant
• Overpromising ease of implementation — they've been burned before
• Not understanding their current tech stack — do your homework
• Generic ROI claims without operational specifics — "saves time" means nothing without numbers
• Underestimating their technical sophistication — they often know more than the sales rep
• Promising AI will solve everything — they're skeptical after seeing AI hype fail
• Ignoring data migration complexity — a major hidden cost they're aware of
• Selling to them when decision requires VP — know the budget threshold
• Marketing fluff instead of technical substance — they value precision

---

Part 4: Developer Relations, Docs & Community

4.1 Head of Developer Relations / VP DevRel

Role Responsibilities:

• Leads and scales global developer engagement strategy
• Establishes goals and KPIs for engagement, activation, retention
• Serves as connective tissue between developers and product teams
• Champions developer needs internally
• Owns end-to-end vision for advocacy, education, community, enablement

Key Metrics/KPIs:

• Top 2 KPIs: Registered developer accounts (48%) and developer satisfaction (48%)
• Primary goal: Driving awareness and adoption (66% cite as top priority)
• Product usage (36% track as top community metric)
• Active users (44% as primary success measure)
• Revenue influence (18% now link directly)

Day-to-Day Activities:

• Content development is #1 activity: 50.3% educational content, 43.5% docs
• Advocacy (43.2% top 3 activity)
• Public speaking/events (40.3%)
• Strategic planning and budget management

Pain Points & Priorities:

1. Proving ROI — difficulty connecting to business outcomes
2. Newsletter signups falling (11.8% → 3.7%)
3. Documentation tools fragmentation
4. Balancing technical credibility vs. marketing perception
5. Resource constraints — small teams covering everything

Buying Behavior:

• Peer-influenced — rely on vendor knowledge and peer reviews
• Experience-focused — expect seamless trial experiences and pricing transparency
• Will personally test tools before recommending
• Budget: Typically has authority for tools under $10-50K

Content Consumption:

• Podcasts: DevRel Roundtable, Community Pulse
• Newsletters: DevRel Weekly
• Communities: DevRel Collective
• Trusted: State of Developer Relations report, JetBrains Developer Ecosystem

Messaging Angle:

• Problem framing: "Your DevRel team is spending 50% on content creation but struggling to prove ROI"
• Proof points: Impact on developer activation, time-to-first-API-call, support ticket reduction
• CTA: "See how [similar company] increased developer activation by X%" / Free pilot

Anti-Patterns:

• Generic "let me pick your brain" outreach
• Treating them like marketing — they identify as technical practitioners
• Not referencing their talks, blogs, or podcasts
• Calendar links in first email
• Buzzword-heavy messaging
• Pitching without understanding their stack

---

4.2 Developer Advocate (Senior/Lead Level)

Role Responsibilities:

• Helps execute developer advocacy strategy
• Owns content series, leads workshops, represents company at conferences
• Creates reference applications and technical deep dives
• Actively champions best practices in technical communities
• Translates developer feedback into product suggestions

Day-to-Day Activities:

• Conference speaking (10+ events per year)
• Content creation: blogs, videos, demos
• Social media management
• Product collaboration on new features
• Customer feedback loops

Pain Points & Priorities:

1. Wearing many hats — too many responsibilities
2. Proving individual impact
3. Travel burnout
4. Balancing technical depth vs. breadth
5. Tool fragmentation
6. AI-generated code quality issues (45% cite "almost right" solutions as pain point)

Messaging Angle:

• Problem framing: "You're creating amazing content but spending too much time on repetitive tasks"
• Proof points: Time saved per week, content production increases
• CTA: Quick async demo / Free trial with existing content

Anti-Patterns:

• Not knowing their public work — reference their talks and blogs
• Asking for too much time upfront
• Over-promising AI capabilities — they're skeptical

---

4.3 Developer Advocate (IC/Junior Level)

Role Responsibilities:

• Manning booths at events, giving presentations, networking
• Creating content, attending team meetings, helping solve developer issues
• Conference speaking with varying audience skill levels
• Community engagement in discussions and Q&A
• Feedback collection and reporting

Pain Points & Priorities:

1. Career path uncertainty
2. Credibility building with engineering peers
3. Content volume pressure
4. Tool overload
5. Imposter syndrome

Buying Behavior:

• Limited budget authority — recommend but rarely approve
• Trial-first — extensively test free tiers
• Peer-influenced — look for tools used by admired DevRel professionals

Messaging Angle:

• Problem framing: "You're juggling conference prep, content creation, and community management with limited time"
• Proof points: "Used by X DevRel professionals" / Templates they can use immediately
• CTA: Free trial / Quick video demo (under 5 min)

Anti-Patterns:

• Assuming they have budget authority
• Too formal/corporate tone
• Ignoring their growth ambitions

---

4.4 Head of Technical Writing / Docs Lead

Role Responsibilities:

• Leads technical writing department; sets documentation strategy
• Ensures materials are accurate, user-friendly, and compliant
• Prioritizes work, defines strategies, organizes work among writers
• Reviews contributions for quality
• Defines and tracks documentation metrics

Key Metrics/KPIs:

• Documentation quality (user feedback, readability, completeness)
• Quantity metrics (pages published, update frequency, coverage)
• Support ticket reduction
• Time-to-publish
• Search analytics (successful vs. failed searches)

Pain Points & Priorities:

1. Documentation going stale — hard to sync with code
2. Review delays — getting feedback when deadlines loom
3. SME coordination — 30% of time spent on this
4. Tool fragmentation — homegrown wikis that break at scale
5. AI tool limitations — docs-focused AI editing largely flunked in 2024

Buying Behavior:

• Evaluation: ease of use, quality, collaboration, customization, integrations, community support
• Typically has budget for documentation tools
• Integration with dev workflows (GitHub, CI/CD) essential
• Creates structured comparison matrices

Content Consumption:

• Communities: Write the Docs (21k+ on Slack)
• Podcasts: I'd Rather Be Writing (4.5/5 rating)
• Conferences: Write the Docs, API the Docs

Messaging Angle:

• Problem framing: "Your team spends 30% of their time chasing SMEs for reviews"
• Proof points: Time saved on coordination, freshness improvements, support ticket reduction
• CTA: "See how [similar company] reduced stale docs by X%" / Compare to competitor

Anti-Patterns:

• Marketing fluff — they value precision (they are professional writers)
• Promising AI will write their docs
• Not understanding docs-as-code

---

4.5 Technical Writer / Documentation Specialist

Role Responsibilities:

• Writing user guides, API documentation, onboarding materials
• Translating technical concepts into clear language
• Working with SMEs to gather accurate information
• Keeping documentation up-to-date
• Ensuring style consistency

Pain Points & Priorities:

1. Developers deprioritizing documentation
2. Information accuracy and consistency
3. Review bottlenecks
4. Tool limitations
5. Copy-paste duplication multiplying maintenance

Buying Behavior:

• Limited direct authority — recommends tools
• Strong influencer — input shapes decisions
• Hands-on testers through free trials
• Community-influenced by Write the Docs recommendations

Messaging Angle:

• Problem framing: "You're spending hours chasing engineers for reviews while documentation gets stale"
• Proof points: Time saved, integration with Git/GitHub, peer testimonials
• CTA: Free trial / "Works with your existing Git workflow"

Anti-Patterns:

• Talking over their heads about business metrics
• Marketing language — they write for clarity
• Promising to replace them with AI

---

4.6 Head / VP / Manager of Community

Role Responsibilities:

• Develops strategies for member participation, loyalty, advocacy
• Ensures community activities sync with company mission
• Focuses on systems, scaling, direction (not day-to-day)
• Manages community team
• Provides strategic insights to leadership

Key Metrics/KPIs:

• Engagement: DAU, MAU, weekly interactions
• Growth: month-over-month, community growth velocity
• Satisfaction: NPS, customer satisfaction
• Business impact: retention, CAC reduction, revenue influence
• 79% report communities positively impact organizational goals

Pain Points & Priorities:

1. Proving ROI — 58% cite perception-based hurdles
2. Resource constraints — 16% have no full-time community staff (highest ever)
3. Manual effort — only 36% use automation tools
4. Member engagement
5. Layoffs impact — 37% have experienced layoffs

Buying Behavior:

• Evaluates all aspects of vendor offerings against community needs
• Incorporates stakeholder input
• Creates comparison matrices across features, pricing, implementation
• Considers long-term partnership potential

Content Consumption:

• Newsletters: CMX Weekly (12k+ readers), Community Club Weekly
• Reports: CMX Community Industry Trends Report
• Communities: CMX Slack, Community Club

Messaging Angle:

• Problem framing: "Your community positively impacts the business, but proving ROI to leadership remains the challenge"
• Proof points: Impact on retention, reduction in CAC, time saved through automation
• CTA: "See how [similar company] proved community ROI to their exec team"

Anti-Patterns:

• Treating community as just marketing
• Ignoring the ROI challenge — it's their biggest pain point
• Overly salesy approach
• Ignoring layoff context — be sensitive to resource constraints

---

Part 5: Growth & Content

5.1 VP / Head of Growth

Role Responsibilities:

• Sets vision and strategy for customer acquisition, retention, monetization
• Works with marketing, sales, product for sustainable expansion
• Responsible for hiring, coaching, retaining growth team
• Controls departmental budgets with authority to greenlight spend
• Compensation: $250K-$450K in US SaaS (60/40 or 70/30 base-to-variable)

Key Metrics/KPIs:

• Revenue: ARR, MRR, Net Revenue Retention (NRR)
• Efficiency: CAC, LTV:CAC ratio, Payback Period
• Customer: Churn Rate, Customer Lifetime Value
• Team: quota attainment, pipeline growth

Pain Points & Priorities:

1. Lead quality crisis — 61% say finding high-quality leads is biggest challenge
2. Rising CAC ($500 to $10,000+ each)
3. Complex buying journeys (266 touchpoints average)
4. Slowing net-new growth
5. Self-serve revenue development

Buying Behavior:

• Software buying power shifted to line-of-business executives
• Evaluation: business alignment, tech stack integration, scalability
• 60% prefer self-led purchasing with hands-on product evaluation
• 13 people involved on average in B2B purchase decisions

Content Consumption:

• Podcasts: SaaStr Podcast, The Growth Hub
• Communities: Reforge, FINITE, SaaStock, B2B Entrepreneurs (17k+)
• Format: Quick educational bursts, micro demos, customer stories

Messaging Angle:

• Problem framing: "Your CAC has doubled in 2 years while conversion rates stayed flat"
• Proof points: Deployment success with similar-stage companies, outcome metrics
• CTA: Question-phrased CTAs get double reply rates; interest-based achieve 30%

Anti-Patterns:

• Generic opening lines ("I hope you are doing well")
• Overly broad targeting (50 or fewer recipients = 5.8% reply vs 2.1% for 1,000+)
• Talking about ROI reduces success by 15% — show, don't tell

---

5.2 Growth Manager / Growth Lead

Role Responsibilities:

• Owns growth metrics and commercial goals
• Sits between marketing and product; facilitates information flow
• Develops hypotheses and designs experiments
• Closely monitors funnel metrics and cohort analyses
• Responsible for acquisition, activation, retention, up-selling
• 43% of B2B SaaS companies now have dedicated growth team

Key Metrics/KPIs:

• Activation Rate, Time to Value (TTV)
• Free-to-paid conversion, adoption rate
• NRR, retention rate, Customer Effort Score
• LTV:CAC ratio, experiment velocity

Pain Points & Priorities:

1. Data silos and fragmentation
2. Tool stack complexity
3. Attribution and reporting gaps
4. Experiment measurement accuracy
5. Balancing cost and insight per experiment

Buying Behavior:

• Often influence rather than final authority
• GPMs may have P&L responsibilities
• Consult end-users and executives regarding budget
• Evaluation: integration, scalability, time-to-value

Messaging Angle:

• Problem framing: "Your team is running experiments but can't connect results to revenue impact"
• Proof points: Experiment velocity improvements, integration ease, activation/conversion improvements
• CTA: Low-commitment: "Worth a 15-minute look at how [similar company] improved activation by 23%?"

Anti-Patterns:

• Wrong targeting (emailing engineering instead of growth)
• Too many personalization variables (>5 can backfire)
• Long-form emails — single pain, single idea, single CTA

---

5.3 Content Creator (Recruiting Context)

Role Responsibilities:

• Creates and publishes digital content: articles, videos, podcasts, social
• Develops engaging content for employer branding and talent attraction
• Creates day-in-the-life videos, employee testimonials, behind-the-scenes
• Develops editorial calendars; ensures consistent production
• Works with marketing, design, and recruiting teams

Key Metrics/KPIs:

• Recruitment: Time to Hire, Cost Per Hire, Source of Hire
• Engagement: video views (200-300% more engagement), content performance
• Brand: Candidate NPS, employer brand awareness
• Content: views, shares, comments, conversion to applicants

Pain Points & Priorities:

1. Time and budget constraints — 88% want more video but production is expensive
2. Limited budget — only 8% of HR leaders have dedicated employer branding budget
3. Content volume demands — 7.5M new blog posts daily
4. Reaching young talent in competitive market
5. Speed requirements in hiring

Buying Behavior:

• Often limited budget — require buy-in from multiple levels
• Decision influencers: CEO (smaller orgs), HR/Talent leads, Communications
• Evaluation: scalability, ease of use, ATS integration, time-to-value

Content Consumption:

• Podcasts: Employer Branding Unfiltered, The Employer Branding Podcast
• Newsletters: Recruiting Brainfood
• Format: Practical how-to, case studies, templates, trend reports

Messaging Angle:

• Problem framing: "Your team creates 1 employer brand video per quarter when competitors publish weekly"
• Proof points: Time savings, cost reduction vs. agency, engagement improvements
• CTA: Personalization boosts replies ~32% in recruiting context

Anti-Patterns:

• Ignoring budget reality (8% have dedicated budget)
• Overpromising production value
• Missing stakeholder dynamics (need multi-level buy-in)
• Ignoring ATS integration requirements

---

Part 6: Individual Contributors & Specialists

6.1 Mid-level / Junior Product Manager

Role Responsibilities:

• Junior: Analyzing data, generating reports, reviewing feedback, working on small features
• Mid-level: Leading full cycle of feature development, conducting market research, guiding junior team members

Key Metrics/KPIs:

• Feature-level: adoption, usage frequency, activation rates
• User engagement: DAU/MAU, session duration
• Quality metrics: bug rates, user complaints, support tickets
• Delivery metrics: sprint completion, story points delivered

Buying Behavior:

• Rarely have budget authority — influence decisions, don't make them
• Key influencers in tool evaluation and adoption
• Evaluate based on ease of use and quick time-to-value
• Price-sensitive — gravitate toward free tiers
• Trial-driven — want to test before recommending

Content Consumption:

• Communities: Product Tribes Discord (10k+), FoundIt Discord, r/productmanagement
• Format preference: Frameworks, templates, career advice, tactical how-tos

Messaging Angle:

• Problem framing: "How do you prove the impact of your features to leadership?"
• Proof points: Time savings, ease of adoption, peer testimonials
• CTA: "Try free" / "See how peers use it" / Quick resource share

Anti-Patterns:

• Asking them to "get their boss on a call"
• Assuming budget authority
• Complex enterprise messaging
• Pricing that requires approval for initial exploration

---

6.2 Technical Product Manager / Platform PM

Role Responsibilities:

• Aligns technical roadmap with business goals
• Bridges technical and non-technical stakeholders
• Data self-sufficient — not dependent on BI; SQL is a superpower
• Platform PMs develop strategy for internal platforms
• Leads discussions on feature integration into existing platforms

Key Metrics/KPIs:

• Platform adoption rate
• DevEx metrics: NPS, CSAT for internal customers
• Value stream improvements: lead time, deployment frequency
• Developer efficiency and system reliability

Pain Points & Priorities:

1. Quantifying infrastructure impact — link to business outcomes rarely obvious
2. Competing priorities across internal teams
3. Difficult feedback collection from internal customers
4. Lack of maturity and support — feeling of isolation
5. Technical debt management

Buying Behavior:

• Technical evaluation is paramount
• Integration capabilities critical
• Security-conscious (81% factor breach history)
• Developer experience matters — empathize with engineering users

Messaging Angle:

• Problem framing: "How do you prove business value of platform improvements?"
• Proof points: Developer productivity metrics, reliability outcomes, architecture case studies
• CTA: Technical deep-dive / API documentation preview / Developer sandbox trial

Anti-Patterns:

• Non-technical messaging — they'll dismiss you
• Generic PM pain points without platform-specific angle
• Fluffy ROI claims without technical backing
• Ignoring security and compliance

---

Part 7: Universal Cold Email Best Practices

What Works Across All Personas

Practice	Impact
Interest-based CTAs	30% response rate vs 15% for direct booking
Question-phrased CTAs	Double reply rates
Personalized CTAs	202% better conversion than generic
Narrow targeting (1 person)	7.8% reply rate vs 3.8% for 10+
Short emails (50-125 words)	Optimal length for cold outreach
Specific date/time CTAs	Double meeting bookings (15% → 37%)
Multi-channel (email + LinkedIn)	~30% reply rates
Scheduling links	1.5x more meetings

What Fails Across All Personas

Anti-Pattern	Impact
Generic templates	Spotted instantly; trust destroyed
Spray-and-pray (10+ people)	Reply rate drops from 7.8% to 3.8%
Long emails (500+ words)	Executives skim in 5-7 seconds
Talking about ROI	Reduces success by 15% — show, don't tell
HTML-heavy formatting	Plain text outperforms
Monday outreach	Only 5.29% reply rate
Excessive follow-ups	Cap at 5 max
Guilt-tripping follow-ups	"I never heard back" decreases meetings by 14%

Follow-Up Strategy

• Email 2 is highest-leverage — +49% reply lift
• 4+ sentence follow-ups get 15x more meetings vs. lazy one-liners
• Optimal sequence: Pain > Proof > Bump > Re-Angle > Value-Add > Objection Preempt > Breakup
• Breakup emails achieve 33-76% response rate

CTA Examples by Persona Level

Level	CTA Approach
Executive (VP+)	"Worth a quick 15-minute chat?" / "Mind if I send a 2-min Loom?"
Director/Manager	"See how [similar company] achieved X" / "Happy to share our benchmark report"
IC/Individual Contributor	"Try free" / "Here's a template you can use today"
Technical roles	"Technical deep-dive available" / "See our API docs"

---

Part 8: Quick Reference Tables

Budget Authority by Role

Role	Budget Authority
CEO, Founder, Chairman	Full (company-wide)
CTO	Full (engineering/dev tools)
VP Engineering	Shared (justify to CEO/CFO)
CIO, Head of AI	Very high (explicit mandate)
CPO / VP Product	Shared (with CEO)
Product Leaders (Director+)	Yes (for product tools)
Senior PM / GPM	Often partial
Mid-level PM	Rarely
Junior PM	No
VP of CX	Full (CX tools)
CS Leaders (Manager+)	Growing; may need VP approval
Support Leaders (VP)	Full (support tools)
Support Leaders (Manager)	Influences; needs VP approval
Support Ops / CX Ops	Yes for operational tools; larger needs approval
Head of DevRel	Yes (<$10-50K); larger needs VP
Developer Advocate (Senior)	Moderate influence
Developer Advocate (Junior)	Limited influence
Head of Technical Writing	Yes (docs tools)
Technical Writer	Strong influencer
Head of Community	Yes; larger needs exec approval
VP/Head of Growth	Yes (dept budget control)
Growth Manager	Influence; may have P&L
Content Creator (Recruiting)	Limited (8% have dedicated budget)

Pain Point Summary by Archetype

Archetype	Top Pain Point
CEO, Founder, Chairman	Growth slowdown; CAC efficiency
CTO, VP Eng, Engineering Leaders	Developer productivity (32% coding time); security
CIO, Head of AI	POC abandonment (42%); proving AI ROI
Product Leaders, CPO	Competing stakeholder priorities
VP of Customer Experience	Proving ROI to leadership
Customer Success Leaders	Burnout; lack of strategic seat
Support Leaders	Knowledge gaps (51%); scaling
Support Ops / CX Ops Leaders	Tool sprawl; integration challenges
Head of DevRel	Proving business value of DevRel
Senior Dev Advocate	Wearing too many hats
Junior Dev Advocate	Career path uncertainty
Head of Tech Writing	Docs going stale
Technical Writer	Review bottlenecks
Head of Community	Proving ROI (58%)
VP/Head of Growth	Lead quality (61%)
Growth Manager	Data silos and attribution
Mid-level / Junior PM	Building credibility
Technical / Platform PM	Quantifying infrastructure impact
Content Creator (Recruiting)	Budget constraints (8% dedicated)

---

Limitations & Open Questions

Dimensions Not Fully Covered

• Regional variations: Content consumption and buying behavior may differ by geography
• Industry-specific messaging: Healthcare, fintech, and enterprise may require tailored approaches
• Company stage dynamics: Seed vs. Series C priorities and buying processes differ

Out of Scope

• Specific email template writing (covered in companion B2B Cold Email Playbook)
• Deliverability and technical setup
• Sequence automation and tooling recommendations

---

References

Evidence Files

• evidence/founder-executive-personas.md - Founder, CTO, VP Eng, CPO research
• evidence/product-leader-personas.md - Product management hierarchy research
• evidence/cx-support-personas.md - Customer experience and support research
• evidence/support-cx-ops-personas.md - Support Operations and CX Operations research
• evidence/vp-customer-experience-personas.md - VP of Customer Experience, CCO, CXO research
• evidence/vp-support-personas.md - VP of Support, Customer Service Leadership research
• evidence/cs-leaders-personas.md - Customer Success Leaders (Manager+) research
• evidence/cio-personas.md - CIO, VP IT, Chief AI Officer research
• evidence/devrel-docs-community-personas.md - Developer relations, docs, community research
• evidence/growth-ai-content-personas.md - Growth, AI, content creator research

Related Research

• ~/.claude/reports/b2b-outbound-email-effectiveness/ - B2B Cold Email Copywriting & Sales Effectiveness Playbook (general cold email principles)

Key External Sources

• State of Developer Relations 2024
• CMX Community Industry Report 2024
• Write the Docs Salary Survey 2024
• ProductLed State of B2B SaaS 2025
• Belkins Cold Email Response Rates
• Gong Cold Email CTA Research
• McKinsey Developer Productivity 2024
• Smartlead Cold Email Statistics