Sign in

Coaching Package

Sell a defined engagement with a fixed number of sessions, a named milestone, and an end date you both agree on.

Pro involved Knowledge Offers

What it adds

Using your intake questions, session frameworks, and engagement notes, the builder produces a scoped one-to-one offer: session count, cadence, what happens between sessions, and the milestone the engagement is built to reach. It converts by replacing open-ended coaching ambiguity with a bounded plan a buyer can evaluate. The goal is a booked fit call or a direct purchase of a specific package tier.

What your builder is told to do

8

The actual instructions, in order.
  1. 1

    Inspect the supplied intake and session-framework files. Extract the typical engagement arc, the number of sessions it takes, and what happens between sessions.

  2. 2

    Name the milestone the package is designed to reach and the horizon it typically takes, phrased as a state the client arrives at rather than a feeling.

  3. 3

    Lay out the engagement map session by session: what the first session establishes, what the middle sessions work through, and what the final session closes. Use the phases in the sources rather than generic numbering.

  4. 4

    Specify the delivery contract: session length, cadence, scheduling method, between-session access channel and its response expectation, and how unused or rescheduled sessions are handled.

  5. 5

    Build the price around the milestone and the access, and if multiple tiers exist, differentiate them by session count and between-session access rather than by vague depth labels.

  6. 6

    Address the objections one-to-one work raises: fit, whether the client's situation is too unusual, and what happens if the milestone is reached early or clearly will not be. Answer with the engagement policies in the sources only.

  7. 7

    Specify responsive behavior: on mobile the engagement map is a vertical stepper with the current-phase card expanded; on tablet render a two-column phase grid with the delivery contract beneath; on desktop show a horizontal engagement timeline with the milestone marked at its end point.

  8. 8

    Close with a single action — book a fit conversation or purchase a named tier — and state exactly what that next step involves and how long it takes.

Edge cases it handles

5

The things an agent skips when you only say "build a coaching package".
  • The sources describe an open-ended retainer rather than a package: propose a bounded structure and flag the conversion from retainer to package as an assumption.
  • Between-session access is described without a response window: state the channel only and mark the response expectation unresolved.
  • Tiers differ only in price in the source material: collapse to a single tier rather than manufacturing differentiation.
  • Intake requires artifacts from the client: list them before the booking action so the first session is not wasted.
  • The engagement arc varies widely by client type: present the phase structure as fixed and the phase contents as adapted, and say so plainly.

Definition of done

7

Your builder is required to check every one of these before reporting the work finished.
  • A named milestone and typical horizon appear above the fold.
  • Session count, session length, and cadence are each stated explicitly.
  • The engagement map shows distinct opening, working, and closing phases drawn from the sources.
  • Between-session access channels and rescheduling terms are stated or flagged as unresolved.
  • Mobile, tablet, and desktop layouts render the engagement map as specified.
  • No outcome, result, or client story is asserted beyond what the source files support.
  • The builder reports which source files defined the engagement arc and delivery terms, and lists every unresolved assumption.

Related offer files

Knowledge Offers

Workbook System

Guide buyers through structured exercises that end with a personalized document they could not have downloaded.

Build This Offer: Workbook System

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.