🎯 Multi-Dimensional Navigator
Content writing varies dramatically by industry, stage, and role. Find your path:
STEP 1: What's Your Industry Vertical?
Your industry determines:
- - Tone and voice (aggressive vs conservative)
- Risk tolerance (what you can/cannot say)
- Approval workflows (direct publish vs legal review)
- Content topics and angles
CODEBLOCK0
STEP 2: What's Your Company Stage?
Your stage determines:
- - Publishing frequency (founder bandwidth vs team)
- Content depth (tactical vs strategic)
- Approval requirements (founder autonomy vs committee)
- Resources available (DIY vs professional design)
CODEBLOCK1
STEP 3: Are You Founder or Employee?
Your role determines:
- - Editorial freedom (can you be contrarian?)
- Approval process (self-publish vs manager review)
- Personal vs company brand
- What topics are "safe" vs "risky"
CODEBLOCK2
STEP 4: What's Your Primary Market?
Your geography determines:
- - Writing style (US direct vs India relationship-focused)
- Examples and case studies (local companies)
- Compliance considerations (GDPR mentions, etc.)
CODEBLOCK3
Quick Navigation by Common Scenarios
- 1. "I'm a Sales Tech founder, want to build thought leadership"
→ Go to:
Section A1 (Sales Tech, Founder, Aggressive Voice Allowed)
- 2. "I'm VP Marketing at HR Tech, team writes content for me to review"
→ Go to:
Section B2 (HR Tech, Series B, Professional Team Content)
- 3. "I'm at fintech, every post needs legal review"
→ Go to:
Section C (Fintech, Compliance-First Content)
- 4. "I'm PMM at ops tech, write about retail execution"
→ Go to:
Section D (Operations Tech, Industry-Specific Content)
📊 SECTION A: SALES TECH CONTENT WRITING
When To Use This Section:
- - Your product: Sales engagement, conversation intelligence, sales enablement
- Your audience: Sales leaders, CROs, RevOps, SDR managers
- Your content angle: Tactical sales tips, data-driven insights, contrarian takes
- Voice: Aggressive, confident, ROI-focused, can challenge incumbents
A1: Sales Tech @ Series A (Founder Voice, Aggressive Allowed)
Your Reality Check:
CODEBLOCK4
The Sales Tech Content Philosophy:
Why Sales Leaders Engage with Content:
CODEBLOCK5
Sales Tech Voice Guidelines:
AGGRESSIVENESS SPECTRUM (Sales Tech):
CODEBLOCK6
Content Types for Sales Tech Founders:
CONTENT MIX (Sales Tech Series A):
CODEBLOCK7
Series A Sales Tech: Daily Content Workflow
MONDAY: Data-Driven Insight (1.5 hours)
CODEBLOCK8
TUESDAY: Tactical Framework (1.5 hours)
CODEBLOCK9
WEDNESDAY: Contrarian Take (1 hour)
CODEBLOCK10
THURSDAY: Quick Tip (30 minutes)
CODEBLOCK11
FRIDAY: Customer Win / Case Study (1 hour)
CODEBLOCK12
LinkedIn Algorithm Optimization (Sales Tech):
CODEBLOCK13
A2: Sales Tech @ Series B (Team Content, Professional Voice)
Your Reality Check:
CODEBLOCK14
Why Series B Content is Different:
CODEBLOCK15
Series B Sales Tech: Content Team Structure
CODEBLOCK16
Series B Approval Workflow:
CODEBLOCK17
Series B Weekly Content Calendar:
CODEBLOCK18
Series B: Data-Driven Content Strategy
CODEBLOCK19
A3: Sales Tech @ Series C+ (Category Ownership)
Your Reality Check:
CODEBLOCK20
Series C+ Content = Category Ownership
CODEBLOCK21
Series C+ Content Team:
CODEBLOCK22
Series C+ Content Strategy: Flagship Initiatives
CODEBLOCK23
Series C+ Content Distribution: Media Company Level
CODEBLOCK24
📊 SECTION B: HR TECH CONTENT WRITING
When To Use This Section:
- - Your product: HRIS, employee engagement, performance, recruiting
- Your audience: HR leaders, CHROs, People Ops, Talent teams
- Your content angle: Employee experience, people analytics, culture
- Voice: Professional, empathetic, research-backed (NEVER aggressive)
B1: HR Tech @ Series A (Founder, Professional Voice Required)
Your Reality Check:
CODEBLOCK25
Why HR Tech Content is FUNDAMENTALLY DIFFERENT:
CODEBLOCK26
HR Tech Voice Guidelines:
TONE SPECTRUM (HR Tech):
CODEBLOCK27
Content Types for HR Tech Founders:
CONTENT MIX (HR Tech Series A):
CODEBLOCK28
HR Tech Daily Content Workflow (3× per Week)
MONDAY: Research-Backed Insight (2 hours)
CODEBLOCK29
WEDNESDAY: Practical Framework (2 hours)
CODEBLOCK30
FRIDAY: Empathetic Observation (1.5 hours)
CODEBLOCK31
HR Tech: What NEVER to Post
CODEBLOCK32
B2: HR Tech @ Series B (Team Content, Brand Voice)
Your Reality Check:
CODEBLOCK33
Series B HR Tech: Elevated Professional Content
CODEBLOCK34
Series B HR Tech: Original Research Content
CODEBLOCK35
Series B HR Tech: Sensitive Topic Guidelines
CODEBLOCK36
B3: HR Tech @ Series C+ (Josh Bersin Academy-Level)
Your Reality Check:
CODEBLOCK37
Series C+ HR Tech: Industry-Defining Content
CODEBLOCK38
Series C+ Flagship Research Example:
CODEBLOCK39
📊 SECTION C: FINTECH CONTENT WRITING
When To Use This Section:
- - Your product: Payments, expense management, corporate cards, payroll
- Your audience: CFOs, Finance leaders, Controllers
- Your content angle: Regulations, compliance, financial efficiency
- Voice: ULTRA-CONSERVATIVE (legal review mandatory)
C1: Fintech @ Series A (Every Post Needs Legal Review)
Your Reality Check:
CODEBLOCK40
Why Fintech Content is HIGHEST RISK:
CODEBLOCK41
Fintech Content Guidelines (Non-Negotiable):
CODEBLOCK42
Fintech Content Mix (Conservative):
CODEBLOCK43
Fintech Approval Workflow (Mandatory):
CODEBLOCK44
Fintech Examples (Compliant vs Non-Compliant):
CODEBLOCK45
📊 SECTION D: OPERATIONS TECH CONTENT WRITING
When To Use This Section:
- - Your product: Retail execution, logistics, field force automation
- Your audience: Sales/Ops leaders at CPG/FMCG companies
- Your content angle: Distribution, retail, supply chain
- Voice: Industry-specific, B2B2B2C complexity
D1: Operations Tech @ Series A (Niche Industry Focus)
Your Reality Check:
CODEBLOCK46
Why Operations Tech Content is NICHE:
CODEBLOCK47
Operations Tech Content Topics:
CODEBLOCK48
🔄 CROSS-CUTTING: UNIVERSAL FRAMEWORKS
Role-Based Content Workflows
FOUNDER CONTENT (Full Autonomy)
CODEBLOCK49
EMPLOYEE CONTENT (Approval Required)
CODEBLOCK50
ENTERPRISE EMPLOYEE (Corporate Comms Control)
CODEBLOCK51
Geography-Specific Content Strategies
India Content Strategy:
CODEBLOCK52
US Content Strategy:
CODEBLOCK53
Common Content Mistakes & How to Fix
Mistake 1: "Writing Same Way for All Industries"
CODEBLOCK54
Mistake 2: "No Approval Process (When You Need One)"
CODEBLOCK55
Mistake 3: "Publishing at Wrong Times"
CODEBLOCK56
Prompt Templates by Scenario
Template 1: Sales Tech Founder, Aggressive Post
CODEBLOCK57
Template 2: HR Tech VP, Professional Post
CODEBLOCK58
Template 3: Fintech Founder, Compliance Post
CODEBLOCK59
CODEBLOCK60
SCENARIO:
- - Company: AI sales coaching, $3M ARR, 30 employees
- You: Co-founder & CEO
- Goal: Challenge Gong's methodology (contrarian take)
- Platform: LinkedIn
- Approval: None (founder autonomy)
CONTENT APPROACH:
TOPIC: "Gong's data on discovery calls is misleading. Here's why:"
STEP 1: GATHER DATA (Your Product)
- - Export: 50,000 sales calls from your product
- Analyze: Average discovery call length
- Finding: Your data shows 25 minutes (vs Gong's 38 minutes)
- Hypothesis: Different ICP (SMB vs enterprise)
STEP 2: WRITE HOOK (Aggressive but Credible)
"Gong says the average discovery call is 38 minutes.
We analyzed 50,000 calls and found 25 minutes.
Here's what Gong missed:"
STEP 3: BUILD CASE (Data-Driven)
The difference:
- - Gong's data: Skews enterprise (longer, more complex sales)
- Our data: Focuses SMB B2B SaaS (faster cycles)
- SMB discovery:
🎯 多维度导航
内容写作因行业、阶段和角色而异。找到你的路径:
第一步:你的行业垂直领域是什么?
你的行业决定:
- - 语气和风格(激进 vs 保守)
- 风险承受能力(能说什么/不能说什么)
- 审批流程(直接发布 vs 法务审核)
- 内容主题和角度
→ 销售科技 - 激进、逆向思维、数据驱动
→ 人力资源科技 - 专业、富有同理心、研究支撑
→ 金融科技 - 极度保守、合规优先
→ 运营科技 - 行业特定、B2B2B2C 复杂
第二步:你的公司处于什么阶段?
你的阶段决定:
- - 发布频率(创始人带宽 vs 团队)
- 内容深度(战术性 vs 战略性)
- 审批要求(创始人自主权 vs 委员会)
- 可用资源(自己动手 vs 专业设计)
→ A轮 - 创始人声音、临时应变、战术性
→ B轮 - 团队协作、专业、战略性
→ C轮以上 - 企业声音、品牌控制、定义品类
第三步:你是创始人还是员工?
你的角色决定:
- - 编辑自由度(你能逆向思维吗?)
- 审批流程(自行发布 vs 经理审核)
- 个人品牌 vs 公司品牌
- 哪些主题“安全” vs “有风险”
→ 创始人 - 完全自主,个人=公司
→ 副总裁/总监 - 经理审批,与品牌一致
→ 产品营销经理/内容 - 团队协作,品牌指南
→ 员工 - 重大限制,企业声音
第四步:你的主要市场是哪里?
你的地域决定:
- - 写作风格(美国直接 vs 印度关系导向)
- 案例和示例(本地公司)
- 合规考量(GDPR提及等)
→ 印度 - 关系驱动、本地案例、价格敏感
→ 美国 - 直接、数据驱动、高端定位
常见场景快速导航
- 1. “我是销售科技创始人,想建立思想领导力”
→ 前往:
A1部分(销售科技,创始人,允许激进声音)
- 2. “我是人力资源科技公司的营销副总裁,团队写内容给我审核”
→ 前往:
B2部分(人力资源科技,B轮,专业团队内容)
- 3. “我在金融科技公司,每篇帖子都需要法务审核”
→ 前往:
C部分(金融科技,合规优先内容)
- 4. “我是运营科技公司的产品营销经理,撰写关于零售执行的内容”
→ 前往:
D部分(运营科技,行业特定内容)
📊 第一部分 A:销售科技内容写作
何时使用本部分:
- - 你的产品:销售互动、对话智能、销售赋能
- 你的受众:销售领导者、首席营收官、营收运营、销售开发经理
- 你的内容角度:战术性销售技巧、数据驱动洞察、逆向思维观点
- 语气:激进、自信、以投资回报率为中心,可以挑战现有企业
A1:A轮销售科技(创始人声音,允许激进)
你的现实情况:
公司概况:
- - 规模:100万-1000万美元年经常性收入,10-100名员工
- 阶段:A轮
- 你:创始人或早期营销人员
- 内容目标:建立思想领导力 + 获取线索
- 发布频率:每周3-5次(主要平台:领英)
- 审批:无(创始人自主权)
- 时间:总计每周5-8小时
销售科技内容理念:
销售领导者为何参与内容互动:
销售领导者不参与的内容:
❌ 通用的励志名言
❌ 没有数据的理论
❌ 冗长的文章(没时间)
❌ 谦虚的炫耀(“我们刚刚完成了...”)
销售领导者参与的内容:
✅ 数据驱动的洞察(“分析了10,000个电话,以下是顶尖销售代表的做法”)
✅ 战术性框架(可直接复制到你的流程中)
✅ 逆向思维观点(“每个人对陌生电话的看法都错了”)
✅ 竞争情报(“Gong没告诉你的那些事”)
✅ 投资回报率计算(“这个策略 = 多23%的会议”)
销售科技语气指南:
激进程度光谱(销售科技):
过于保守(不要这样做):
“我们认为对话智能可能对某些团队有帮助...”
适度自信(这样做):
“Gong分析了100万个电话。我们分析了200万个。以下是他们遗漏的。”
过于激进(即使对销售科技来说也过了):
“Gong是垃圾。他们的数据是假的。我们比他们好100倍。”
最佳点:
- - 自信、有数据支持的论断
- 尊重但逆向思维的观点
- 在方法论上挑战品类领导者
- 但:绝不进行人身攻击,绝不提出未经证实的说法
销售科技创始人的内容类型:
内容组合(A轮销售科技):
40% 数据驱动洞察
- - “我们分析了X个销售电话,以下是我们的发现”
- “数据显示[令人惊讶的洞察]”
- 来源:你的产品数据、公开研究(Gong, Pavilion)
- 长度:300-500字
- 频率:每周2次
30% 战术性框架
- - “3个问题的发现框架”
- “如何处理价格异议 [分步指南]”
- 来源:你的经验、客户成功案例
- 长度:400-600字
- 频率:每周1-2次
20% 逆向思维观点
- - “为什么每个人都错了关于[X]”
- “Gong说[X],但数据显示[Y]”
- 来源:你独特的视角、反向研究
- 长度:200-400字
- 频率:每周1次
10% 个人/幕后故事
- - “我们是如何失去一个5万美元交易的(以及我学到的)”
- “那个改变了我们轨迹的销售招聘”
- 来源:你的经历
- 长度:300-500字
- 频率:每两周1次
A轮销售科技:每日内容工作流程
周一:数据驱动洞察(1.5小时)
09:00-09:30 | 寻找数据
销售科技数据来源:
□ 你的产品:导出匿名化指标
示例:“在我们的数据中,平均发现通话时长为32分钟”
□ 公开研究:
- Gong Labs报告(免费)
- Pavilion基准测试(如果是会员)
- 公开财报电话会(查看Salesforce, ZoomInfo)
□ 客户访谈:
- “使用我们之前/之后的成交率是多少?”
- 转化为:“客户X将成交率提高了23%”
09:30-10:30 | 撰写帖子
结构:
钩子(前两行):
“我们分析了来自中小企业B2B SaaS公司的50,000个销售电话。
平均发现通话时长为32分钟。但顶尖表现者呢?19分钟。”
展开(3-5段):
为什么这很重要:
- - 更短的通话 = 更合格的潜在客户
- 顶尖代表问更少的问题(但问题更好)
- 他们不“审问”,而是诊断
我们的发现:
- 1. 普通代表在发现阶段问18个问题
- 顶尖代表问9个问题(但都是开放式的)
- 顶尖代表67%的时间在倾听(而普通代表只有42%)
收尾(1-2段):
顶尖代表总是会问的3个问题:
- 1. “请向我介绍你目前处理[X]的流程”
- “如果未来90天内不解决这个问题,会发生什么?”
- “还有谁受到这个问题的影响?”
行动号召:
“你最喜欢的发现阶段问题是什么?”
10:30-11:00 | 编辑与发布
销售科技编辑检查清单:
□ 删减20-30%的字数(简洁 = 尊重时间)
□ 核实:每个主张都有数据/来源
□ 添加:数字、百分比、具体细节
□ 移除:废话、限定词(“我认为”、“也许”)
□ 检查:这能让销售领导者更聪明吗?
发布:
- - 时间:美国东部时间上午9点 / 太平洋时间上午6点(覆盖美国东海岸+西海岸)
- 如果在印度:印度标准时间上午9点(覆盖印度B2B受众)
- 平台:主要平台领英,次要平台X(推特)话题串
周二:战术性框架(1.5小时)
结构:
钩子:
“每个销售开发代表都应该记住的价格异议处理框架:
(从观察1,000+次价格对话中学到的)”
框架:
当他们说:“太贵了”
不要这样说:
❌ “我们其实挺实惠的”
❌ “让我和我的经理谈谈折扣”
❌ “你的预算是多少?”
要这样说(三步框架):
第一步:重新定义
“和什么相比贵?[竞争对手]?”
→ 迫使他们明确比较对象
第二步:量化他们的问题
“请告诉我,这个问题今天让你付出了什么代价。
每周