Sign in

Office-Hours Subscription

Open a standing slot where subscribers bring whatever is stuck this week and leave the call with it unstuck.

Pro moderate Knowledge Offers

What it adds

The builder turns your recurring open-session format and question logs into a low-commitment subscription sold on availability rather than curriculum — a reliable time each week where a subscriber can get a direct answer. It converts because the value is insurance against being blocked, which recurring buyers renew for even in weeks they do not attend. The goal is a monthly subscription with a first session already on the calendar.

What your builder is told to do

8

The actual instructions, in order.
  1. 1

    Inspect the supplied session and question-log files. Extract the recurring day and time, session duration, typical attendance pattern, and the categories of questions actually answered.

  2. 2

    Sell availability: state the recurring slot, its duration, and how many sessions a subscriber gets per month before describing anything else.

  3. 3

    Describe the queue mechanic — how a subscriber submits a question, whether questions are answered in order or by submission time, and what happens when the session runs out of time.

  4. 4

    Publish the scope boundary using the question-log categories: what kinds of questions get answered here and what belongs in a different engagement. Vague scope is the main churn cause for this format.

  5. 5

    Define the asynchronous fallback: whether unanswered questions receive a written reply, whether sessions are recorded, and whether subscribers who cannot attend can submit in advance.

  6. 6

    Handle the value objection directly — 'what if I don't have a question that week' — with the recording, archive, and advance-submission policies from the sources, and price it as a small recurring amount rather than a per-session fee.

  7. 7

    Specify responsive behavior: on mobile show the next session as a countdown card above a stacked policy list with a persistent subscribe button; on tablet render schedule and queue rules side by side; on desktop show a recurring schedule strip with the past-session archive listed beneath it.

  8. 8

    Close with one action — subscribe — and display the first session the subscriber will be able to attend directly beside it.

Edge cases it handles

5

The things an agent skips when you only say "build a office-hours subscription".
  • Session frequency changed over the logs' history: publish the current cadence and note when it changed.
  • Question volume regularly exceeds session time: state the carry-over rule instead of implying every question is answered live.
  • Subscribers in distant time zones cannot attend live: make advance submission and recordings explicit rather than optional-sounding.
  • Some question categories require reviewing private material: state what may be shared in a group setting before purchase.
  • No archive of past sessions exists: remove archive value claims entirely and price on live access alone.

Definition of done

7

Your builder is required to check every one of these before reporting the work finished.
  • The recurring slot, duration, and sessions-per-month are stated in the first screen.
  • The question queue mechanic, including overflow handling, is described explicitly.
  • In-scope and out-of-scope question categories are both listed, drawn from the question logs.
  • Recording, archive, and advance-submission policies are stated or flagged as unresolved.
  • Mobile, tablet, and desktop layouts behave as specified, including the mobile next-session countdown.
  • The first attendable session date is shown adjacent to the subscribe action.
  • The builder reports which session logs and scheduling files it used, and lists unresolved assumptions such as missing archive or carry-over rules.

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.