Distribution is the path to the right people; monetization is the fair exchange for a proven outcome. Neither is a page added after the build. Parts XIV and XV taught them as systems; this lesson designs your first route and first exchange together, before code hardens around their absence.

One of each, designed together

The first go-to-market plan needs exactly four commitments:

• One channel — the single credible route from Lesson 67: search, one newsletter, one community, one map listing, one partner. Not seven.
• One promise — the audience-facing outcome in their words: "a brief you can forward," "a slot confirmed tonight."
• One action — the useful first conversion: run your question through the template, book the fitting, complete the first check.
• One revenue hypothesis — the fair exchange to test: seat, report, slot fee, workshop — with a number and a moment.

Channel without promise is noise. Promise without action is admiration. Action without exchange is a hobby. Exchange without a proven outcome is a paywall around generic information (Lesson 80.1). Design all four now so the system map (90.2), release (90.6), and evidence loop (90.7) include them.

The message chain orders the work:

audience problem → useful outcome → proof/experience
→ next action → follow-up → value exchange

Each link earns the next. The problem earns attention; the outcome earns interest; proof earns belief; the action earns a trial; follow-up earns return; the exchange earns sustainability. Skip proof and the action feels risky. Skip follow-up and one-time trials never become revenue worth keeping.

Four examples, four different first moves

The running examples diverge on purpose — copy the shape, not the channel:

• ByeBuy Classroom: audience — self-taught builders searching for answers. Route — search to one generous free lesson. Proof — the lesson itself, completed. Action — finish the first check. Exchange — a paid workshop producing a finished artifact, tested after readers return.
• Research Desk (Sonariq): audience — solo analysts drowning in unverified summaries. Route — one niche newsletter placement. Proof — a source-linked sample brief they can inspect. Action — run their own question through the template. Exchange — per-seat pilot with manual invoicing, cancel anytime.
• Local service launcher: audience — neighbors needing same-week work. Route — map listing plus one useful local video. Proof — reviews and a visible before/after. Action — book a fitting slot. Exchange — fixed slot fee at drop-off with a stated refund rule.
• Creator-led niche media: audience — 500 working practitioners. Route — one community or email placement. Proof — one original, verifiable piece. Action — subscribe to the free brief. Exchange — quarterly paid report with disclosed methods, tested after open rates hold.

Same chain, different links. The classroom leads with searchable usefulness; the desk leads with inspectable evidence; the launcher leads with proximity and trust; the publication leads with originality. Your project must make the same kind of specific choice — and defer the other three routes by name.

Exercise: create GO-TO-MARKET.md

Create FINAL-PROJECT/GO-TO-MARKET.md:

# GO-TO-MARKET — [Project], [date]

## Audience (one, named + reachable)
- Who + where they already gather: …

## Discovery route (one channel)
- Channel + why credible here: …
- Deferred routes (3, each with reason): …

## Promise (in their words)
- …

## Proof (useful before asked to pay)
- [sample / template run / video / review — inspectable]

## Conversion (one action)
- [verb + path + what happens next]

## Follow-up (how trials become returns)
- [message / cadence / trigger]

## Payment/offer test (one hypothesis)
- [offer + price + moment + refund/cancel rule]

## Trust boundary (what you will not do)
- [no-go: e.g., no paywalled generic content, no bought lists, no dark patterns]

Finish line: a route from useful work to a real person and a clear learning signal — one audience, one route, one proof, one action, one payment test, one boundary.

Verify: walk the chain forward with a stranger. State their problem; show the proof; ask them to take the action. If they hesitate, the weak link is the diagnosis — usually proof ("why should I believe it?") or action ("what exactly do I do?"). Fix that link before adding channels.

Common failure mode: the seven-channel launch — posting everywhere, learning nowhere. Its mirror is the paywall-first plan: charging before proof exists. Proof precedes payment; one route precedes scale. Lesson 90.7's hypotheses will tell you when the second route is earned.

Pricing the first exchange honestly

The first price is a learning instrument, not a valuation. Pick a number tied to the alternative it replaces: three analyst hours, one missed booking fee, one week of manual research. State payment moment and exit clearly — manual invoice with cancel anytime beats automated billing with a dark-pattern trail for a pilot. Test willingness with a small cohort before wiring full payments infrastructure, per Lesson 90.4. If five pilots pay the manual invoice and two renew, the exchange is real enough to automate. If they praise the proof but dodge the invoice, the outcome or buyer is wrong, and no checkout flow will fix it.

Check your understanding

1. Why must proof come before the payment test in the message chain? 2. How do the four examples' first routes differ — and what would copying the wrong one cost? 3. What belongs in a trust boundary, and why does it constrain monetization choices?

Next

Someone can find you and pay you fairly. Lesson 90.9 keeps that promise after launch — the smallest operating system worth keeping.