Sign in

Mini-Course

Turn one narrow skill into a 60-minute paid win a buyer can finish tonight and use tomorrow morning.

Pro moderate Knowledge Offers

What it adds

The builder reads your source lessons, notes, or recordings and compresses them into a tightly scoped micro-curriculum aimed at a single measurable result, then wraps it in a page that sells speed rather than volume. Conversion comes from shrinking perceived time-to-result: the buyer sees exactly how few steps stand between them and the outcome. The goal is a low-friction first purchase that a cold visitor completes without a call or a demo.

What your builder is told to do

7

The actual instructions, in order.
  1. 1

    Inspect the supplied lesson notes, transcripts, and outlines. Tag every section as load-bearing (required for the result) or optional, and list the load-bearing ones in order of dependency.

  2. 2

    Write the outcome line as a finished state, not a topic: what the buyer will have built, fixed, or decided when the last lesson ends. Pull the specifics from the source files only.

  3. 3

    Sequence 3 to 5 lessons where each lesson ends in a completed micro-artifact. Show the runtime of each lesson beside its title so total time is visible above the fold.

  4. 4

    Build a short value stack: the lessons, the artifact template each lesson produces, and any checklist present in the sources. Price it as an impulse decision and state plainly what is deliberately excluded so the scope reads honest rather than thin.

  5. 5

    Handle the two objections this format always draws — 'too short to be worth it' and 'I already know this' — by contrasting completion rate against shelf-ware, and by naming the exact starting point the course assumes.

  6. 6

    Specify responsive behavior: on mobile the lesson list stacks with runtime badges and a sticky buy bar; on tablet the outcome statement and lesson list sit side by side in two columns; on desktop show the full curriculum without an accordion so total scope is scannable in one view.

  7. 7

    Close with one action — an enroll button repeated after the curriculum and after the objection block, with no competing links, no newsletter capture, and no secondary tier.

Edge cases it handles

5

The things an agent skips when you only say "build a mini-course".
  • Source material clearly exceeds one hour of instruction: split it and build only the first outcome, noting the remainder as out of scope rather than padding the runtime.
  • Sources contain no artifact or worksheet: generate the artifact structure from the steps described, and mark it as an inferred asset needing review.
  • The outcome depends on a paid third-party tool the sources assume: surface that requirement above the price, not in the FAQ.
  • Runtimes are absent from the sources: estimate from transcript length and label the estimates as approximate rather than presenting them as exact.
  • Multiple candidate outcomes appear in the sources: choose the one with the shortest dependency chain and list the others as separate future mini-courses.

Definition of done

7

Your builder is required to check every one of these before reporting the work finished.
  • A single finished-state outcome appears above the fold and is traceable to a specific source file.
  • Between 3 and 5 lessons are listed, each with a visible runtime and a named micro-artifact.
  • Total time-to-result is stated numerically in the first screen of content.
  • Excluded scope is stated explicitly somewhere on the page.
  • Mobile, tablet, and desktop layouts each match the behavior described in the responsive step.
  • Exactly one conversion action exists on the page, with no competing calls to action.
  • The builder reports which source files it used for the outcome and lesson sequence, and lists every assumption it could not resolve from those files.

Related offer files

How it works

  1. 1

    Copy the link

    Grab the Markdown blueprint URL for this offer type.

  2. 2

    Give it to your builder

    Paste it into Claude Code, Cursor, Codex, or whatever AI builder is already working in your app.

  3. 3

    It maps, then builds

    Your agent reads the blueprint first, then builds the offer into your app around the product, audience, and stack.

Works with your stack

These blueprints are written to adapt. They tell the agent to detect your framework, match your existing design system, and use your source files instead of guessing the offer.

Need it tighter than that? Customize the offer file and tell it exactly which source docs and stack to use.