Marcus C. — From one episode to four formats, published the same week.

The situation

Marcus had been running a weekly business podcast for three years. Forty-plus episodes, consistently strong audio production, a loyal listener base that grew slowly through word of mouth. The episodes were good. The distribution was minimal.

Every week, he uploaded the episode to his RSS feed and posted a “new episode is live” update on LinkedIn. That was the workflow. The content lived inside the audio file and rarely reached anyone who hadn't already subscribed.

Marcus knew the content was there. He just didn't have a systematic way to extract it without spending two hours per episode doing individual rewrites for each platform.

The workflow he built

After setting up a Ghostpen Voice DNA™ profile, Marcus built a four-output repurpose workflow triggered by each new episode transcript.

Each week, after the transcript came in, the workflow generated:

• A newsletter issue — framed as his editorial reflection on the episode's central argument, with a subscriber-specific close
• A Twitter thread — leading with the episode's sharpest claim, built as an argument rather than a summary
• A LinkedIn post — hook-first, authority-forward, with a CTA to the full episode
• Show notes — timestamped, with per-section takeaways and a resource list

Each output was reviewed, adjusted if needed, and published in the same week as the episode. The review-and-adjust step took roughly 30–45 minutes total across all four formats. The Voice DNA™ profile handled the register shift between formats — the newsletter sounded intimate, the thread was direct, the LinkedIn post was authoritative.

What changed

The audience for each format was different. Newsletter subscribers rarely found the podcast through Twitter; LinkedIn followers rarely subscribed to the newsletter. The same content was now reaching distinct segments in the format each segment preferred — without Marcus writing four separate pieces per week.

Content Score™ became the quality gate for the Twitter thread specifically, where Hook Strength was the make-or-break dimension. When a generated thread scored below 70, Marcus used the score reasoning to identify the weaker opening and adjusted before posting. That edit loop took 5 minutes, not 45.

The workflow result