Sign in

Mastermind

Assemble a small selective peer room where members solve each other's problems on a rotating hot seat.

Free moderate Knowledge Offers

What it adds

From your facilitation notes and member criteria the builder produces an application-first offer whose value lives in the room composition rather than the curriculum: who qualifies, how sessions run, and what each member gets from the seat. It converts through selectivity and peer-level matching — the qualification bar is the marketing. The goal is a submitted application, not an instant checkout.

What your builder is told to do

8

The actual instructions, in order.
  1. 1

    Read the supplied criteria and facilitation files first. Extract the qualification bar, group size, meeting rhythm, and the structure of a single session.

  2. 2

    Lead with who the room is for, stated as disqualifying specifics rather than flattering generalities. The page should cause the wrong buyer to self-select out on the first screen.

  3. 3

    Explain the hot seat mechanic step by step — how time is allocated, how a member prepares their case, how feedback is captured, and how often each member sits. This is the product; describe it operationally.

  4. 4

    Define membership terms as the sources state them: commitment length, meeting frequency, attendance expectations, confidentiality norms, and what happens to a seat if someone leaves mid-term.

  5. 5

    Make the application the conversion event. Ask qualifying questions drawn from the criteria file — current stage, the problem they would bring to a hot seat, and capacity to attend — so the form itself signals selectivity.

  6. 6

    Handle the objections a high-commitment peer format raises: whether the room is senior enough, whether the time commitment is survivable, and what happens if the fit is wrong after the first session. Answer only with policies present in the sources.

  7. 7

    Specify responsive behavior: on mobile the criteria and session-structure sections stack with a persistent apply button; on tablet render criteria and session structure as paired columns; on desktop show the meeting rhythm as a recurring-calendar visual beside the qualification panel.

  8. 8

    End with one action — submit an application — and state what happens after submission and in what order.

Edge cases it handles

5

The things an agent skips when you only say "build a mastermind".
  • The criteria file describes an ideal member but no hard bar: convert the description into explicit inclusion and exclusion statements and flag which were inferred.
  • Group size is defined as a range: show the range and describe how hot-seat frequency changes across it.
  • Pricing is stated per term while meetings are monthly: display both the term price and the per-meeting math so the commitment is unambiguous.
  • Sources reference existing members: describe the composition in role and stage terms only, never with names, companies, or attributed results.
  • No exit or refund terms exist: state the commitment length plainly and mark exit terms unresolved.

Definition of done

7

Your builder is required to check every one of these before reporting the work finished.
  • Qualification criteria appear on the first screen and include explicit exclusions.
  • The hot-seat mechanic is described operationally with time allocation and rotation frequency.
  • Commitment length, meeting rhythm, and attendance expectations are stated and sourced.
  • An application form collects qualifying answers drawn from the criteria file.
  • Mobile, tablet, and desktop layouts match the specified behavior at each breakpoint.
  • No member is named, quoted, or characterized by attributed results anywhere on the page.
  • The builder reports which source files defined criteria and session structure, and lists unresolved assumptions such as missing exit terms.

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.