{ "schemaVersion": "1.0", "item": { "slug": "content-writing-thought-leadership", "name": "Content Writing & Thought Leadership", "source": "tencent", "type": "skill", "category": "内容创作", "sourceUrl": "https://clawhub.ai/shashwatgtm/content-writing-thought-leadership", "canonicalUrl": "https://clawhub.ai/shashwatgtm/content-writing-thought-leadership", "targetPlatform": "OpenClaw" }, "install": { "downloadMode": "redirect", "downloadUrl": "/downloads/content-writing-thought-leadership", "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=content-writing-thought-leadership", "sourcePlatform": "tencent", "targetPlatform": "OpenClaw", "installMethod": "Manual import", "extraction": "Extract archive", "prerequisites": [ "OpenClaw" ], "packageFormat": "ZIP package", "includedAssets": [ "README.md", "SKILL.md" ], "primaryDoc": "SKILL.md", "quickSetup": [ "Download the package from Yavira.", "Extract the archive and review SKILL.md first.", "Import or place the package into your OpenClaw setup." ], "agentAssist": { "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.", "steps": [ "Download the package from Yavira.", "Extract it into a folder your agent can access.", "Paste one of the prompts below and point your agent at the extracted folder." ], "prompts": [ { "label": "New install", "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete." }, { "label": "Upgrade existing", "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run." } ] }, "sourceHealth": { "source": "tencent", "status": "healthy", "reason": "direct_download_ok", "recommendedAction": "download", "checkedAt": "2026-04-23T16:43:11.935Z", "expiresAt": "2026-04-30T16:43:11.935Z", "httpStatus": 200, "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=4claw-imageboard", "contentType": "application/zip", "probeMethod": "head", "details": { "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=4claw-imageboard", "contentDisposition": "attachment; filename=\"4claw-imageboard-1.0.1.zip\"", "redirectLocation": null, "bodySnippet": null }, "scope": "source", "summary": "Source download looks usable.", "detail": "Yavira can redirect you to the upstream package for this source.", "primaryActionLabel": "Download for OpenClaw", "primaryActionHref": "/downloads/content-writing-thought-leadership" }, "validation": { "installChecklist": [ "Use the Yavira download entry.", "Review SKILL.md after the package is downloaded.", "Confirm the extracted package contains the expected setup assets." ], "postInstallChecks": [ "Confirm the extracted package includes the expected docs or setup files.", "Validate the skill or prompts are available in your target agent workspace.", "Capture any manual follow-up steps the agent could not complete." ] }, "downloadPageUrl": "https://openagent3.xyz/downloads/content-writing-thought-leadership", "agentPageUrl": "https://openagent3.xyz/skills/content-writing-thought-leadership/agent", "manifestUrl": "https://openagent3.xyz/skills/content-writing-thought-leadership/agent.json", "briefUrl": "https://openagent3.xyz/skills/content-writing-thought-leadership/agent.md" }, "agentAssist": { "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.", "steps": [ "Download the package from Yavira.", "Extract it into a folder your agent can access.", "Paste one of the prompts below and point your agent at the extracted folder." ], "prompts": [ { "label": "New install", "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete." }, { "label": "Upgrade existing", "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run." } ] }, "documentation": { "source": "clawhub", "primaryDoc": "SKILL.md", "sections": [ { "title": "šŸŽÆ Multi-Dimensional Navigator", "body": "Content writing varies dramatically by industry, stage, and role. Find your path:" }, { "title": "STEP 1: What's Your Industry Vertical?", "body": "Your industry determines:\n\nTone and voice (aggressive vs conservative)\nRisk tolerance (what you can/cannot say)\nApproval workflows (direct publish vs legal review)\nContent topics and angles\n\nā†’ Sales Tech - Aggressive, contrarian, data-driven\nā†’ HR Tech - Professional, empathetic, research-backed\nā†’ Fintech - Ultra-conservative, compliance-first\nā†’ Operations Tech - Industry-specific, B2B2B2C nuanced" }, { "title": "STEP 2: What's Your Company Stage?", "body": "Your stage determines:\n\nPublishing frequency (founder bandwidth vs team)\nContent depth (tactical vs strategic)\nApproval requirements (founder autonomy vs committee)\nResources available (DIY vs professional design)\n\nā†’ Series A - Founder voice, scrappy, tactical\nā†’ Series B - Team effort, professional, strategic\nā†’ Series C+ - Corporate voice, brand-controlled, category-defining" }, { "title": "STEP 3: Are You Founder or Employee?", "body": "Your role determines:\n\nEditorial freedom (can you be contrarian?)\nApproval process (self-publish vs manager review)\nPersonal vs company brand\nWhat topics are \"safe\" vs \"risky\"\n\nā†’ Founder - Full autonomy, personal = company\nā†’ VP/Director - Manager approval, aligned with brand\nā†’ PMM/Content - Team collaboration, brand guidelines\nā†’ Employee - Significant constraints, corporate voice" }, { "title": "STEP 4: What's Your Primary Market?", "body": "Your geography determines:\n\nWriting style (US direct vs India relationship-focused)\nExamples and case studies (local companies)\nCompliance considerations (GDPR mentions, etc.)\n\nā†’ India - Relationship-driven, local examples, price-conscious\nā†’ US - Direct, data-driven, premium positioning" }, { "title": "Quick Navigation by Common Scenarios", "body": "\"I'm a Sales Tech founder, want to build thought leadership\"\nā†’ Go to: Section A1 (Sales Tech, Founder, Aggressive Voice Allowed)\n\n\n\"I'm VP Marketing at HR Tech, team writes content for me to review\"\nā†’ Go to: Section B2 (HR Tech, Series B, Professional Team Content)\n\n\n\"I'm at fintech, every post needs legal review\"\nā†’ Go to: Section C (Fintech, Compliance-First Content)\n\n\n\"I'm PMM at ops tech, write about retail execution\"\nā†’ Go to: Section D (Operations Tech, Industry-Specific Content)" }, { "title": "šŸ“Š SECTION A: SALES TECH CONTENT WRITING", "body": "When To Use This Section:\n\nYour product: Sales engagement, conversation intelligence, sales enablement\nYour audience: Sales leaders, CROs, RevOps, SDR managers\nYour content angle: Tactical sales tips, data-driven insights, contrarian takes\nVoice: Aggressive, confident, ROI-focused, can challenge incumbents" }, { "title": "Your Reality Check:", "body": "COMPANY PROFILE:\n- Size: $1M-10M ARR, 10-100 employees\n- Stage: Series A\n- You: Founder or early marketing hire\n- Content goal: Build thought leadership + leads\n- Publishing: 3-5Ɨ per week (LinkedIn primary)\n- Approval: None (founder autonomy)\n- Time: 5-8 hours/week total" }, { "title": "The Sales Tech Content Philosophy:", "body": "Why Sales Leaders Engage with Content:\n\nSALES LEADERS DON'T ENGAGE WITH:\nāŒ Generic motivational quotes\nāŒ Theory without data\nāŒ Long-winded essays (no time)\nāŒ Humble bragging (\"We just closed...\")\n\nSALES LEADERS ENGAGE WITH:\nāœ… Data-driven insights (\"Analyzed 10K calls, here's what top reps do\")\nāœ… Tactical frameworks (copy-paste into your process)\nāœ… Contrarian takes (\"Everyone is wrong about cold calling\")\nāœ… Competitive intelligence (\"What Gong doesn't tell you\")\nāœ… ROI calculations (\"This tactic = 23% more meetings\")" }, { "title": "Sales Tech Voice Guidelines:", "body": "AGGRESSIVENESS SPECTRUM (Sales Tech):\n\nTOO TIMID (Don't Do This):\n\"We think conversation intelligence might be helpful for some teams...\"\n\nAPPROPRIATELY CONFIDENT (Do This):\n\"Gong analyzed 1M calls. We analyzed 2M. Here's what they missed.\"\n\nTOO AGGRESSIVE (Even for Sales Tech):\n\"Gong is garbage. Their data is fake. We're 100Ɨ better.\"\n\nSWEET SPOT:\n- Confident, data-backed assertions\n- Respectful but contrarian takes\n- Challenge category leaders on methodology\n- But: Never personal attacks, never unverified claims" }, { "title": "Content Types for Sales Tech Founders:", "body": "CONTENT MIX (Sales Tech Series A):\n\n40% DATA-DRIVEN INSIGHTS\n- \"We analyzed X sales calls, here's what we found\"\n- \"The data says [surprising insight]\"\n- Source: Your product data, public research (Gong, Pavilion)\n- Length: 300-500 words\n- Frequency: 2Ɨ per week\n\n30% TACTICAL FRAMEWORKS\n- \"The 3-question discovery framework\"\n- \"How to handle pricing objections [step-by-step]\"\n- Source: Your experience, customer wins\n- Length: 400-600 words\n- Frequency: 1-2Ɨ per week\n\n20% CONTRARIAN TAKES\n- \"Why everyone is wrong about [X]\"\n- \"Gong says [X], but the data shows [Y]\"\n- Source: Your unique perspective, counter-research\n- Length: 200-400 words\n- Frequency: 1Ɨ per week\n\n10% PERSONAL/BEHIND-THE-SCENES\n- \"How we lost a $50K deal (and what I learned)\"\n- \"The sales hire that changed our trajectory\"\n- Source: Your journey\n- Length: 300-500 words\n- Frequency: 1Ɨ every 2 weeks" }, { "title": "Series A Sales Tech: Daily Content Workflow", "body": "MONDAY: Data-Driven Insight (1.5 hours)\n\n09:00-09:30 | Find Data\n\nSALES TECH DATA SOURCES:\nā–” Your product: Export anonymized metrics\n Example: \"Average discovery call = 32 minutes in our data\"\n \nā–” Public research:\n - Gong Labs reports (free)\n - Pavilion benchmarks (if member)\n - Public earnings calls (check Salesforce, ZoomInfo)\n \nā–” Customer interviews:\n - \"What was your close rate before/after using us?\"\n - Turn into: \"Customer X increased close rate 23%\"\n\n09:30-10:30 | Write Post\n\nSTRUCTURE:\n\n**HOOK (First 2 lines):**\n\"We analyzed 50,000 sales calls from SMB B2B SaaS companies.\nThe average discovery call is 32 minutes. But top performers? 19 minutes.\"\n\n**BUILD (3-5 paragraphs):**\nWhy this matters:\n- Shorter calls = more qualified prospects\n- Top reps ask fewer questions (but better ones)\n- They don't \"interrogate,\" they diagnose\n\nWhat we found:\n1. Average rep asks 18 questions in discovery\n2. Top rep asks 9 questions (but they're open-ended)\n3. Top rep listens 67% of the time (vs 42% for average)\n\n**PAYOFF (1-2 paragraphs):**\nThe 3 questions top reps always ask:\n1. \"Walk me through your current process for [X]\"\n2. \"What happens if you don't solve this in the next 90 days?\"\n3. \"Who else is impacted by this problem?\"\n\n**CTA:**\n\"What's your go-to discovery question?\"\n\n10:30-11:00 | Edit & Publish\n\nSALES TECH EDITING CHECKLIST:\nā–” Cut 20-30% of words (brevity = respect for time)\nā–” Verify: Every claim has data/source\nā–” Add: Numbers, percentages, specifics\nā–” Remove: Fluff, qualifiers (\"I think,\" \"maybe\")\nā–” Check: Does this make sales leaders smarter?\n\nPUBLISH:\n- Time: 9 AM EST / 6 AM PST (catch US East + West)\n- If India: 9 AM IST (catch Indian B2B audience)\n- Platform: LinkedIn primary, Twitter thread secondary\n\nTUESDAY: Tactical Framework (1.5 hours)\n\nSTRUCTURE:\n\n**HOOK:**\n\"The pricing objection framework every SDR should memorize:\n(Learned this from watching 1,000+ pricing conversations)\"\n\n**FRAMEWORK:**\nWhen they say: \"That's too expensive\"\n\nDON'T say:\nāŒ \"We're actually quite affordable\"\nāŒ \"Let me talk to my manager about a discount\"\nāŒ \"What's your budget?\"\n\nDO say (3-step framework):\n\nStep 1: REFRAME\n\"Expensive compared to what? [competitor]?\"\nā†’ Forces them to make comparison explicit\n\nStep 2: QUANTIFY THEIR PROBLEM\n\"Walk me through what this problem costs you today.\n How many hours per week? What's your team's loaded cost?\"\nā†’ Now you have their ROI baseline\n\nStep 3: CONTRAST VALUE\n\"So you're spending $50K/year in time right now.\n Our solution is $15K/year and eliminates 90% of that.\n That's a $35K gain. Does that math work?\"\nā†’ Reframe from cost to investment\n\n**EXAMPLE:**\n[Insert short dialogue showing this in action]\n\n**CTA:**\n\"Try this next time you hear 'too expensive.'\n Let me know how it goes.\"\n\nLENGTH: 400-600 words\nTIME: 1.5 hours (research + write + edit)\n\nWEDNESDAY: Contrarian Take (1 hour)\n\nSTRUCTURE:\n\n**HOOK (Provocative):**\n\"Unpopular opinion: Gong is making your sales team WORSE.\n(And I have data to prove it)\"\n\n**SETUP:**\nEveryone thinks conversation intelligence = better sales.\nMore data = better coaching = more wins.\n\nBut here's what we're seeing:\n\n**THE CONTRARIAN INSIGHT:**\nWhen sales teams get Gong:\n- Month 1-3: 15% improvement (reps more aware)\n- Month 4-6: Flatline (back to baseline)\n- Month 7+: Often 5-10% decline\n\nWhy?\n1. Analysis paralysis (too much data, not enough action)\n2. Reps game the metrics (talk more to hit \"talk time\" goals)\n3. Managers overwhelmed (100 dashboards, 0 time to coach)\n\n**THE ALTERNATIVE VIEW:**\nConversation intelligence isn't the problem.\nHow you USE it is.\n\nBest teams:\n- Track 3 metrics max (not 30)\n- Focus on ONE skill per quarter\n- Coach live (not post-call reviews)\n\n**NUANCE (Important for Aggressive Takes):**\n\"Am I saying Gong is bad? No.\nAm I saying most teams use it wrong? Yes.\"\n\n**CTA:**\n\"Using conversation intelligence? What's working for you?\"\n\nRISK LEVEL: Medium-High\nAPPROVAL: Founder only (don't do this as employee)\nWHEN: Only if you have data + alternative\n\nTHURSDAY: Quick Tip (30 minutes)\n\nSTRUCTURE:\n\n**HOOK:**\n\"The 2-minute LinkedIn outreach hack that 3Ɨ my reply rate:\"\n\n**THE HACK:**\nBefore sending connection request:\n1. Comment on their post (genuine, add value)\n2. Wait 24 hours\n3. THEN send personalized connection request\n\nWhy it works:\n- They remember you (positive association)\n- Not cold anymore (warm intro via comment)\n- Shows you did research (not spray-and-pray)\n\n**EXAMPLE:**\n[Screenshot or dialogue]\n\n**CTA:**\n\"Try it. Let me know your reply rate.\"\n\nLENGTH: 150-250 words\nTIME: 30 minutes\nFREQUENCY: 1Ɨ per week (easy win days)\n\nFRIDAY: Customer Win / Case Study (1 hour)\n\nSTRUCTURE:\n\n**HOOK:**\n\"How a 10-person startup beat Salesforce for a $100K deal:\n(A masterclass in positioning)\"\n\n**SETUP:**\nOur customer: Small sales tech startup\nCompetitor: Salesforce (800 lb gorilla)\nDeal size: $100K annual\n\nHow they won:\n\n**THE STORY:**\nStep 1: They DIDN'T compete on features\nā†’ Salesforce has 10Ɨ more features\nā†’ That's a losing battle\n\nStep 2: They reframed the decision\nā†’ \"You have 15 sales reps. Salesforce is built for 500+ rep teams.\n You'll pay for complexity you don't need.\"\n\nStep 3: They offered implementation in 1 week\nā†’ Salesforce: 3-month implementation\nā†’ Them: Live in 1 week\n\nStep 4: They made it founder-to-founder\nā†’ CEO jumped on call (rare for Salesforce)\nā†’ Committed to being \"partner, not vendor\"\n\n**THE WIN:**\nCustomer chose them despite:\n- Salesforce brand\n- Salesforce features\n- Salesforce pricing power\n\nWhy?\n- Speed to value\n- Right-sized solution\n- Personal relationship\n\n**LESSON:**\n\"Don't compete on the incumbent's terms.\n Reframe the decision criteria.\"\n\n**CTA:**\n\"Ever competed against a giant? How'd you position?\"\n\nLENGTH: 500-700 words\nTIME: 1 hour\nFREQUENCY: 1Ɨ per week" }, { "title": "LinkedIn Algorithm Optimization (Sales Tech):", "body": "POST TIMING:\nāœ… Tuesday-Thursday, 9-11 AM EST (highest engagement)\nāœ… Avoid Monday AM (too busy), Friday PM (weekend mode)\n\nFor India market:\nāœ… Tuesday-Thursday, 9 AM-2 PM IST\n\nPOST LENGTH:\nāœ… 300-600 words (sweet spot for LinkedIn)\nāŒ <100 words (not enough depth)\nāŒ >800 words (tl;dr, save for newsletter)\n\nENGAGEMENT TACTICS:\nā–” First comment: Add value (not \"What do you think?\")\nā–” Reply to all comments within first hour (algorithm boost)\nā–” Ask specific question in CTA (not generic \"Thoughts?\")\nā–” Tag max 2 people (more = spam signal)\nā–” Use 3-5 hashtags max (Sales, SalesLeadership, B2BSales, etc.)\n\nCAROUSEL STRATEGY (Sales Tech Specific):\nWhen: Complex frameworks, multi-step processes, data visualization\nFormat: 7-10 slides\nStructure:\n- Slide 1: Hook (bold claim + data point)\n- Slides 2-8: Framework/data (one point per slide)\n- Slide 9: Summary (recap key points)\n- Slide 10: CTA (apply this, share results)\n\nTools:\n- Free: Canva (templates available)\n- Paid: Taplio ($29/mo), Shield ($12/mo)" }, { "title": "Your Reality Check:", "body": "COMPANY PROFILE:\n- Size: $10M-40M ARR, 150-500 employees\n- Stage: Series B\n- You: VP Marketing or Content Lead\n- Team: 1-2 content writers + designer\n- Content goal: Thought leadership + brand building\n- Publishing: 5-7Ɨ per week (company account)\n- Approval: Manager/CEO review for company posts\n- Budget: $3K-10K/month for content" }, { "title": "Why Series B Content is Different:", "body": "SERIES A CONTENT:\n- Founder voice (personal, authentic)\n- Scrappy (founder writes everything)\n- Tactical (helping peers)\n- Goal: Build personal + company brand\n\nSERIES B CONTENT:\n- Brand voice (professional, consistent)\n- Team effort (writers, designers, approval)\n- Strategic (thought leadership)\n- Goal: Category positioning\n\nNEW CHALLENGES:\n- Maintain authenticity while scaling\n- Multiple stakeholders (CEO, Sales, Product)\n- Balancing founder voice vs company voice\n- Higher quality bar (professional design expected)" }, { "title": "Series B Sales Tech: Content Team Structure", "body": "TEAM ROLES:\n\nCONTENT LEAD (You):\n- Strategy (what topics, what angles)\n- Approval (final say on all posts)\n- Stakeholder management (CEO, Sales, Product)\n- Metrics (track engagement, leads, brand impact)\nTime: 15-20 hours/week\n\nCONTENT WRITER (1-2 FTE):\n- Research (find data, customer stories)\n- Drafting (write posts, threads, articles)\n- Editing (polish, optimize)\n- SEO (keywords, hashtags)\nTime: 30-40 hours/week\n\nDESIGNER (Part-time or contractor):\n- Carousels (LinkedIn carousels for complex topics)\n- Infographics (data visualization)\n- Branded templates (consistent look)\nTime: 10-15 hours/week\n\nFOUNDER/CEO (Guest):\n- 1-2 posts per week under their name\n- High-level strategic takes\n- Company announcements\nTime: 2-3 hours/week (ghost-written, they edit)\n\nTOOLS & BUDGET ($3K-10K/month):\nā–” Design: Canva Pro ($13/mo) or Figma ($12/user/mo)\nā–” Scheduling: Taplio ($39/mo) or Shield ($12/mo)\nā–” Analytics: Shield Analytics ($12/mo)\nā–” Carousel creation: Canva or custom designer ($500-2K/mo)\nā–” Stock photos: Unsplash (free) or Shutterstock ($29-199/mo)\nā–” Writing tools: Grammarly Premium ($12/mo), Hemingway (free)" }, { "title": "Series B Approval Workflow:", "body": "STANDARD POST (Product update, tactical tip):\nWriter ā†’ Content Lead ā†’ Publish\nTimeline: Same day\n\nSTRATEGIC POST (Contrarian take, competitor analysis):\nWriter ā†’ Content Lead ā†’ VP Marketing ā†’ Publish\nTimeline: 1-2 days\n\nSENSITIVE POST (Pricing, roadmap, executive POV):\nWriter ā†’ Content Lead ā†’ VP Marketing ā†’ CEO ā†’ Legal (if needed) ā†’ Publish\nTimeline: 3-5 days\n\nFOUNDER GHOST-WRITE:\nWriter draft ā†’ Content Lead edit ā†’ Founder review/edit ā†’ Publish (under founder name)\nTimeline: 2-3 days\nCRITICAL: Founder has final say (it's their voice)\n\nAPPROVAL DECISION TREE:\n\nQuestion: Is this factual/tactical?\nYES ā†’ Standard approval (Content Lead)\nNO ā†’ Continue...\n\nQuestion: Does this challenge competitors/industry?\nYES ā†’ Strategic approval (VP Marketing)\nNO ā†’ Continue...\n\nQuestion: Does this touch pricing/strategy/roadmap?\nYES ā†’ Sensitive approval (CEO)\nNO ā†’ Standard approval\n\nQuestion: Could this create legal risk?\nYES ā†’ Legal review (add 3-5 days)\nNO ā†’ Proceed with appropriate approval tier" }, { "title": "Series B Weekly Content Calendar:", "body": "MONDAY:\nā–” 09:00 | Company post: Data-driven insight\n Topic: \"We analyzed 100K sales calls in Q4. Here's what changed.\"\n Writer: Staff writer\n Format: LinkedIn post (400-500 words)\n Visual: Data viz (bar chart or line graph)\n Approval: Content Lead\n \nā–” 12:00 | Founder post: Weekend reflection\n Topic: \"5 sales trends I'm watching in 2026\"\n Writer: Ghost-written (founder edits heavily)\n Format: LinkedIn post (300-400 words)\n Approval: Founder (final say)\n\nTUESDAY:\nā–” 09:00 | Company post: Tactical framework (carousel)\n Topic: \"The objection handling framework we teach customers\"\n Format: LinkedIn carousel (8-10 slides)\n Designer: Create branded template\n Writer: Framework content\n Approval: Content Lead ā†’ VP Marketing (if new framework)\n \nā–” 14:00 | Customer story (LinkedIn article)\n Topic: \"How [Customer] scaled from $5M to $20M ARR\"\n Format: Long-form article (800-1200 words)\n Writer: Interview customer, write case study\n Approval: Customer approval + Content Lead\n\nWEDNESDAY:\nā–” 09:00 | Company post: Industry commentary\n Topic: \"Gong's Series D: What it means for SMB sales tech\"\n Writer: Research news, add perspective\n Format: Analysis (400-500 words)\n Approval: Content Lead ā†’ VP Marketing (competitive topic)\n \nā–” 16:00 | Founder post: Personal insight\n Topic: \"The sales hire that changed our trajectory\"\n Writer: Ghost-written from founder interview\n Format: Story (400-500 words)\n Approval: Founder\n\nTHURSDAY:\nā–” 09:00 | Company post: Quick win\n Topic: \"3 LinkedIn prospecting tips from our SDR team\"\n Format: Short tips (250-350 words)\n Writer: Interview SDR manager\n Approval: Content Lead\n \nā–” 12:00 | Product Marketing: Feature announcement (if launching)\n Writer: PMM writes, Content Lead edits\n Format: Feature post + carousel\n Approval: PMM ā†’ Content Lead ā†’ VP Marketing\n\nFRIDAY:\nā–” 09:00 | Founder post: Weekly learnings\n Topic: \"3 things I learned this week about sales coaching\"\n Writer: Founder writes this one (authentic)\n Format: Quick reflection (200-300 words)\n Approval: None (founder direct)\n \nā–” 14:00 | Community engagement post\n Topic: \"Friday question: What's your biggest sales challenge right now?\"\n Format: Simple question + comment engagement\n Goal: Build community, spark discussion\n Approval: Content Lead\n\nWEEKEND (Schedule for Monday):\nā–” SAT | Batch write next week's drafts\nā–” SUN | Review analytics from previous week" }, { "title": "Series B: Data-Driven Content Strategy", "body": "QUARTERLY CONTENT INITIATIVES:\n\nQ1: ORIGINAL RESEARCH REPORT\n\"The State of SMB Sales 2026\"\n\nProduction:\nWeek 1-2: Survey design\n- 500+ sales leaders\n- 20 questions (multiple choice + open-ended)\n- Incentive: $50 Amazon gift card (100 recipients)\n- Platform: Typeform ($35/mo)\n\nWeek 3-4: Data collection\n- Email outreach (to customer list)\n- LinkedIn post (survey link)\n- Partner distribution (Pavilion, Sales Hacker)\n- Goal: 500+ responses\n\nWeek 5-6: Analysis\n- Data analyst: Clean data, find insights\n- Writer: Identify 5-7 key findings\n- Designer: Create data visualizations\n\nWeek 7-8: Content production\n- Full report (30-40 pages PDF)\n- Summary blog post (1,000 words)\n- LinkedIn carousel series (3-4 carousels)\n- Webinar presentation\n\nWeek 9-12: Distribution & amplification\n- Publish report (gated, capture emails)\n- 4-week LinkedIn series (one finding per week)\n- Guest posts on Sales Hacker, Pavilion\n- PR outreach (TechCrunch, SaaStr)\n- Webinar (present findings, Q&A)\n\nBudget:\n- Survey incentives: $5,000\n- Design (report): $2,000-5,000\n- Promotion: $3,000-5,000\n- Total: $10,000-15,000\n\nImpact:\n- 1,000-2,000 report downloads\n- 100-200 SQLs\n- Media coverage (TechCrunch, SaaStr mention)\n- Sales enablement (differentiation vs competitors)\n- Thought leadership (cited by industry)\n\nQ2-Q4: Additional initiatives\n- Q2: Customer benchmarking report\n- Q3: Competitive landscape analysis\n- Q4: 2027 predictions + trends" }, { "title": "Your Reality Check:", "body": "COMPANY PROFILE:\n- Size: $50M+ ARR, 500+ employees\n- Stage: Series C/D or preparing IPO\n- You: Director of Content / Head of Thought Leadership\n- Team: 3-5 FTE (writers, designers, analysts, video)\n- Content: Category-defining thought leadership\n- Budget: $20K-50K/month\n- Goal: Own the conversation (like Gong Labs, Pavilion, SaaStr)" }, { "title": "Series C+ Content = Category Ownership", "body": "SERIES A/B GOALS:\n- Generate leads\n- Build brand awareness\n- Establish thought leadership\n\nSERIES C+ GOAL:\n- OWN the conversation in your category\n- Be THE source that media/analysts/customers cite\n- Influence industry direction\n- Recruiting magnet (top talent reads your content)\n\nEXAMPLES OF CATEGORY OWNERSHIP:\n- Gong Labs (conversation intelligence insights)\n- Pavilion (GTM community + content)\n- SaaStr (B2B SaaS conferences + content)\n- First Round Review (startup advice)\n- a16z blog (startup/tech trends)\n\nYOUR CONTENT BECOMES:\n- Industry-defining (sets agenda)\n- Media-cited (journalists reference you)\n- Board-level reading (not just practitioners)\n- Recruiting tool (\"I read your blog\" in interviews)" }, { "title": "Series C+ Content Team:", "body": "ORGANIZATIONAL STRUCTURE:\n\nDIRECTOR OF CONTENT (You):\n- Strategy: What makes us category leaders?\n- Partnerships: Media, analysts, industry orgs\n- Executive alignment: CEO/CMO/Board\n- Budget management: $20K-50K/month\n- Metrics: Brand awareness, category leadership signals\n\nMANAGING EDITOR:\n- Editorial calendar: Plan 3 months ahead\n- Quality control: Everything excellent or doesn't ship\n- Writer management: Assign, edit, coach\n- Process: Systems that scale\n\nSENIOR CONTENT WRITER (2-3):\n- Original research: Lead quarterly reports\n- Thought leadership: Strategic analysis\n- Specialization: Each owns topic area\n * Writer 1: Sales methodology, frameworks\n * Writer 2: Data/research, benchmarks\n * Writer 3: Industry trends, competitive analysis\n\nDATA ANALYST:\n- Research design: Survey questions, methodology\n- Data analysis: Find insights in product data\n- Visualization: Charts, graphs, dashboards\n- Reporting: Present findings to exec team\n\nSENIOR DESIGNER:\n- Brand-level quality: Every asset premium\n- Data visualization: Make complex data clear\n- Templates: Scalable, consistent design system\n- Video production: Motion graphics for social\n\nVIDEO PRODUCER (Optional but recommended):\n- Short-form: 60-90 second LinkedIn videos\n- Webinars: Professional production quality\n- Podcast: If you have one\n- YouTube: Thought leadership channel\n\nCONTENT OPERATIONS / COORDINATOR:\n- Scheduling: Manage content calendar\n- Distribution: LinkedIn, Twitter, email, etc.\n- Analytics: Track performance across channels\n- Coordination: Keep everyone aligned\n\nTOOLS & BUDGET ($20K-50K/month):\n\nTIER 1: Publishing Infrastructure ($1K-3K/month)\nā–” CMS: WordPress, Webflow ($50-200/mo)\nā–” Email: HubSpot, Marketo ($1K-2K/mo for enterprise)\nā–” Scheduling: Hootsuite, Sprout Social ($200-500/mo)\nā–” Analytics: Google Analytics + custom dashboards\n\nTIER 2: Research & Data ($3K-10K/month)\nā–” Survey platform: Qualtrics ($200-500/mo)\nā–” Research incentives: $2K-5K per study\nā–” Data visualization: Tableau ($70/user/mo)\nā–” Industry subscriptions: Gartner, Forrester ($3K-5K/mo)\n\nTIER 3: Content Production ($5K-15K/month)\nā–” Team salaries: $15K-30K/month (3-5 FTE fully loaded)\nā–” Freelancers: Subject matter experts ($500-2K per piece)\nā–” Design tools: Adobe Creative Cloud ($55/mo/user)\nā–” Stock assets: Photos, videos ($200-500/mo)\n\nTIER 4: Distribution & Amplification ($5K-15K/month)\nā–” Paid social: LinkedIn ads ($3K-8K/mo)\nā–” Sponsorships: Industry newsletters ($2K-5K/placement)\nā–” PR agency: If needed ($5K-15K/mo retainer)\nā–” Events: Speaking slots, sponsored content\n\nTIER 5: Video & Multimedia ($5K-10K/month if doing video)\nā–” Video production: Equipment, editing software\nā–” Video editor: Part-time or contractor\nā–” Podcast production: If applicable\nā–” YouTube optimization: Thumbnails, SEO" }, { "title": "Series C+ Content Strategy: Flagship Initiatives", "body": "ANNUAL CONTENT FLAGSHIP: \"THE STATE OF B2B SALES [2026]\"\n\nThis is your category-defining research report.\n\nSCOPE:\n- Survey: 2,000-5,000 sales leaders\n- Product data: Analyze 10M+ sales conversations\n- Academic partnership: Validate with university researchers\n- Executive interviews: 50 CROs/VPs Sales\n- Timeline: 4-6 months production\n- Budget: $40K-80K\n\nMETHODOLOGY:\nMonth 1-2: Research design\n- Survey questions (partner with Qualtrics)\n- IRB approval (if partnering with university)\n- Sample selection (ensure representative)\n- Pre-test survey (100 respondents, iterate)\n\nMonth 3-4: Data collection\n- Survey distribution:\n * Email to 50K sales leaders (bought list)\n * LinkedIn campaign ($10K ad spend)\n * Partner promotion (Pavilion, Sales Hacker, SaaStr)\n * Customer outreach (guaranteed responses)\n- Goal: 2,000-5,000 complete responses\n- Incentive: $100 Amazon gift card (200 winners)\n\nMonth 5: Analysis\n- Data cleaning: Remove incomplete/invalid\n- Statistical analysis: Regression, correlation, segmentation\n- Product data integration: Combine survey + product insights\n- Visualization: 30-50 charts/graphs\n- Insights identification: What's surprising? What matters?\n\nMonth 6: Production\n- Report writing: 60-80 pages\n- Executive summary: 4-page overview\n- Design: Premium quality (looks like Gartner/Forrester)\n- Infographics: Shareable data visualizations\n- Landing page: Report download (gated)\n\nPOST-LAUNCH AMPLIFICATION (3 months):\n\nWeek 1: Launch\n- Press release: Wire services\n- Media outreach: TechCrunch, WSJ, Forbes\n- LinkedIn campaign: Promote to 100K sales leaders\n- Customer email: Send to all customers\n- Webinar: Present findings (500+ registrants)\n\nWeek 2-4: Content series\n- LinkedIn: 12 posts (one finding per post)\n- Blog: 4 deep-dive articles\n- Podcast: 3 episodes discussing findings\n- Guest posts: Publish on Pavilion, Sales Hacker, etc.\n\nMonth 2-3: Speaking circuit\n- Conferences: Present at SaaStr, Pavilion Summit, Sales 3.0\n- Webinars: Partner with complementary tools\n- Podcasts: Guest on top 10 sales podcasts\n- Customer events: Present at your user conference\n\nIMPACT METRICS:\n\nREACH:\n- 10,000+ report downloads\n- 500,000+ social impressions\n- 50+ media mentions\n- 20+ conference/podcast presentations\n\nBUSINESS:\n- 300-500 SQLs directly attributed\n- $2M-5M pipeline influenced\n- Sales enablement (differentiation in 100+ deals)\n- Recruiting (mentioned in 50+ candidate interviews)\n\nCATEGORY LEADERSHIP:\n- Cited by Gartner/Forrester in their reports\n- Referenced in competitor earnings calls\n- Academic papers cite your research\n- Industry orgs invite you to present\n- Media calls YOU for expert commentary\n\nROI:\n- Cost: $60K-100K (full production + promotion)\n- Pipeline influenced: $2M-5M\n- ROI: 20-50Ɨ (if even 1-2% of pipeline closes)" }, { "title": "Series C+ Content Distribution: Media Company Level", "body": "OWNED CHANNELS:\n\nBLOG:\n- Frequency: 2-3Ɨ per week\n- Topics: Thought leadership, research, frameworks\n- SEO: Optimized for category keywords\n- Goal: 50K-100K monthly visitors\n\nLINKEDIN (Company):\n- Frequency: 5-7Ɨ per week\n- Mix: Data insights, frameworks, company updates\n- Followers: 50K-150K+\n- Engagement: 2-5% (very high for company page)\n\nLINKEDIN (Founder/Execs):\n- CEO: 2-3Ɨ per week (high-level strategy)\n- CMO: 1-2Ɨ per week (marketing insights)\n- CRO: 1-2Ɨ per week (sales insights)\n- Followers: 10K-50K each\n- Engagement: 5-10% (personal accounts higher)\n\nYOUTUBE:\n- Frequency: 1-2Ɨ per week\n- Content: Research summaries, webinar recordings, interviews\n- Subscribers: 5K-20K\n- Goal: Thought leadership, not viral videos\n\nPODCAST:\n- Frequency: Weekly\n- Format: Interview sales leaders (30-45 min)\n- Distribution: Apple, Spotify, YouTube\n- Downloads: 1K-5K per episode\n\nEMAIL NEWSLETTER:\n- Frequency: Weekly\n- Subscribers: 20K-60K\n- Open rate: 25-35%\n- Content: Curated insights + original commentary\n\nEARNED CHANNELS:\n\nMEDIA COVERAGE:\n- TechCrunch, Forbes, WSJ (2-4Ɨ per year)\n- Industry pubs: Sales Hacker, SaaStr, Pavilion (monthly)\n- Podcasts: Top 20 sales podcasts (quarterly)\n- Position: Expert source (journalists quote you)\n\nSPEAKING:\n- Tier 1 conferences: SaaStr, Pavilion Summit, Sales 3.0 (keynote)\n- Tier 2 conferences: Regional sales events (breakout sessions)\n- Customer events: Your user conference (opening keynote)\n- Virtual: 10-20 webinars per year\n\nANALYST RELATIONS:\n- Gartner: Briefings 2Ɨ per year\n- Forrester: Wave participation\n- Pavilion: Community partnership\n- Josh Bersin: If HR Tech adjacency\n\nACADEMIC:\n- University partnerships: Research collaborations\n- Journal publications: Peer-reviewed if possible\n- Guest lectures: MBA programs (sales/marketing)\n- Thesis advising: If relevant\n\nPAID CHANNELS:\n\nSPONSORED CONTENT:\n- Industry newsletters: Pavilion, Sales Hacker ($5K-15K per placement)\n- LinkedIn ads: Promote flagship research ($10K-20K per campaign)\n- Conference sponsorships: SaaStr, Pavilion ($20K-50K per event)\n\nPARTNER CHANNELS:\n- Integration partners: Salesforce, HubSpot, Outreach (co-marketing)\n- Community partners: Pavilion, Revenue Collective (content swaps)\n- Analyst firms: Gartner, Forrester (sponsor research)\n- Academic: Universities (research partnerships)" }, { "title": "šŸ“Š SECTION B: HR TECH CONTENT WRITING", "body": "When To Use This Section:\n\nYour product: HRIS, employee engagement, performance, recruiting\nYour audience: HR leaders, CHROs, People Ops, Talent teams\nYour content angle: Employee experience, people analytics, culture\nVoice: Professional, empathetic, research-backed (NEVER aggressive)" }, { "title": "Your Reality Check:", "body": "COMPANY PROFILE:\n- Size: $2M-8M ARR, 20-80 employees\n- Stage: Series A\n- You: Founder (often ex-CHRO background)\n- Content goal: Build trust, establish expertise\n- Publishing: 2-3Ɨ per week (quality > quantity)\n- Voice: Professional, empathetic, never aggressive" }, { "title": "Why HR Tech Content is FUNDAMENTALLY DIFFERENT:", "body": "SALES TECH CONTENT:\nāœ… Aggressive, contrarian takes\nāœ… \"Gong is wrong about X\"\nāœ… Challenge incumbents publicly\nāœ… Data-driven, ROI-focused\nRisk: Low (worst case = lose followers)\n\nHR TECH CONTENT:\nāŒ NEVER aggressive or confrontational\nāŒ NEVER \"Competitor X is wrong\"\nāŒ NEVER attack category leaders\nāœ… Professional, empathetic, supportive\nāœ… Research-backed, people-focused\nRisk: HIGH (HR community is small, reputation matters)\n\nWHY THE DIFFERENCE:\n- HR community is tight-knit (everyone knows everyone)\n- HR leaders value relationships over aggressive positioning\n- HR topics are sensitive (people, culture, layoffs)\n- Attacking competitors = unprofessional (damages your brand)\n- CHRO job changes = everyone moves to different companies\n ā†’ Today's competitor could be tomorrow's customer/partner" }, { "title": "HR Tech Voice Guidelines:", "body": "TONE SPECTRUM (HR Tech):\n\nTOO AGGRESSIVE (Never Do This):\n\"Traditional performance reviews are BROKEN. Anyone still using them is hurting their team.\"\nā†’ Judgmental, attacks current practices\n\nTOO SOFT (Also Wrong):\n\"We think maybe employee engagement could possibly be important...\"\nā†’ Lacks confidence, not thought leadership\n\nAPPROPRIATE (Do This):\n\"Research shows traditional annual reviews have limitations. Here's what forward-thinking CHROs are trying instead.\"\nā†’ Research-backed, helpful, not judgmental\n\nIDEAL HR TECH VOICE:\n- Confident but not arrogant\n- Research-backed (cite studies, surveys)\n- Empathetic (understand HR challenges)\n- Helpful (provide frameworks, not just criticism)\n- Inclusive (not everyone can afford premium tools)\n- Professional (appropriate for CHRO audience)" }, { "title": "Content Types for HR Tech Founders:", "body": "CONTENT MIX (HR Tech Series A):\n\n50% RESEARCH-BACKED INSIGHTS\n- \"Culture Amp's 2026 benchmark shows X\"\n- \"New study on hybrid work effectiveness\"\n- \"People analytics: What the data actually says\"\nSource: Industry research, academic studies, your product benchmarks\nLength: 400-600 words\nFrequency: 1-2Ɨ per week\n\n30% PRACTICAL FRAMEWORKS\n- \"The 1-on-1 framework top managers use\"\n- \"How to measure culture (beyond surveys)\"\n- \"Performance review template for 100-person companies\"\nSource: Best practices, customer insights\nLength: 500-700 words\nFrequency: 1Ɨ per week\n\n15% EMPATHETIC OBSERVATIONS\n- \"The CHRO challenge no one talks about\"\n- \"Navigating layoffs with empathy [guide]\"\n- \"What I learned from 100 employee exit interviews\"\nSource: Your experience, HR community insights\nLength: 400-600 words\nFrequency: 1Ɨ every 2 weeks\n\n5% PERSONAL/VULNERABLE\n- \"The employee engagement program I launched (that failed)\"\n- \"What I got wrong about performance management\"\nSource: Your honest journey\nLength: 400-600 words\nFrequency: Monthly or less (HR = professional, limit oversharing)" }, { "title": "HR Tech Daily Content Workflow (3Ɨ per Week)", "body": "MONDAY: Research-Backed Insight (2 hours)\n\n08:00-09:00 | Find Research\n\nHR TECH RESEARCH SOURCES:\nā–” SHRM (Society for HR Management) - industry gold standard\nā–” Josh Bersin research - HR thought leader\nā–” Culture Amp blog - engagement benchmarks\nā–” Lattice blog - performance management insights\nā–” Gartner HR research (if accessible)\nā–” Harvard Business Review - people management\nā–” Academic journals - organizational psychology\n\n09:00-10:00 | Write Post\n\nSTRUCTURE:\n\n**HOOK (Research Finding):**\n\"Culture Amp's 2026 benchmark report analyzed 500,000 employee surveys.\nThe #1 driver of retention isn't compensation. It's manager effectiveness.\nBy a margin of 3Ɨ.\"\n\n**CONTEXT:**\nThis challenges conventional wisdom.\nMost CHROs focus budget on:\n- Competitive comp packages\n- Benefits improvements\n- Perks (ping pong, free lunch)\n\nMeanwhile, the data shows:\n- Manager quality = 3Ɨ more predictive of retention\n- Direct manager relationship = #1 factor\n- Yet: 60% of companies have no manager training budget\n\n**FRAMEWORK:**\nWhat top-performing companies do differently:\n1. Manager selection (promote based on leadership, not tenure)\n2. Manager training (quarterly coaching skills development)\n3. Manager accountability (retention = performance metric)\n\n**PRACTICAL APPLICATION:**\nFor small teams (50-200 employees):\n- Start: Monthly manager training (2-hour sessions)\n- Focus: 1 skill per quarter (giving feedback, career development, etc.)\n- Measure: Manager effectiveness scores in engagement surveys\n\nFor mid-market (200-1000):\n- Implement: Manager development program\n- Budget: $500-1K per manager annually\n- ROI: If retention improves 5%, savings = $X (calculate)\n\n**CTA (Professional):**\n\"How does your company invest in manager development?\nI'd love to learn from your approach.\"\n\nNOT: \"What do you think?\" (too generic)\nNOT: \"Tag a bad manager\" (unprofessional)\n\nWEDNESDAY: Practical Framework (2 hours)\n\nSTRUCTURE:\n\n**HOOK:**\n\"The 1-on-1 framework I've used with 50+ managers.\n(Backed by research from MIT Sloan and Josh Bersin)\"\n\n**PROBLEM:**\nMost 1-on-1s are status updates.\nManager asks: \"What are you working on?\"\nEmployee shares: \"Project X, Project Y\"\nNo growth. No connection. No development.\n\n**FRAMEWORK: THE 3-TOPIC STRUCTURE**\n\nTopic 1: IMMEDIATE (10 minutes)\n- What's blocking you this week?\n- Where do you need help?\n- Any urgent concerns?\n\nTopic 2: DEVELOPMENT (15 minutes)\n- What skill do you want to build this quarter?\n- What stretch opportunity interests you?\n- How can I support your growth?\n\nTopic 3: CONNECTION (5 minutes)\n- How are you feeling about work?\n- What's energizing you lately?\n- Anything personal I should know about?\n\n**WHY THIS WORKS:**\nResearch shows effective 1-on-1s have 3 elements:\n1. Task support (immediate blockers)\n2. Career development (future growth)\n3. Relationship building (personal connection)\n\nMost managers only do #1.\nTop managers balance all 3.\n\n**TEMPLATE:**\n\"Here's a simple template you can copy:\n[Link to doc or image]\"\n\n**CTA:**\n\"What's your 1-on-1 structure?\nAlways looking to improve mine.\"\n\nTONE: Helpful, not preachy\n\nFRIDAY: Empathetic Observation (1.5 hours)\n\nSTRUCTURE:\n\n**HOOK (Vulnerable Opening):**\n\"The CHRO challenge no one talks about:\nYou're responsible for culture. But you don't control it.\"\n\n**SETUP:**\nEvery CHRO has felt this:\n- CEO wants \"better culture\"\n- Board asks about \"employee engagement scores\"\n- But: You can't mandate culture\n\nYou can:\n- Design programs\n- Measure engagement\n- Create policies\n\nYou can't:\n- Control manager quality\n- Force authentic relationships\n- Manufacture belonging\n\n**THE TENSION:**\nThis creates an impossible dynamic:\nā†’ Accountable for outcomes\nā†’ Limited control over inputs\nā†’ Success depends on 100+ managers you don't directly manage\n\n**WHAT HELPS:**\nAfter talking to 30+ CHROs about this:\n\n1. REFRAME YOUR ROLE\nNot: \"Owner of culture\"\nBut: \"Enabler of culture\"\n\nYou don't create culture.\nManagers create culture.\nYou enable them to do it well.\n\n2. FOCUS ON SYSTEMS\n- Manager selection (who gets promoted)\n- Manager training (how we develop leaders)\n- Manager accountability (metrics that matter)\n\n3. MEASURE LEADING INDICATORS\nNot just: Annual engagement scores\nBut: Monthly manager effectiveness scores\n\n**CTA:**\n\"Fellow CHROs: How do you navigate this tension?\nWhat's helped you?\"\n\nTONE: Vulnerable but professional\nGOAL: Build community, not just thought leadership" }, { "title": "HR Tech: What NEVER to Post", "body": "āŒ NEVER POST:\n\n\"Workday is terrible. Here's why:\"\nā†’ Attacks competitor (unprofessional)\n\n\"If your company still does annual reviews, you're behind\"\nā†’ Judgmental to audience (many still do this)\n\n\"The engagement survey results that shocked us [gossip]\"\nā†’ Violates employee privacy\n\n\"We just poached a great CHRO from [Company]\"\nā†’ Inappropriate, burns bridges\n\n\"Hot take: HR is mostly useless\"\nā†’ Self-destructive, alienates audience\n\n\"Check out this hilarious HR meme [generic meme]\"\nā†’ Low-value, undermines expertise\n\nRULE FOR HR TECH:\nIf you wouldn't say it at SHRM Annual Conference, don't post it on LinkedIn." }, { "title": "Your Reality Check:", "body": "COMPANY PROFILE:\n- Size: $12M-40M ARR, 200-600 employees\n- Stage: Series B\n- You: Director of Content or VP Marketing\n- Team: Writer + Designer (HR background preferred)\n- Content goal: Category thought leadership\n- Publishing: 3-5Ɨ per week\n- Approval: Manager/Founder for sensitive topics\n- Budget: $5K-15K/month" }, { "title": "Series B HR Tech: Elevated Professional Content", "body": "TEAM STRUCTURE:\n\nCONTENT DIRECTOR (You):\n- Strategy (topics, angles, positioning)\n- Stakeholder management (Founder/CHRO, Sales, Product)\n- Approval (final sign-off)\n- Metrics (engagement, brand awareness, pipeline)\n\nHR CONTENT WRITER (1 FTE):\n- Ideally: Background in HR or People Ops\n- Research (SHRM, Josh Bersin, academic studies)\n- Writing (blog posts, LinkedIn, thought leadership)\n- Editing (professional quality)\n\nDESIGNER (Part-time):\n- People-focused visuals (diverse, inclusive imagery)\n- Data visualization (engagement benchmarks, survey results)\n- Brand consistency (HR Tech = warm, professional aesthetic)\n\nFOUNDER/CHRO (Guest Voice):\n- 1Ɨ per week under their name\n- Strategic POV, industry trends\n- Vulnerable shares (culture challenges)\n\nAPPROVAL WORKFLOW:\n\nSTANDARD POST (Research summary, framework):\nWriter ā†’ Content Director ā†’ Publish\nTimeline: Same day to 1 day\n\nSTRATEGIC POST (Industry POV, predictions):\nWriter ā†’ Content Director ā†’ VP Marketing ā†’ Publish\nTimeline: 2-3 days\n\nSENSITIVE POST (Layoffs, DE&I, compensation):\nWriter ā†’ Content Director ā†’ VP Marketing ā†’ Founder/CHRO ā†’ Legal (if needed)\nTimeline: 3-7 days\n\nWHY STRICTER APPROVAL FOR HR TECH:\n- People topics = sensitive (layoffs, DE&I, mental health)\n- Legal risk (employment law, EEOC, GDPR)\n- Reputation risk (HR community is small)\n- Every post reflects on company culture (practice what you preach)" }, { "title": "Series B HR Tech: Original Research Content", "body": "QUARTERLY RESEARCH INITIATIVES:\n\nQ1: \"THE STATE OF EMPLOYEE ENGAGEMENT 2026\"\n- Survey: 500-1,000 HR leaders\n- Partner: SHRM chapter for distribution\n- Content series:\n * Week 1: \"Early findings: What's changing in engagement\"\n * Week 2: \"Hybrid work impact on engagement [data]\"\n * Week 3: \"Manager effectiveness = #1 driver [deep dive]\"\n * Week 4: \"Full report release + webinar\"\n\nProduction:\n- Survey: $2K-5K (Typeform, SurveyMonkey)\n- Design: $1K-3K (report design)\n- Writer: 40 hours (analysis + writing)\n- Timeline: 6-8 weeks\n\nImpact:\n- 800-1,500 new followers\n- 50-100 inbound leads\n- Media coverage (HR Dive, HRExecutive)\n- Sales enablement (differentiation)\n\nQ2: \"MANAGER EFFECTIVENESS BENCHMARKS\"\n- Your product data: Anonymized manager scores\n- Customer interviews: 20 case studies\n- Academic validation: Partner with university\n\nQ3: \"HYBRID WORK BEST PRACTICES [2026]\"\n- Timely, high-interest\n- Multi-company research\n- Expert commentary (industrial-organizational psychologists)\n\nQ4: \"HR TECH STACK SURVEY\"\n- What tools do CHROs use?\n- Integration challenges\n- Budget benchmarks\n- Vendor satisfaction" }, { "title": "Series B HR Tech: Sensitive Topic Guidelines", "body": "LAYOFFS / WORKFORCE REDUCTIONS:\n\nIF YOUR COMPANY IS LAYING OFF:\nāŒ Don't post about it personally until official announcement\nāŒ Don't hint or foreshadow (\"Hard times ahead...\")\nāœ… Wait for official company communication\nāœ… Then: Can share empathetic reflection (after announcement)\n\nIF WRITING ABOUT LAYOFFS GENERALLY:\nāœ… Empathetic tone (people are losing jobs)\nāœ… Practical guidance (for HR leaders navigating this)\nāœ… Mental health resources\nāŒ \"Layoffs are good actually\" (insensitive)\nāŒ Naming companies doing layoffs (unless public news)\n\nEXAMPLE POST (After Your Company Layoff):\n\"We had to make difficult decisions this week.\nAs someone who had to deliver the news to incredible people,\nhere's what I learned about navigating reductions with empathy:\n\n1. Clarity (people deserve straightforward communication)\n2. Dignity (everyone gets proper support)\n3. Transparency (explain the why, not just the what)\n\nThis is hard. If you're going through this, I see you.\"\n\nTONE: Humble, empathetic, human\n\n---\n\nDIVERSITY, EQUITY & INCLUSION (DE&I):\n\nAPPROPRIATE CONTENT:\nāœ… Share research on DE&I impact\nāœ… Best practices (blind resume reviews, structured interviews)\nāœ… Personal commitment (\"We're working on...\")\nāœ… Progress + transparency (\"Here's where we are...\")\n\nINAPPROPRIATE CONTENT:\nāŒ Virtue signaling (\"We're the most diverse!\")\nāŒ Tokenism (featuring one diverse employee repeatedly)\nāŒ Oversimplifying complex topics\nāŒ Speaking over marginalized communities\n\nGUIDANCE:\n- If you're not from the community, amplify voices that are\n- Focus on systems/policies (not individual stories without permission)\n- Be honest about challenges (not just wins)\n- Legal review recommended (DE&I = potential discrimination claims)\n\n---\n\nMENTAL HEALTH:\n\nAPPROPRIATE CONTENT:\nāœ… Normalize mental health discussions\nāœ… Share company resources (EAP, mental health days)\nāœ… Manager training on recognizing signs\nāœ… Empathetic leadership (sharing your own experience)\n\nINAPPROPRIATE CONTENT:\nāŒ Armchair diagnosing (\"I think X has anxiety\")\nāŒ Oversharing personal struggles (maintain professionalism)\nāŒ Suggesting company programs replace professional help\n\nDISCLAIMERS:\nAlways include: \"If you're struggling, please seek professional help.\nResources: [crisis hotline, EAP, etc.]\"" }, { "title": "Your Reality Check:", "body": "COMPANY PROFILE:\n- Size: $50M+ ARR, 800+ employees\n- Stage: Series C/D, category leader\n- You: VP Content/Thought Leadership\n- Team: 4-6 FTE content team\n- Newsletter: Industry authority\n- Budget: $20K-50K/month\n- Subscribers: 15,000-60,000+" }, { "title": "Series C+ HR Tech: Industry-Defining Content", "body": "AMBITION:\nNot just \"a content team\"\nGoal: Be THE source for HR insights (like Josh Bersin Academy, SHRM)\n\nYOUR CONTENT BECOMES:\n- Category-defining (sets the HR agenda)\n- Academic-level rigor (published in journals)\n- SHRM conference content (you're invited to speak)\n- Board-level reading (not just HR practitioners)\n\nEXAMPLES:\n- Josh Bersin Academy (HR research + community)\n- Culture Amp content (engagement thought leadership)\n- SHRM (professional association content)\n- Lattice blog (performance management insights)\n\nTEAM STRUCTURE:\n\nVP CONTENT (You):\n- Strategy: Category ownership in HR tech\n- Partnerships: SHRM, Josh Bersin, universities\n- Executive alignment: CHRO/CEO/Board\n- Budget: $20K-50K/month\n\nMANAGING EDITOR:\n- Editorial calendar: 3-6 months ahead\n- Quality control: Academic-level rigor\n- Team management: 3-5 writers/researchers\n\nRESEARCH DIRECTOR:\n- Original research: Quarterly flagship reports\n- Academic partnerships: University collaborations\n- Data analysis: Product data + survey insights\n- Peer review: Submit to academic journals\n\nSENIOR HR CONTENT WRITERS (2-3):\n- Deep specialization:\n * Writer 1: Employee engagement, culture\n * Writer 2: Performance management, development\n * Writer 3: HR tech, analytics\n- Each owns their beat (like journalists)\n\nCOMMUNITY MANAGER:\n- SHRM chapters: Build relationships\n- LinkedIn groups: Engage HR leaders\n- Events: Coordinate speaking, webinars\n- Member support: If you have membership model\n\nTOOLS & PARTNERSHIPS:\n\nRESEARCH PARTNERS:\nā–” Universities: MIT Sloan, Stanford, Wharton (academic credibility)\nā–” SHRM: Distribution + validation\nā–” Josh Bersin Academy: Co-research opportunities\nā–” Gartner/Forrester: Analyst relations\n\nMEMBERSHIP MODEL (Advanced):\n- Free tier: Basic research, blog access\n- Premium ($199-499/year):\n * Exclusive research reports\n * Templates, frameworks, toolkits\n * Private HR community access\n * Quarterly roundtables with CHROs\n\nREVENUE POTENTIAL:\n- 5,000 premium members Ɨ $299/year = $1.5M/year\n- Reinvest in content ā†’ more free content ā†’ more members (flywheel)" }, { "title": "Series C+ Flagship Research Example:", "body": "\"THE FUTURE OF WORK: 2026 COMPREHENSIVE REPORT\"\n\nSCOPE:\n- Survey: 3,000-5,000 HR leaders globally\n- Product data: 5M+ employee engagement responses\n- Academic partnership: MIT Sloan + Stanford\n- Timeline: 6-9 months\n- Budget: $50K-100K\n\nPRODUCTION:\n\nMonth 1-2: Research Design\n- Literature review (existing research)\n- Survey design (validated questions)\n- IRB approval (university ethics board)\n- Methodology documentation (academic standards)\n\nMonth 3-5: Data Collection\n- Survey distribution:\n * SHRM partnership (300K members)\n * LinkedIn ads ($15K budget)\n * Customer outreach\n * Partner organizations\n- Goal: 3,000-5,000 complete responses\n- Executive interviews: 100 CHROs (qualitative data)\n\nMonth 6-7: Analysis\n- Quantitative: Statistical analysis (regression, factor analysis)\n- Qualitative: Theme coding (interview transcripts)\n- Product data integration: Combine survey + behavioral data\n- Validation: University researchers review methodology\n\nMonth 8: Production\n- Report: 80-100 pages (academic quality)\n- Executive summary: 6-8 pages\n- Infographic: 1-page visual summary\n- Interactive dashboard: Explore data online\n\nMonth 9: Publication & Amplification\n- Academic submission: Journal of Applied Psychology (peer review)\n- Industry release: SHRM, HR Executive, HR Dive\n- Conference: Present at SHRM Annual Conference\n- Media: Secure coverage in HBR, WSJ, Forbes\n\nIMPACT:\n\nCATEGORY LEADERSHIP:\n- Cited by Gartner in their HR Tech Magic Quadrant\n- Referenced in competitor earnings calls\n- Becomes THE source media references\n- SHRM invites you to their conferences annually\n\nBUSINESS:\n- 3,000-5,000 report downloads\n- 200-400 SQLs\n- $3M-8M influenced pipeline\n- Sales wins: \"Your research on hybrid work sealed the deal\"\n\nRECRUITING:\n- \"I read your Future of Work report\" (candidate interviews)\n- Top CHRO talent wants to work at research-driven companies\n\nACADEMIC:\n- Published in peer-reviewed journal (credibility)\n- Professors assign your research in MBA programs\n- University partnerships for future research" }, { "title": "šŸ“Š SECTION C: FINTECH CONTENT WRITING", "body": "When To Use This Section:\n\nYour product: Payments, expense management, corporate cards, payroll\nYour audience: CFOs, Finance leaders, Controllers\nYour content angle: Regulations, compliance, financial efficiency\nVoice: ULTRA-CONSERVATIVE (legal review mandatory)" }, { "title": "Your Reality Check:", "body": "COMPANY PROFILE:\n- Size: $2M-8M ARR, 20-100 employees\n- Stage: Series A\n- You: Founder\n- Content goal: Build trust (not leads - trust comes first)\n- Publishing: 1-2Ɨ per week (slower due to legal review)\n- CRITICAL: Legal review mandatory for every single post\n- Voice: Conservative, compliant, trustworthy" }, { "title": "Why Fintech Content is HIGHEST RISK:", "body": "SALES TECH:\nāœ… Aggressive positioning\nāœ… \"Gong is wrong about X\"\nRisk: Low (lose followers)\n\nHR TECH:\nāš ļø Professional, no attacks\nRisk: Medium (reputation)\n\nFINTECH:\nšŸ”“ ULTRA-CONSERVATIVE MANDATORY\nšŸ”“ LEGAL REVIEW FOR EVERY POST\nšŸ”“ NEVER make unverified claims\nšŸ”“ NEVER attack competitors\nšŸ”“ NEVER share user data\nRisk: EXTREME (regulatory fines, license revocation, criminal liability)\n\nWHY:\n- Financial regulations: RBI (India), SEC (US), FCA (UK)\n- Financial advertising rules: Can't make unverified ROI claims\n- Data privacy: Can't share user financial data (RBI compliance)\n- Reputational risk: Finance = trust-driven (one mistake = brand death)\n- Legal liability: Directors personally liable for violations" }, { "title": "Fintech Content Guidelines (Non-Negotiable):", "body": "āœ… ALWAYS ALLOWED:\n\n\"RBI released new payment aggregator guidelines. Here's what fintech companies need to know:\"\nā†’ Regulatory updates (factual, helpful)\n\n\"3 compliance checklist items for Indian fintechs [2026 edition]\"\nā†’ Educational, compliance-focused\n\n\"How we achieved SOC 2 compliance in 12 months [timeline]\"\nā†’ Your journey (factual, no claims about others)\n\n\"CFO's guide to expense management compliance\"\nā†’ Educational, helpful\n\nāŒ NEVER ALLOWED:\n\n\"Traditional banking is broken. Here's why fintech is better.\"\nā†’ Attacks incumbents (regulatory risk)\n\n\"Save 50% on payment fees with our solution\"\nā†’ Unverified ROI claim (unless proven and methodology disclosed)\n\n\"We're the fastest-growing fintech in India\"\nā†’ Superlative claim (unless third-party verified)\n\n\"Customer X saved ā‚¹10L using our product\"\nā†’ Customer data (compliance violation without written permission)\n\n\"Why [Competitor] is overpriced\"\nā†’ Competitor attack (could trigger legal action)\n\nCRITICAL RULE:\nIf you're not 100% certain it's compliant, get legal review.\nIn fintech, \"better to ask forgiveness\" DOES NOT APPLY." }, { "title": "Fintech Content Mix (Conservative):", "body": "60% REGULATORY/COMPLIANCE UPDATES\n- \"New RBI guidelines for payment companies\"\n- \"KYC requirements: What changed in 2026\"\n- \"Data localization compliance checklist\"\nSource: Official sources only (RBI, NPCI, Ministry of Finance)\nTone: Factual, educational, helpful\nFrequency: 1Ɨ per week (as regulations change)\n\n25% EDUCATIONAL BEST PRACTICES\n- \"CFO's guide to corporate expense management\"\n- \"How to evaluate payment aggregators [checklist]\"\n- \"SOC 2 compliance: Step-by-step guide\"\nSource: Industry standards, your experience\nTone: Helpful, not sales-y\nFrequency: 1Ɨ every 2 weeks\n\n10% COMPANY UPDATES (Factual Only)\n- \"We achieved SOC 2 Type II certification\"\n- \"Announcing: RBI Payment Aggregator license\"\n- \"New integration: Zoho Books\"\nSource: Your company (factual announcements)\nTone: Professional, humble\nFrequency: As milestones happen\n\n5% THOUGHT LEADERSHIP (Extremely Careful)\n- \"The future of UPI payments in India [analysis]\"\n- \"Cross-border payments: 2027 predictions\"\nSource: Industry trends (clearly labeled as opinion)\nTone: Measured, balanced, acknowledges uncertainty\nFrequency: Monthly or less" }, { "title": "Fintech Approval Workflow (Mandatory):", "body": "EVERY POST FOLLOWS THIS PROCESS:\n\nSTEP 1: DRAFT (You or Writer)\n- Write post\n- Cite all sources\n- Include disclaimers\nTime: 1-2 hours\n\nSTEP 2: SELF-CHECK\nā–” Is this factual? (verifiable)\nā–” Do I cite sources? (RBI, official sources)\nā–” Am I making claims? (if yes, can I prove them?)\nā–” Am I mentioning competitors? (if yes, is it necessary?)\nā–” Am I sharing user data? (if yes, do I have written permission?)\nā–” Is there any regulatory risk? (when in doubt, YES)\n\nSTEP 3: LEGAL REVIEW (1-3 days)\n- Send to legal counsel\n- They review for:\n * Regulatory compliance\n * Financial advertising rules\n * Data privacy\n * Competitor mention risk\n- They may:\n * Approve as-is\n * Request edits\n * Reject entirely\n\nSTEP 4: REVISE (If Needed)\n- Incorporate legal feedback\n- Re-submit for final approval\n\nSTEP 5: PUBLISH\n- Only after legal sign-off\n- Include all required disclaimers\n\nTIMELINE:\n- Simple post: 1-2 days (draft ā†’ legal ā†’ publish)\n- Complex post: 3-5 days\n- Controversial topic: May be rejected\n\nCOST:\n- Legal counsel retainer: $5K-10K/month\n- Per-post review: $200-500 (if not on retainer)\n- Worth it: Avoiding ā‚¹1 Cr fine or license revocation" }, { "title": "Fintech Examples (Compliant vs Non-Compliant):", "body": "TOPIC: Payment Processing Speeds\n\nāŒ NON-COMPLIANT:\n\"We process payments 10Ɨ faster than Razorpay.\nSwitch to us and save hours of processing time.\"\n\nISSUES:\n- Unverified claim (\"10Ɨ faster\" - can you prove it?)\n- Competitor attack (Razorpay could sue)\n- Implied guarantee (\"save hours\" - what if customer doesn't?)\n\nāœ… COMPLIANT:\n\"Payment processing speeds vary by provider and use case.\nIn our testing with 100 transactions, average processing time was X seconds.\n(Methodology: [link to documentation])\"\n\nWHY IT'S COMPLIANT:\n- Factual (your own testing)\n- Methodology disclosed\n- No competitor attacks\n- No guarantees\n\n---\n\nTOPIC: Cost Savings\n\nāŒ NON-COMPLIANT:\n\"Save 50% on payment fees!\"\n\nISSUES:\n- Unverified ROI claim\n- No methodology\n- Implies guarantee\n\nāœ… COMPLIANT:\n\"Payment fee structures vary by volume and use case.\nOur pricing: X% per transaction + ā‚¹Y fixed fee.\n[Link to pricing page]\nCompare options based on your transaction volume.\"\n\nWHY IT'S COMPLIANT:\n- Factual (your own pricing)\n- No claims about competitors\n- No ROI guarantee\n- Helpful (empowers comparison)" }, { "title": "šŸ“Š SECTION D: OPERATIONS TECH CONTENT WRITING", "body": "When To Use This Section:\n\nYour product: Retail execution, logistics, field force automation\nYour audience: Sales/Ops leaders at CPG/FMCG companies\nYour content angle: Distribution, retail, supply chain\nVoice: Industry-specific, B2B2B2C complexity" }, { "title": "Your Reality Check:", "body": "COMPANY PROFILE:\n- Size: $1M-5M ARR, 15-60 employees\n- Stage: Series A\n- You: Founder (ex-CPG or tech)\n- Content focus: India retail execution insights\n- Publishing: 2-3Ɨ per week\n- Audience: Small but highly engaged (CPG sales leaders)" }, { "title": "Why Operations Tech Content is NICHE:", "body": "SALES/HR/FINTECH:\n- Broad audience (all B2B SaaS)\n- Generic topics (sales, HR, finance)\n- Large following potential (10K+ followers)\n\nOPERATIONS TECH:\n- Niche audience (CPG/FMCG/logistics)\n- Specific topics (retail execution, distribution, field force)\n- Smaller following (1K-3K) but HIGH engagement\n- B2B2B2C complexity (You ā†’ CPG ā†’ Distributor ā†’ Retailer ā†’ Consumer)\n\nADVANTAGE OF NICHE:\nāœ… Less competition (few people write about retail execution)\nāœ… Higher engagement rate (exactly what audience needs)\nāœ… Easier to become THE expert\nāœ… Stronger community (CPG sales leaders all know each other)\nāœ… Higher intent leads (if they follow you, they're serious)" }, { "title": "Operations Tech Content Topics:", "body": "CORE TOPICS:\n\n40% RETAIL EXECUTION INSIGHTS\n- \"State of general trade in India [Q4 2025 data]\"\n- \"How kiranas are adapting to quick commerce\"\n- \"Distribution coverage: North vs South India [analysis]\"\nSource: Your product data, industry reports, field observations\nAudience: CPG sales heads, ops leaders\n\n30% FIELD FORCE BEST PRACTICES\n- \"The beat planning framework that increased coverage by 20%\"\n- \"How top field reps use mobile apps [case study]\"\n- \"Offline-first: Why it matters for rural distribution\"\nSource: Customer success stories, your product\nAudience: Field force managers, ops leaders\n\n20% CPG INDUSTRY TRENDS\n- \"Quick commerce impact on FMCG distribution [2026]\"\n- \"D2C brands: Distribution lessons for CPG\"\n- \"How HUL/ITC are changing go-to-market\"\nSource: Industry news, earnings calls, your analysis\nAudience: CPG strategy, business leaders\n\n10% TECHNOLOGY IN RETAIL/LOGISTICS\n- \"How AI is changing retail audits\"\n- \"Image recognition for planogram compliance\"\n- \"Route optimization: Tech vs manual planning\"\nSource: Your product innovation, industry tech trends\nAudience: Tech-forward ops leaders" }, { "title": "FOUNDER CONTENT (Full Autonomy)", "body": "ADVANTAGES:\nāœ… No approval needed (publish freely)\nāœ… Personal voice = authentic\nāœ… Can be contrarian (if industry allows)\nāœ… Can share company metrics\nāœ… Can pivot messaging quickly\n\nWORKFLOW:\nMonday: Idea generation (30 min)\nTuesday: Write post #1 (1 hour)\nWednesday: Publish + engage (30 min)\nThursday: Write post #2 (1 hour)\nFriday: Publish + weekly recap (30 min)\n\nTotal time: 3.5 hours/week\n\nBEST PRACTICES:\nā–” Batch content (write 2-3 posts in one sitting)\nā–” Use voice memos (capture ideas on the go)\nā–” Repurpose (newsletter ā†’ LinkedIn ā†’ Twitter thread)\nā–” Engage (comment on others' posts daily)\nā–” Track (what topics get most engagement?)" }, { "title": "EMPLOYEE CONTENT (Approval Required)", "body": "SCENARIO: VP Marketing Writing Personal Content\n\nCHALLENGES:\nāš ļø Company wants brand consistency\nāš ļø Can't share company confidential info\nāš ļø Must add \"Views are my own\" disclaimer\nāš ļø Manager needs to approve (at minimum)\n\nAPPROVAL WORKFLOW:\n\nSTEP 1: Get Manager Alignment (One-Time)\nā–” Pitch: \"I want to build thought leadership in [category]\"\nā–” Clarify: Personal brand, not company official content\nā–” Agree on boundaries:\n - What I CAN share about company\n - What I CANNOT share\n - Approval process\n\nSTEP 2: Write with Constraints\nCAN SHARE:\nāœ… Industry insights (not company-specific)\nāœ… Your professional opinions\nāœ… Public company information\nāœ… General frameworks\n\nCANNOT SHARE:\nāŒ Revenue/ARR/growth numbers (unless public)\nāŒ Roadmap/unannounced features\nāŒ Customer names (without permission)\nāŒ Internal metrics/team size\nāŒ Fundraising plans\n\nSTEP 3: Add Disclaimer\nEVERY post includes:\n\"Views expressed here are my own and do not necessarily represent the views of [Company Name].\"\n\nSTEP 4: Periodic Review\nā–” Monthly: Show manager your content\nā–” Quarterly: Confirm still aligned with company\nā–” Annually: Review and renew agreement\n\nWORKFLOW (Slower Than Founder):\nMonday: Draft post #1\nTuesday: Get manager feedback\nWednesday: Revise + publish\nThursday-Friday: Draft post #2 (publish Monday)\n\nTime: 4-5 hours/week (approval adds overhead)" }, { "title": "ENTERPRISE EMPLOYEE (Corporate Comms Control)", "body": "SCENARIO: CMO at Public SaaS Company\n\nREALITY:\nšŸ”“ EVERYTHING requires PR approval\nšŸ”“ Can't publish without 1-2 week review\nšŸ”“ Ghost-written by PR team\nšŸ”“ No personal opinions\nšŸ”“ No controversial takes\n\nCONSTRAINTS:\nā–” All posts pre-approved by:\n - Corporate Communications\n - Legal (if financial topics)\n - Executive team\n - Investor Relations (if public company)\n \nā–” Topics must be:\n - Brand-safe\n - On-message\n - Non-controversial\n - Aligned with company narrative\n\nā–” Timeline:\n - Draft ā†’ Corporate Comms (3-5 days)\n - Revisions (2-3 days)\n - Legal review (1-2 days if needed)\n - Final approval (1 day)\n - Total: 1-2 weeks per post\n\nOPTIONS:\n1. Accept constraints (corporate voice)\n2. Limit posting (1Ɨ per month, big announcements only)\n3. Internal content only (employees, not public)\n4. Wait until you leave company (build personal brand then)\n\nRECOMMENDATION:\nIf at public company or highly-regulated industry:\nā†’ Focus on thought leadership via:\n - Speaking at conferences (pre-approved topics)\n - Bylines in trade publications (legal review)\n - Podcasts as guest (talking points approved)\nā†’ Save personal LinkedIn brand for next role" }, { "title": "India Content Strategy:", "body": "PUBLISHING TIMES:\nāœ… Tuesday-Thursday, 9 AM-2 PM IST\nāœ… Avoid Monday early (week starting)\nāœ… Avoid Friday late (weekend mode)\n\nCONTENT STYLE:\n- Relationship-focused (build connections)\n- Local examples (FieldAssist, not Gong)\n- Price-conscious (acknowledge budget constraints)\n- WhatsApp mentions (\"Share this in your team WhatsApp group\")\n\nEXAMPLES:\nāœ… \"How Darwinbox scaled from 100 to 1,000 customers\"\nāœ… \"Retail execution in India: General trade vs modern trade\"\nāœ… \"RBI's new guidelines for payment companies\"\nāŒ \"How we're disrupting the US market\" (wrong geography)\n\nCOMMUNITY ENGAGEMENT:\nā–” SaaSBoomi (India B2B SaaS community)\nā–” IAMAI (fintech, if applicable)\nā–” India-specific LinkedIn groups\nā–” Respond to comments in IST hours" }, { "title": "US Content Strategy:", "body": "PUBLISHING TIMES:\nāœ… Tuesday-Thursday, 9-11 AM EST\nāœ… Some success: 12-2 PM EST (lunch scrolling)\nāœ… Avoid early mornings (West Coast asleep)\n\nCONTENT STYLE:\n- Direct, data-driven\n- US examples (Gong, Lattice, Stripe)\n- Premium positioning (value > price)\n- Email CTAs (\"Download the report\")\n\nEXAMPLES:\nāœ… \"How Gong uses conversation intelligence [analysis]\"\nāœ… \"Sales tech landscape: The rise of AI coaching\"\nāœ… \"SOC 2 compliance timeline for SaaS companies\"\nāŒ \"How we're winning in India\" (wrong geography for US audience)\n\nCOMMUNITY ENGAGEMENT:\nā–” SaaStr (B2B SaaS)\nā–” Pavilion (GTM leaders)\nā–” Revenue Collective (CROs)\nā–” Respond during US business hours" }, { "title": "Mistake 1: \"Writing Same Way for All Industries\"", "body": "WRONG:\nSame aggressive contrarian post for Sales Tech, HR Tech, and Fintech\n\nWHY IT FAILS:\n- Sales Tech: Aggressive = good\n- HR Tech: Aggressive = unprofessional\n- Fintech: Aggressive = regulatory risk\n\nFIX:\nā†’ Sales Tech ā†’ Section A (aggressive allowed)\nā†’ HR Tech ā†’ Section B (professional required)\nā†’ Fintech ā†’ Section C (ultra-conservative mandatory)" }, { "title": "Mistake 2: \"No Approval Process (When You Need One)\"", "body": "SCENARIO: Employee Publishes Without Manager Knowing\n\nRISKS:\n- Share confidential info accidentally\n- Company asks you to delete post (embarrassing)\n- Misaligned with company messaging\n- Career risk (manager upset)\n\nFIX:\nā†’ Role-Based Workflows section\nā†’ Get manager alignment BEFORE posting\nā†’ Monthly check-ins on content" }, { "title": "Mistake 3: \"Publishing at Wrong Times\"", "body": "PROBLEM:\nPublishing Friday 5 PM EST for US sales leaders\n\nRESULT:\n- Low engagement (everyone checked out)\n- Algorithm doesn't boost\n- Wasted content\n\nFIX:\n- India: Tuesday-Thursday, 9 AM-2 PM IST\n- US: Tuesday-Thursday, 9-11 AM EST\n- Test and track what works for YOUR audience" }, { "title": "Template 1: Sales Tech Founder, Aggressive Post", "body": "Using Content Writing skill, Section A1:\n\nI'm a Sales Tech founder. I want to write an aggressive but data-backed post.\n\nTopic: [Your contrarian take]\nData: [What data do you have?]\nCompetitor context: [Are you challenging Gong/Outreach/etc?]\n\nPlease:\n1. Write hook (contrarian, attention-grabbing)\n2. Present data (credible, specific)\n3. Build case (logical progression)\n4. Include nuance (not just aggressive)\n5. End with CTA (spark discussion)\n\nLength: 400-500 words\nTone: Confident but not arrogant\nGuardrails: Attack ideas, not people" }, { "title": "Template 2: HR Tech VP, Professional Post", "body": "Using Content Writing skill, Section B:\n\nI'm VP Marketing at HR Tech company.\n\nTopic: [Employee engagement, performance management, etc.]\nResearch: [SHRM, Josh Bersin, Culture Amp data?]\nGoal: [Build credibility, not leads]\n\nPlease:\n1. Open with research finding\n2. Provide context (why this matters)\n3. Offer practical framework\n4. Include CTA (professional, inviting discussion)\n\nLength: 500-600 words\nTone: Professional, empathetic, helpful\nConstraints: NEVER aggressive, NEVER attack competitors" }, { "title": "Template 3: Fintech Founder, Compliance Post", "body": "Using Content Writing skill, Section C:\n\nI'm a fintech founder. I need a compliant post.\n\nTopic: [Regulatory update, compliance topic]\nSource: [RBI announcement, official source]\nLegal review: Will review before publishing\n\nPlease:\n1. Summarize regulation factually\n2. Explain impact on fintech companies\n3. Provide compliance checklist\n4. Include disclaimer\n5. No competitor mentions\n6. No unverified claims\n\nLength: 400-500 words\nTone: Educational, helpful, conservative\nCRITICAL: Flag anything that might need legal review\n\n---\n\n## **Worked Examples: Multi-Dimensional Scenarios**\n\n### **Example 1: Sales Tech Founder, Series A, Aggressive Post**\n\nSCENARIO:\n\nCompany: AI sales coaching, $3M ARR, 30 employees\nYou: Co-founder & CEO\nGoal: Challenge Gong's methodology (contrarian take)\nPlatform: LinkedIn\nApproval: None (founder autonomy)\n\nCONTENT APPROACH:\n\nTOPIC: \"Gong's data on discovery calls is misleading. Here's why:\"\n\nSTEP 1: GATHER DATA (Your Product)\n\nExport: 50,000 sales calls from your product\nAnalyze: Average discovery call length\nFinding: Your data shows 25 minutes (vs Gong's 38 minutes)\nHypothesis: Different ICP (SMB vs enterprise)\n\nSTEP 2: WRITE HOOK (Aggressive but Credible)\n\"Gong says the average discovery call is 38 minutes.\nWe analyzed 50,000 calls and found 25 minutes.\n\nHere's what Gong missed:\"\n\nSTEP 3: BUILD CASE (Data-Driven)\nThe difference:\n\nGong's data: Skews enterprise (longer, more complex sales)\nOur data: Focuses SMB B2B SaaS (faster cycles)\nSMB discovery: 15-25 minutes (more efficient)\nEnterprise discovery: 35-45 minutes (more stakeholders)\n\nSTEP 4: NUANCE (Important)\n\"Am I saying Gong is wrong? No.\nAm I saying their data doesn't apply to SMB? Yes.\n\nIf you're selling to SMB, optimize for 20-minute discovery.\nIf you're enterprise, 35-40 minutes is right.\"\n\nSTEP 5: PUBLISH + AMPLIFY\n\nLinkedIn: Tuesday 9 AM EST\nFirst comment: Link to methodology\nTag: @mention Gong (they might engage)\nMonitor: Reply to all comments within 1 hour\n\nRESULT:\n\nEngagement: 2-3Ɨ normal (controversial = engagement)\nComments: Mix of agreement + Gong defenders (debate = algorithm boost)\nLeads: 15-20 inbound \"I agree with your SMB POV\"\nGong might respond (if they do, be respectful)\n\nRISK ASSESSMENT:\n\nRisk level: Medium (challenging industry leader)\nMitigation: Data-backed, nuanced, respectful\nWorst case: Gong ignores or politely disagrees\nBest case: Healthy debate, massive reach\n\n### **Example 2: HR Tech VP, Series B, Sensitive Topic (Layoffs)**\n\nSCENARIO:\n\nCompany: Employee engagement platform, $20M ARR\nYou: VP Marketing\nContext: Your company just laid off 15% of staff\nGoal: Address layoffs professionally\nConstraint: Can't post until official announcement\n\nTIMELINE:\n\nDAY 1 (Layoff Day):\nāŒ Don't post anything on LinkedIn yet\nāœ… Focus on: Supporting impacted employees internally\nāœ… Wait for: Official company communication\n\nDAY 2-3 (After Official Announcement):\nāœ… Now you can post (company has communicated)\n\nCONTENT APPROACH:\n\nSTEP 1: CHECK WITH LEADERSHIP\nBefore writing:\nā–” Does CEO/CHRO want me to post?\nā–” What's the approved messaging?\nā–” Any topics to avoid?\nā–” Legal review needed?\n\nSTEP 2: WRITE POST (Empathetic, Honest)\n\nHOOK:\n\"We made difficult decisions this week.\nAs someone who had to deliver hard news to people I deeply respect,\nI want to share what I learned about navigating reductions with empathy.\"\n\nBODY:\nWhat mattered most:\n\nClarity (people deserve straightforward answers, not corporate speak)\nDignity (generous severance, extended benefits, placement support)\nSupport (for those leaving AND those staying)\n\nFor those impacted:\n\nI'm happy to provide LinkedIn recommendations\nI'll make intros where I can\nYou deserved better timing, and I'm sorry\n\nFor the team staying:\n\nWe're committed to getting this right\nYour questions deserve honest answers\nWe'll rebuild trust through actions\n\nCTA:\n\"If you've navigated this as a leader, I'd appreciate your guidance.\nAnd if you're hiring for [roles], several incredible people are looking.\"\n\nSTEP 3: LEGAL REVIEW\nā–” Send to legal counsel\nā–” Check: Any liability concerns?\nā–” Confirm: Severance terms not disclosed (confidential)\nā–” Ensure: No promises made that company can't keep\n\nSTEP 4: PUBLISH + MONITOR\n\nTime: Not Friday evening (shows lack of care)\nBetter: Tuesday-Wednesday (thoughtful timing)\nMonitor: Comments (many will be supportive, some critical)\nRespond: Acknowledge, don't defend\n\nAPPROVAL CHAIN:\nDraft ā†’ Legal ā†’ VP Marketing ā†’ CHRO ā†’ CEO ā†’ Publish\nTimeline: 3-5 days\n\nRESULT:\n\nHumanizes difficult decision\nShows empathy + accountability\nHelps impacted employees (visibility for job search)\nMaintains professional reputation\n\n### **Example 3: Fintech Founder, Series A, Regulatory Update Post**\n\nSCENARIO:\n\nCompany: Payment aggregator, $4M ARR, 40 employees\nYou: Founder & CEO\nContext: RBI just released new PA guidelines\nGoal: Educate fintech community\nConstraint: Legal review mandatory\n\nCONTENT APPROACH:\n\nSTEP 1: READ OFFICIAL SOURCE\n\nRBI circular: Download PDF, read thoroughly\nIdentify: 5-7 key changes\nClarify: What's new vs what's unchanged\nConsult: Legal counsel for interpretation\n\nSTEP 2: DRAFT POST (Conservative, Educational)\n\nHOOK:\n\"RBI released updated Payment Aggregator guidelines yesterday.\nHere's what fintech companies need to know:\"\n\nBODY:\nKey changes (effective April 1, 2026):\n\nKYC Requirements Strengthened\n\nPrevious: Basic KYC for merchants\nNew: Enhanced due diligence for high-risk categories\nAction: Review your merchant onboarding process\n\nData Localization Timeline\n\nPrevious: \"As soon as possible\"\nNew: Mandatory by June 30, 2026\nAction: If you're not compliant, start now (6-month timeline)\n\nReporting Requirements\n\nPrevious: Quarterly\nNew: Monthly submission to RBI\nAction: Update your compliance calendar\n\nNet-Worth Requirements\n\nNo change: Still ā‚¹15 crore minimum\nClarification: Must be maintained at all times\n\nNOT CHANGED (Important):\n\nLicense renewal: Still 3 years\nMerchant agreement requirements: Unchanged\nSettlement timelines: Remain T+1\n\nDISCLAIMER:\n\"This is for informational purposes only and does not constitute legal advice.\nAlways consult qualified legal counsel for your specific situation.\"\n\nSTEP 3: LEGAL REVIEW (1-2 days)\nSend to legal counsel:\nā–” Check factual accuracy\nā–” Verify no overstatement\nā–” Confirm disclaimer is appropriate\nā–” Ensure no competitive mentions\n\nSTEP 4: PUBLISH + DISTRIBUTE\n\nLinkedIn: Tuesday 10 AM IST (India market)\nFirst comment: Link to official RBI circular\nDistribution: Share in IAMAI fintech group\nEmail: Send to customer list (value-add)\n\nRESULT:\n\nPositions you as: Helpful expert (not sales-y)\nBuilds trust: Fintech community appreciates clarity\nLeads: \"We need help with compliance\" inquiries\nRisk: Zero (factual, legal-reviewed, helpful)\n\nCONTRAST WITH WRONG APPROACH:\n\nāŒ DON'T WRITE:\n\"RBI's new rules will kill most payment companies.\nHere's why we're better positioned than our competitors.\"\n\nWHY IT'S WRONG:\n\nFear-mongering (unprofessional)\nCompetitor mention (unnecessary)\nCould trigger regulatory scrutiny\n\n---\n\n## **Tool Comparison Matrix**\n\n| Tool | Cost | Best For | Not Good For | Series A | Series B | Series C+ |\n|------|------|----------|--------------|----------|----------|-----------|\n| **LinkedIn Native** | Free | Everyone (start here) | Scheduling, analytics | āœ… | āœ… | āœ… |\n| **Buffer** | $6/mo/channel | Budget-conscious, multi-platform | Advanced analytics | āœ… | āœ… | āœ… |\n| **Taplio** | $39/mo | LinkedIn power users, carousel creation | Multi-platform | āš ļø | āœ… | āœ… |\n| **Shield** | $12/mo | Analytics junkies, engagement tracking | Content creation | āš ļø | āœ… | āœ… |\n| **Canva Pro** | $13/mo | Visual content (carousels, infographics) | Video editing | āœ… | āœ… | āœ… |\n| **Figma** | Free-$12/mo | Design teams, brand consistency | Solo founders (overkill) | āŒ | āœ… | āœ… |\n| **Grammarly Premium** | $12/mo | Error-free writing, tone checker | Creative writing | āš ļø | āœ… | āœ… |\n| **Hemingway** | Free | Simplifying complex writing | Sales copy (too simple) | āœ… | āœ… | āœ… |\n\n**RECOMMENDATIONS BY STAGE:**\n\n**Series A ($0-50/month):**\nāœ… LinkedIn Native (free)\nāœ… Canva Free (visual content)\nāœ… Hemingway (editing)\nāŒ Skip: Taplio, paid tools (use budget for product)\n\n**Series B ($50-200/month):**\nāœ… Taplio or Shield ($39-50/mo)\nāœ… Canva Pro ($13/mo)\nāœ… Grammarly ($12/mo)\nTotal: ~$64/mo\n\n**Series C+ ($200-500/month):**\nāœ… Taplio + Shield ($51/mo)\nāœ… Canva Pro + Figma ($25/mo)\nāœ… Buffer ($60/mo for team)\nāœ… Premium design tools\nTotal: $200-500/mo (small portion of $20K-50K content budget)\n\n---\n\n## **Quick Reference Cards**\n\n### **By Industry Tone:**\n\nSALES TECH:\nāœ… Aggressive, contrarian, data-driven\nāœ… Challenge incumbents (Gong, Outreach)\nāœ… ROI-focused, tactical frameworks\nāœ… LinkedIn posts: 300-500 words, 3-5Ɨ/week\nPublishing: Tuesday-Thursday 9 AM EST / 9 AM IST\n\nHR TECH:\nāœ… Professional, empathetic, research-backed\nāŒ NEVER aggressive or attack competitors\nāœ… SHRM/Josh Bersin citations\nāœ… LinkedIn posts: 400-600 words, 2-3Ɨ/week\nPublishing: Tuesday/Thursday 10 AM EST / 2 PM IST\n\nFINTECH:\nšŸ”“ Ultra-conservative, legal review mandatory\nāŒ NO competitor attacks, NO unverified claims\nāœ… Regulatory updates, compliance education\nāœ… LinkedIn posts: 400-500 words, 1-2Ɨ/week\nPublishing: Tuesday-Wednesday 10 AM EST / 10 AM IST\n\nOPERATIONS TECH:\nāœ… Industry-specific, B2B2B2C aware\nāœ… Retail/distribution insights\nāœ… CPG case studies\nāœ… LinkedIn posts: 300-500 words, 2-3Ɨ/week\nPublishing: Tuesday-Thursday 9 AM EST / 9 AM IST\n\n### **By Company Stage:**\n\nSERIES A:\n\nFounder voice (authentic, scrappy)\nPublishing: 3-5Ɨ/week\nApproval: None (founder)\nBudget: $0-50/month (free tools)\nGoal: Leads (10-20 SQLs/month)\nTime: 5-8 hours/week\n\nSERIES B:\n\nTeam content (professional, branded)\nPublishing: 5-7Ɨ/week\nApproval: Content Lead ā†’ VP Marketing\nBudget: $3K-10K/month (team + tools)\nGoal: Thought leadership + pipeline\nTime: 40-60 hours/week (team total)\n\nSERIES C+:\n\nCategory ownership (industry-defining)\nPublishing: 7-10Ɨ/week (multi-channel)\nApproval: Complex (legal, exec, PR)\nBudget: $20K-50K/month (media-level)\nGoal: Own the conversation\nTime: 100-150 hours/week (full team)\n\n### **Approval Workflow Quick Reference:**\n\nFOUNDER (No Approval):\nDraft ā†’ Publish (same day)\nTimeline: 1 hour total\n\nEMPLOYEE - STANDARD POST:\nDraft ā†’ Manager review ā†’ Publish\nTimeline: 1-2 days\n\nEMPLOYEE - STRATEGIC POST:\nDraft ā†’ Manager ā†’ VP Marketing ā†’ Publish\nTimeline: 2-3 days\n\nEMPLOYEE - SENSITIVE POST:\nDraft ā†’ Manager ā†’ VP ā†’ CEO ā†’ Legal (if needed) ā†’ Publish\nTimeline: 3-7 days\n\nFINTECH - ANY POST:\nDraft ā†’ Legal review (mandatory) ā†’ Publish\nTimeline: 1-3 days minimum\n\nPUBLIC COMPANY:\nDraft ā†’ Corp Comms ā†’ Legal ā†’ Exec ā†’ IR ā†’ Publish\nTimeline: 1-2 weeks\n\n---\n\n**END OF SKILL**" } ], "body": "šŸŽÆ Multi-Dimensional Navigator\n\nContent writing varies dramatically by industry, stage, and role. Find your path:\n\nSTEP 1: What's Your Industry Vertical?\n\nYour industry determines:\n\nTone and voice (aggressive vs conservative)\nRisk tolerance (what you can/cannot say)\nApproval workflows (direct publish vs legal review)\nContent topics and angles\nā†’ Sales Tech - Aggressive, contrarian, data-driven\nā†’ HR Tech - Professional, empathetic, research-backed\nā†’ Fintech - Ultra-conservative, compliance-first\nā†’ Operations Tech - Industry-specific, B2B2B2C nuanced\n\nSTEP 2: What's Your Company Stage?\n\nYour stage determines:\n\nPublishing frequency (founder bandwidth vs team)\nContent depth (tactical vs strategic)\nApproval requirements (founder autonomy vs committee)\nResources available (DIY vs professional design)\nā†’ Series A - Founder voice, scrappy, tactical\nā†’ Series B - Team effort, professional, strategic\nā†’ Series C+ - Corporate voice, brand-controlled, category-defining\n\nSTEP 3: Are You Founder or Employee?\n\nYour role determines:\n\nEditorial freedom (can you be contrarian?)\nApproval process (self-publish vs manager review)\nPersonal vs company brand\nWhat topics are \"safe\" vs \"risky\"\nā†’ Founder - Full autonomy, personal = company\nā†’ VP/Director - Manager approval, aligned with brand\nā†’ PMM/Content - Team collaboration, brand guidelines\nā†’ Employee - Significant constraints, corporate voice\n\nSTEP 4: What's Your Primary Market?\n\nYour geography determines:\n\nWriting style (US direct vs India relationship-focused)\nExamples and case studies (local companies)\nCompliance considerations (GDPR mentions, etc.)\nā†’ India - Relationship-driven, local examples, price-conscious\nā†’ US - Direct, data-driven, premium positioning\n\nQuick Navigation by Common Scenarios\n\n\"I'm a Sales Tech founder, want to build thought leadership\" ā†’ Go to: Section A1 (Sales Tech, Founder, Aggressive Voice Allowed)\n\n\"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)\n\n\"I'm at fintech, every post needs legal review\" ā†’ Go to: Section C (Fintech, Compliance-First Content)\n\n\"I'm PMM at ops tech, write about retail execution\" ā†’ Go to: Section D (Operations Tech, Industry-Specific Content)\n\nšŸ“Š SECTION A: SALES TECH CONTENT WRITING\n\nWhen To Use This Section:\n\nYour product: Sales engagement, conversation intelligence, sales enablement\nYour audience: Sales leaders, CROs, RevOps, SDR managers\nYour content angle: Tactical sales tips, data-driven insights, contrarian takes\nVoice: Aggressive, confident, ROI-focused, can challenge incumbents\nA1: Sales Tech @ Series A (Founder Voice, Aggressive Allowed)\nYour Reality Check:\nCOMPANY PROFILE:\n- Size: $1M-10M ARR, 10-100 employees\n- Stage: Series A\n- You: Founder or early marketing hire\n- Content goal: Build thought leadership + leads\n- Publishing: 3-5Ɨ per week (LinkedIn primary)\n- Approval: None (founder autonomy)\n- Time: 5-8 hours/week total\n\nThe Sales Tech Content Philosophy:\n\nWhy Sales Leaders Engage with Content:\n\nSALES LEADERS DON'T ENGAGE WITH:\nāŒ Generic motivational quotes\nāŒ Theory without data\nāŒ Long-winded essays (no time)\nāŒ Humble bragging (\"We just closed...\")\n\nSALES LEADERS ENGAGE WITH:\nāœ… Data-driven insights (\"Analyzed 10K calls, here's what top reps do\")\nāœ… Tactical frameworks (copy-paste into your process)\nāœ… Contrarian takes (\"Everyone is wrong about cold calling\")\nāœ… Competitive intelligence (\"What Gong doesn't tell you\")\nāœ… ROI calculations (\"This tactic = 23% more meetings\")\n\nSales Tech Voice Guidelines:\n\nAGGRESSIVENESS SPECTRUM (Sales Tech):\n\nTOO TIMID (Don't Do This):\n\"We think conversation intelligence might be helpful for some teams...\"\n\nAPPROPRIATELY CONFIDENT (Do This):\n\"Gong analyzed 1M calls. We analyzed 2M. Here's what they missed.\"\n\nTOO AGGRESSIVE (Even for Sales Tech):\n\"Gong is garbage. Their data is fake. We're 100Ɨ better.\"\n\nSWEET SPOT:\n- Confident, data-backed assertions\n- Respectful but contrarian takes\n- Challenge category leaders on methodology\n- But: Never personal attacks, never unverified claims\n\nContent Types for Sales Tech Founders:\n\nCONTENT MIX (Sales Tech Series A):\n\n40% DATA-DRIVEN INSIGHTS\n- \"We analyzed X sales calls, here's what we found\"\n- \"The data says [surprising insight]\"\n- Source: Your product data, public research (Gong, Pavilion)\n- Length: 300-500 words\n- Frequency: 2Ɨ per week\n\n30% TACTICAL FRAMEWORKS\n- \"The 3-question discovery framework\"\n- \"How to handle pricing objections [step-by-step]\"\n- Source: Your experience, customer wins\n- Length: 400-600 words\n- Frequency: 1-2Ɨ per week\n\n20% CONTRARIAN TAKES\n- \"Why everyone is wrong about [X]\"\n- \"Gong says [X], but the data shows [Y]\"\n- Source: Your unique perspective, counter-research\n- Length: 200-400 words\n- Frequency: 1Ɨ per week\n\n10% PERSONAL/BEHIND-THE-SCENES\n- \"How we lost a $50K deal (and what I learned)\"\n- \"The sales hire that changed our trajectory\"\n- Source: Your journey\n- Length: 300-500 words\n- Frequency: 1Ɨ every 2 weeks\n\nSeries A Sales Tech: Daily Content Workflow\n\nMONDAY: Data-Driven Insight (1.5 hours)\n\n09:00-09:30 | Find Data\n\nSALES TECH DATA SOURCES:\nā–” Your product: Export anonymized metrics\n Example: \"Average discovery call = 32 minutes in our data\"\n \nā–” Public research:\n - Gong Labs reports (free)\n - Pavilion benchmarks (if member)\n - Public earnings calls (check Salesforce, ZoomInfo)\n \nā–” Customer interviews:\n - \"What was your close rate before/after using us?\"\n - Turn into: \"Customer X increased close rate 23%\"\n\n09:30-10:30 | Write Post\n\nSTRUCTURE:\n\n**HOOK (First 2 lines):**\n\"We analyzed 50,000 sales calls from SMB B2B SaaS companies.\nThe average discovery call is 32 minutes. But top performers? 19 minutes.\"\n\n**BUILD (3-5 paragraphs):**\nWhy this matters:\n- Shorter calls = more qualified prospects\n- Top reps ask fewer questions (but better ones)\n- They don't \"interrogate,\" they diagnose\n\nWhat we found:\n1. Average rep asks 18 questions in discovery\n2. Top rep asks 9 questions (but they're open-ended)\n3. Top rep listens 67% of the time (vs 42% for average)\n\n**PAYOFF (1-2 paragraphs):**\nThe 3 questions top reps always ask:\n1. \"Walk me through your current process for [X]\"\n2. \"What happens if you don't solve this in the next 90 days?\"\n3. \"Who else is impacted by this problem?\"\n\n**CTA:**\n\"What's your go-to discovery question?\"\n\n10:30-11:00 | Edit & Publish\n\nSALES TECH EDITING CHECKLIST:\nā–” Cut 20-30% of words (brevity = respect for time)\nā–” Verify: Every claim has data/source\nā–” Add: Numbers, percentages, specifics\nā–” Remove: Fluff, qualifiers (\"I think,\" \"maybe\")\nā–” Check: Does this make sales leaders smarter?\n\nPUBLISH:\n- Time: 9 AM EST / 6 AM PST (catch US East + West)\n- If India: 9 AM IST (catch Indian B2B audience)\n- Platform: LinkedIn primary, Twitter thread secondary\n\n\nTUESDAY: Tactical Framework (1.5 hours)\n\nSTRUCTURE:\n\n**HOOK:**\n\"The pricing objection framework every SDR should memorize:\n(Learned this from watching 1,000+ pricing conversations)\"\n\n**FRAMEWORK:**\nWhen they say: \"That's too expensive\"\n\nDON'T say:\nāŒ \"We're actually quite affordable\"\nāŒ \"Let me talk to my manager about a discount\"\nāŒ \"What's your budget?\"\n\nDO say (3-step framework):\n\nStep 1: REFRAME\n\"Expensive compared to what? [competitor]?\"\nā†’ Forces them to make comparison explicit\n\nStep 2: QUANTIFY THEIR PROBLEM\n\"Walk me through what this problem costs you today.\n How many hours per week? What's your team's loaded cost?\"\nā†’ Now you have their ROI baseline\n\nStep 3: CONTRAST VALUE\n\"So you're spending $50K/year in time right now.\n Our solution is $15K/year and eliminates 90% of that.\n That's a $35K gain. Does that math work?\"\nā†’ Reframe from cost to investment\n\n**EXAMPLE:**\n[Insert short dialogue showing this in action]\n\n**CTA:**\n\"Try this next time you hear 'too expensive.'\n Let me know how it goes.\"\n\nLENGTH: 400-600 words\nTIME: 1.5 hours (research + write + edit)\n\n\nWEDNESDAY: Contrarian Take (1 hour)\n\nSTRUCTURE:\n\n**HOOK (Provocative):**\n\"Unpopular opinion: Gong is making your sales team WORSE.\n(And I have data to prove it)\"\n\n**SETUP:**\nEveryone thinks conversation intelligence = better sales.\nMore data = better coaching = more wins.\n\nBut here's what we're seeing:\n\n**THE CONTRARIAN INSIGHT:**\nWhen sales teams get Gong:\n- Month 1-3: 15% improvement (reps more aware)\n- Month 4-6: Flatline (back to baseline)\n- Month 7+: Often 5-10% decline\n\nWhy?\n1. Analysis paralysis (too much data, not enough action)\n2. Reps game the metrics (talk more to hit \"talk time\" goals)\n3. Managers overwhelmed (100 dashboards, 0 time to coach)\n\n**THE ALTERNATIVE VIEW:**\nConversation intelligence isn't the problem.\nHow you USE it is.\n\nBest teams:\n- Track 3 metrics max (not 30)\n- Focus on ONE skill per quarter\n- Coach live (not post-call reviews)\n\n**NUANCE (Important for Aggressive Takes):**\n\"Am I saying Gong is bad? No.\nAm I saying most teams use it wrong? Yes.\"\n\n**CTA:**\n\"Using conversation intelligence? What's working for you?\"\n\nRISK LEVEL: Medium-High\nAPPROVAL: Founder only (don't do this as employee)\nWHEN: Only if you have data + alternative\n\n\nTHURSDAY: Quick Tip (30 minutes)\n\nSTRUCTURE:\n\n**HOOK:**\n\"The 2-minute LinkedIn outreach hack that 3Ɨ my reply rate:\"\n\n**THE HACK:**\nBefore sending connection request:\n1. Comment on their post (genuine, add value)\n2. Wait 24 hours\n3. THEN send personalized connection request\n\nWhy it works:\n- They remember you (positive association)\n- Not cold anymore (warm intro via comment)\n- Shows you did research (not spray-and-pray)\n\n**EXAMPLE:**\n[Screenshot or dialogue]\n\n**CTA:**\n\"Try it. Let me know your reply rate.\"\n\nLENGTH: 150-250 words\nTIME: 30 minutes\nFREQUENCY: 1Ɨ per week (easy win days)\n\n\nFRIDAY: Customer Win / Case Study (1 hour)\n\nSTRUCTURE:\n\n**HOOK:**\n\"How a 10-person startup beat Salesforce for a $100K deal:\n(A masterclass in positioning)\"\n\n**SETUP:**\nOur customer: Small sales tech startup\nCompetitor: Salesforce (800 lb gorilla)\nDeal size: $100K annual\n\nHow they won:\n\n**THE STORY:**\nStep 1: They DIDN'T compete on features\nā†’ Salesforce has 10Ɨ more features\nā†’ That's a losing battle\n\nStep 2: They reframed the decision\nā†’ \"You have 15 sales reps. Salesforce is built for 500+ rep teams.\n You'll pay for complexity you don't need.\"\n\nStep 3: They offered implementation in 1 week\nā†’ Salesforce: 3-month implementation\nā†’ Them: Live in 1 week\n\nStep 4: They made it founder-to-founder\nā†’ CEO jumped on call (rare for Salesforce)\nā†’ Committed to being \"partner, not vendor\"\n\n**THE WIN:**\nCustomer chose them despite:\n- Salesforce brand\n- Salesforce features\n- Salesforce pricing power\n\nWhy?\n- Speed to value\n- Right-sized solution\n- Personal relationship\n\n**LESSON:**\n\"Don't compete on the incumbent's terms.\n Reframe the decision criteria.\"\n\n**CTA:**\n\"Ever competed against a giant? How'd you position?\"\n\nLENGTH: 500-700 words\nTIME: 1 hour\nFREQUENCY: 1Ɨ per week\n\nLinkedIn Algorithm Optimization (Sales Tech):\nPOST TIMING:\nāœ… Tuesday-Thursday, 9-11 AM EST (highest engagement)\nāœ… Avoid Monday AM (too busy), Friday PM (weekend mode)\n\nFor India market:\nāœ… Tuesday-Thursday, 9 AM-2 PM IST\n\nPOST LENGTH:\nāœ… 300-600 words (sweet spot for LinkedIn)\nāŒ <100 words (not enough depth)\nāŒ >800 words (tl;dr, save for newsletter)\n\nENGAGEMENT TACTICS:\nā–” First comment: Add value (not \"What do you think?\")\nā–” Reply to all comments within first hour (algorithm boost)\nā–” Ask specific question in CTA (not generic \"Thoughts?\")\nā–” Tag max 2 people (more = spam signal)\nā–” Use 3-5 hashtags max (Sales, SalesLeadership, B2BSales, etc.)\n\nCAROUSEL STRATEGY (Sales Tech Specific):\nWhen: Complex frameworks, multi-step processes, data visualization\nFormat: 7-10 slides\nStructure:\n- Slide 1: Hook (bold claim + data point)\n- Slides 2-8: Framework/data (one point per slide)\n- Slide 9: Summary (recap key points)\n- Slide 10: CTA (apply this, share results)\n\nTools:\n- Free: Canva (templates available)\n- Paid: Taplio ($29/mo), Shield ($12/mo)\n\nA2: Sales Tech @ Series B (Team Content, Professional Voice)\nYour Reality Check:\nCOMPANY PROFILE:\n- Size: $10M-40M ARR, 150-500 employees\n- Stage: Series B\n- You: VP Marketing or Content Lead\n- Team: 1-2 content writers + designer\n- Content goal: Thought leadership + brand building\n- Publishing: 5-7Ɨ per week (company account)\n- Approval: Manager/CEO review for company posts\n- Budget: $3K-10K/month for content\n\nWhy Series B Content is Different:\nSERIES A CONTENT:\n- Founder voice (personal, authentic)\n- Scrappy (founder writes everything)\n- Tactical (helping peers)\n- Goal: Build personal + company brand\n\nSERIES B CONTENT:\n- Brand voice (professional, consistent)\n- Team effort (writers, designers, approval)\n- Strategic (thought leadership)\n- Goal: Category positioning\n\nNEW CHALLENGES:\n- Maintain authenticity while scaling\n- Multiple stakeholders (CEO, Sales, Product)\n- Balancing founder voice vs company voice\n- Higher quality bar (professional design expected)\n\nSeries B Sales Tech: Content Team Structure\nTEAM ROLES:\n\nCONTENT LEAD (You):\n- Strategy (what topics, what angles)\n- Approval (final say on all posts)\n- Stakeholder management (CEO, Sales, Product)\n- Metrics (track engagement, leads, brand impact)\nTime: 15-20 hours/week\n\nCONTENT WRITER (1-2 FTE):\n- Research (find data, customer stories)\n- Drafting (write posts, threads, articles)\n- Editing (polish, optimize)\n- SEO (keywords, hashtags)\nTime: 30-40 hours/week\n\nDESIGNER (Part-time or contractor):\n- Carousels (LinkedIn carousels for complex topics)\n- Infographics (data visualization)\n- Branded templates (consistent look)\nTime: 10-15 hours/week\n\nFOUNDER/CEO (Guest):\n- 1-2 posts per week under their name\n- High-level strategic takes\n- Company announcements\nTime: 2-3 hours/week (ghost-written, they edit)\n\nTOOLS & BUDGET ($3K-10K/month):\nā–” Design: Canva Pro ($13/mo) or Figma ($12/user/mo)\nā–” Scheduling: Taplio ($39/mo) or Shield ($12/mo)\nā–” Analytics: Shield Analytics ($12/mo)\nā–” Carousel creation: Canva or custom designer ($500-2K/mo)\nā–” Stock photos: Unsplash (free) or Shutterstock ($29-199/mo)\nā–” Writing tools: Grammarly Premium ($12/mo), Hemingway (free)\n\nSeries B Approval Workflow:\nSTANDARD POST (Product update, tactical tip):\nWriter ā†’ Content Lead ā†’ Publish\nTimeline: Same day\n\nSTRATEGIC POST (Contrarian take, competitor analysis):\nWriter ā†’ Content Lead ā†’ VP Marketing ā†’ Publish\nTimeline: 1-2 days\n\nSENSITIVE POST (Pricing, roadmap, executive POV):\nWriter ā†’ Content Lead ā†’ VP Marketing ā†’ CEO ā†’ Legal (if needed) ā†’ Publish\nTimeline: 3-5 days\n\nFOUNDER GHOST-WRITE:\nWriter draft ā†’ Content Lead edit ā†’ Founder review/edit ā†’ Publish (under founder name)\nTimeline: 2-3 days\nCRITICAL: Founder has final say (it's their voice)\n\nAPPROVAL DECISION TREE:\n\nQuestion: Is this factual/tactical?\nYES ā†’ Standard approval (Content Lead)\nNO ā†’ Continue...\n\nQuestion: Does this challenge competitors/industry?\nYES ā†’ Strategic approval (VP Marketing)\nNO ā†’ Continue...\n\nQuestion: Does this touch pricing/strategy/roadmap?\nYES ā†’ Sensitive approval (CEO)\nNO ā†’ Standard approval\n\nQuestion: Could this create legal risk?\nYES ā†’ Legal review (add 3-5 days)\nNO ā†’ Proceed with appropriate approval tier\n\nSeries B Weekly Content Calendar:\nMONDAY:\nā–” 09:00 | Company post: Data-driven insight\n Topic: \"We analyzed 100K sales calls in Q4. Here's what changed.\"\n Writer: Staff writer\n Format: LinkedIn post (400-500 words)\n Visual: Data viz (bar chart or line graph)\n Approval: Content Lead\n \nā–” 12:00 | Founder post: Weekend reflection\n Topic: \"5 sales trends I'm watching in 2026\"\n Writer: Ghost-written (founder edits heavily)\n Format: LinkedIn post (300-400 words)\n Approval: Founder (final say)\n\nTUESDAY:\nā–” 09:00 | Company post: Tactical framework (carousel)\n Topic: \"The objection handling framework we teach customers\"\n Format: LinkedIn carousel (8-10 slides)\n Designer: Create branded template\n Writer: Framework content\n Approval: Content Lead ā†’ VP Marketing (if new framework)\n \nā–” 14:00 | Customer story (LinkedIn article)\n Topic: \"How [Customer] scaled from $5M to $20M ARR\"\n Format: Long-form article (800-1200 words)\n Writer: Interview customer, write case study\n Approval: Customer approval + Content Lead\n\nWEDNESDAY:\nā–” 09:00 | Company post: Industry commentary\n Topic: \"Gong's Series D: What it means for SMB sales tech\"\n Writer: Research news, add perspective\n Format: Analysis (400-500 words)\n Approval: Content Lead ā†’ VP Marketing (competitive topic)\n \nā–” 16:00 | Founder post: Personal insight\n Topic: \"The sales hire that changed our trajectory\"\n Writer: Ghost-written from founder interview\n Format: Story (400-500 words)\n Approval: Founder\n\nTHURSDAY:\nā–” 09:00 | Company post: Quick win\n Topic: \"3 LinkedIn prospecting tips from our SDR team\"\n Format: Short tips (250-350 words)\n Writer: Interview SDR manager\n Approval: Content Lead\n \nā–” 12:00 | Product Marketing: Feature announcement (if launching)\n Writer: PMM writes, Content Lead edits\n Format: Feature post + carousel\n Approval: PMM ā†’ Content Lead ā†’ VP Marketing\n\nFRIDAY:\nā–” 09:00 | Founder post: Weekly learnings\n Topic: \"3 things I learned this week about sales coaching\"\n Writer: Founder writes this one (authentic)\n Format: Quick reflection (200-300 words)\n Approval: None (founder direct)\n \nā–” 14:00 | Community engagement post\n Topic: \"Friday question: What's your biggest sales challenge right now?\"\n Format: Simple question + comment engagement\n Goal: Build community, spark discussion\n Approval: Content Lead\n\nWEEKEND (Schedule for Monday):\nā–” SAT | Batch write next week's drafts\nā–” SUN | Review analytics from previous week\n\nSeries B: Data-Driven Content Strategy\nQUARTERLY CONTENT INITIATIVES:\n\nQ1: ORIGINAL RESEARCH REPORT\n\"The State of SMB Sales 2026\"\n\nProduction:\nWeek 1-2: Survey design\n- 500+ sales leaders\n- 20 questions (multiple choice + open-ended)\n- Incentive: $50 Amazon gift card (100 recipients)\n- Platform: Typeform ($35/mo)\n\nWeek 3-4: Data collection\n- Email outreach (to customer list)\n- LinkedIn post (survey link)\n- Partner distribution (Pavilion, Sales Hacker)\n- Goal: 500+ responses\n\nWeek 5-6: Analysis\n- Data analyst: Clean data, find insights\n- Writer: Identify 5-7 key findings\n- Designer: Create data visualizations\n\nWeek 7-8: Content production\n- Full report (30-40 pages PDF)\n- Summary blog post (1,000 words)\n- LinkedIn carousel series (3-4 carousels)\n- Webinar presentation\n\nWeek 9-12: Distribution & amplification\n- Publish report (gated, capture emails)\n- 4-week LinkedIn series (one finding per week)\n- Guest posts on Sales Hacker, Pavilion\n- PR outreach (TechCrunch, SaaStr)\n- Webinar (present findings, Q&A)\n\nBudget:\n- Survey incentives: $5,000\n- Design (report): $2,000-5,000\n- Promotion: $3,000-5,000\n- Total: $10,000-15,000\n\nImpact:\n- 1,000-2,000 report downloads\n- 100-200 SQLs\n- Media coverage (TechCrunch, SaaStr mention)\n- Sales enablement (differentiation vs competitors)\n- Thought leadership (cited by industry)\n\nQ2-Q4: Additional initiatives\n- Q2: Customer benchmarking report\n- Q3: Competitive landscape analysis\n- Q4: 2027 predictions + trends\n\nA3: Sales Tech @ Series C+ (Category Ownership)\nYour Reality Check:\nCOMPANY PROFILE:\n- Size: $50M+ ARR, 500+ employees\n- Stage: Series C/D or preparing IPO\n- You: Director of Content / Head of Thought Leadership\n- Team: 3-5 FTE (writers, designers, analysts, video)\n- Content: Category-defining thought leadership\n- Budget: $20K-50K/month\n- Goal: Own the conversation (like Gong Labs, Pavilion, SaaStr)\n\nSeries C+ Content = Category Ownership\nSERIES A/B GOALS:\n- Generate leads\n- Build brand awareness\n- Establish thought leadership\n\nSERIES C+ GOAL:\n- OWN the conversation in your category\n- Be THE source that media/analysts/customers cite\n- Influence industry direction\n- Recruiting magnet (top talent reads your content)\n\nEXAMPLES OF CATEGORY OWNERSHIP:\n- Gong Labs (conversation intelligence insights)\n- Pavilion (GTM community + content)\n- SaaStr (B2B SaaS conferences + content)\n- First Round Review (startup advice)\n- a16z blog (startup/tech trends)\n\nYOUR CONTENT BECOMES:\n- Industry-defining (sets agenda)\n- Media-cited (journalists reference you)\n- Board-level reading (not just practitioners)\n- Recruiting tool (\"I read your blog\" in interviews)\n\nSeries C+ Content Team:\nORGANIZATIONAL STRUCTURE:\n\nDIRECTOR OF CONTENT (You):\n- Strategy: What makes us category leaders?\n- Partnerships: Media, analysts, industry orgs\n- Executive alignment: CEO/CMO/Board\n- Budget management: $20K-50K/month\n- Metrics: Brand awareness, category leadership signals\n\nMANAGING EDITOR:\n- Editorial calendar: Plan 3 months ahead\n- Quality control: Everything excellent or doesn't ship\n- Writer management: Assign, edit, coach\n- Process: Systems that scale\n\nSENIOR CONTENT WRITER (2-3):\n- Original research: Lead quarterly reports\n- Thought leadership: Strategic analysis\n- Specialization: Each owns topic area\n * Writer 1: Sales methodology, frameworks\n * Writer 2: Data/research, benchmarks\n * Writer 3: Industry trends, competitive analysis\n\nDATA ANALYST:\n- Research design: Survey questions, methodology\n- Data analysis: Find insights in product data\n- Visualization: Charts, graphs, dashboards\n- Reporting: Present findings to exec team\n\nSENIOR DESIGNER:\n- Brand-level quality: Every asset premium\n- Data visualization: Make complex data clear\n- Templates: Scalable, consistent design system\n- Video production: Motion graphics for social\n\nVIDEO PRODUCER (Optional but recommended):\n- Short-form: 60-90 second LinkedIn videos\n- Webinars: Professional production quality\n- Podcast: If you have one\n- YouTube: Thought leadership channel\n\nCONTENT OPERATIONS / COORDINATOR:\n- Scheduling: Manage content calendar\n- Distribution: LinkedIn, Twitter, email, etc.\n- Analytics: Track performance across channels\n- Coordination: Keep everyone aligned\n\nTOOLS & BUDGET ($20K-50K/month):\n\nTIER 1: Publishing Infrastructure ($1K-3K/month)\nā–” CMS: WordPress, Webflow ($50-200/mo)\nā–” Email: HubSpot, Marketo ($1K-2K/mo for enterprise)\nā–” Scheduling: Hootsuite, Sprout Social ($200-500/mo)\nā–” Analytics: Google Analytics + custom dashboards\n\nTIER 2: Research & Data ($3K-10K/month)\nā–” Survey platform: Qualtrics ($200-500/mo)\nā–” Research incentives: $2K-5K per study\nā–” Data visualization: Tableau ($70/user/mo)\nā–” Industry subscriptions: Gartner, Forrester ($3K-5K/mo)\n\nTIER 3: Content Production ($5K-15K/month)\nā–” Team salaries: $15K-30K/month (3-5 FTE fully loaded)\nā–” Freelancers: Subject matter experts ($500-2K per piece)\nā–” Design tools: Adobe Creative Cloud ($55/mo/user)\nā–” Stock assets: Photos, videos ($200-500/mo)\n\nTIER 4: Distribution & Amplification ($5K-15K/month)\nā–” Paid social: LinkedIn ads ($3K-8K/mo)\nā–” Sponsorships: Industry newsletters ($2K-5K/placement)\nā–” PR agency: If needed ($5K-15K/mo retainer)\nā–” Events: Speaking slots, sponsored content\n\nTIER 5: Video & Multimedia ($5K-10K/month if doing video)\nā–” Video production: Equipment, editing software\nā–” Video editor: Part-time or contractor\nā–” Podcast production: If applicable\nā–” YouTube optimization: Thumbnails, SEO\n\nSeries C+ Content Strategy: Flagship Initiatives\nANNUAL CONTENT FLAGSHIP: \"THE STATE OF B2B SALES [2026]\"\n\nThis is your category-defining research report.\n\nSCOPE:\n- Survey: 2,000-5,000 sales leaders\n- Product data: Analyze 10M+ sales conversations\n- Academic partnership: Validate with university researchers\n- Executive interviews: 50 CROs/VPs Sales\n- Timeline: 4-6 months production\n- Budget: $40K-80K\n\nMETHODOLOGY:\nMonth 1-2: Research design\n- Survey questions (partner with Qualtrics)\n- IRB approval (if partnering with university)\n- Sample selection (ensure representative)\n- Pre-test survey (100 respondents, iterate)\n\nMonth 3-4: Data collection\n- Survey distribution:\n * Email to 50K sales leaders (bought list)\n * LinkedIn campaign ($10K ad spend)\n * Partner promotion (Pavilion, Sales Hacker, SaaStr)\n * Customer outreach (guaranteed responses)\n- Goal: 2,000-5,000 complete responses\n- Incentive: $100 Amazon gift card (200 winners)\n\nMonth 5: Analysis\n- Data cleaning: Remove incomplete/invalid\n- Statistical analysis: Regression, correlation, segmentation\n- Product data integration: Combine survey + product insights\n- Visualization: 30-50 charts/graphs\n- Insights identification: What's surprising? What matters?\n\nMonth 6: Production\n- Report writing: 60-80 pages\n- Executive summary: 4-page overview\n- Design: Premium quality (looks like Gartner/Forrester)\n- Infographics: Shareable data visualizations\n- Landing page: Report download (gated)\n\nPOST-LAUNCH AMPLIFICATION (3 months):\n\nWeek 1: Launch\n- Press release: Wire services\n- Media outreach: TechCrunch, WSJ, Forbes\n- LinkedIn campaign: Promote to 100K sales leaders\n- Customer email: Send to all customers\n- Webinar: Present findings (500+ registrants)\n\nWeek 2-4: Content series\n- LinkedIn: 12 posts (one finding per post)\n- Blog: 4 deep-dive articles\n- Podcast: 3 episodes discussing findings\n- Guest posts: Publish on Pavilion, Sales Hacker, etc.\n\nMonth 2-3: Speaking circuit\n- Conferences: Present at SaaStr, Pavilion Summit, Sales 3.0\n- Webinars: Partner with complementary tools\n- Podcasts: Guest on top 10 sales podcasts\n- Customer events: Present at your user conference\n\nIMPACT METRICS:\n\nREACH:\n- 10,000+ report downloads\n- 500,000+ social impressions\n- 50+ media mentions\n- 20+ conference/podcast presentations\n\nBUSINESS:\n- 300-500 SQLs directly attributed\n- $2M-5M pipeline influenced\n- Sales enablement (differentiation in 100+ deals)\n- Recruiting (mentioned in 50+ candidate interviews)\n\nCATEGORY LEADERSHIP:\n- Cited by Gartner/Forrester in their reports\n- Referenced in competitor earnings calls\n- Academic papers cite your research\n- Industry orgs invite you to present\n- Media calls YOU for expert commentary\n\nROI:\n- Cost: $60K-100K (full production + promotion)\n- Pipeline influenced: $2M-5M\n- ROI: 20-50Ɨ (if even 1-2% of pipeline closes)\n\nSeries C+ Content Distribution: Media Company Level\nOWNED CHANNELS:\n\nBLOG:\n- Frequency: 2-3Ɨ per week\n- Topics: Thought leadership, research, frameworks\n- SEO: Optimized for category keywords\n- Goal: 50K-100K monthly visitors\n\nLINKEDIN (Company):\n- Frequency: 5-7Ɨ per week\n- Mix: Data insights, frameworks, company updates\n- Followers: 50K-150K+\n- Engagement: 2-5% (very high for company page)\n\nLINKEDIN (Founder/Execs):\n- CEO: 2-3Ɨ per week (high-level strategy)\n- CMO: 1-2Ɨ per week (marketing insights)\n- CRO: 1-2Ɨ per week (sales insights)\n- Followers: 10K-50K each\n- Engagement: 5-10% (personal accounts higher)\n\nYOUTUBE:\n- Frequency: 1-2Ɨ per week\n- Content: Research summaries, webinar recordings, interviews\n- Subscribers: 5K-20K\n- Goal: Thought leadership, not viral videos\n\nPODCAST:\n- Frequency: Weekly\n- Format: Interview sales leaders (30-45 min)\n- Distribution: Apple, Spotify, YouTube\n- Downloads: 1K-5K per episode\n\nEMAIL NEWSLETTER:\n- Frequency: Weekly\n- Subscribers: 20K-60K\n- Open rate: 25-35%\n- Content: Curated insights + original commentary\n\nEARNED CHANNELS:\n\nMEDIA COVERAGE:\n- TechCrunch, Forbes, WSJ (2-4Ɨ per year)\n- Industry pubs: Sales Hacker, SaaStr, Pavilion (monthly)\n- Podcasts: Top 20 sales podcasts (quarterly)\n- Position: Expert source (journalists quote you)\n\nSPEAKING:\n- Tier 1 conferences: SaaStr, Pavilion Summit, Sales 3.0 (keynote)\n- Tier 2 conferences: Regional sales events (breakout sessions)\n- Customer events: Your user conference (opening keynote)\n- Virtual: 10-20 webinars per year\n\nANALYST RELATIONS:\n- Gartner: Briefings 2Ɨ per year\n- Forrester: Wave participation\n- Pavilion: Community partnership\n- Josh Bersin: If HR Tech adjacency\n\nACADEMIC:\n- University partnerships: Research collaborations\n- Journal publications: Peer-reviewed if possible\n- Guest lectures: MBA programs (sales/marketing)\n- Thesis advising: If relevant\n\nPAID CHANNELS:\n\nSPONSORED CONTENT:\n- Industry newsletters: Pavilion, Sales Hacker ($5K-15K per placement)\n- LinkedIn ads: Promote flagship research ($10K-20K per campaign)\n- Conference sponsorships: SaaStr, Pavilion ($20K-50K per event)\n\nPARTNER CHANNELS:\n- Integration partners: Salesforce, HubSpot, Outreach (co-marketing)\n- Community partners: Pavilion, Revenue Collective (content swaps)\n- Analyst firms: Gartner, Forrester (sponsor research)\n- Academic: Universities (research partnerships)\n\nšŸ“Š SECTION B: HR TECH CONTENT WRITING\n\nWhen To Use This Section:\n\nYour product: HRIS, employee engagement, performance, recruiting\nYour audience: HR leaders, CHROs, People Ops, Talent teams\nYour content angle: Employee experience, people analytics, culture\nVoice: Professional, empathetic, research-backed (NEVER aggressive)\nB1: HR Tech @ Series A (Founder, Professional Voice Required)\nYour Reality Check:\nCOMPANY PROFILE:\n- Size: $2M-8M ARR, 20-80 employees\n- Stage: Series A\n- You: Founder (often ex-CHRO background)\n- Content goal: Build trust, establish expertise\n- Publishing: 2-3Ɨ per week (quality > quantity)\n- Voice: Professional, empathetic, never aggressive\n\nWhy HR Tech Content is FUNDAMENTALLY DIFFERENT:\nSALES TECH CONTENT:\nāœ… Aggressive, contrarian takes\nāœ… \"Gong is wrong about X\"\nāœ… Challenge incumbents publicly\nāœ… Data-driven, ROI-focused\nRisk: Low (worst case = lose followers)\n\nHR TECH CONTENT:\nāŒ NEVER aggressive or confrontational\nāŒ NEVER \"Competitor X is wrong\"\nāŒ NEVER attack category leaders\nāœ… Professional, empathetic, supportive\nāœ… Research-backed, people-focused\nRisk: HIGH (HR community is small, reputation matters)\n\nWHY THE DIFFERENCE:\n- HR community is tight-knit (everyone knows everyone)\n- HR leaders value relationships over aggressive positioning\n- HR topics are sensitive (people, culture, layoffs)\n- Attacking competitors = unprofessional (damages your brand)\n- CHRO job changes = everyone moves to different companies\n ā†’ Today's competitor could be tomorrow's customer/partner\n\nHR Tech Voice Guidelines:\n\nTONE SPECTRUM (HR Tech):\n\nTOO AGGRESSIVE (Never Do This):\n\"Traditional performance reviews are BROKEN. Anyone still using them is hurting their team.\"\nā†’ Judgmental, attacks current practices\n\nTOO SOFT (Also Wrong):\n\"We think maybe employee engagement could possibly be important...\"\nā†’ Lacks confidence, not thought leadership\n\nAPPROPRIATE (Do This):\n\"Research shows traditional annual reviews have limitations. Here's what forward-thinking CHROs are trying instead.\"\nā†’ Research-backed, helpful, not judgmental\n\nIDEAL HR TECH VOICE:\n- Confident but not arrogant\n- Research-backed (cite studies, surveys)\n- Empathetic (understand HR challenges)\n- Helpful (provide frameworks, not just criticism)\n- Inclusive (not everyone can afford premium tools)\n- Professional (appropriate for CHRO audience)\n\nContent Types for HR Tech Founders:\n\nCONTENT MIX (HR Tech Series A):\n\n50% RESEARCH-BACKED INSIGHTS\n- \"Culture Amp's 2026 benchmark shows X\"\n- \"New study on hybrid work effectiveness\"\n- \"People analytics: What the data actually says\"\nSource: Industry research, academic studies, your product benchmarks\nLength: 400-600 words\nFrequency: 1-2Ɨ per week\n\n30% PRACTICAL FRAMEWORKS\n- \"The 1-on-1 framework top managers use\"\n- \"How to measure culture (beyond surveys)\"\n- \"Performance review template for 100-person companies\"\nSource: Best practices, customer insights\nLength: 500-700 words\nFrequency: 1Ɨ per week\n\n15% EMPATHETIC OBSERVATIONS\n- \"The CHRO challenge no one talks about\"\n- \"Navigating layoffs with empathy [guide]\"\n- \"What I learned from 100 employee exit interviews\"\nSource: Your experience, HR community insights\nLength: 400-600 words\nFrequency: 1Ɨ every 2 weeks\n\n5% PERSONAL/VULNERABLE\n- \"The employee engagement program I launched (that failed)\"\n- \"What I got wrong about performance management\"\nSource: Your honest journey\nLength: 400-600 words\nFrequency: Monthly or less (HR = professional, limit oversharing)\n\nHR Tech Daily Content Workflow (3Ɨ per Week)\n\nMONDAY: Research-Backed Insight (2 hours)\n\n08:00-09:00 | Find Research\n\nHR TECH RESEARCH SOURCES:\nā–” SHRM (Society for HR Management) - industry gold standard\nā–” Josh Bersin research - HR thought leader\nā–” Culture Amp blog - engagement benchmarks\nā–” Lattice blog - performance management insights\nā–” Gartner HR research (if accessible)\nā–” Harvard Business Review - people management\nā–” Academic journals - organizational psychology\n\n09:00-10:00 | Write Post\n\nSTRUCTURE:\n\n**HOOK (Research Finding):**\n\"Culture Amp's 2026 benchmark report analyzed 500,000 employee surveys.\nThe #1 driver of retention isn't compensation. It's manager effectiveness.\nBy a margin of 3Ɨ.\"\n\n**CONTEXT:**\nThis challenges conventional wisdom.\nMost CHROs focus budget on:\n- Competitive comp packages\n- Benefits improvements\n- Perks (ping pong, free lunch)\n\nMeanwhile, the data shows:\n- Manager quality = 3Ɨ more predictive of retention\n- Direct manager relationship = #1 factor\n- Yet: 60% of companies have no manager training budget\n\n**FRAMEWORK:**\nWhat top-performing companies do differently:\n1. Manager selection (promote based on leadership, not tenure)\n2. Manager training (quarterly coaching skills development)\n3. Manager accountability (retention = performance metric)\n\n**PRACTICAL APPLICATION:**\nFor small teams (50-200 employees):\n- Start: Monthly manager training (2-hour sessions)\n- Focus: 1 skill per quarter (giving feedback, career development, etc.)\n- Measure: Manager effectiveness scores in engagement surveys\n\nFor mid-market (200-1000):\n- Implement: Manager development program\n- Budget: $500-1K per manager annually\n- ROI: If retention improves 5%, savings = $X (calculate)\n\n**CTA (Professional):**\n\"How does your company invest in manager development?\nI'd love to learn from your approach.\"\n\nNOT: \"What do you think?\" (too generic)\nNOT: \"Tag a bad manager\" (unprofessional)\n\n\nWEDNESDAY: Practical Framework (2 hours)\n\nSTRUCTURE:\n\n**HOOK:**\n\"The 1-on-1 framework I've used with 50+ managers.\n(Backed by research from MIT Sloan and Josh Bersin)\"\n\n**PROBLEM:**\nMost 1-on-1s are status updates.\nManager asks: \"What are you working on?\"\nEmployee shares: \"Project X, Project Y\"\nNo growth. No connection. No development.\n\n**FRAMEWORK: THE 3-TOPIC STRUCTURE**\n\nTopic 1: IMMEDIATE (10 minutes)\n- What's blocking you this week?\n- Where do you need help?\n- Any urgent concerns?\n\nTopic 2: DEVELOPMENT (15 minutes)\n- What skill do you want to build this quarter?\n- What stretch opportunity interests you?\n- How can I support your growth?\n\nTopic 3: CONNECTION (5 minutes)\n- How are you feeling about work?\n- What's energizing you lately?\n- Anything personal I should know about?\n\n**WHY THIS WORKS:**\nResearch shows effective 1-on-1s have 3 elements:\n1. Task support (immediate blockers)\n2. Career development (future growth)\n3. Relationship building (personal connection)\n\nMost managers only do #1.\nTop managers balance all 3.\n\n**TEMPLATE:**\n\"Here's a simple template you can copy:\n[Link to doc or image]\"\n\n**CTA:**\n\"What's your 1-on-1 structure?\nAlways looking to improve mine.\"\n\nTONE: Helpful, not preachy\n\n\nFRIDAY: Empathetic Observation (1.5 hours)\n\nSTRUCTURE:\n\n**HOOK (Vulnerable Opening):**\n\"The CHRO challenge no one talks about:\nYou're responsible for culture. But you don't control it.\"\n\n**SETUP:**\nEvery CHRO has felt this:\n- CEO wants \"better culture\"\n- Board asks about \"employee engagement scores\"\n- But: You can't mandate culture\n\nYou can:\n- Design programs\n- Measure engagement\n- Create policies\n\nYou can't:\n- Control manager quality\n- Force authentic relationships\n- Manufacture belonging\n\n**THE TENSION:**\nThis creates an impossible dynamic:\nā†’ Accountable for outcomes\nā†’ Limited control over inputs\nā†’ Success depends on 100+ managers you don't directly manage\n\n**WHAT HELPS:**\nAfter talking to 30+ CHROs about this:\n\n1. REFRAME YOUR ROLE\nNot: \"Owner of culture\"\nBut: \"Enabler of culture\"\n\nYou don't create culture.\nManagers create culture.\nYou enable them to do it well.\n\n2. FOCUS ON SYSTEMS\n- Manager selection (who gets promoted)\n- Manager training (how we develop leaders)\n- Manager accountability (metrics that matter)\n\n3. MEASURE LEADING INDICATORS\nNot just: Annual engagement scores\nBut: Monthly manager effectiveness scores\n\n**CTA:**\n\"Fellow CHROs: How do you navigate this tension?\nWhat's helped you?\"\n\nTONE: Vulnerable but professional\nGOAL: Build community, not just thought leadership\n\nHR Tech: What NEVER to Post\nāŒ NEVER POST:\n\n\"Workday is terrible. Here's why:\"\nā†’ Attacks competitor (unprofessional)\n\n\"If your company still does annual reviews, you're behind\"\nā†’ Judgmental to audience (many still do this)\n\n\"The engagement survey results that shocked us [gossip]\"\nā†’ Violates employee privacy\n\n\"We just poached a great CHRO from [Company]\"\nā†’ Inappropriate, burns bridges\n\n\"Hot take: HR is mostly useless\"\nā†’ Self-destructive, alienates audience\n\n\"Check out this hilarious HR meme [generic meme]\"\nā†’ Low-value, undermines expertise\n\nRULE FOR HR TECH:\nIf you wouldn't say it at SHRM Annual Conference, don't post it on LinkedIn.\n\nB2: HR Tech @ Series B (Team Content, Brand Voice)\nYour Reality Check:\nCOMPANY PROFILE:\n- Size: $12M-40M ARR, 200-600 employees\n- Stage: Series B\n- You: Director of Content or VP Marketing\n- Team: Writer + Designer (HR background preferred)\n- Content goal: Category thought leadership\n- Publishing: 3-5Ɨ per week\n- Approval: Manager/Founder for sensitive topics\n- Budget: $5K-15K/month\n\nSeries B HR Tech: Elevated Professional Content\nTEAM STRUCTURE:\n\nCONTENT DIRECTOR (You):\n- Strategy (topics, angles, positioning)\n- Stakeholder management (Founder/CHRO, Sales, Product)\n- Approval (final sign-off)\n- Metrics (engagement, brand awareness, pipeline)\n\nHR CONTENT WRITER (1 FTE):\n- Ideally: Background in HR or People Ops\n- Research (SHRM, Josh Bersin, academic studies)\n- Writing (blog posts, LinkedIn, thought leadership)\n- Editing (professional quality)\n\nDESIGNER (Part-time):\n- People-focused visuals (diverse, inclusive imagery)\n- Data visualization (engagement benchmarks, survey results)\n- Brand consistency (HR Tech = warm, professional aesthetic)\n\nFOUNDER/CHRO (Guest Voice):\n- 1Ɨ per week under their name\n- Strategic POV, industry trends\n- Vulnerable shares (culture challenges)\n\nAPPROVAL WORKFLOW:\n\nSTANDARD POST (Research summary, framework):\nWriter ā†’ Content Director ā†’ Publish\nTimeline: Same day to 1 day\n\nSTRATEGIC POST (Industry POV, predictions):\nWriter ā†’ Content Director ā†’ VP Marketing ā†’ Publish\nTimeline: 2-3 days\n\nSENSITIVE POST (Layoffs, DE&I, compensation):\nWriter ā†’ Content Director ā†’ VP Marketing ā†’ Founder/CHRO ā†’ Legal (if needed)\nTimeline: 3-7 days\n\nWHY STRICTER APPROVAL FOR HR TECH:\n- People topics = sensitive (layoffs, DE&I, mental health)\n- Legal risk (employment law, EEOC, GDPR)\n- Reputation risk (HR community is small)\n- Every post reflects on company culture (practice what you preach)\n\nSeries B HR Tech: Original Research Content\nQUARTERLY RESEARCH INITIATIVES:\n\nQ1: \"THE STATE OF EMPLOYEE ENGAGEMENT 2026\"\n- Survey: 500-1,000 HR leaders\n- Partner: SHRM chapter for distribution\n- Content series:\n * Week 1: \"Early findings: What's changing in engagement\"\n * Week 2: \"Hybrid work impact on engagement [data]\"\n * Week 3: \"Manager effectiveness = #1 driver [deep dive]\"\n * Week 4: \"Full report release + webinar\"\n\nProduction:\n- Survey: $2K-5K (Typeform, SurveyMonkey)\n- Design: $1K-3K (report design)\n- Writer: 40 hours (analysis + writing)\n- Timeline: 6-8 weeks\n\nImpact:\n- 800-1,500 new followers\n- 50-100 inbound leads\n- Media coverage (HR Dive, HRExecutive)\n- Sales enablement (differentiation)\n\nQ2: \"MANAGER EFFECTIVENESS BENCHMARKS\"\n- Your product data: Anonymized manager scores\n- Customer interviews: 20 case studies\n- Academic validation: Partner with university\n\nQ3: \"HYBRID WORK BEST PRACTICES [2026]\"\n- Timely, high-interest\n- Multi-company research\n- Expert commentary (industrial-organizational psychologists)\n\nQ4: \"HR TECH STACK SURVEY\"\n- What tools do CHROs use?\n- Integration challenges\n- Budget benchmarks\n- Vendor satisfaction\n\nSeries B HR Tech: Sensitive Topic Guidelines\nLAYOFFS / WORKFORCE REDUCTIONS:\n\nIF YOUR COMPANY IS LAYING OFF:\nāŒ Don't post about it personally until official announcement\nāŒ Don't hint or foreshadow (\"Hard times ahead...\")\nāœ… Wait for official company communication\nāœ… Then: Can share empathetic reflection (after announcement)\n\nIF WRITING ABOUT LAYOFFS GENERALLY:\nāœ… Empathetic tone (people are losing jobs)\nāœ… Practical guidance (for HR leaders navigating this)\nāœ… Mental health resources\nāŒ \"Layoffs are good actually\" (insensitive)\nāŒ Naming companies doing layoffs (unless public news)\n\nEXAMPLE POST (After Your Company Layoff):\n\"We had to make difficult decisions this week.\nAs someone who had to deliver the news to incredible people,\nhere's what I learned about navigating reductions with empathy:\n\n1. Clarity (people deserve straightforward communication)\n2. Dignity (everyone gets proper support)\n3. Transparency (explain the why, not just the what)\n\nThis is hard. If you're going through this, I see you.\"\n\nTONE: Humble, empathetic, human\n\n---\n\nDIVERSITY, EQUITY & INCLUSION (DE&I):\n\nAPPROPRIATE CONTENT:\nāœ… Share research on DE&I impact\nāœ… Best practices (blind resume reviews, structured interviews)\nāœ… Personal commitment (\"We're working on...\")\nāœ… Progress + transparency (\"Here's where we are...\")\n\nINAPPROPRIATE CONTENT:\nāŒ Virtue signaling (\"We're the most diverse!\")\nāŒ Tokenism (featuring one diverse employee repeatedly)\nāŒ Oversimplifying complex topics\nāŒ Speaking over marginalized communities\n\nGUIDANCE:\n- If you're not from the community, amplify voices that are\n- Focus on systems/policies (not individual stories without permission)\n- Be honest about challenges (not just wins)\n- Legal review recommended (DE&I = potential discrimination claims)\n\n---\n\nMENTAL HEALTH:\n\nAPPROPRIATE CONTENT:\nāœ… Normalize mental health discussions\nāœ… Share company resources (EAP, mental health days)\nāœ… Manager training on recognizing signs\nāœ… Empathetic leadership (sharing your own experience)\n\nINAPPROPRIATE CONTENT:\nāŒ Armchair diagnosing (\"I think X has anxiety\")\nāŒ Oversharing personal struggles (maintain professionalism)\nāŒ Suggesting company programs replace professional help\n\nDISCLAIMERS:\nAlways include: \"If you're struggling, please seek professional help.\nResources: [crisis hotline, EAP, etc.]\"\n\nB3: HR Tech @ Series C+ (Josh Bersin Academy-Level)\nYour Reality Check:\nCOMPANY PROFILE:\n- Size: $50M+ ARR, 800+ employees\n- Stage: Series C/D, category leader\n- You: VP Content/Thought Leadership\n- Team: 4-6 FTE content team\n- Newsletter: Industry authority\n- Budget: $20K-50K/month\n- Subscribers: 15,000-60,000+\n\nSeries C+ HR Tech: Industry-Defining Content\nAMBITION:\nNot just \"a content team\"\nGoal: Be THE source for HR insights (like Josh Bersin Academy, SHRM)\n\nYOUR CONTENT BECOMES:\n- Category-defining (sets the HR agenda)\n- Academic-level rigor (published in journals)\n- SHRM conference content (you're invited to speak)\n- Board-level reading (not just HR practitioners)\n\nEXAMPLES:\n- Josh Bersin Academy (HR research + community)\n- Culture Amp content (engagement thought leadership)\n- SHRM (professional association content)\n- Lattice blog (performance management insights)\n\nTEAM STRUCTURE:\n\nVP CONTENT (You):\n- Strategy: Category ownership in HR tech\n- Partnerships: SHRM, Josh Bersin, universities\n- Executive alignment: CHRO/CEO/Board\n- Budget: $20K-50K/month\n\nMANAGING EDITOR:\n- Editorial calendar: 3-6 months ahead\n- Quality control: Academic-level rigor\n- Team management: 3-5 writers/researchers\n\nRESEARCH DIRECTOR:\n- Original research: Quarterly flagship reports\n- Academic partnerships: University collaborations\n- Data analysis: Product data + survey insights\n- Peer review: Submit to academic journals\n\nSENIOR HR CONTENT WRITERS (2-3):\n- Deep specialization:\n * Writer 1: Employee engagement, culture\n * Writer 2: Performance management, development\n * Writer 3: HR tech, analytics\n- Each owns their beat (like journalists)\n\nCOMMUNITY MANAGER:\n- SHRM chapters: Build relationships\n- LinkedIn groups: Engage HR leaders\n- Events: Coordinate speaking, webinars\n- Member support: If you have membership model\n\nTOOLS & PARTNERSHIPS:\n\nRESEARCH PARTNERS:\nā–” Universities: MIT Sloan, Stanford, Wharton (academic credibility)\nā–” SHRM: Distribution + validation\nā–” Josh Bersin Academy: Co-research opportunities\nā–” Gartner/Forrester: Analyst relations\n\nMEMBERSHIP MODEL (Advanced):\n- Free tier: Basic research, blog access\n- Premium ($199-499/year):\n * Exclusive research reports\n * Templates, frameworks, toolkits\n * Private HR community access\n * Quarterly roundtables with CHROs\n\nREVENUE POTENTIAL:\n- 5,000 premium members Ɨ $299/year = $1.5M/year\n- Reinvest in content ā†’ more free content ā†’ more members (flywheel)\n\nSeries C+ Flagship Research Example:\n\"THE FUTURE OF WORK: 2026 COMPREHENSIVE REPORT\"\n\nSCOPE:\n- Survey: 3,000-5,000 HR leaders globally\n- Product data: 5M+ employee engagement responses\n- Academic partnership: MIT Sloan + Stanford\n- Timeline: 6-9 months\n- Budget: $50K-100K\n\nPRODUCTION:\n\nMonth 1-2: Research Design\n- Literature review (existing research)\n- Survey design (validated questions)\n- IRB approval (university ethics board)\n- Methodology documentation (academic standards)\n\nMonth 3-5: Data Collection\n- Survey distribution:\n * SHRM partnership (300K members)\n * LinkedIn ads ($15K budget)\n * Customer outreach\n * Partner organizations\n- Goal: 3,000-5,000 complete responses\n- Executive interviews: 100 CHROs (qualitative data)\n\nMonth 6-7: Analysis\n- Quantitative: Statistical analysis (regression, factor analysis)\n- Qualitative: Theme coding (interview transcripts)\n- Product data integration: Combine survey + behavioral data\n- Validation: University researchers review methodology\n\nMonth 8: Production\n- Report: 80-100 pages (academic quality)\n- Executive summary: 6-8 pages\n- Infographic: 1-page visual summary\n- Interactive dashboard: Explore data online\n\nMonth 9: Publication & Amplification\n- Academic submission: Journal of Applied Psychology (peer review)\n- Industry release: SHRM, HR Executive, HR Dive\n- Conference: Present at SHRM Annual Conference\n- Media: Secure coverage in HBR, WSJ, Forbes\n\nIMPACT:\n\nCATEGORY LEADERSHIP:\n- Cited by Gartner in their HR Tech Magic Quadrant\n- Referenced in competitor earnings calls\n- Becomes THE source media references\n- SHRM invites you to their conferences annually\n\nBUSINESS:\n- 3,000-5,000 report downloads\n- 200-400 SQLs\n- $3M-8M influenced pipeline\n- Sales wins: \"Your research on hybrid work sealed the deal\"\n\nRECRUITING:\n- \"I read your Future of Work report\" (candidate interviews)\n- Top CHRO talent wants to work at research-driven companies\n\nACADEMIC:\n- Published in peer-reviewed journal (credibility)\n- Professors assign your research in MBA programs\n- University partnerships for future research\n\nšŸ“Š SECTION C: FINTECH CONTENT WRITING\n\nWhen To Use This Section:\n\nYour product: Payments, expense management, corporate cards, payroll\nYour audience: CFOs, Finance leaders, Controllers\nYour content angle: Regulations, compliance, financial efficiency\nVoice: ULTRA-CONSERVATIVE (legal review mandatory)\nC1: Fintech @ Series A (Every Post Needs Legal Review)\nYour Reality Check:\nCOMPANY PROFILE:\n- Size: $2M-8M ARR, 20-100 employees\n- Stage: Series A\n- You: Founder\n- Content goal: Build trust (not leads - trust comes first)\n- Publishing: 1-2Ɨ per week (slower due to legal review)\n- CRITICAL: Legal review mandatory for every single post\n- Voice: Conservative, compliant, trustworthy\n\nWhy Fintech Content is HIGHEST RISK:\nSALES TECH:\nāœ… Aggressive positioning\nāœ… \"Gong is wrong about X\"\nRisk: Low (lose followers)\n\nHR TECH:\nāš ļø Professional, no attacks\nRisk: Medium (reputation)\n\nFINTECH:\nšŸ”“ ULTRA-CONSERVATIVE MANDATORY\nšŸ”“ LEGAL REVIEW FOR EVERY POST\nšŸ”“ NEVER make unverified claims\nšŸ”“ NEVER attack competitors\nšŸ”“ NEVER share user data\nRisk: EXTREME (regulatory fines, license revocation, criminal liability)\n\nWHY:\n- Financial regulations: RBI (India), SEC (US), FCA (UK)\n- Financial advertising rules: Can't make unverified ROI claims\n- Data privacy: Can't share user financial data (RBI compliance)\n- Reputational risk: Finance = trust-driven (one mistake = brand death)\n- Legal liability: Directors personally liable for violations\n\nFintech Content Guidelines (Non-Negotiable):\nāœ… ALWAYS ALLOWED:\n\n\"RBI released new payment aggregator guidelines. Here's what fintech companies need to know:\"\nā†’ Regulatory updates (factual, helpful)\n\n\"3 compliance checklist items for Indian fintechs [2026 edition]\"\nā†’ Educational, compliance-focused\n\n\"How we achieved SOC 2 compliance in 12 months [timeline]\"\nā†’ Your journey (factual, no claims about others)\n\n\"CFO's guide to expense management compliance\"\nā†’ Educational, helpful\n\nāŒ NEVER ALLOWED:\n\n\"Traditional banking is broken. Here's why fintech is better.\"\nā†’ Attacks incumbents (regulatory risk)\n\n\"Save 50% on payment fees with our solution\"\nā†’ Unverified ROI claim (unless proven and methodology disclosed)\n\n\"We're the fastest-growing fintech in India\"\nā†’ Superlative claim (unless third-party verified)\n\n\"Customer X saved ā‚¹10L using our product\"\nā†’ Customer data (compliance violation without written permission)\n\n\"Why [Competitor] is overpriced\"\nā†’ Competitor attack (could trigger legal action)\n\nCRITICAL RULE:\nIf you're not 100% certain it's compliant, get legal review.\nIn fintech, \"better to ask forgiveness\" DOES NOT APPLY.\n\nFintech Content Mix (Conservative):\n60% REGULATORY/COMPLIANCE UPDATES\n- \"New RBI guidelines for payment companies\"\n- \"KYC requirements: What changed in 2026\"\n- \"Data localization compliance checklist\"\nSource: Official sources only (RBI, NPCI, Ministry of Finance)\nTone: Factual, educational, helpful\nFrequency: 1Ɨ per week (as regulations change)\n\n25% EDUCATIONAL BEST PRACTICES\n- \"CFO's guide to corporate expense management\"\n- \"How to evaluate payment aggregators [checklist]\"\n- \"SOC 2 compliance: Step-by-step guide\"\nSource: Industry standards, your experience\nTone: Helpful, not sales-y\nFrequency: 1Ɨ every 2 weeks\n\n10% COMPANY UPDATES (Factual Only)\n- \"We achieved SOC 2 Type II certification\"\n- \"Announcing: RBI Payment Aggregator license\"\n- \"New integration: Zoho Books\"\nSource: Your company (factual announcements)\nTone: Professional, humble\nFrequency: As milestones happen\n\n5% THOUGHT LEADERSHIP (Extremely Careful)\n- \"The future of UPI payments in India [analysis]\"\n- \"Cross-border payments: 2027 predictions\"\nSource: Industry trends (clearly labeled as opinion)\nTone: Measured, balanced, acknowledges uncertainty\nFrequency: Monthly or less\n\nFintech Approval Workflow (Mandatory):\nEVERY POST FOLLOWS THIS PROCESS:\n\nSTEP 1: DRAFT (You or Writer)\n- Write post\n- Cite all sources\n- Include disclaimers\nTime: 1-2 hours\n\nSTEP 2: SELF-CHECK\nā–” Is this factual? (verifiable)\nā–” Do I cite sources? (RBI, official sources)\nā–” Am I making claims? (if yes, can I prove them?)\nā–” Am I mentioning competitors? (if yes, is it necessary?)\nā–” Am I sharing user data? (if yes, do I have written permission?)\nā–” Is there any regulatory risk? (when in doubt, YES)\n\nSTEP 3: LEGAL REVIEW (1-3 days)\n- Send to legal counsel\n- They review for:\n * Regulatory compliance\n * Financial advertising rules\n * Data privacy\n * Competitor mention risk\n- They may:\n * Approve as-is\n * Request edits\n * Reject entirely\n\nSTEP 4: REVISE (If Needed)\n- Incorporate legal feedback\n- Re-submit for final approval\n\nSTEP 5: PUBLISH\n- Only after legal sign-off\n- Include all required disclaimers\n\nTIMELINE:\n- Simple post: 1-2 days (draft ā†’ legal ā†’ publish)\n- Complex post: 3-5 days\n- Controversial topic: May be rejected\n\nCOST:\n- Legal counsel retainer: $5K-10K/month\n- Per-post review: $200-500 (if not on retainer)\n- Worth it: Avoiding ā‚¹1 Cr fine or license revocation\n\nFintech Examples (Compliant vs Non-Compliant):\nTOPIC: Payment Processing Speeds\n\nāŒ NON-COMPLIANT:\n\"We process payments 10Ɨ faster than Razorpay.\nSwitch to us and save hours of processing time.\"\n\nISSUES:\n- Unverified claim (\"10Ɨ faster\" - can you prove it?)\n- Competitor attack (Razorpay could sue)\n- Implied guarantee (\"save hours\" - what if customer doesn't?)\n\nāœ… COMPLIANT:\n\"Payment processing speeds vary by provider and use case.\nIn our testing with 100 transactions, average processing time was X seconds.\n(Methodology: [link to documentation])\"\n\nWHY IT'S COMPLIANT:\n- Factual (your own testing)\n- Methodology disclosed\n- No competitor attacks\n- No guarantees\n\n---\n\nTOPIC: Cost Savings\n\nāŒ NON-COMPLIANT:\n\"Save 50% on payment fees!\"\n\nISSUES:\n- Unverified ROI claim\n- No methodology\n- Implies guarantee\n\nāœ… COMPLIANT:\n\"Payment fee structures vary by volume and use case.\nOur pricing: X% per transaction + ā‚¹Y fixed fee.\n[Link to pricing page]\nCompare options based on your transaction volume.\"\n\nWHY IT'S COMPLIANT:\n- Factual (your own pricing)\n- No claims about competitors\n- No ROI guarantee\n- Helpful (empowers comparison)\n\nšŸ“Š SECTION D: OPERATIONS TECH CONTENT WRITING\n\nWhen To Use This Section:\n\nYour product: Retail execution, logistics, field force automation\nYour audience: Sales/Ops leaders at CPG/FMCG companies\nYour content angle: Distribution, retail, supply chain\nVoice: Industry-specific, B2B2B2C complexity\nD1: Operations Tech @ Series A (Niche Industry Focus)\nYour Reality Check:\nCOMPANY PROFILE:\n- Size: $1M-5M ARR, 15-60 employees\n- Stage: Series A\n- You: Founder (ex-CPG or tech)\n- Content focus: India retail execution insights\n- Publishing: 2-3Ɨ per week\n- Audience: Small but highly engaged (CPG sales leaders)\n\nWhy Operations Tech Content is NICHE:\nSALES/HR/FINTECH:\n- Broad audience (all B2B SaaS)\n- Generic topics (sales, HR, finance)\n- Large following potential (10K+ followers)\n\nOPERATIONS TECH:\n- Niche audience (CPG/FMCG/logistics)\n- Specific topics (retail execution, distribution, field force)\n- Smaller following (1K-3K) but HIGH engagement\n- B2B2B2C complexity (You ā†’ CPG ā†’ Distributor ā†’ Retailer ā†’ Consumer)\n\nADVANTAGE OF NICHE:\nāœ… Less competition (few people write about retail execution)\nāœ… Higher engagement rate (exactly what audience needs)\nāœ… Easier to become THE expert\nāœ… Stronger community (CPG sales leaders all know each other)\nāœ… Higher intent leads (if they follow you, they're serious)\n\nOperations Tech Content Topics:\nCORE TOPICS:\n\n40% RETAIL EXECUTION INSIGHTS\n- \"State of general trade in India [Q4 2025 data]\"\n- \"How kiranas are adapting to quick commerce\"\n- \"Distribution coverage: North vs South India [analysis]\"\nSource: Your product data, industry reports, field observations\nAudience: CPG sales heads, ops leaders\n\n30% FIELD FORCE BEST PRACTICES\n- \"The beat planning framework that increased coverage by 20%\"\n- \"How top field reps use mobile apps [case study]\"\n- \"Offline-first: Why it matters for rural distribution\"\nSource: Customer success stories, your product\nAudience: Field force managers, ops leaders\n\n20% CPG INDUSTRY TRENDS\n- \"Quick commerce impact on FMCG distribution [2026]\"\n- \"D2C brands: Distribution lessons for CPG\"\n- \"How HUL/ITC are changing go-to-market\"\nSource: Industry news, earnings calls, your analysis\nAudience: CPG strategy, business leaders\n\n10% TECHNOLOGY IN RETAIL/LOGISTICS\n- \"How AI is changing retail audits\"\n- \"Image recognition for planogram compliance\"\n- \"Route optimization: Tech vs manual planning\"\nSource: Your product innovation, industry tech trends\nAudience: Tech-forward ops leaders\n\nšŸ”„ CROSS-CUTTING: UNIVERSAL FRAMEWORKS\nRole-Based Content Workflows\nFOUNDER CONTENT (Full Autonomy)\nADVANTAGES:\nāœ… No approval needed (publish freely)\nāœ… Personal voice = authentic\nāœ… Can be contrarian (if industry allows)\nāœ… Can share company metrics\nāœ… Can pivot messaging quickly\n\nWORKFLOW:\nMonday: Idea generation (30 min)\nTuesday: Write post #1 (1 hour)\nWednesday: Publish + engage (30 min)\nThursday: Write post #2 (1 hour)\nFriday: Publish + weekly recap (30 min)\n\nTotal time: 3.5 hours/week\n\nBEST PRACTICES:\nā–” Batch content (write 2-3 posts in one sitting)\nā–” Use voice memos (capture ideas on the go)\nā–” Repurpose (newsletter ā†’ LinkedIn ā†’ Twitter thread)\nā–” Engage (comment on others' posts daily)\nā–” Track (what topics get most engagement?)\n\nEMPLOYEE CONTENT (Approval Required)\nSCENARIO: VP Marketing Writing Personal Content\n\nCHALLENGES:\nāš ļø Company wants brand consistency\nāš ļø Can't share company confidential info\nāš ļø Must add \"Views are my own\" disclaimer\nāš ļø Manager needs to approve (at minimum)\n\nAPPROVAL WORKFLOW:\n\nSTEP 1: Get Manager Alignment (One-Time)\nā–” Pitch: \"I want to build thought leadership in [category]\"\nā–” Clarify: Personal brand, not company official content\nā–” Agree on boundaries:\n - What I CAN share about company\n - What I CANNOT share\n - Approval process\n\nSTEP 2: Write with Constraints\nCAN SHARE:\nāœ… Industry insights (not company-specific)\nāœ… Your professional opinions\nāœ… Public company information\nāœ… General frameworks\n\nCANNOT SHARE:\nāŒ Revenue/ARR/growth numbers (unless public)\nāŒ Roadmap/unannounced features\nāŒ Customer names (without permission)\nāŒ Internal metrics/team size\nāŒ Fundraising plans\n\nSTEP 3: Add Disclaimer\nEVERY post includes:\n\"Views expressed here are my own and do not necessarily represent the views of [Company Name].\"\n\nSTEP 4: Periodic Review\nā–” Monthly: Show manager your content\nā–” Quarterly: Confirm still aligned with company\nā–” Annually: Review and renew agreement\n\nWORKFLOW (Slower Than Founder):\nMonday: Draft post #1\nTuesday: Get manager feedback\nWednesday: Revise + publish\nThursday-Friday: Draft post #2 (publish Monday)\n\nTime: 4-5 hours/week (approval adds overhead)\n\nENTERPRISE EMPLOYEE (Corporate Comms Control)\nSCENARIO: CMO at Public SaaS Company\n\nREALITY:\nšŸ”“ EVERYTHING requires PR approval\nšŸ”“ Can't publish without 1-2 week review\nšŸ”“ Ghost-written by PR team\nšŸ”“ No personal opinions\nšŸ”“ No controversial takes\n\nCONSTRAINTS:\nā–” All posts pre-approved by:\n - Corporate Communications\n - Legal (if financial topics)\n - Executive team\n - Investor Relations (if public company)\n \nā–” Topics must be:\n - Brand-safe\n - On-message\n - Non-controversial\n - Aligned with company narrative\n\nā–” Timeline:\n - Draft ā†’ Corporate Comms (3-5 days)\n - Revisions (2-3 days)\n - Legal review (1-2 days if needed)\n - Final approval (1 day)\n - Total: 1-2 weeks per post\n\nOPTIONS:\n1. Accept constraints (corporate voice)\n2. Limit posting (1Ɨ per month, big announcements only)\n3. Internal content only (employees, not public)\n4. Wait until you leave company (build personal brand then)\n\nRECOMMENDATION:\nIf at public company or highly-regulated industry:\nā†’ Focus on thought leadership via:\n - Speaking at conferences (pre-approved topics)\n - Bylines in trade publications (legal review)\n - Podcasts as guest (talking points approved)\nā†’ Save personal LinkedIn brand for next role\n\nGeography-Specific Content Strategies\nIndia Content Strategy:\nPUBLISHING TIMES:\nāœ… Tuesday-Thursday, 9 AM-2 PM IST\nāœ… Avoid Monday early (week starting)\nāœ… Avoid Friday late (weekend mode)\n\nCONTENT STYLE:\n- Relationship-focused (build connections)\n- Local examples (FieldAssist, not Gong)\n- Price-conscious (acknowledge budget constraints)\n- WhatsApp mentions (\"Share this in your team WhatsApp group\")\n\nEXAMPLES:\nāœ… \"How Darwinbox scaled from 100 to 1,000 customers\"\nāœ… \"Retail execution in India: General trade vs modern trade\"\nāœ… \"RBI's new guidelines for payment companies\"\nāŒ \"How we're disrupting the US market\" (wrong geography)\n\nCOMMUNITY ENGAGEMENT:\nā–” SaaSBoomi (India B2B SaaS community)\nā–” IAMAI (fintech, if applicable)\nā–” India-specific LinkedIn groups\nā–” Respond to comments in IST hours\n\nUS Content Strategy:\nPUBLISHING TIMES:\nāœ… Tuesday-Thursday, 9-11 AM EST\nāœ… Some success: 12-2 PM EST (lunch scrolling)\nāœ… Avoid early mornings (West Coast asleep)\n\nCONTENT STYLE:\n- Direct, data-driven\n- US examples (Gong, Lattice, Stripe)\n- Premium positioning (value > price)\n- Email CTAs (\"Download the report\")\n\nEXAMPLES:\nāœ… \"How Gong uses conversation intelligence [analysis]\"\nāœ… \"Sales tech landscape: The rise of AI coaching\"\nāœ… \"SOC 2 compliance timeline for SaaS companies\"\nāŒ \"How we're winning in India\" (wrong geography for US audience)\n\nCOMMUNITY ENGAGEMENT:\nā–” SaaStr (B2B SaaS)\nā–” Pavilion (GTM leaders)\nā–” Revenue Collective (CROs)\nā–” Respond during US business hours\n\nCommon Content Mistakes & How to Fix\nMistake 1: \"Writing Same Way for All Industries\"\nWRONG:\nSame aggressive contrarian post for Sales Tech, HR Tech, and Fintech\n\nWHY IT FAILS:\n- Sales Tech: Aggressive = good\n- HR Tech: Aggressive = unprofessional\n- Fintech: Aggressive = regulatory risk\n\nFIX:\nā†’ Sales Tech ā†’ Section A (aggressive allowed)\nā†’ HR Tech ā†’ Section B (professional required)\nā†’ Fintech ā†’ Section C (ultra-conservative mandatory)\n\nMistake 2: \"No Approval Process (When You Need One)\"\nSCENARIO: Employee Publishes Without Manager Knowing\n\nRISKS:\n- Share confidential info accidentally\n- Company asks you to delete post (embarrassing)\n- Misaligned with company messaging\n- Career risk (manager upset)\n\nFIX:\nā†’ Role-Based Workflows section\nā†’ Get manager alignment BEFORE posting\nā†’ Monthly check-ins on content\n\nMistake 3: \"Publishing at Wrong Times\"\nPROBLEM:\nPublishing Friday 5 PM EST for US sales leaders\n\nRESULT:\n- Low engagement (everyone checked out)\n- Algorithm doesn't boost\n- Wasted content\n\nFIX:\n- India: Tuesday-Thursday, 9 AM-2 PM IST\n- US: Tuesday-Thursday, 9-11 AM EST\n- Test and track what works for YOUR audience\n\nPrompt Templates by Scenario\nTemplate 1: Sales Tech Founder, Aggressive Post\nUsing Content Writing skill, Section A1:\n\nI'm a Sales Tech founder. I want to write an aggressive but data-backed post.\n\nTopic: [Your contrarian take]\nData: [What data do you have?]\nCompetitor context: [Are you challenging Gong/Outreach/etc?]\n\nPlease:\n1. Write hook (contrarian, attention-grabbing)\n2. Present data (credible, specific)\n3. Build case (logical progression)\n4. Include nuance (not just aggressive)\n5. End with CTA (spark discussion)\n\nLength: 400-500 words\nTone: Confident but not arrogant\nGuardrails: Attack ideas, not people\n\nTemplate 2: HR Tech VP, Professional Post\nUsing Content Writing skill, Section B:\n\nI'm VP Marketing at HR Tech company.\n\nTopic: [Employee engagement, performance management, etc.]\nResearch: [SHRM, Josh Bersin, Culture Amp data?]\nGoal: [Build credibility, not leads]\n\nPlease:\n1. Open with research finding\n2. Provide context (why this matters)\n3. Offer practical framework\n4. Include CTA (professional, inviting discussion)\n\nLength: 500-600 words\nTone: Professional, empathetic, helpful\nConstraints: NEVER aggressive, NEVER attack competitors\n\nTemplate 3: Fintech Founder, Compliance Post\nUsing Content Writing skill, Section C:\n\nI'm a fintech founder. I need a compliant post.\n\nTopic: [Regulatory update, compliance topic]\nSource: [RBI announcement, official source]\nLegal review: Will review before publishing\n\nPlease:\n1. Summarize regulation factually\n2. Explain impact on fintech companies\n3. Provide compliance checklist\n4. Include disclaimer\n5. No competitor mentions\n6. No unverified claims\n\nLength: 400-500 words\nTone: Educational, helpful, conservative\nCRITICAL: Flag anything that might need legal review\n\n\n---\n\n## **Worked Examples: Multi-Dimensional Scenarios**\n\n### **Example 1: Sales Tech Founder, Series A, Aggressive Post**\n\n\n\nSCENARIO:\n\nCompany: AI sales coaching, $3M ARR, 30 employees\nYou: Co-founder & CEO\nGoal: Challenge Gong's methodology (contrarian take)\nPlatform: LinkedIn\nApproval: None (founder autonomy)\n\nCONTENT APPROACH:\n\nTOPIC: \"Gong's data on discovery calls is misleading. Here's why:\"\n\nSTEP 1: GATHER DATA (Your Product)\n\nExport: 50,000 sales calls from your product\nAnalyze: Average discovery call length\nFinding: Your data shows 25 minutes (vs Gong's 38 minutes)\nHypothesis: Different ICP (SMB vs enterprise)\n\nSTEP 2: WRITE HOOK (Aggressive but Credible) \"Gong says the average discovery call is 38 minutes. We analyzed 50,000 calls and found 25 minutes.\n\nHere's what Gong missed:\"\n\nSTEP 3: BUILD CASE (Data-Driven) The difference:\n\nGong's data: Skews enterprise (longer, more complex sales)\nOur data: Focuses SMB B2B SaaS (faster cycles)\nSMB discovery: 15-25 minutes (more efficient)\nEnterprise discovery: 35-45 minutes (more stakeholders)\n\nSTEP 4: NUANCE (Important) \"Am I saying Gong is wrong? No. Am I saying their data doesn't apply to SMB? Yes.\n\nIf you're selling to SMB, optimize for 20-minute discovery. If you're enterprise, 35-40 minutes is right.\"\n\nSTEP 5: PUBLISH + AMPLIFY\n\nLinkedIn: Tuesday 9 AM EST\nFirst comment: Link to methodology\nTag: @mention Gong (they might engage)\nMonitor: Reply to all comments within 1 hour\n\nRESULT:\n\nEngagement: 2-3Ɨ normal (controversial = engagement)\nComments: Mix of agreement + Gong defenders (debate = algorithm boost)\nLeads: 15-20 inbound \"I agree with your SMB POV\"\nGong might respond (if they do, be respectful)\n\nRISK ASSESSMENT:\n\nRisk level: Medium (challenging industry leader)\nMitigation: Data-backed, nuanced, respectful\nWorst case: Gong ignores or politely disagrees\nBest case: Healthy debate, massive reach\n\n### **Example 2: HR Tech VP, Series B, Sensitive Topic (Layoffs)**\n\n\n\nSCENARIO:\n\nCompany: Employee engagement platform, $20M ARR\nYou: VP Marketing\nContext: Your company just laid off 15% of staff\nGoal: Address layoffs professionally\nConstraint: Can't post until official announcement\n\nTIMELINE:\n\nDAY 1 (Layoff Day): āŒ Don't post anything on LinkedIn yet āœ… Focus on: Supporting impacted employees internally āœ… Wait for: Official company communication\n\nDAY 2-3 (After Official Announcement): āœ… Now you can post (company has communicated)\n\nCONTENT APPROACH:\n\nSTEP 1: CHECK WITH LEADERSHIP Before writing: ā–” Does CEO/CHRO want me to post? ā–” What's the approved messaging? ā–” Any topics to avoid? ā–” Legal review needed?\n\nSTEP 2: WRITE POST (Empathetic, Honest)\n\nHOOK: \"We made difficult decisions this week. As someone who had to deliver hard news to people I deeply respect, I want to share what I learned about navigating reductions with empathy.\"\n\nBODY: What mattered most:\n\nClarity (people deserve straightforward answers, not corporate speak)\nDignity (generous severance, extended benefits, placement support)\nSupport (for those leaving AND those staying)\n\nFor those impacted:\n\nI'm happy to provide LinkedIn recommendations\nI'll make intros where I can\nYou deserved better timing, and I'm sorry\n\nFor the team staying:\n\nWe're committed to getting this right\nYour questions deserve honest answers\nWe'll rebuild trust through actions\n\nCTA: \"If you've navigated this as a leader, I'd appreciate your guidance. And if you're hiring for [roles], several incredible people are looking.\"\n\nSTEP 3: LEGAL REVIEW ā–” Send to legal counsel ā–” Check: Any liability concerns? ā–” Confirm: Severance terms not disclosed (confidential) ā–” Ensure: No promises made that company can't keep\n\nSTEP 4: PUBLISH + MONITOR\n\nTime: Not Friday evening (shows lack of care)\nBetter: Tuesday-Wednesday (thoughtful timing)\nMonitor: Comments (many will be supportive, some critical)\nRespond: Acknowledge, don't defend\n\nAPPROVAL CHAIN: Draft ā†’ Legal ā†’ VP Marketing ā†’ CHRO ā†’ CEO ā†’ Publish Timeline: 3-5 days\n\nRESULT:\n\nHumanizes difficult decision\nShows empathy + accountability\nHelps impacted employees (visibility for job search)\nMaintains professional reputation\n\n### **Example 3: Fintech Founder, Series A, Regulatory Update Post**\n\n\n\nSCENARIO:\n\nCompany: Payment aggregator, $4M ARR, 40 employees\nYou: Founder & CEO\nContext: RBI just released new PA guidelines\nGoal: Educate fintech community\nConstraint: Legal review mandatory\n\nCONTENT APPROACH:\n\nSTEP 1: READ OFFICIAL SOURCE\n\nRBI circular: Download PDF, read thoroughly\nIdentify: 5-7 key changes\nClarify: What's new vs what's unchanged\nConsult: Legal counsel for interpretation\n\nSTEP 2: DRAFT POST (Conservative, Educational)\n\nHOOK: \"RBI released updated Payment Aggregator guidelines yesterday. Here's what fintech companies need to know:\"\n\nBODY: Key changes (effective April 1, 2026):\n\nKYC Requirements Strengthened\nPrevious: Basic KYC for merchants\nNew: Enhanced due diligence for high-risk categories\nAction: Review your merchant onboarding process\nData Localization Timeline\nPrevious: \"As soon as possible\"\nNew: Mandatory by June 30, 2026\nAction: If you're not compliant, start now (6-month timeline)\nReporting Requirements\nPrevious: Quarterly\nNew: Monthly submission to RBI\nAction: Update your compliance calendar\nNet-Worth Requirements\nNo change: Still ā‚¹15 crore minimum\nClarification: Must be maintained at all times\n\nNOT CHANGED (Important):\n\nLicense renewal: Still 3 years\nMerchant agreement requirements: Unchanged\nSettlement timelines: Remain T+1\n\nDISCLAIMER: \"This is for informational purposes only and does not constitute legal advice. Always consult qualified legal counsel for your specific situation.\"\n\nSTEP 3: LEGAL REVIEW (1-2 days) Send to legal counsel: ā–” Check factual accuracy ā–” Verify no overstatement ā–” Confirm disclaimer is appropriate ā–” Ensure no competitive mentions\n\nSTEP 4: PUBLISH + DISTRIBUTE\n\nLinkedIn: Tuesday 10 AM IST (India market)\nFirst comment: Link to official RBI circular\nDistribution: Share in IAMAI fintech group\nEmail: Send to customer list (value-add)\n\nRESULT:\n\nPositions you as: Helpful expert (not sales-y)\nBuilds trust: Fintech community appreciates clarity\nLeads: \"We need help with compliance\" inquiries\nRisk: Zero (factual, legal-reviewed, helpful)\n\nCONTRAST WITH WRONG APPROACH:\n\nāŒ DON'T WRITE: \"RBI's new rules will kill most payment companies. Here's why we're better positioned than our competitors.\"\n\nWHY IT'S WRONG:\n\nFear-mongering (unprofessional)\nCompetitor mention (unnecessary)\nCould trigger regulatory scrutiny\n\n---\n\n## **Tool Comparison Matrix**\n\n| Tool | Cost | Best For | Not Good For | Series A | Series B | Series C+ |\n|------|------|----------|--------------|----------|----------|-----------|\n| **LinkedIn Native** | Free | Everyone (start here) | Scheduling, analytics | āœ… | āœ… | āœ… |\n| **Buffer** | $6/mo/channel | Budget-conscious, multi-platform | Advanced analytics | āœ… | āœ… | āœ… |\n| **Taplio** | $39/mo | LinkedIn power users, carousel creation | Multi-platform | āš ļø | āœ… | āœ… |\n| **Shield** | $12/mo | Analytics junkies, engagement tracking | Content creation | āš ļø | āœ… | āœ… |\n| **Canva Pro** | $13/mo | Visual content (carousels, infographics) | Video editing | āœ… | āœ… | āœ… |\n| **Figma** | Free-$12/mo | Design teams, brand consistency | Solo founders (overkill) | āŒ | āœ… | āœ… |\n| **Grammarly Premium** | $12/mo | Error-free writing, tone checker | Creative writing | āš ļø | āœ… | āœ… |\n| **Hemingway** | Free | Simplifying complex writing | Sales copy (too simple) | āœ… | āœ… | āœ… |\n\n**RECOMMENDATIONS BY STAGE:**\n\n**Series A ($0-50/month):**\nāœ… LinkedIn Native (free)\nāœ… Canva Free (visual content)\nāœ… Hemingway (editing)\nāŒ Skip: Taplio, paid tools (use budget for product)\n\n**Series B ($50-200/month):**\nāœ… Taplio or Shield ($39-50/mo)\nāœ… Canva Pro ($13/mo)\nāœ… Grammarly ($12/mo)\nTotal: ~$64/mo\n\n**Series C+ ($200-500/month):**\nāœ… Taplio + Shield ($51/mo)\nāœ… Canva Pro + Figma ($25/mo)\nāœ… Buffer ($60/mo for team)\nāœ… Premium design tools\nTotal: $200-500/mo (small portion of $20K-50K content budget)\n\n---\n\n## **Quick Reference Cards**\n\n### **By Industry Tone:**\n\n\n\nSALES TECH: āœ… Aggressive, contrarian, data-driven āœ… Challenge incumbents (Gong, Outreach) āœ… ROI-focused, tactical frameworks āœ… LinkedIn posts: 300-500 words, 3-5Ɨ/week Publishing: Tuesday-Thursday 9 AM EST / 9 AM IST\n\nHR TECH: āœ… Professional, empathetic, research-backed āŒ NEVER aggressive or attack competitors āœ… SHRM/Josh Bersin citations āœ… LinkedIn posts: 400-600 words, 2-3Ɨ/week Publishing: Tuesday/Thursday 10 AM EST / 2 PM IST\n\nFINTECH: šŸ”“ Ultra-conservative, legal review mandatory āŒ NO competitor attacks, NO unverified claims āœ… Regulatory updates, compliance education āœ… LinkedIn posts: 400-500 words, 1-2Ɨ/week Publishing: Tuesday-Wednesday 10 AM EST / 10 AM IST\n\nOPERATIONS TECH: āœ… Industry-specific, B2B2B2C aware āœ… Retail/distribution insights āœ… CPG case studies āœ… LinkedIn posts: 300-500 words, 2-3Ɨ/week Publishing: Tuesday-Thursday 9 AM EST / 9 AM IST\n\n\n### **By Company Stage:**\n\n\n\nSERIES A:\n\nFounder voice (authentic, scrappy)\nPublishing: 3-5Ɨ/week\nApproval: None (founder)\nBudget: $0-50/month (free tools)\nGoal: Leads (10-20 SQLs/month)\nTime: 5-8 hours/week\n\nSERIES B:\n\nTeam content (professional, branded)\nPublishing: 5-7Ɨ/week\nApproval: Content Lead ā†’ VP Marketing\nBudget: $3K-10K/month (team + tools)\nGoal: Thought leadership + pipeline\nTime: 40-60 hours/week (team total)\n\nSERIES C+:\n\nCategory ownership (industry-defining)\nPublishing: 7-10Ɨ/week (multi-channel)\nApproval: Complex (legal, exec, PR)\nBudget: $20K-50K/month (media-level)\nGoal: Own the conversation\nTime: 100-150 hours/week (full team)\n\n### **Approval Workflow Quick Reference:**\n\n\n\nFOUNDER (No Approval): Draft ā†’ Publish (same day) Timeline: 1 hour total\n\nEMPLOYEE - STANDARD POST: Draft ā†’ Manager review ā†’ Publish Timeline: 1-2 days\n\nEMPLOYEE - STRATEGIC POST: Draft ā†’ Manager ā†’ VP Marketing ā†’ Publish Timeline: 2-3 days\n\nEMPLOYEE - SENSITIVE POST: Draft ā†’ Manager ā†’ VP ā†’ CEO ā†’ Legal (if needed) ā†’ Publish Timeline: 3-7 days\n\nFINTECH - ANY POST: Draft ā†’ Legal review (mandatory) ā†’ Publish Timeline: 1-3 days minimum\n\nPUBLIC COMPANY: Draft ā†’ Corp Comms ā†’ Legal ā†’ Exec ā†’ IR ā†’ Publish Timeline: 1-2 weeks\n\n\n---\n\n**END OF SKILL**" }, "trust": { "sourceLabel": "tencent", "provenanceUrl": "https://clawhub.ai/shashwatgtm/content-writing-thought-leadership", "publisherUrl": "https://clawhub.ai/shashwatgtm/content-writing-thought-leadership", "owner": "shashwatgtm", "version": "1.0.0", "license": null, "verificationStatus": "Indexed source record" }, "links": { "detailUrl": "https://openagent3.xyz/skills/content-writing-thought-leadership", "downloadUrl": "https://openagent3.xyz/downloads/content-writing-thought-leadership", "agentUrl": "https://openagent3.xyz/skills/content-writing-thought-leadership/agent", "manifestUrl": "https://openagent3.xyz/skills/content-writing-thought-leadership/agent.json", "briefUrl": "https://openagent3.xyz/skills/content-writing-thought-leadership/agent.md" } }