ByeBuy.ai
BUILD YOUR ESCAPE ROUTE · ✦ CURSOR · HOST IT · ◫ SUPABASE · CONNECT IT · ↯ RELAY · BUILD YOUR ESCAPE ROUTE · ✦ CURSOR · HOST IT · ◫ SUPABASE · CONNECT IT · ↯ RELAY ·
CURRICULUM
← BYEBUY NOTES

September 13, 2026

TWO PATHWAYS: PRODUCT-LED OR COMMUNITY-LED (CHOOSE ONE FIRST)

ByeBuy.ai artwork for Two Pathways: Product-Led or Community-Led (Choose One First)

Distribution taught you how the right people find, try, and return to useful work. Monetization asks the next question: when value is real, how do you turn it into a fair, durable exchange — without breaking what made it valuable?

Before you pick a pricing page or a payment tool, you must pick a pathway. Everything downstream — your offer, your metrics, your weekly cadence — depends on it.

The fork

There are two fundamentally different ways to earn revenue from useful work:

Path 1 — Product / direct path. Build a valuable outcome, distribute it, charge for access or for the completed job. The Research Desk charges for a source-linked research workflow. A local tailor charges for same-week alterations. A classroom charges for a workshop that produces a working project.

Path 2 — Community path. Gather people around a shared purpose, deepen repeated interaction, then monetize *around* that interaction — membership, sponsors, events, affiliates, or qualified leads — without turning members into inventory. A niche investment-research publication charges members for belonging and funds reporting with a relevant sponsor. A local makers' group charges dues and runs paid workshops.

The money arrives from a different place. In Path 1, the buyer pays for what the product *does*. In Path 2, members and partners pay for what the gathering *sustains*.

Hybrids are real — but start single

Many durable businesses end up hybrid: a product with a community around it (Notion templates plus a builder community), or a community whose needs shape a product (a research community that funds a shared data tool).

Here is the rule for Class 80: run one pathway first.

Why? Because the first commitment differs:

| | Product-first | Community-first |

|---|---|---|

| Serves | interaction to adoption and feedback | product decisions to participation |

| Core question | Does this outcome work and will someone pay for it? | Will people return, contribute, and bring others? |

| Weekly work | activation, onboarding, support | rituals, recognition, moderation |

Doing both half-heartedly earns neither. A product with three paying users and a community with six quiet members is not a hybrid. It is two unfinished starts.

ByeBuy Classroom itself is a good example. The free lessons are product value — read, learn, build. A future member community around builders would be a second system with its own rituals and renewal reason. Either could lead, but the team must choose which one it staffs first.

First moves, metrics, and risks

Each pathway has a different bottleneck. Learn to recognize yours.

Product pathway:

  • First moves: carve one wedge outcome (80.3), make one understandable offer (80.4), set one testable price (80.5), collect money cleanly once (80.6).
  • Metrics that matter: activation (did they reach first value?), retention and churn (did they return?), monthly recurring revenue if the value recurs (Class 81).
  • Characteristic risks: nobody activates, the outcome is one-time but you priced it as recurring, support cost eats the margin, you build billing before anyone wants to pay.

Community pathway:

  • First moves: name the shared purpose, start one repeatable ritual (weekly office hours, a critique thread, a local meetup), earn the first ten contributors, then test one revenue stream that funds the purpose (Class 83).
  • Metrics that matter: purpose clarity, ritual attendance, participation and contribution rate, renewal reason — why would someone rejoin next quarter?
  • Characteristic risks: a quiet room you have to bribe people to visit, one sponsor becoming the whole budget, ads or affiliates that make members feel like the product, moderation cost outrunning dues.

Notice the cadences differ. Product work is daily: fix onboarding, answer support, ship the missing step. Community work is weekly and seasonal: hold the rhythm, notice who went quiet, plan the next gathering.

Choose primary, defer explicitly

Your exercise is a forcing function. Pick the pathway that matches what already exists:

  • If you have a working outcome someone used twice — go product-first. Charge for the outcome.
  • If you have ten people who keep showing up to talk shop with each other — go community-first. Charge for belonging and its extensions.
  • If you have neither yet, go product-first by default. A concrete outcome is faster to test than a gathering.

Then write the deferral sentence. It sounds like this:

Three real examples:

  • Research Desk: "We monetize first through a scoped research service for two pilot teams, not a community membership yet, because we do not yet know which outcome professionals will pay to repeat."
  • Local tailoring shop: "We monetize first through fixed-price event packages, not a maintenance subscription yet, because capacity is two fittings a day and we need proof of repeat demand."
  • Niche publication: "We monetize first through a paid member tier funding deeper reporting, not sponsorships yet, because we need a hundred committed readers before any sponsor conversation is honest."

The "because" is the whole point. It names your evidence gap.

DO: pick your lane this week

Exercise — one sentence, one paragraph. Open a note or a PATHWAY-CHOICE.md:

1. Write: "We monetize first through ___, not ___ yet, because ___." 2. Below it, add three lines: your first move, the one metric you will watch for four weeks, and the risk you are watching for.

Finish line: one sentence you can say out loud — "We monetize first through ___, not ___ yet, because ___" — plus a named first move and metric.

Verify: read the sentence to someone outside the project. If they can repeat back which path you chose and what you deferred, it passes. If they ask "so which is it?", rewrite it.

Common failure mode: "We will do both — product sales *and* a community." That is allowed in year two. This month, circle one word: primary. The other pathway goes in a "later" list with a date you will revisit it.

Check your understanding

1. What does a product-first builder optimize weekly, and what does a community-first builder optimize weekly? 2. Why does a hybrid still need a primary pathway at the start? 3. What three things belong in your deferral sentence?

Next

Lesson 80.1 starts where both pathways start: the value exchange itself. A signup is not a sale and a member is not a customer. Before families of models or pricing, you need to name who receives value, what changes for them, and what they might fairly exchange for it.

ARTICLE DISCUSSION

JOIN THE
CONVERSATION.

0 COMMENTS

BYEBUY ACCOUNT ACCESS

Sign in

Use your account to save routes and make the catalogue yours.

Enter your email and we’ll send a secure sign-in link and code.

NEW ROUTES ADDED WEEKLY · 9,235 CATALOGUE ENTRIES · BUILD · DEPLOY · QUERY · STACK · SAY BYE TO BUY · NEW ROUTES ADDED WEEKLY · 9,235 CATALOGUE ENTRIES · BUILD · DEPLOY · QUERY · STACK · SAY BYE TO BUY ·