Sign in

Flagship Course

Package your deepest body of work into the definitive paid path buyers choose when they want the whole system.

Pro involved Knowledge Offers

What it adds

From your accumulated curriculum, recordings, and frameworks the builder assembles a multi-module program with a visible learning architecture — prerequisites, module outcomes, and a clear order of operations. It converts on completeness and authority: the page proves the method is a system rather than a collection of tips, and justifies a premium price against the cost of assembling the same knowledge piecemeal. The goal is a considered, higher-ticket purchase from a warm buyer.

What your builder is told to do

8

The actual instructions, in order.
  1. 1

    Inventory the supplied curriculum files and recordings. Produce a dependency map showing which concepts must precede others, and flag any gap where a promised step has no source material behind it.

  2. 2

    Define the terminal competence: the thing a graduate can do unaided that a non-graduate cannot. Write it as an observable capability drawn from the source outcomes.

  3. 3

    Group the material into 5 to 10 modules. Give each module its own one-line outcome and lesson count so the page reads as a progression, not a playlist.

  4. 4

    Name the method. Use the framework language already present in the sources, and show the framework as a labeled sequence so the buyer can see the system before buying it.

  5. 5

    Build price logic on substitution cost: enumerate what the buyer would otherwise have to assemble, in what order, and how the course collapses that. Present tiers only if the sources support genuinely different deliverables per tier.

  6. 6

    Answer the premium-price objections that this format attracts — 'will I actually finish', 'is this current', and 'can I get this free' — using only what the sources evidence, such as update history, module lengths, and included working files.

  7. 7

    Define responsive behavior: on mobile modules render as collapsed cards expanding to lesson lists; on tablet show a two-column module grid with the framework diagram full width above it; on desktop present a persistent curriculum sidebar that tracks scroll position across the sales page.

  8. 8

    End with one enrollment action and a single clarifying secondary link to a syllabus detail view — nothing else.

Edge cases it handles

5

The things an agent skips when you only say "build a flagship course".
  • Sources cover advanced material but omit fundamentals the promise implies: either narrow the promise or mark a prerequisite module as missing content.
  • Two source frameworks overlap or contradict: choose the more recent file and record the conflict rather than blending them into something neither file supports.
  • Recordings are dated in ways that show in the material: state the recording period factually instead of implying the content is newly produced.
  • The sources support only three substantive modules: reduce the module count rather than splitting thin material to look larger.
  • Tier deliverables cannot be differentiated from the sources: ship a single tier.

Definition of done

7

Your builder is required to check every one of these before reporting the work finished.
  • A terminal competence statement appears near the top and is phrased as an observable capability.
  • Between 5 and 10 modules are shown, each with its own outcome line and lesson count.
  • The named method is rendered as a visible labeled sequence, using framework language found in the sources.
  • Price logic references substitution cost with an itemized list, not an arbitrary comparison figure.
  • Mobile, tablet, and desktop layouts behave as specified, including the desktop curriculum sidebar.
  • No tier, bonus, or module appears on the page without corresponding source material.
  • The builder reports which source files informed the module map and method naming, and lists unresolved assumptions including any content gaps it flagged.

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.