How to Turn Your Online Course Into a Book

From the inside, your course probably looks like this: seven or eight modules, forty-odd short lessons, a folder of worksheets, a template library, every cohort’s Q&A recordings and a community where the same five questions come up each month. Students who finish it get results.

So the book feels close. Export the transcripts, tidy them, call each module a chapter.

That plan produces a long, repetitive document that keeps telling the reader to “grab the worksheet below”. A course and a book can share one method, but they do different jobs. The main site’s guide to turning an online course or cohort into a book walks through a module-to-chapter map. Here we cover the decisions around that map: the book’s promise, its order, its exercises and what you keep back for paying students.

A course is built for doing; a book is built for reading and deciding

Look at the machinery of a good course: finishable lessons, drip release, a quick win in week one, recaps, deadlines, a community that notices when someone goes quiet. Nearly all of it exists to get a student to the end.

Finishing is hard even so. When MIT’s Justin Reich and José Ruipérez-Valiente analysed every MIT and Harvard course on edX from 2012 to 2018, 3.13 percent of all participants completed in 2017–18, against 46 percent of learners who paid for a verified certificate (Inside Higher Ed). Those were open university courses, not your cohort, and the gap says as much about who chose to pay as about the courses. Content alone rarely carries people to the end.

A book does a different job. Nobody checks whether a reader finished chapter four. The reader is deciding whether your diagnosis is right and whether you are worth enrolling with. Your students have already bought. Your readers have not. So the course follows a practice schedule and the book follows an argument.

Course element	What it becomes in the book	What stays in the course
Welcome and platform tour	Nothing, or a note on how to use the book	All of it
Screen-share or role-play demonstrations	A worked example written out step by step	The live demonstration
Recap videos	Three or four recall questions per chapter	All of it
Worksheets and quizzes	One-page exercises with a filled-in example	Editable and graded versions
Template and script library	The principle plus one sample	The full library
Tool and software tutorials	A sentence naming the type of tool	All of it
Live Q&A and hot seats	Objections answered where they arise	Feedback on students’ own work
Community	A plan the reader can follow alone	All of it
Student wins wall	Two or three permissioned stories with context	The wall

Step 1: Transcribe the lessons, then tag each one by what it does

Get everything into text: lesson transcripts, slide notes, worksheets, and the questions from Q&A calls and community threads. Spoken lessons need the same repairs as any recorded talk (missing transitions, undefined terms, filler). Our guide to turning talks, webinars and sessions into a book covers those repairs and how to sort live Q&A, so we skip them here.

Then build a spreadsheet with one row per lesson, its runtime and one of five tags:

• Idea: explains why or what. A belief, a principle, a diagnosis.
• Demonstration: shows you doing it.
• Practice: makes the student do it.
• Support: Q&A, hot seats, feedback.
• Logistics: setup, platform, deadlines, bonuses.

Ideas become the spine of your chapters, demonstrations become worked examples, practice becomes exercises, support becomes objections, and logistics leave. The tally tells you how much writing lies ahead. Our rule of thumb: if Idea lessons make up less than a third of the runtime, your course is mostly a practice programme, and the book will need a lot of new explanation because the reasoning you show by doing was never said aloud. That is not bad news. It usually means a book cannot replace your course.

When the material runs to dozens of transcripts and documents, guided software can do the first sort. WritebookAI reads PDF, Word and text files and pasted notes; its source analysis shows what your material covers and what is missing, and a verification interview asks you about gaps and conflicts, such as two cohorts’ versions of a lesson that teach different steps. It does not transcribe video or decide what stays in the course, and you approve every chapter. See also writing a book with AI from your documents.

Step 2: Find the one promise the book can keep

A course promises a change over weeks, with support. A book should promise less. Before mapping any module, write:

“After reading this book, [reader] will be able to [result] on their own.”

The last three words carry the weight. If the result needs your feedback or a cohort, it is a course promise, and the book will disappoint. The honest promise usually takes one of three shapes.

The first-stage book

It teaches the first stage of your method completely, where students’ results usually begin: modules two to four of eight, say. The later stages are named and sketched in a closing chapter. For premium cohorts this is our default, because it is complete about something rather than vague about everything.

The whole-method book

It covers every stage at the level of principle and judgement, with less execution detail. It suits creators whose method earns trust and whose course sells implementation. Course creator Jessica Murnane wrote that she “used my course sections as the basic outline of the book’s table of contents” for Know Your Endo, and transcribed course audio for “a big head start on the sample chapters”, then added research studies (Teachable, 2021). Even that book needed material the course lacked.

The problem book

It covers only the diagnosis: why the problem persists and why common fixes fail. We would rarely choose it. Without a method it reads as a trailer. For the case for giving the method away, see using a book to attract clients.

Step 3: Re-sequence for a reader who has no cohort

Course order is built around momentum: setup first, a quick win early, practice spread across weeks, a recap at the start of each module. Book order is built around belief: the reader’s problem in their own words, why it persists, the method stage by stage, hard cases, and limits.

A few moves come up in almost every conversion:

• The quick-win lesson moves. Open with the problem it solves and use the quick win as an early example.
• Setup goes to an appendix, or out. Tool choices date fast and stop the argument cold.
• Recaps become recall questions. Three or four questions the reader answers from memory at the end of each chapter do more than a summary. As RetrievalPractice.org puts it, “a significant amount of learning occurs when students pull information ‘out’” (RetrievalPractice.org).
• Community questions become objections, answered in the chapter where the doubt would arise.

For the overall order, see how to structure a business book and writing a book around your methodology.

Step 4: Rebuild worksheets so they work without you

In a course, someone often reviews the worksheet. In a book, nobody does. Each exercise that survives should fit on one page, show a filled-in example from a clearly hypothetical reader, give self-check criteria (“your answer is strong if it names a specific client, not a market”) and say how long it takes. Offer the editable version as a download on your site.

We would keep one exercise per chapter, two at most. A book with a worksheet every few pages becomes a workbook. Keep the ones that produce something the reader goes on using: a diagnostic, a one-page plan, a decision rule. Anything that needs a partner or your review gets described, not assigned.

Step 5: Add the stories and evidence the videos never needed

On video, your confidence carries claims like “most of my students double their rates” further than they should. On the page, the claim just sits there. Mark every number, result and “research shows” in the transcripts, then source it or restate it as your own observation. The fuller discipline is in how to stop AI inventing facts in your book.

A wins wall is not a set of stories. A story needs a before, a decision, an outcome and a telling detail. Ask permission specifically for the book, as Murnane did when she asked students “to share their words in a future book proposal”. Include one story where the method did not fit; it does more for credibility than a fourth success. Consent wording is covered in client stories and case studies in a book.

If the book exists to sell the course, its student results can start to work like advertising. In the US, the FTC’s Endorsement Guides say that when an ad features someone with above-average results and the advertiser lacks proof they are typical, it “must make clear to the audience what the generally expected results” are (FTC). Whether a particular book counts as an ad is a question for a lawyer. We would write the results passages as if it does.

What stays in the paid course, and how the book points to it

Our decision rule: the method goes in the book, and whatever a reader cannot get from a page stays in the course. A lesson stays behind if:

• it depends on feedback on the student’s own work;
• it will be out of date within about eighteen months (tool tutorials, platform tactics, algorithm advice), because a lesson can be re-recorded in an afternoon and a printed book cannot be patched;
• it is a library whose value is volume, such as sixty scripts or a hundred templates;
• it depends on other people: the cohort, accountability partners, live calls.

The book is the front door, not a replacement. Say in the introduction what the book covers and what the course adds, mention the course once where students most often get stuck, and describe in the final chapter who it is for and not for. The main-site guide lists more ways to point readers to a programme.

Will the book eat your course sales? Our opinion

Some readers will finish the book and never enrol, and we think that is fine: someone who gets the whole result from a book was unlikely to stay in a cohort built on practice and feedback. If your course is mainly information at a premium price, a cheaper book will compete with it, and that is worth knowing about the course. Some creators hold back the key steps instead. We think a book that reads like a trailer does more damage, because it teaches readers that you withhold.

A worked example: an eight-week cohort becomes a first-stage book

Imagine a sales trainer, an invented composite, who runs an eight-week cohort teaching founders of small B2B consultancies to run discovery calls: seven modules, 41 lessons, twelve worksheets, sixty call and email scripts, weekly hot seats.

• Inventory. 14 Idea, 9 Demonstration, 11 Practice, 4 Support and 3 Logistics lessons. Ideas sit just above a third of the runtime, so the book needs new explanation but not a rewrite.
• Promise. “After reading this book, a founder will be able to run a discovery call that ends in a clear yes or no, on their own.” That is modules two to four in depth; proposals and follow-up get one closing chapter.
• Order. The course opened with a quick win on the booking email. The book opens with calls that end in “send me something”.
• Worksheets. Twelve become five exercises, each with a worked example.
• Stays in the course. The script library, live role-play with feedback, hot seats and CRM setup.
• New writing. Why discovery calls stall, which she showed in role-plays but never said; two founder stories used with written permission; one case where the method did not fit, a sale run through a procurement team.

Before you open a single transcript

Write the promise sentence. If you cannot end it with “on their own” without wincing, you are still describing a course, and the book needs a smaller promise or a different shape.

Then tag the lessons in one module. That hour will tell you more than a week of exporting files: how much is explanation, how much is practice, and how much new writing the page will ask of you. More on this stage is collected under turning expertise into books.