content-writing-thought-leadership-2
B2B content writing with daily workflows and batching systems across Sales/HR/Fintech/Ops Tech
What this skill does
## **๐ฏ 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")
```
### **Sales Tech Voice Guidelines:**
**AGGRESSIVENESS SPECTRUM (Sales Tech):**
```
TOO TIMID (Don't Do This):
"We think conversation intelligence might be helpful for some teams..."
APPROPRIATELY CONFIDENT (Do This):
"Gong analyzed 1M calls. We analyzed 2M. Here's what they missed."
TOO AGGRESSIVE (Even for Sales Tech):
"Gong is garbage. Their data is fake. We're 100ร better."
SWEET SPOT:
- Confident, data-backed assertions
- Respectful but contrarian takes
- Challenge category leaders on methodology
- But: Never personal attacks, never unverified claims
```
### **Content Types for Sales Tech Founders:**
**CONTENT MIX (Sales Tech Series A):**
```
40% DATA-DRIVEN INSIGHTS
- "We analyzed X sales calls, here's what we found"
- "The data says [surprising insight]"
- Source: Your product data, public research (Gong, Pavilion)
- Length: 300-500 words
- Frequency: 2ร per week
30% TACTICAL FRAMEWORKS
- "The 3-question discovery framework"
- "How to handle pricing objections [step-by-step]"
- Source: Your experience, customer wins
- Length: 400-600 words
- Frequency: 1-2ร per week
20% CONTRARIAN TAKES
- "Why everyone is wrong about [X]"
- "Gong says [X], but the data shows [Y]"
- Source: Your unique perspective, counter-research
- Length: 200-400 words
- Frequency: 1ร per week
10% PERSONAL/BEHIND-THE-SCENES
- "How we lost a $50K deal (and what I learned)"
- "The sales hire that changed our trajectory"
- Source: Your journey
- Length: 300-500 words
- Frequency: 1ร every 2 weeks
```
### **Series A Sales Tech: Daily Content Workflow**
**MONDAY: Data-Driven Insight (1.5 hours)**
```
09:00-09:30 | Find Data
SALES TECH DATA SOURCES:
โก Your product: Export anonymized metrics
Example: "Average discovery call = 32 minutes in our data"
โก Public research:
- Gong Labs reports (free)
- Pavilion benchmarks (if member)
- Public earnings calls (check Salesforce, ZoomInfo)
โก Customer interviews:
- "What was your close rate before/after using us?"
- Turn into: "Customer X increased close rate 23%"
09:30-10:30 | Write Post
STRUCTURE:
**HOOK (First 2 lines):**
"We analyzed 50,000 sales calls from SMB B2B SaaS companies.
The average discovery call is 32 minutes. But top performers? 19 minutes."
**BUILD (3-5 paragraphs):**
Why this matters:
- Shorter calls = more qualified prospects
- Top reps ask fewer questions (but better ones)
- They don't "interrogate," they diagnose
What we found:
1. Average rep asks 18 questions in discovery
2. Top rep asks 9 questions (but they're open-ended)
3. Top rep listens 67% of the time (vs 42% for average)
**PAYOFF (1-2 paragraphs):**
The 3 questions top reps always ask:
1. "Walk me through your current process for [X]"
2. "What happens if you don't solve this in the next 90 days?"
3. "Who else is impacted by this problem?"
**CTA:**
"What's your go-to discovery question?"
10:30-11:00 | Edit & Publish
SALES TECH EDITING CHECKLIST:
โก Cut 20-30% of words (brevity = respect for time)
โก Verify: Every claim has data/source
โก Add: Numbers, percentages, specifics
โก Remove: Fluff, qualifiers ("I think," "maybe")
โก Check: Does this make sales leaders smarter?
PUBLISH:
- Time: 9 AM EST / 6 AM PST (catch US East + West)
- If India: 9 AM IST (catch Indian B2B audience)
- Platform: LinkedIn primary, Twitter thread secondary
```
**TUESDAY: Tactical Framework (1.5 hours)**
```
STRUCTURE:
**HOOK:**
"The pricing objection framework every SDR should memorize:
(Learned this from watching 1,000+ pricing conversations)"
**FRAMEWORK:**
When they say: "That's too expensive"
DON'T say:
โ "We're actually quite affordable"
โ "Let me talk to my manager about a discount"
โ "What's your budget?"
DO say (3-step framework):
Step 1: REFRAME
"Expensive compared to what? [competitor]?"
โ Forces them to make comparison explicit
Step 2: QUANTIFY THEIR PROBLEM
"Walk me through what this problem costs you today.
How many hours per week? What's your team's loaded cost?"
โ Now you have their ROI baseline
Step 3: CONTRAST VALUE
"So you're spending $50K/year in time right now.
Our solution is $15K/year and eliminates 90% of that.
That's a $35K gain. Does that math work?"
โ Reframe from cost to investment
**EXAMPLE:**
[Insert short dialogue showing this in actioRelated in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing โ use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.