Sign in

Paid Community

Grow a members-only room where the people in it are the product and the paywall is what keeps it worth reading.

Free moderate Knowledge Offers

What it adds

The builder shapes your channel structure, norms, and member profile into a community offer where the value proposition is peer access, curated composition, and signal quality rather than published content. It converts on who is inside and how conversation is governed — the paywall is framed as a filter, not a fee. The goal is a paid join with the new member posting an introduction in their first session.

What your builder is told to do

8

The actual instructions, in order.
  1. 1

    Read the supplied guidelines and channel-structure files first. Extract the channel map, the posting norms, the moderation model, and the described member profile.

  2. 2

    Lead with composition: who is in the room, described by role, stage, and what they are working on — never by name or attributed result. Peers are the product.

  3. 3

    Publish the channel map with the purpose of each channel, so a prospective member can see where their question would go on day one.

  4. 4

    Make the norms visible before purchase: what is encouraged, what is not allowed, how self-promotion is handled, and who moderates. Stated norms are the conversion argument for a paid room.

  5. 5

    Design the first-week path — introduction prompt, where to ask a first question, and any recurring ritual such as a weekly thread — because early participation determines retention in this format.

  6. 6

    Set price as a filter and say so plainly: a membership fee that removes drive-by participation. State billing terms, whether access ends at cancellation, and any application step from the sources.

  7. 7

    Specify responsive behavior: on mobile the channel map is a stacked list with purposes beneath each name and a fixed join button; on tablet show channels and norms as adjacent columns; on desktop render a sidebar-style channel preview alongside the member-profile panel so the room's shape is apparent at a glance.

  8. 8

    Drive one action — join the community — with the first-week path summarized directly beneath it.

Edge cases it handles

5

The things an agent skips when you only say "build a paid community".
  • The community is small at launch: describe the intended composition and current stage honestly rather than implying an established population.
  • Channels exist in the sources with no defined purpose: either assign one from observed use or omit the channel from the map.
  • Moderation is informal: describe the actual model rather than implying staffed moderation.
  • Some channels are restricted to certain tiers: mark access level on the channel map itself.
  • No member count is verifiable: omit all size claims entirely rather than estimating.

Definition of done

7

Your builder is required to check every one of these before reporting the work finished.
  • Member composition is described by role and stage without naming or quoting any individual.
  • A channel map with per-channel purpose and access level appears before the join action.
  • Posting norms and the moderation model are visible without purchase.
  • A first-week participation path is described concretely.
  • Mobile, tablet, and desktop layouts match the specified behavior, including the desktop channel preview.
  • No member count, growth figure, or member outcome appears unless a source file states it.
  • The builder reports which guideline and channel files it used, and lists unresolved assumptions such as undefined channels or moderation coverage.

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.