From the document you have to a course you can stand behind
Coursecast is deliberately simple to use and deliberately careful underneath. Here is exactly what happens when you draft.
You choose one focused source
A policy, a how-to guide, a product release note, one meeting. PDF, DOCX, PPTX (speaker notes included), TXT, Markdown, VTT or SRT, up to 8 MB; PDFs up to 40 pages; or paste 200 to 60,000 characters.
You set the shape
Audience, number of lessons (3 to 8), lesson length and tone. These steer the plan, not the facts.
Claude plans the outline
Your source goes over an encrypted connection to our server and on to Claude, Anthropic's AI model. First it plans the course: title, summary, objectives and lesson sequence.
Each lesson is written in its own step
With the full source and the outline in view, Claude writes each lesson: a narration script, key points, knowledge-check questions with explanations, and review notes. Lessons appear as they're finished.
You review, starting with the notes
Review notes list gaps in your source and claims an expert should check. Every field is editable, and you can ask for a fresh version of any single lesson.
You preview and export
Hear any lesson with your browser's voices, check word count and speaking time, then export to Word, Markdown, narration scripts or JSON, or print to PDF.
What happens to your data
- Your file is discarded when the request finishes; we don't save it.
- The draft is saved only in your browser's local storage.
- Anthropic processes content under commercial terms that don't allow training on API data, and may keep API data for a limited period for safety monitoring.
- We log technical details (time, hashed IP, file type and size, token counts), never your content.
Plan first, then write with everything in view
One giant prompt produces a vague course. Planning first gives every lesson a clear job; writing each lesson separately, with the whole source and outline in view, keeps lessons specific and consistent with each other.
It also means a failed lesson can be retried on its own, and a rewrite touches one lesson, not the course.
Plan
Source + settings → title, objectives, lesson sequence.
Write
Source + outline → script, key points, checks, review notes.
Five tips from the help guide
One focused document
A whole binder makes a vague course. Split by topic.
Text-rich beats slide-only
For decks, speaker notes help a lot.
Clean transcripts
Export .vtt or .srt from Zoom, Teams or Meet. Only use recordings you have rights to.
Leave out personal data
Remove names and anything confidential learners don't need.
Review notes first
They point your expert at exactly what needs checking.
Export before clearing data
Drafts live in your browser until you export them.