Sign in

Coach-Led Intensive

Book a compressed one-or-two-day immersion that produces the single decision or asset months of calls keep deferring.

Pro moderate Knowledge Offers

What it adds

The builder shapes your intensive agendas and pre-work materials into a high-touch, short-duration offer defined by one substantial deliverable completed inside the session window. It converts on compression against a premium price: the buyer trades a large fee for finishing something in days that would otherwise drift for a quarter. The goal is a booked intensive date with pre-work assigned at purchase.

What your builder is told to do

8

The actual instructions, in order.
  1. 1

    Inspect the supplied agenda and pre-work files. Identify the deliverable the intensive produces, the pre-work it depends on, and the hour-by-hour session structure.

  2. 2

    Lead with the deliverable and the duration together — one named output, a defined number of days — and make explicit that the output exists by the end of the window.

  3. 3

    Publish the hour-by-hour agenda for each day. At this price point buyers need to see how the time is spent before committing.

  4. 4

    Make pre-work a gating requirement: list what must be submitted, by when, and state that the intensive cannot start without it. Pre-work is what makes compression possible, so treat it as part of the product.

  5. 5

    Describe the follow-through window exactly as the sources define it — any post-intensive check-in, review pass, or support period — and state clearly when the engagement ends.

  6. 6

    Handle premium-price objections with structure rather than reassurance: the alternative timeline for producing the same deliverable, what is included in the day rate, and what would constitute out-of-scope work.

  7. 7

    Specify responsive behavior: on mobile each day renders as a collapsible hour-by-hour block with pre-work requirements pinned above; on tablet show the two days as adjacent columns; on desktop present a full-width day timeline with pre-work deadlines marked before the start point.

  8. 8

    End with one action — book an intensive date — and show the earliest available date and the pre-work lead time required before it.

Edge cases it handles

5

The things an agent skips when you only say "build a coach-led intensive".
  • Pre-work is not returned in time: state the reschedule policy from the sources rather than implying the date holds regardless.
  • The deliverable depends on inputs only the buyer's team holds: list required attendees or data access as booking conditions.
  • Sources describe a single-day and a two-day variant: present them as distinct scopes with different deliverables, not as pricing tiers.
  • Remote and in-person delivery differ in agenda: publish separate agendas rather than one blended schedule.
  • No follow-through period exists: state that the engagement ends at the session close instead of leaving it ambiguous.

Definition of done

7

Your builder is required to check every one of these before reporting the work finished.
  • One named deliverable and the exact duration appear in the first screen.
  • An hour-by-hour agenda is published for every day of the intensive.
  • Pre-work requirements and their submission deadline are stated as booking conditions.
  • The follow-through window and engagement end point are explicitly defined.
  • Mobile, tablet, and desktop agenda layouts match the specification.
  • Out-of-scope work is enumerated alongside what the fee includes.
  • The builder reports which agenda and pre-work files it used, and lists unresolved assumptions such as missing reschedule or follow-through 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.