Membership is member money. This lesson handles outside money: sponsors, advertisers, and affiliates. Done well, a relevant partner funds better work for members. Done carelessly, the room starts to feel rented — and the members who gave it credibility leave first.

From placement to portfolio decision

Part XIV taught the mechanics: sponsored placements (Lesson 72.3), affiliate selection and attribution (Lessons 75.2–75.3). Class 83 turns mechanics into a portfolio decision with four questions: who pays, what do they receive, what do members receive, and where can trust break?

Map every deal on those four lines before discussing price. Illustrative hypothetical: a filing-data tool pays $800 for one monthly teardown slot; it receives a disclosed demo plus Q&A; members receive a genuinely useful workflow plus a discount; trust breaks if the tool is untested, the review is scripted, or the slot multiplies into weekly interruptions. If you cannot fill in the member-receives line with something specific, there is no deal — only a rental.

Learn the vocabulary:

• Sponsor fit: relevance plus tested utility for this room's actual practice.
• Audience inventory: the attention you sell — slots, mentions, placements — kept scarce on purpose.
• Editorial independence: payment never buys conclusions; reviewers can criticize the sponsor.
• Partner disclosure: plain, upfront language about who paid and what they got.
• Affiliate recommendation: a product you would suggest unpaid, with the commission disclosed.
• Conflict of interest: any payment that could bend a recommendation, ranking, or review.

The five-part sponsor filter

Reject or approve every offer against all five. One failure is a decline.

1. Relevance: would members discuss this product unprompted? A citation-checking tool in an analyst room — yes. A generic crypto exchange — no. 2. Actual utility: has someone you trust tested it on real work? Untested products do not get the room's credibility as a launch pad. 3. Transparency: can you disclose payment, terms, and affiliate cut in one plain sentence members understand? 4. Separation: is editorial judgment walled off — sponsor briefed after the review draft, no veto, criticism allowed? 5. No-go list: does it touch a pre-written banned category — untested financial products, data-harvesting tools, anything members cannot evaluate?

Compare outcomes. A niche tool that funds one reported teardown a month — tested by two members, disclosed up top, reviewer free to note flaws — deepens the room: members learn a workflow, dues stay lower, the archive gains a worked example. An untested, unrelated product slipped into every thread with vague "partner" language makes the whole publication feel rented. Members stop citing the room's recommendations anywhere else, which destroys the sponsor's value too. Selling out is not just unethical; it is bad inventory management.

Affiliates get the same filter with one extra rule: recommend as if no commission existed, then disclose the commission. If the recommendation changes when the commission disappears, it was never a recommendation. Keep a public log of every active affiliate relationship — product, commission rate, and date last re-tested — so members can audit your incentives without asking. A log you will not publish is a deal you should not sign.

Exercise: draft COMMUNITY-PARTNER-POLICY.md

Create COMMUNITY-PARTNER-POLICY.md using this template:

# COMMUNITY-PARTNER-POLICY.md — [Community/publication], [date]

## Qualifying criteria (must pass all five)
- Relevance / utility / transparency / separation / no-go: ___

## No-go list (named categories)
- ___

## Inventory cap (scarcity on purpose)
- Max sponsor slots per month: ___ / max affiliate mentions per issue: ___

## Disclosure language (copy-paste exact wording)
- Sponsored segment: "___"
- Affiliate link: "___"

## Editorial boundary
- Who writes/reviews: ___ / sponsor veto? never / flaw-note rule: ___

## Approval owner + decline rule
- Owner: ___ / review cadence: ___ / decline script: "___"

Worked mini-example — niche research memo: one sponsor slot per month, max two affiliate links per issue; disclosure reads "Paid partner — they funded this teardown; conclusions are ours; flaws noted below"; owner is the editor, quarterly review; decline script is "This doesn't pass our tested-utility bar for members, so we're passing." For tier and disclosure patterns worth borrowing, browse Patreon Creator Hub.

Finish line: a one-page partner policy with criteria, caps, exact disclosure wording, an editorial boundary, a named owner, and a decline rule.

Verify quickly: hand the policy plus a real past offer to someone else. If they reach a different decision than you, the criteria are vague — tighten until two readers agree.

Common failure mode: the "just this once" exception for a big check. Exceptions are the policy. Write the decline script before the check arrives, because after it arrives you will not.

Check your understanding

1. What are the four portfolio questions for any sponsor deal? 2. State the five-part filter and explain why one failure means decline. 3. Why does exact disclosure wording belong in the policy rather than improvised per deal?

Next

Outside money is governed. Lesson 83.4 turns inward demand — recurring member questions — into events, workshops, reports, and qualified leads without mining the conversation.