One source of truth
The output starts from the reviewed episode transcript.
podcast to blog post
Use a saved custom prompt to turn episode material into a structured article draft while keeping claims grounded in the source conversation.
Upload an episode and read a transcript of the first 60 seconds — no account needed.
Upload an audio or video file. Cicadas will preview the first 60 seconds.
Create blog post draft as a custom-prompt asset connected to the episode transcript. It is not one of the default Content Kit cards.
HOW IT WORKS
Upload an MP3, WAV, or M4A recording up to two hours long, or import a compatible episode from an RSS feed. Cicadas starts from the recording, not a disconnected text prompt.
Read the transcript preview first, then use the full workspace after signup to confirm speakers, terms, and episode context.
Create and run a saved custom prompt for blog post draft; Cicadas grounds the draft in the episode transcript.
WHY CICADAS
The output starts from the reviewed episode transcript.
Save instructions for blog post draft, then reuse or duplicate the prompt for later episodes.
Keep the draft alongside notes, timestamps, social posts, and quotes.
WHY IT MATTERS
Saved custom prompts create separate reusable assets grounded in the reviewed transcript; they do not override built-in Content Kit cards.
Before
One-off blog post draft: rebuild the instructions and context every episode.
Cicadas
Cicadas custom asset: reuse saved instructions with the new reviewed transcript.
OUTPUT GUIDE
A transcript is source material, not an article structure. Use a custom prompt to create a deliberate editorial shape.
Choose one useful claim from the episode instead of covering every topic.
Arrange headings so each section advances the argument or practical lesson.
Use episode moments as evidence without inventing facts or external context.
COMPARISON
| Decision point | Cicadas | generic AI generators |
|---|---|---|
| Primary workflow | One recording becomes a transcript-first content kit. | Often require pasted context and separate editing for each blog post draft. |
| Transcript role | The transcript is treated as the source layer for every output. | Often one feature among many outputs. |
| Customization model | Saved show direction guides built-in drafts; custom prompts create separate transcript-backed assets. | Customization varies by product and plan. |
| Pricing model | Plans communicate included minutes per month. | Pricing may use multiple usage dimensions. |
FAQ
Yes, through a saved custom prompt. blog post draft is not a default Content Kit card, but you can create a transcript-backed custom asset and reuse its instructions for later episodes.
Uploading keeps transcription, review, and the content kit in one workflow, which reduces repeated setup and missing context.
Cicadas is built for professional solo podcasters and podcast production agencies. It is not aimed at one-off file conversion or hobbyist transcription searches.
Yes. Saved custom prompts create additional transcript-backed assets; they do not override the fixed Content Kit cards. Saved show direction can guide the kit's tone and preferences.
No. The free plan includes 60 minutes per month for testing the core workflow. Audio enhancement is part of paid plans.
Yes. The Agency plan is built for managing multiple shows with a shared production workflow.
NEXT STEP
Use the teaser first, then create a free account and save a custom prompt for blog post draft.
Create a free account