Lessons 83.1 through 83.4 built the streams: member dues, outside partners, and paid extensions. This lesson closes the pathway by combining them into a portfolio you can defend — to members, to partners, and to yourself at review time. A portfolio survives one stream stalling. A single stream, however lucrative, is a hostage note.

Five streams, one discovery engine

A balanced community portfolio holds five positions:

1. Member revenue: dues or tiers from Lesson 83.2 — the trust anchor. It should cover core operating cost so no sponsor can dictate the room. 2. Relevant partner revenue: sponsored slots governed by your partner policy from Lesson 83.3 — capped, disclosed, separated. 3. Events and learning: workshops, reports, cohorts from Lesson 83.4 — priced outcomes that deepen the practice. 4. Careful affiliate and lead routes: disclosed recommendations and introductions that serve members first. 5. Free public value that continues discovery: the weekly memo, sample briefs, open threads — the top of the funnel that keeps newcomers arriving and the archive compounding.

The fifth stream earns no money directly and that is the point. Kill free discovery to "convert harder" and the membership pipeline dries up within two quarters. Every portfolio review should confirm the free layer is still generous, still current, and still pointing at the paid layers without pressure.

Name the concentration risks

Teach four concentrations that silently become the whole model:

• One sponsor: a single partner above roughly a third of revenue can veto criticism. Cap per-sponsor share and keep a waiting list, not a dependency.
• One platform: a room living entirely on a rented surface (a social group, a marketplace) can be re-priced or de-ranked overnight. Keep the member list, archive, and payment relationship portable — email plus owned docs, per Lessons 78–79.
• One member: a single high-paying member or client whose exit halves revenue. If one account dominates, that is consulting with an audience, not community revenue — reprice or resign the concentration deliberately.
• One launch: a single cohort, event, or campaign that must succeed for the year to work. Replace launch-or-die with cadence: smaller repeating offers with kill-or-continue dates.

For each concentration, write the early-warning metric: sponsor share of revenue, platform share of arrivals, top-member share of dues, launch share of annual target. Review them quarterly before they review you.

Study how membership programs communicate sustaining support — the ongoing-membership framing on Patreon Creator Hub is a useful reference for keeping member revenue the anchor rather than the afterthought.

Scale only after value, quality, and evidence

The bridge to Part XVI: expand a stream only after three conditions hold — member value improved (renewals, participation, and outcomes rose), delivery quality held (feedback scores and capacity margins intact), and evidence exists (a repeatable run with numbers, not a launch spike). Top-line growth without those three is theater: more members with thinner review, more sponsors with weaker fit, more events with emptier follow-through.

Apply the gate per stream. Dues scale when the renewal reason from MEMBER-JOURNEY.md holds across two cohorts. Sponsors scale from one slot to two only when members rate sponsored segments useful. Workshops scale from quarterly to monthly only when prep hours per run fall without quality dropping. Anything that fails the gate gets fixed, shrunk, or killed — Lesson 83.6 gives hybrids the kill criteria; this lesson gives portfolios the discipline.

Exercise: write the 12-month portfolio

Create COMMUNITY-REVENUE-PORTFOLIO.md:

# COMMUNITY-REVENUE-PORTFOLIO.md — [Community], 12 months from [date]

## Streams (each: target / member benefit / ops owner + hours / risk + cap)
1. Member revenue: ___ / benefit: ___ / ops: ___ / risk: ___
2. Partner revenue: ___ / benefit: ___ / ops: ___ / risk: ___
3. Events/learning: ___ / benefit: ___ / ops: ___ / risk: ___
4. Affiliate/lead routes: ___ / benefit: ___ / ops: ___ / risk: ___
5. Free discovery (cost center, feeds 1–4): ___ / ops: ___ / health metric: ___

## Concentration dashboard (quarterly numbers)
- Top sponsor share: ___ (cap: ___) / top platform share of arrivals: ___
- Top member share: ___ (cap: ___) / biggest launch share of annual target: ___

## Review cadence
- Monthly (30 min): renewals, participation, per-stream margin: owner ___
- Quarterly (2 hr): concentration check + scale gate per stream: ___
- Annual: purpose re-alignment — does revenue still deepen the practice? ___

## Scale gates (per stream: value + quality + evidence required)
- ___

## Stop/shrink rules (written before success tempts you)
- Shrink partner slots if: ___ / pause events if: ___ / cut a stream if: ___

Worked mini-example — analyst room, year one (illustrative hypothetical, not a forecast): $12 dues × 150 members anchor core costs; one $800/month sponsor capped at 25% of revenue; quarterly $49 workshop; two disclosed affiliate tools; free Tuesday memo as discovery. Monthly review tracks renewals and per-stream margin; quarterly review checks sponsor share and runs each scale gate; stop rule shrinks sponsors to zero if member usefulness scores dip twice.

Finish line: a 12-month portfolio with all five streams, a concentration dashboard with caps, a monthly-plus-quarterly cadence, per-stream scale gates, and written stop rules.

Verify quickly: cover the revenue column and read only the member-benefit column. If the benefits do not describe a room worth joining, the portfolio funds operations, not purpose — rewrite it.

Common failure mode: the rented year — sponsor and launch revenue mask flat renewals and falling participation until the renewal cliff arrives all at once. The dashboard exists to surface that cliff while there is still time to act.

Check your understanding

1. Why is free public value a portfolio position even though it earns nothing directly? 2. Name the four concentration risks and one early-warning metric for each. 3. What three conditions must hold before scaling any stream?

Next

The standalone community pathway is complete. Lesson 83.6 — the new hybrid — teaches how to run product and community together without starving either: shared economics, firewall rules, and kill criteria per side.