article-writing-professional

name	article-writing-professional
description	Professional-grade article writing for blogs, guides, tutorials, newsletters, and long-form content. Enhanced with audience targeting, SEO optimization, distribution strategy, quality metrics, voice profiling, content frameworks, research methodology, and comprehensive quality assurance. Write distinctive, credible content that converts readers into users, customers, or advocates.
origin	ECC
tier	professional
version	2

Article Writing Skill (Professional Edition)

Write long-form content that sounds like an actual expert with conviction, backed by evidence, optimized for your audience and distribution channel.

---

When to Activate

Content Type Triggers:

• Blog posts, essays, launch announcements, thought leadership
• Technical guides, tutorials, how-to articles, documentation
• Newsletter issues, email sequences, brand communications
• Case studies, research reports, whitepapers
• Landing page copy, product guides, educational content
• Guides, frameworks, playbooks, best-practice documents

Situation Triggers:

• User wants polished written content longer than a paragraph
• Voice consistency matters (founder voice, brand voice, personal brand)
• Credibility, structure, and evidence are critical
• Content will be distributed (blog, email, social, publication)
• SEO or conversion performance matters
• Turning notes, transcripts, research, or raw ideas into polished copy
• Audience targeting and messaging strategy needed
• Multi-channel distribution strategy required

---

Core Rules (Enhanced)

1. Lead with the concrete thing: artifact, example, output, anecdote, number, screenshot, or code.

   • Not: "Many people struggle with X"
   • Yes: "We shipped 3 months faster when we changed X"

2. Explain after the example, not before.

   • Show the result, then explain why it works
   • Reverse academic structure: proof → analysis (not thesis → proof)

3. Keep sentences tight unless the source voice is intentionally expansive.

   • Default: 12-18 words per sentence
   • Edit for clarity, not just brevity
   • One idea per sentence (usually)

4. Use proof instead of adjectives.

   • Bad: "This framework is incredibly powerful"
   • Good: "This framework helped us ship 40% faster"
   • Replace superlatives with specific results, metrics, examples

5. Never invent facts, credibility, or customer evidence.

   • Back every claim with data, sources, or your direct experience
   • Acknowledge limitations and trade-offs
   • Disclose if you're affiliated with a tool or company

6. Voice is earned through specificity, not tone.

   • Don't announce your personality ("As a scrappy founder...")
   • Let it emerge through word choices, examples, and what you care about
   • Your voice = sum of your choices, not your stated persona

7. Match audience expectations for format and depth.

   • Developers want working code, not theory
   • Founders want strategic insights, not management platitudes
   • Executives want ROI, not complexity
   • Design audiences want research, not trends

---

Content Format Profiles

Blog Post / Essay

Purpose: Share insight, argue a position, tell a story, build audience Ideal Length: 1,200 - 2,500 words Time to Read: 5-8 minutes

Structure:

• Hook (specific observation, contradiction, or anecdote) — 50 words
• Problem (concrete, not abstract) — 200-300 words
• Insight or approach (with examples) — 600-1000 words
• Counter-arguments or complexity — 200-300 words
• Actionable takeaway or next steps — 100-200 words

Opening Formula: "[Concrete observation]. I used to [assumption]. Then [event happened]. Now [new understanding]."

Example: "Most founders optimize for growth rate. I used to obsess over it too. Then we hit a revenue wall. Now I think unit economics matter more than growth."

SEO Focus: Keyword in headline, subheadings, first 100 words CTA: Appropriate to format (download, share, discuss, subscribe)

---

Technical Tutorial / How-To

Purpose: Teach a specific skill; get reader to a working result Ideal Length: 1,500 - 3,000 words Time to Complete: 15-45 minutes (including setup)

Structure:

• What you'll build (screenshot, demo, end state) — 100 words
• Prerequisites (tools, knowledge, setup) — 100-150 words
• Step 1, 2, 3... (each with code, command, screenshot) — 200-300 words each
• Troubleshooting (common failures and solutions) — 200-300 words
• Extension ideas (how to customize or go further) — 150-200 words
• Recap (point forward, don't recapitulate) — 50-100 words

Code Blocks:

• Always show complete, runnable examples
• Include expected output or screenshots
• Highlight what changed and why
• Add comments for non-obvious steps

Tone: Patient, precise, concrete. Assume reader has tried similar things but is new to this approach.

SEO Focus: Long-tail keywords ("how to X with Y"), internal links to prerequisites, external links to tools CTA: "Try it now (5 min setup)", "Use the template", "Build your own version"

---

Newsletter / Email Issue

Purpose: Build habit, deliver value, move reader toward action Ideal Length: 500 - 1,200 words Time to Read: 3-5 minutes

Structure:

• Hook (what you learned, a question, a data point) — 50-100 words, first screen
• One main idea or story (not a list of items) — 400-700 words
• What to do about it (concrete next step) — 100-200 words
• CTA or sign-off — 1-3 sentences

Rules:

• First screen must deliver value on its own
• No diary filler ("This week was crazy...")
• Use section labels only for clarity (not decoration)
• One voice, one perspective, one thread
• Assume reader is skimming; each paragraph should stand alone

Subject Line Formula: "[Hook] + [Specific benefit]" (50 chars max)

• "We shipped 40% faster—here's how"
• "Why unit economics beats growth rate"
• "3 mistakes founders make in year one"

CTA: "Try this", "Get the template", "Read more", one action per issue Metrics: Track open rate, click-through rate, forward rate; adjust based on performance

---

Case Study

Purpose: Prove that your approach works; build trust through specificity Ideal Length: 2,000 - 4,000 words Time to Read: 8-12 minutes

Structure:

• The customer (who they are, what problem they faced) — 200-300 words
• The approach (exactly what you did, decisions, trade-offs) — 800-1,200 words
• The results (metrics, before/after, testimonial) — 300-500 words
• Lessons learned (what worked, what didn't, why it matters) — 300-500 words
• How to replicate (can another team do this? What do they need?) — 200-400 words

Tone: Specific, humble, honest about constraints and trade-offs.

Include:

• Specific metrics (not "improved a lot" but "40% faster")
• Customer testimonial (optional but powerful)
• What didn't work (builds credibility)
• Constraints specific to this customer
• Replicable framework others can apply

CTA: "Book a demo", "See implementation guide", "Try with your team" Distribution: Landing pages, LinkedIn, webinars, sales collateral

---

Research Report / Whitepaper

Purpose: Establish authority; provide data others can cite Ideal Length: 3,000 - 8,000 words Time to Read: 15-25 minutes

Structure:

• Executive summary (headline + key findings) — 150-250 words
• Methodology (sample size, time period, limitations) — 300-500 words
• Findings (organized by theme, with data) — 2,000-4,000 words
• Analysis (what findings mean, why they matter) — 1,000-1,500 words
• Recommendations (what organizations should do) — 300-500 words
• Appendices (raw data, survey questions, sources) — As needed

Tone: Confident but measured. Do not overstate findings. Acknowledge limitations clearly.

Include:

• Clear methodology (builds credibility)
• Primary research when possible (surveys, interviews)
• Acknowledgment of biases and limitations
• Specific, citable data (not general claims)
• Actionable recommendations

CTA: "Download full report", "Access raw data", "Schedule consultation" Distribution: Email signup gate, industry publications, speaking opportunities

---

Voice Handling (Enhanced)

Default Voice: Sharp Operator

If no examples are given, use this voice:

• Concrete, unsentimental, useful
• Short sentences; minimal adjectives
• Examples over abstractions
• What works, not what sounds good
• Assumes reader is intelligent and busy

Example: "We shipped three months faster when we stopped optimizing for perfect code reviews."

Voice Extraction Process

If the user supplies examples, examples, or brand guidance:

1. Identify the voice profile from examples:

   • Sentence length (short/varied/expansive)
   • Adjective density (sparse/moderate/rich)
   • Example usage (abundant/selective/rare)
   • Metaphor preference (technical/natural/business)
   • Opinionation level (strong/balanced/questioning)

2. Document the VOICE PROFILE:

   VOICE PROFILE
   ─────────────
   Sentence Length: [varied, 10-25 words]
   Adjective Density: [sparse, prefers metrics]
   Example Style: [specific anecdotes, one per section]
   Metaphors: [technical/business concepts]
   Opinionation: [strong POV, willing to take stands]
   Credibility Markers: [years of experience, shipped products]
   Signature Patterns: [contrasts, battle-scars, specificity]
   

3. Reuse this profile throughout writing (don't redo voice analysis)

Voice Variations Available

Technical Expert Voice

• Precise terminology; explains unfamiliar concepts
• Deep specificity about implementation
• Acknowledges trade-offs and constraints
• Shows working (code, architecture, metrics)
• Assumes reader has domain knowledge but not this specific knowledge

Founder / Thought Leader Voice

• Personal journey woven through sparingly
• Strong POV; willing to be wrong in public
• Connects ideas to bigger trends or principles
• Credentials earned through specific wins
• Assumes reader respects candor over polish

Storyteller Voice

• Narrative arc: tension → turning point → resolution
• Sensory details where they matter
• Dialogue that reveals character
• Emotions earned through specificity, not told
• Assumes reader wants to understand the human dimension

Educational Voice

• Assumes reader is intelligent but new to topic
• Builds concepts step-by-step
• Uses metaphors and analogies where helpful
• Anticipates confusion and addresses it
• Encourages questions and exploration

---

Audience Profiles

Developer Audience

Values: Working code, time saved, clear explanations Respects: Specificity, trade-offs, honesty about limitations Hates: Hand-waving, untested claims, marketing speak Format Preference: Code-heavy, interactive, testable, with examples in multiple languages Attention Span: Low for theory; high for practical payoff Example CTA: "Try it (5 min setup)", "Use the template", "Fork on GitHub"

Writing Tips:

• Lead with code or working example
• Explain trade-offs and performance implications
• Show both the happy path and failure modes
• Link to open source implementations
• Assume they'll extend or modify your approach

---

Founder / Executive Audience

Values: Strategic insights, founder experience, competitive edge Respects: Battle scars, hard-won lessons, contrarian takes Hates: Consultancy speak, buzzwords, ivory-tower theory Format Preference: Narratives, frameworks, benchmarks, playbooks Attention Span: Low for explanation; high for "this is how you win" Example CTA: "Get the playbook", "See the framework", "Book a strategy call"

Writing Tips:

• Lead with business result or strategic insight
• Share failures and lessons learned
• Provide actionable frameworks or templates
• Benchmark against competitors or alternatives
• Assume they'll customize for their context

---

Product / Design Audience

Values: User insight, precedent, craft, research Respects: Research, concrete examples, user feedback Hates: Trends, dogma, solutions before problem definition Format Preference: Case studies, research, design patterns, design systems Attention Span: Moderate for context; high for "how" Example CTA: "See how we built this", "Download the design system", "Read the case study"

Writing Tips:

• Lead with user insight or design problem
• Show process, not just final output
• Include before/after or user feedback
• Acknowledge constraints and trade-offs
• Provide design files or open-source components

---

Operations / Business Audience

Values: ROI, competitive advantage, team velocity, scaling Respects: Metrics, case studies, frameworks they can reuse Hates: Complexity, jargon, things that don't scale Format Preference: Data, examples, step-by-step playbooks, templates Attention Span: Low for preamble; high for results Example CTA: "Get the template", "Download the checklist", "Start free trial"

Writing Tips:

• Lead with ROI or business metric
• Provide step-by-step implementation guide
• Include templates, checklists, spreadsheets
• Show cost-benefit or time savings
• Assume they need to implement quickly

---

Enterprise / Corporate Audience

Values: Risk reduction, compliance, proven approaches, vendor credibility Respects: Credentials, case studies with recognizable customers, best practices, research Hates: Unproven approaches, lone-wolf thinking, unvetted ideas Format Preference: Whitepapers, research reports, implementation guides, security documentation Attention Span: High for anything with ROI; low for theory Example CTA: "Download implementation guide", "Schedule security review", "Request enterprise plan"

Writing Tips:

• Lead with risk reduction or compliance benefit
• Provide detailed implementation roadmap
• Include security, compliance, and scalability documentation
• Reference recognizable customers or case studies
• Assume they'll need to justify the purchase internally

---

Banned Patterns (Complete List)

Delete and rewrite any of these immediately:

Generic AI Transitions

❌ "In today's rapidly evolving landscape" ❌ "Have you ever wondered why..." ❌ "Let's dive deep into..." ❌ "It goes without saying that..." ❌ "As we all know..." ❌ "The world is changing..."

✅ Replace with: Specific observation or conflict "Most founders optimize for growth. Revenue can hide profitability disasters."

---

Empty Superlatives

❌ "This game-changing, cutting-edge, revolutionary approach" ❌ "Incredibly powerful framework" ❌ "Best practices" ❌ "Industry-leading solution" ❌ "Truly transformative"

✅ Replace with: Proof "This framework helped us ship 40% faster. Here's exactly how."

---

Fake Vulnerability

❌ "As a scrappy founder, I'm not a fancy strategist, but..." ❌ "I'm no expert, but I think..." ❌ "I probably don't know what I'm talking about, but..." ❌ "Full disclosure: I don't have a PhD in economics..."

✅ Replace with: Just the insight "After ten years and three exits, here's what I learned about hiring."

---

Unearned Emotion

❌ "This will absolutely blow your mind" ❌ "I fell in love with this approach" ❌ "It was magical to see this work" ❌ "I'm incredibly passionate about this"

✅ Replace with: Why it matters "This approach reduced our hiring time from 6 weeks to 2. We could staff 3x faster."

---

Closing Questions for Engagement Only

❌ [At the end of a guide] "What's your favorite framework? Let me know in the comments!" ❌ "How do you think about this problem?" ❌ "What would you do differently?"

✅ Replace with: Next step "Try this with one team. Let me know what breaks."

---

Biography Padding

❌ "I'm a seasoned entrepreneur with 20 years in the space. I've worn many hats. I'm passionate about innovation..." ❌ "I've been building products since I was 12..."

✅ Replace with: Relevant credential "After three exits, I learned that unit economics matter more than growth rate."

---

Hedging Language

❌ "I would argue that..." ❌ "Some might say..." ❌ "It could be that..." ❌ "In my opinion..." ❌ "Many believe..."

✅ Replace with: Direct statement "Unit economics matter more than growth rate."

---

Here's Why This Matters (Bridge Too Far)

❌ As a standalone bridge: "Here's why this matters: [general statement]" ❌ "That's the key insight" [followed by obvious restatement]

✅ Better: Show why it matters through concrete consequence "This means your hiring budget could staff the team 3 months earlier."

---

Writing Process (Detailed)

Stage 1: Clarify (Before Writing)

• What's the core insight or outcome?
• Who's the reader? (Developer, founder, operator, designer, executive)
• What action do you want them to take? (Learn, implement, hire you, share, change opinion, invest)
• What will they know / have / believe after reading?
• What's the format? (Blog, email, guide, case study, report)
• What's the success metric? (CTR, shares, conversions, signups)

Stage 2: Build the Outline

• One job per section (not multiple ideas stacked)
• Major sections only (3-5 sections maximum)
• For each section: What's the proof point, example, or anecdote that anchors it?
• Note where you'll include code, data, or screenshots
• Identify any sections that need external sources or research

Outline template:

I. Hook / Problem (proof point: _____)
II. Approach or Insight (proof point: _____)
III. Why This Matters (proof point: _____)
IV. How to Start (proof point: _____)

Stage 3: Research and Gather Proof

• Identify all factual claims that need evidence
• Find sources: data, research, case studies, examples
• Gather code examples, screenshots, or artifacts
• Collect customer testimonials (with permission)
• Document all sources for citing

Stage 4: Write the First Draft

• Write sections with proof points, code, examples first
• Don't edit while writing (just go)
• Use outline as a rail, not a cage (can deviate)
• Aim for 150-200% of final length
• Don't worry about SEO, tone matching, or perfection

Stage 5: Tighten and Voice-Check

• Cut anything that sounds templated or filler
• Replace adjectives with examples or data
• Tighten long sentences (goal: 12-18 words average)
• Read aloud; mark where you stumble or repeat
• Does the voice match your examples? (If tone-deaf, rewrite)
• Check that every claim has backing (sources, data, experience)

Stage 6: Quality Gate

• Is every factual claim backed by evidence or your experience?
• Are all AI clichés gone?
• Does the first paragraph deliver value on its own?
• Can any section be deleted without breaking the argument?
• Is the CTA specific and actionable?
• Does it match the audience's expectations and format requirements?

---

Structure Guidance (Detailed)

Technical Guides

• Open with: What the reader gets (screenshot, demo, end state)
• Each section starts with: Code, command, or concrete output
• Troubleshooting section includes: Common failures, debug steps, solutions
• Extension section shows: How to customize or go further
• End with: Actionable takeaways, not a soft recap
• Links included: Prerequisites, related guides, tools mentioned

Essays / Opinion

• Start with: Tension, contradiction, or a specific observation
• Keep: One argument thread per section
• Make opinions: Answer to evidence, not assertion
• Address: Counter-arguments or complexity (don't strawman)
• End with: Forward-looking insight, not summary

Newsletters

• Keep: First screen doing real work
• Do not: Front-load diary filler or personal news
• Use: Section labels only when they improve scanability
• Maintain: One voice, one perspective, one thread
• Write: As if reader is skimming; each paragraph stands alone
• End with: One specific action or CTA

Case Studies

• Include: Specific metrics (not "improved a lot")
• Show: What didn't work (builds credibility)
• Be: Honest about constraints specific to this customer
• Provide: Replicable framework others can apply
• Get: Permission before using customer data or story

---

SEO and Performance Optimization

Headline Formula

Structure: [Specific result] + [method or perspective] + [context/constraint]

Examples:

• "We Ship 40% Faster With Smaller Pull Request Reviews"
• "Why Unit Economics Matter More Than Growth Rate"
• "Building a $10M SaaS Company Without VC"
• "How We Reduced Hiring Time From 6 Weeks to 2"

Rules:

• Lead with the benefit or insight
• Avoid clickbait ("You Won't Believe...")
• Avoid ALL CAPS or multiple punctuation
• Aim for 8-12 words
• Include primary keyword (naturally)
• Make it specific enough to stand out in feeds

Keyword Optimization

• Primary keyword in: Title, first 100 words, at least one H2
• Variations: Use synonyms and related terms naturally throughout
• Density: Aim for 1-2% keyword density (don't stuff)
• Long-tail keywords: Include common questions ("how to X", "why Y matters")
• LSI keywords: Semantically related terms improve ranking

Readability Optimization

• Reading level: Target 10th-grade reading level (shorter sentences, simpler words)
• White space: Short paragraphs (3-5 sentences max), plenty of breaks
• Bullets: Use only where they add clarity (not for decoration)
• Visuals: Include images, code blocks, or data visualizations every 300 words
• Formatting: Bold key terms, use code blocks for technical content

Link Strategy

• Internal links: 2-5 per post to related content
• External links: 2-5 to high-authority sources
• Anchor text: Descriptive ("how to hire engineers"), not generic ("read more")
• Link timing: Don't frontload all links; distribute throughout
• Link to: Your own content, credible sources, tools/frameworks you reference

Meta Description

• Length: 150-160 characters
• Lead with: Benefit or insight
• Include: Primary keyword
• End with: Call to action or promise ("Learn X", "Get the playbook")

Example: "Learn the exact framework we used to ship 40% faster. Includes templates and common mistakes to avoid."

Social Media Optimization

• Twitter/X: Create thread-version of key points; link to full article
• LinkedIn: Lead with insight relevant to executives; tag people/companies
• Email: Compelling subject line (curiosity + specificity); preview text counts
• Slack: 1-line description + link for sharing in communities

---

Call-to-Action (CTA) Framework

Types of CTAs

Informational CTA (for educational or thought leadership content)

• "Get the research report"
• "Download the full case study"
• "See the data"
• Deliver: Gated or ungated asset; PDF, interactive, or tool

Action CTA (for how-to, tutorial, or implementation content)

• "Try it now (5 min setup)"
• "Use the template"
• "Build your own version"
• "Use our free audit tool"
• Deliver: Working code, template, tool, or free trial

Conversion CTA (for product, service, or hire)

• "Start free trial"
• "Book a demo"
• "Apply to join the program"
• "See pricing"
• Deliver: Clear path to sales / onboarding

Community CTA (for community building or feedback)

• "Join our Slack"
• "Share your approach"
• "Tell me your experience"
• Deliver: Community platform or feedback mechanism

Expansion CTA (for related content)

• "Read the related guide"
• "See the implementation guide"
• "Watch the video"
• Deliver: More content in related topic

CTA Placement

• Primary CTA: End of article (be specific about what happens next)
• Secondary CTA: Mid-article, if relevant (e.g., "You can use our tool here")
• Email: In button text, not just headline ("Try it now" > "Learn more")
• Social: In first reply, not hidden in thread

CTA Best Practices

✅ Be specific about time or effort ("5 min setup", "30 min to implement") ✅ Make the next step obvious (what happens when they click?) ✅ One primary CTA per piece ✅ Align CTA with content goal (educational → resource; tutorial → try it) ✅ Test different CTAs; measure click rates ✅ Make it easy to act (minimal friction)

---

Revision Checklist

Clarity

• Can the reader understand the main point from the headline?
• Does the first paragraph deliver value on its own?
• Is every paragraph one idea?
• Would a smart person new to this topic understand it?
• Are jargon terms defined on first use?

Evidence

• Is every claim backed by data, example, or experience?
• Are the examples specific and vivid (not hypothetical)?
• Are the numbers/metrics credible and current?
• Would a skeptic believe this?
• Are sources cited where relevant?

Voice

• Does this sound like a real person (not generic AI)?
• Would the author actually say this out loud?
• Are superlatives replaced with proof?
• Is the tone consistent throughout?
• Does it match the audience's expectations?

Structure

• Does each section follow the outline?
• Can any section be deleted without breaking the argument?
• Are transitions smooth (not abrupt)?
• Does the ending point forward, not recap?
• Does it match the intended format (blog, tutorial, email, etc.)?

Mechanics

• No typos or grammatical errors
• Sentences average 12-18 words (check one messy paragraph)
• No repeated words or phrases in the same sentence
• Tense consistent throughout
• Formatting (bold, code, links) clean and consistent
• Proper punctuation and paragraph breaks

SEO and Performance

• Headline includes primary keyword and benefit
• First 100 words include primary keyword
• Subheadings are descriptive and scannable
• Content includes visuals every 300 words
• Meta description is compelling and specific
• CTA is specific and relevant
• URL is descriptive and keyword-relevant
• Images have alt text (accessibility + SEO)

Compliance and Ethics

• No false claims or unsubstantiated promises
• Disclosures clear (if you're affiliated, paid, biased)
• Sources cited where relevant
• Permissions secured for quotes, images, data
• Customer data anonymized or permission-based
• Links are not all affiliate or sponsored

---

Quality Scoring Rubric

Score each section 1-5:

Element	1 (Needs Work)	3 (Acceptable)	5 (Excellent)
Clarity	Reader is confused	Reader understands the main point	Reader knows exactly what they'll get and why it matters
Evidence	Claims lack support	Some examples or data	Every claim backed by specific examples or metrics
Voice	Generic AI	Competent but forgettable	Distinctive, memorable, sounds like a real person
Structure	Sections jump around	Clear sections with logical flow	Each section builds on the last; no fat
SEO	No keywords, generic headline	Headline has keyword; some optimization	Headline compelling + keyword optimized; readable
CTA	No call to action	CTA present but vague	Specific, relevant, clear what happens next

Scoring:

• 27-30 = Ready to publish
• 21-26 = Needs one more revision pass
• 15-20 = Needs significant work
• <15 = Start over

---

Common Pitfalls and Solutions

Pitfall	Why It Happens	Solution
Buried lead	Author assumes reader knows the problem	Start with concrete outcome. Cut everything before it.
Too much background	Fear that reader won't understand	Assume reader is intelligent. Explain jargon, not context.
Passive voice	Easier to write during drafting	Search for "is", "was", "been" — rewrite to active voice.
Repeated adjectives	Reach for the same intensifiers	Use data instead. "Really powerful" → "30% faster".
Vague examples	Skip specifics to move faster	Go back and be specific: name, metric, timeline.
Too many ideas	Want to show all you know	Pick one thread. Save the rest for part 2.
No CTA	Assume reader knows what's next	Always include one: "Try this", "Get report", "Book demo".
Formatting chaos	No plan for scannability	Use white space. Short paragraphs. One idea per section.
Weak headline	Prioritize cleverness over clarity	Use formula: [benefit] + [method] + [context].
Unfinished thought	Cut short to meet deadline	Every section needs closure. If unfinished, it's an outline.

---

Research Methodology

For Data-Driven Claims

1. Find the source: Academic research, industry reports, original research, news (cite original)
2. Verify the data: Check methodology, sample size, bias, corroboration, recency
3. Cite properly: Full attribution (author, publication, date, URL), link when possible

For Case Studies or Examples

1. Use your own or get explicit permission
   • Your own company: no permission needed
   • Customer story: explicit permission from the company
   • Another company's public story: cite and link
2. Anonymize if needed: Change names, metrics; preserve the learning
3. Be specific about trade-offs: "This worked for us, but we had [constraint]..."

For Expert Quotes or Interviews

1. Always ask permission — Email, confirm quote, allow revision
2. Credit properly — Full name, title, company, URL to their work
3. Use sparingly — One expert quote max per 1,500 words

---

Distribution and Amplification

Blog Post

• Publish on own site (or Medium, Substack)
• Promote via email list (same day)
• Share on Twitter/X, LinkedIn (multiple times over 2 weeks)
• Ask collaborators/experts to share
• Link from relevant internal pages
• Submit to news/aggregator sites (if relevant)

Newsletter

• Promote via social media (link to archive)
• Tease next issue on social
• Encourage forwards/shares
• Track open rate and click rate; adjust based on performance

Technical Guide

• Publish on own site with full code
• Link from documentation/tutorial pages
• Share on relevant communities (Reddit, Dev.to, HackerNews)
• Create video walkthrough (optional but effective)
• Update every 6-12 months (software changes)

Case Study

• Use on landing pages (social proof)
• Link from relevant service pages
• Share on LinkedIn (with permission)
• Repurpose as webinar or recorded demo
• Update annually (results change)

Research Report

• Gate behind email signup (builds list)
• Promote to publications in the space
• Create summary blog post
• Share key findings on social media
• Offer as resource to sales team

---

Templates by Format

Blog Post Template

[HEADLINE]
[Meta description: 150-160 characters]

[Hook: Specific observation or conflict — 1 paragraph]

[Section 1: Problem or Context — 2-3 paragraphs with example]

[Section 2: The Approach or Insight — 3-4 paragraphs with proof]

[Section 3: Why This Matters or How to Implement — 2-3 paragraphs]

[Counter-arguments or Complexity — 1-2 paragraphs if needed]

[CTA: Specific next step]

Tutorial Template

[HEADLINE]
[What you'll build — screenshot or demo]
[Time estimate]

[Prerequisites]

Step 1: [Concrete outcome]
[Code block or command]
[Expected output or screenshot]
[Explanation]

Step 2: [Concrete outcome]
[Code block or command]
[Explanation]

[Troubleshooting: Common mistakes and fixes]

[Next steps or extensions]

[CTA: Try it now / Use the template]

Newsletter Template

[SUBJECT LINE: Hook + specific benefit, 50 chars]

[Hook: What I learned or observed this week — 1 paragraph]

[One main idea or story — 4-5 paragraphs]

[What to do about it — 1-2 paragraphs]

[CTA: One action]

[Sign-off]

Case Study Template

[HEADLINE: Result + Company name or vertical]

[CUSTOMER: Who, what industry, size, problem faced — 2-3 paragraphs]

[APPROACH: Exactly what we did, timeline, trade-offs — 4-5 paragraphs]

[RESULTS: Metrics, before/after, testimonial — 1-2 paragraphs]

[LESSONS: What worked, what didn't, why it matters — 2-3 paragraphs]

[REPLICATION: Can another team do this? What do they need? — 1-2 paragraphs]

[CTA: Relevant to readers' situation]

---

Quality Gate (Final Checklist)

Before delivering:

• Factual claims are backed by provided sources or your experience
• Generic AI transitions and clichés are gone
• Voice matches the supplied examples or agreed VOICE PROFILE
• Every section adds something new (no fluff or repetition)
• Formatting matches the intended medium (blog, email, PDF, etc.)
• Headline is specific and includes the main benefit
• First paragraph delivers value on its own
• Every claim is backed by data or example
• No empty superlatives (replace with proof)
• Sentences average 12-18 words
• There's a specific CTA at the end
• SEO keywords naturally throughout (not forced)
• The ending points forward, not backward
• No typos or grammatical errors
• Images/code blocks break up long text
• All links are working and relevant
• Disclosures are clear (if affiliated, paid, biased)

---

Final Thoughts

Good writing is proof + clarity + voice.

It's not about sounding smart; it's about making the reader smarter. It's not about being entertaining; it's about being useful. It's not about being first; it's about being right.

Write for someone real. Give them proof. Let them decide.