Sign in

Bootcamp

Compress months of scattered self-teaching into an intensive stretch that ends with portfolio-grade work in hand.

Pro involved Knowledge Offers

What it adds

The builder assembles your curriculum, projects, and assessment material into a high-intensity, multi-week program organized around graded projects and a demanding weekly load. It converts on compression and evidence: buyers accept the intensity because the timeline is short and the output is demonstrable work they can show. The goal is an application or enrollment for a specific start date at a premium price point.

What your builder is told to do

8

The actual instructions, in order.
  1. 1

    Inspect the supplied curriculum and project-brief files. Extract weekly hour expectations, the project sequence, and how each project is evaluated.

  2. 2

    State the time commitment before anything else — hours per week and total weeks — because under-disclosed intensity is the primary cause of drop-out and refund pressure in this format.

  3. 3

    Structure the page around projects, not lessons: each project gets its brief, the skills it exercises, and the evaluation criteria from the rubric.

  4. 4

    Show the weekly load pattern across the whole program so buyers can see where the heaviest weeks fall and plan around them.

  5. 5

    Define the support model: instructor contact hours, review turnaround on submitted projects, peer collaboration expectations, and what happens if someone falls behind.

  6. 6

    Justify the price against compression — the alternative timeline of self-directed learning and the graded feedback loop that self-study cannot provide — using only what the sources support, with no employment or income claims of any kind.

  7. 7

    Specify responsive behavior: on mobile the project sequence is a vertical stepper with the weekly-load chart scrollable horizontally; on tablet show projects in a two-column grid with the load chart full width; on desktop present a program timeline with projects and load overlaid on one continuous axis.

  8. 8

    Close with one action — apply or enroll for the named start date — and state the prerequisite check that happens before acceptance.

Edge cases it handles

5

The things an agent skips when you only say "build a bootcamp".
  • Prerequisites are implied but not stated in the curriculum: convert them into an explicit prerequisite list and flag which were inferred.
  • Project rubrics are missing for later projects: describe those projects without evaluation claims and mark the gap.
  • Weekly hours vary widely between weeks: show the range and the peak rather than an average that hides the hardest week.
  • Sources reference career outcomes: remove all employment, hiring, and income framing regardless of what the sources assert.
  • The program can be taken part time: present it as a separate track with its own week count rather than softening the intensive claim.

Definition of done

7

Your builder is required to check every one of these before reporting the work finished.
  • Hours per week and total program length appear in the first screen of content.
  • Every project shows its brief, skills exercised, and evaluation criteria from the rubric.
  • A weekly-load view makes peak weeks visible across the full program.
  • Support model, review turnaround, and falling-behind policy are stated or flagged unresolved.
  • Mobile, tablet, and desktop layouts match the specified behavior for the project sequence and load view.
  • No employment, hiring, salary, or income claim appears anywhere on the page.
  • The builder reports which curriculum and rubric files it used, and lists unresolved assumptions including inferred prerequisites.

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.