Bmj Patreon Strategy Response

Source: bmj-patreon-strategy-response.md (ingested 2026-03-28)

Full Strategic Response to the Three Questions I've just re-examined every page of the live site — About, Pricing, Resources, Downloads, Handbooks, Blog, Video, Academy, and Signup — to make sure my recommendations are grounded in what actually exists right now, not assumptions. Here's my answer to each of the three questions, followed by a decision framework.

A. Patreon — What It Should Be and How It Differs Right now, Patreon sits in the footer alongside PayPal, CashApp, and Venmo — all styled the same, all pointing to # (placeholder links). That's a problem because it positions Patreon as just another payment method, when it should function as something structurally different from the site itself.

Here's the distinction I'd recommend:

The site (Free / Basic / Premium) is the publication. It's where people read, learn, and access the archive. The membership tiers gate content. That's the core product — the journal, the briefings, the academy, the handbooks.

Patreon should be the patronage layer — not a content destination, but a support channel for people who believe in the mission and want to fund it beyond what a subscription covers. Think of it as the difference between a subscriber and a donor. A subscriber pays for access. A patron pays because they want the work to exist.

What Patreon could offer that the site doesn't: behind-the-scenes editorial notes (why a piece was written, what was cut, what's coming next), early drafts or working documents, a monthly "Chairman's Letter" that doesn't appear on the main site, naming recognition on a supporters page, and possibly quarterly voice memos or short audio reflections — content that's more intimate and personal than what goes on the public platform.

This keeps Patreon from cannibalizing Premium. Premium gets you everything the publication produces. Patreon gets you proximity to the person producing it. Those are different value propositions and they attract different motivations. The footer should reflect this — Patreon shouldn't sit next to CashApp like a tip jar. It should either have its own callout (a small "Support the Work" section) or be separated from the one-time payment links entirely.

B. Ancestors & Architects — What to Keep, What to Change I read the full section on the About page. Right now it features Dr. Amos N. Wilson and Rev. Jesse L. Jackson Sr. under "In Memoriam" headings, with biographical descriptions and dates. The section heading reads "Ancestors & Architects" with the subheading "We Honor Those Who Built the Road."

Your friend's instinct is sound on every count. Here's my breakdown:

The legal concern is real but manageable. Using a deceased public figure's name and likeness in an editorial or educational context — honoring their intellectual legacy, not selling a product with their face on it — is generally protected under the First Amendment and fair use doctrine. You're not endorsing a product with their image. You're acknowledging intellectual debt. That said, the risk increases if the section ever expands to include living figures, if imagery is used, or if it appears in any commercial or merchandising context. The safest position is to keep the language clearly editorial and reverential, not promotional.

The conceptual concern is the stronger one. Your friend is right that some of these figures may never have known the brand exists. The word "Ancestors" implies a direct lineage — a chain of intentional transmission — and that's a claim the brand can't fully substantiate. It also carries spiritual and cultural weight in Black tradition that deserves careful handling. Using it loosely could feel appropriative of a sacred concept, even within the community.

My recommendation: rename the section "Intellectual Lineage & Architects." This preserves the ancestral reverence your friend values — "lineage" honors the chain of thought and tradition without claiming personal relationship or consent — while "Architects" becomes the active, living category for contributing writers, consultants, and educators who directly build the academy and platform. The "In Memoriam" framing already on the page is elegant and respectful. Keep that. But shift the framing from "these are our ancestors" to "these thinkers built the road we walk on." That's a claim of gratitude, not ownership.

If your friend later brings on contributing writers or academy educators, "Architects" becomes the natural home for those bios. The section then has two halves: those who came before (Lineage) and those who build alongside (Architects). That's clean, defensible, and scalable.

C. Navigation — Whether the Restructuring Is the Right Call I audited every page your friend wants to reorganize. Here's what currently exists:

Current nav (10 items): Home, About, Academy, Handbooks, Downloads, Resources, Video, Blog, Pricing, Contact

Proposed nav (8 items): Home, About, Academy, Downloads, Content, Contact, Log In, Join

Let me evaluate each proposed change against what I found on the live site:

Moving Handbooks under Downloads — yes, absolutely. The Downloads page right now shows "No downloads available yet" with filter tabs for Templates, Worksheets, Guides, and Toolkits. Handbooks currently has one item ("Letters to a Young King"). These are the same content type — downloadable documents. Handbooks should become a filter category under Downloads alongside the existing ones, or simply appear as items in the Downloads feed. This eliminates a near-empty standalone page and gives Downloads real content.

Merging Pricing into Join — yes, with a structural change. The current Pricing page already shows Basic ($9/mo) and Premium ($19/mo) tiers with feature lists. The current Join/Signup page is just a bare account creation form (name, email, password) with no tier selection. Your friend is right that these should merge. The flow should be: click "Join" → see the three tiers (Free, Basic, Premium) with feature comparisons → select a tier → create account. That's one decision point, not two separate pages. This is a significant UX improvement. The current setup forces users to visit Pricing to understand value, then navigate separately to Signup to act on it. That's unnecessary friction.

Adding a Free tier — yes, and it's already implied. The Pricing page already describes what free members get ("public articles, briefing previews, the video gallery, and the academy"). Making "Free" an explicit, visible tier on the Join page validates the no-cost entry point and reduces signup hesitation. Three-tier pricing (Free / Basic / Premium) is industry standard for a reason — it anchors the middle option as the default choice.

Moving Video and Blog under a renamed "Content" section — yes, with one naming caveat. The Resources page already functions as a content hub — it lists Weekend Briefings, Articles, Dispatches, Academy, and Video as "Content Sections." Blog (/blog) is actually titled "Dispatches" on the site itself, and Video (/video) has minimal content (one item). Rolling both under a parent section makes sense because neither justifies a top-level nav position at this stage. However, I'd recommend keeping the name "Resources" rather than renaming it "Content." Here's why: "Content" is generic and says nothing about value. Every website has "content." "Resources" implies utility — things you can use, reference, return to. It positions the material as tools, not just things to consume. That aligns better with the platform's mission of building discipline and knowledge. If the word "Resources" feels too corporate, an alternative like "Library" or "Archive" would also work and feel more on-brand for a publication.

The proposed order — mostly good, one adjustment. Home, About, Academy, Downloads, Resources (or Content), Contact, Log In, Join. This reads logically: identity first (Home, About), then value (Academy, Downloads, Resources), then action (Contact, Log In, Join). I'd suggest one change: move Contact to the footer only and keep the top nav even leaner. Contact pages on media platforms get very low traffic — it's a utility page, not a destination. That would give you seven items total: Home, About, Academy, Downloads, Resources, Log In, Join. That's clean, decisive, and leaves room to grow without ever feeling cluttered again.

Decision Summary Decision 1 — Section naming: Rename to "Intellectual Lineage & Architects." Keep the In Memoriam framing for deceased figures. Reserve "Architects" for living contributors as the team grows.

Decision 3 — Membership tiers: Confirm three tiers on a unified Join page: Free | Basic ($9/mo) | Premium ($19/mo). Merge current Pricing content into the Join flow.

Decision 4 — Content architecture: Handbooks becomes a category within Downloads. Blog (Dispatches) and Video become sections within Resources. Both lose their top-level nav positions.

Decision 5 — Lenses: Update from 3 to 5. This affects the About page framework section, the homepage "Three Lenses" section, the Resources "Browse by Lens" filter, and all article categorization. This is the deepest structural change and should be scoped separately once the two new lenses are defined.

Decision 6 — Patreon: Reposition as a patronage/support channel distinct from site membership. Separate it visually from payment method links in the footer. Give it its own context — "Support the Work" or similar — that communicates what it's for.

What I'd Say Back to Your Friend If I were drafting a reply, the core message would be: every instinct here is correct. The menu is too long, the pricing and join flow should be unified, Handbooks belongs under Downloads, and the Ancestors framing carries risk that "Intellectual Lineage" resolves cleanly. The only place I'd push back is on renaming Resources to "Content" — Resources is the stronger word for this brand. And I'd suggest dropping Contact from the top nav entirely to keep the header as sharp as possible.

The 3-to-5 lens expansion is the biggest structural question still open, because it cascades across almost every page. That deserves its own focused conversation once the navigation and section changes are locked in.