Build an online course

Learning objectives

Design a course around one transformation, not a pile of topics
Script and record lessons that are actually finishable
Know which CF tool runs each step, and the one real gap that is left

Step 1 — The promise and the modules (Spark, then Forge for the full architecture)

explain

A course sells one transformation: 'by the end you can do X.' Spark generates the one-sentence promise and candidate module titles that ladder toward it. If you want the full module-by-module architecture — 5 to 7 modules, each with its own angle and the friction it resolves, plus a production checklist mapped to CF tools and an honesty-gated viability score — hand the same seed to Forge, CF's series-planning engine.

Try this

Use Spark for the one-sentence transformation, then run the same seed through Forge and compare its module architecture to your own.

Step 2 — Lesson scripts (Cut)

explain

Unscripted courses ramble. Cut's Faceless builder turns a lesson topic and outline into a full narration script before it renders anything — the hook, the teach, the recap — short enough to record without a teleprompter wrestling match. You edit for accuracy; the structure is already there.

Try this

Script one lesson with Cut. Time yourself reading it back.

Step 3 — Slides and visuals (Design)

explain

Design's Graphic mode builds slide backgrounds, title cards, and diagrams — clean, on-brand type and shapes, or a photo you upload yourself (no AI photo generation live yet). Clean visuals make a course feel produced. Keep one visual idea per slide.

Try this

Build the title slide and one diagram for your first module in Design.

Step 4 — Record (Cut)

explain

Cut records your camera or screen right in the browser and stitches the clips into one file — no separate recorder needed, though the recording itself stays on your device until you export it. For a lesson you don't want to appear on camera for, Cut's Faceless builder can render the scripted narration over stock footage instead, with burned-in captions — but that path is capped by your plan (30-180 seconds depending on tier), so it fits a short lesson segment, not a full 8-minute one. For a longer on-camera lesson, record and stitch with Cut's plain recorder, which has no such cap.

Try this

Record your first scripted lesson in Cut, on camera or Faceless depending on length. One take is fine — done beats perfect.

Step 5 — Host and deliver (outside CF today)

explain

Honest gap: hosting the course, gating access, and streaming the video to students is an LMS job, and CF doesn't have one yet. This is the single biggest hole for course creators — it's named clearly in the tool-gap register as a tool we intend to build.

Try this

Pick where you'll host for now. Note what you wish it did better.

Step 6 — Launch copy and rollout (Spark + Push + Pilot)

explain

Spark writes the sales-page hook, Push drafts the honest launch post copy in a click, Pilot plans the launch runway across platforms. Alfred keeps the promise from step 1 stitched through the launch so you don't over-claim.

Try this

Draft a sales hook (Spark) + a launch post (Push).

One real gap left

recap

Course design, scripting, recording, and launch copy all run on CF tools today. Hosting and delivering the finished course to students does not — that is the one course-creator gap in the register. CF's rule is: if finishing requires leaving CF, that's a tool we owe you.

Key takeaways

Design around one transformation (Spark); Forge can build the full module architecture from the same seed.
Cut scripts, records, and renders the lesson video — Faceless builds are capped by your plan's duration, plain recording is not.
Hosting/delivery (the LMS job) is the one real gap left today — named in the register.
Spark + Push write the launch; Pilot plans it; Alfred guards the promise.