content-writing-thought-leadership

The saved excerpt is a snapshot from review. The external source remains the complete and most current version.

---
name: content-writing-thought-leadership
description: B2B content writing with daily workflows and batching systems across Sales/HR/Fintech/Ops Tech
metadata: {"clawdbot":{"emoji":"✍️","homepage":"https://github.com/shashwatgtm","always":true}}
---
## **🎯 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

```
→ Sales Tech - Aggressive, contrarian, data-driven
→ HR Tech - Professional, empathetic, research-backed
→ Fintech - Ultra-conservative, compliance-first
→ Operations Tech - Industry-specific, B2B2B2C nuanced
```

### **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)

```
→ Series A - Founder voice, scrappy, tactical
→ Series B - Team effort, professional, strategic
→ Series C+ - Corporate voice, brand-controlled, category-defining
```

### **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"

```
→ Founder - Full autonomy, personal = company
→ VP/Director - Manager approval, aligned with brand
→ PMM/Content - Team collaboration, brand guidelines
→ Employee - Significant constraints, corporate voice
```

### **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.)

```
→ India - Relationship-driven, local examples, price-conscious
→ US - Direct, data-driven, premium positioning
```

---

## **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:**

```
COMPANY PROFILE:
- Size: $1M-10M ARR, 10-100 employees
- Stage: Series A
- You: Founder or early marketing hire
- Content goal: Build thought leadership + leads
- Publishing: 3-5× per week (LinkedIn primary)
- Approval: None (founder autonomy)
- Time: 5-8 hours/week total
```

### **The Sales Tech Content Philosophy:**

**Why Sales Leaders Engage with Content:**

```
SALES LEADERS DON'T ENGAGE WITH:
❌ Generic motivational quotes
❌ Theory without data
❌ Long-winded essays (no time)
❌ Humble bragging ("We just closed...")

SALES LEADERS ENGAGE WITH:
✅ Data-driven insights ("Analyzed 10K calls, here's what top reps do")
✅ Tactical frameworks (copy-paste into your process)
✅ Contrarian takes ("Everyone is wrong about cold calling")
✅ Competitive intelligence ("What Gong doesn't tell you")
✅ ROI calculations ("This tactic = 23% more meetings")
```

#