- My role
- Product design & implementation
- Integration
- Captivate + AI
- Status
- Independent working prototype
The design problem
Connect the work before publishing.
A solo creator managing several shows moves between audio files, AI conversations and a hosting platform. I designed around one episode: capture the audio, prepare supporting copy, review it and create a host draft. Captivate continues to handle hosting.
Capture
Record or select an audio file.
Prepare
Generate titles, notes and suggestions.
Review
Choose and edit the material yourself.
Create a draft
Explicitly send reviewed material to the selected show.
Inside the workspace
One episode, three useful views.

Put production decisions in one view.
Shows, drafts and scheduled episodes share a view with recording and review actions. I separated deeper analytics from the everyday task of preparing the next episode.
Use the episode as the organising object.

AI prepares. The creator decides.
I placed editable titles and notes beside an explicit Captivate draft action. The creator reviews the suggestions and chooses the destination. An AI assessment is labelled as a model judgement, not an audience result.
Keep the review and the external action together.

Make prepared content findable again.
The Content hub groups saved titles, notes and transcripts by show and episode. I kept generated material attached to its production context so a creator can return without starting another AI conversation.
Show what was saved separately from what was generated.
Name the action and its consequence.
I replaced abstract AI language with task labels such as “AI review” and “Create Captivate draft”. The interface distinguishes a generated suggestion, a saved result and an action that affects another service. Example mode identifies sample material and disables draft creation.
Implementation boundaries
Connected operations require configured services. Local recording does not mean all later processing is offline. If analysis succeeds but saving fails, the review remains visible with a warning. This is a focused workflow prototype, not a public hosting platform or multitrack editor.
Let’s work together
What could be easier to use?
Tell me about the product and the part that needs fixing. A few sentences is enough.
Tell me about it