Content Atomizer

Content Atomizer for Talosix EDC

Purpose

Take ONE piece of content -- a blog post, white paper, webinar transcript, case study, podcast notes, or any long-form content -- and systematically extract every reusable idea, data point, quote, and insight to produce 20+ distinct content pieces optimized for different platforms and formats. This is the content multiplication engine that turns one week of writing into one month of publishing.

Content Atomization Process

Phase 1: Source Analysis

Before atomizing, deconstruct the source content into its fundamental components.

Extract and catalog:

1. Core thesis -- The single main argument or insight (1 sentence)
2. Supporting arguments -- Each distinct sub-point (typically 3-7)
3. Data points -- Every statistic, metric, benchmark, or quantified claim
4. Quotes -- Any quotable statements (from customers, experts, or the author)
5. Stories/examples -- Narrative elements, case studies, scenarios
6. Frameworks/models -- Any structured thinking tools, matrices, processes
7. Definitions -- Terms explained, concepts clarified
8. Contrarian takes -- Anything that challenges conventional wisdom
9. How-to elements -- Step-by-step instructions, best practices, tips
10. Questions raised -- Open questions or prompts for audience engagement

Create a numbered inventory of all extracted elements. Each content piece produced below should reference which elements it draws from.

Phase 2: Content Production

Produce all outputs below. Each must be self-contained (reader should not need the source to understand it) while being consistent in messaging.

Load the brand-voice skill as background context for all outputs.

Output 1: LinkedIn Posts (5 Variants)

Each post uses a different angle from the source content. Maximum 1,300 characters per post. Use line breaks for readability. Include 3-5 hashtags from the clinical trial hashtag bank.

Post 1: The Data Hook

• Lead with the most compelling statistic or metric from the source
• Contextualize why that number matters to clinical ops professionals
• Close with an insight or question
• Pattern: Stat -> Context -> "Here is why that matters" -> Insight

Post 2: The Contrarian Take

• Challenge a common assumption in the source content
• Present the counter-argument with evidence
• Invite discussion
• Pattern: "Most people think X. But Y." -> Evidence -> "What if Z?"

Post 3: The Practical Tip

• Extract one actionable takeaway from the source
• Present it as a quick win the reader can implement today
• Make it specific to clinical trial operations
• Pattern: "Here is something you can do this week:" -> Tip -> Why it works

Post 4: The Story

• Pull a narrative element, example, or scenario from the source
• Tell it as a mini-story with a beginning, tension, and resolution
• Connect to a broader lesson
• Pattern: "A [role] at a [org type] was dealing with [problem]..." -> Resolution -> Lesson

Post 5: The Question Post

• Distill the source into one thought-provoking question
• Provide brief context (2-3 lines)
• Designed to drive comments and engagement
• Pattern: Question -> Brief context -> "I would love to hear your experience"

Clinical trial hashtag bank: #ClinicalTrials #EDC #DataManagement #DigitalHealth #ClinOps #ClinicalData #eCRF #CDISC #DrugDevelopment #PatientSafety #ClinicalResearch #DataIntegrity #RegulatoryCompliance #SCDM #MedicalResearch

Use 3-5 per post. Rotate to avoid repetition. Place at the end of the post.

Output 2: Twitter/X Threads (5 Variants)

Each thread is 4-8 tweets. Each tweet is 280 characters maximum. Use the numbered thread format (1/n).

Thread 1: The Breakdown

• Take the core thesis and break it into component parts
• Each tweet covers one sub-point
• Final tweet ties it all together with a CTA
• Tweet 1 is the hook: must be compelling enough to make people click "Show this thread"

Thread 2: The Listicle

• Extract 5-7 tips, lessons, or takeaways from the source
• One per tweet, each self-contained
• Number them for easy reference
• Hook tweet: "X things I learned about [topic]:"

Thread 3: The Myth Buster

• Identify 3-5 misconceptions the source addresses
• Format: "Myth: X. Reality: Y."
• Each tweet tackles one myth
• Closing tweet points to the source for details

Thread 4: The Data Thread

• Lead with the most striking metric
• Each subsequent tweet adds a data point that builds the argument
• Visual-friendly (use arrows, numbers, simple formatting)
• Close with the implication

Thread 5: The Mini-Case-Study

• If source contains an example or case study, tell it in thread format
• Tweet 1: The problem
• Tweets 2-3: What was tried / the approach
• Tweet 4-5: The results
• Final tweet: The takeaway and link to full content

Output 3: Email Snippets (3 Variants)

Each snippet is 100-150 words, ready to be dropped into a nurture email or newsletter. Include a subject line and preview text for each.

Snippet 1: The Insight Share

• Subject line: Curiosity-driven, references the core insight
• Body: Share one key finding from the source, explain why it matters, link to full content
• CTA: "Read the full [article/guide/study]"

Snippet 2: The Data Drop

• Subject line: Includes a specific number or metric
• Body: Lead with the data point, provide brief context, tease additional insights in the source
• CTA: "See all the data"

Snippet 3: The Question Tease

• Subject line: Poses a question the source answers
• Body: Frame the question, hint at the answer, create curiosity gap
• CTA: "Here is what we found"

For each snippet, provide:

• Subject line (40-60 characters)
• Preview text (80-100 characters)
• Body copy (100-150 words)
• CTA button text
• CTA link anchor description

Output 4: One-Pager Summary (1)

A single-page executive summary of the source content. Structured for print or PDF.

Layout:

• Hero headline: Captures the core insight in 8-12 words
• Subhead: One sentence expanding the headline
• Key finding callout box: The single most important data point or insight, styled as a pull quote
• 3-4 bullet summary: The main supporting points, each in one sentence
• Supporting data: 2-3 metrics in a visual-friendly format (think: large number + label + context)
• Bottom CTA: Link to full content and a contact/demo CTA

Provide both the text content and layout guidance (what goes where, suggested visual treatment).

Output 5: Slide Talking Points (3 Slides)

Three slides that could be added to a sales deck, webinar, or conference presentation. For each slide, provide:

• Slide title (6-10 words)
• 3-4 bullet points (one line each, no full sentences on slides)
• Speaker notes (2-3 sentences of what to say for each bullet)
• Visual suggestion (chart type, icon, image concept)

Slide 1: The Problem Slide

• Quantifies the challenge the source content addresses
• Uses data to establish urgency

Slide 2: The Insight Slide

• Presents the core finding or approach
• Shows the "aha moment"

Slide 3: The Proof Slide

• Results, metrics, outcomes
• Before/after or comparison format

Output 6: Infographic Outline (1)

A structured outline for a visual infographic. Not the design itself, but everything a designer needs.

Provide:

• Infographic title
• Visual flow (top-to-bottom narrative arc)
• 5-7 sections with:
  • Section header
  • Key data point or statement (one per section)
  • Suggested visual treatment (icon, chart type, comparison, timeline)
• Color/style notes -- Reference Talosix brand palette
• Footer -- Source attribution, Talosix branding, CTA
• Dimensions recommendation -- Long-format for Pinterest/blog embed or square for social

Output 7: Newsletter Section (1)

A 150-200 word section ready to drop into a company newsletter or email digest.

Format:

• Section header (5-8 words)
• Teaser paragraph (2-3 sentences summarizing the most compelling angle)
• Pull quote or callout stat
• Read more link text

Tone: Informative, quick-scan friendly. Assume the reader is scrolling through multiple newsletter items.

Atomization Quality Checks

After producing all outputs, verify:

• Each piece stands alone -- no "as mentioned above" or "in the full article" dependencies
• Core message is consistent across all 20+ pieces
• No two pieces are too similar -- each offers a distinct angle or format
• Platform constraints are respected (character limits, format norms)
• Clinical trial audience context is present in every piece
• Brand voice guidelines are followed (check against brand-voice skill)
• Hashtags and keywords are relevant and rotated
• CTAs vary appropriately across pieces (not all "request a demo")
• Data points cited accurately match the source content
• No compliance-sensitive claims overstated

Content Calendar Integration

After atomization, suggest a 2-4 week publishing schedule:

Timing guidance for clinical trial audience:

• LinkedIn: Tuesday-Thursday, 7-9 AM or 12-1 PM (Eastern US) for North American audience; 8-10 AM CET for European audience
• Twitter: Tuesday-Thursday, 10-11 AM or 1-2 PM Eastern
• Email: Tuesday or Wednesday, 9-10 AM recipient local time
• Avoid: Major conference weeks (DIA, SCOPE, ACRP) unless content is conference-related

Delivery Format

Present all outputs in a single structured document with clear section headers. Number every piece for easy reference. Include an index at the top:

## Content Atom Index
Source: [Title of source content]
Date atomized: [Date]
Total pieces produced: [Count]

1. LinkedIn Post 1: [The Data Hook] -- "[First 10 words...]"
2. LinkedIn Post 2: [The Contrarian Take] -- "[First 10 words...]"
...
[Continue for all pieces]