Class 85 gave you a content pipeline that publishes reliably: research becomes a brief, a draft, a reviewed piece, a reusable library. Now a new question arrives. People read, click, reply, buy, or vanish — and each of those moments means something. Marketing operations is the system that catches those meanings and follows up usefully, instead of letting them evaporate.

The vocabulary, in plain language

• Lead: a person who has shown interest and given you a way to continue — a download with an email, a booking inquiry, a reply. Attention without contact is audience; contact with context is a lead.
• Signal: any observable action that hints at need or readiness — opened the pricing page twice, finished the checklist, asked about team seats, went quiet after the trial started.
• Segment: a group that deserves a different next step (Lesson 86.2 covers this fully).
• Campaign: a bounded effort with one objective, one audience, one promise, and a clock (Lesson 86.3).
• Lifecycle stage: where the person stands in a longer relationship — stranger, subscriber, trial user, customer, repeat buyer, advocate. Stages tell you which follow-up is appropriate.
• Conversion event: the specific action you count — signup, booking, purchase, renewal. One campaign, one primary conversion; everything else is context.
• Attribution: your honest answer to "what gets credit for this conversion?" Clicks, emails, and conversations often assist; rarely does one touchpoint deserve all the credit.
• Follow-up: the useful next thing you send or do because a signal earned it — not a scheduled blast, but a response.

The mental model: tools are plumbing; signals are water. A new email platform, ad account, or CRM changes the pipes. The job stays the same — notice what the person did, record it where the next helper can find it, and respond with something genuinely useful.

The journey: source to record

Every lead journey follows the same six stations. Memorize them:

source → offer → consented contact → useful next action → signal → record

1. Source. Where the person came from — a lesson page, a partner link, a search result, a talk. Source matters because it carries intent: someone arriving from "deployment checklist" needs something different from someone arriving from "what is a model?"

2. Offer. The specific value exchanged for contact — the checklist download, the office-hours invite, the trial, the quote. Vague offers ("join our newsletter for updates") produce vague leads. Concrete offers produce readable signals.

3. Consented contact. Permission with scope, as Class 78 taught: what arrives, how often, how to leave. No consent, no follow-up — that is not a lead, that is a stranger you are about to annoy.

4. Useful next action. The one thing you invite them to do next — run the checklist, book the walkthrough, reply with their stack. If you cannot name the next action, you do not have a journey; you have a pile of addresses.

5. Signal. What they actually did — or did not do. Opened, clicked, completed, booked, bought, stalled, unsubscribed. Signals are facts, not grades.

6. Record. Where the fact lives so the next message, human, or automation can use it — the CRM row, the lifecycle stage, the note. A signal nobody records is a signal you will pay to re-learn.

Walk it with ByeBuy. Source: a reader finds the Models lesson on context windows. Offer: "the context-budget worksheet." Consented contact: email, promised "one worksheet plus two follow-up build notes, unsubscribe anytime." Next action: "run the worksheet on your project and reply with your result." Signals: downloaded, opened follow-up 1, replied — or downloaded and went silent. Record: subscriber → engaged builder, note attached. The reply gets a human answer; the silence gets one useful nudge, then suppression (Lesson 86.2).

The local service version is identical in miniature: inquiry (source: Google profile) → free quote (offer) → phone number with "one quote plus one reminder" (consent) → "confirm Thursday slot" (next action) → confirmed, rescheduled, or silent (signal) → calendar + note (record).

Why "signals, not tools" changes decisions

Teams that think in tools ask "which platform sends the sequence?" Teams that think in signals ask "what did the person just tell us, and what do they deserve next?" The second question survives every platform migration.

Three consequences follow. First, conversion means one thing at a time. If the trial signup, the onboarding call, and the annual upgrade all count as "conversion," your reports prove everything and explain nothing. Name the event per campaign. Second, attribution stays humble. The checklist, the reminder email, and the founder's reply probably all assisted that purchase. Record all three touches; credit the journey, not one hero click (Lesson 86.5 makes this operational). Third, follow-up earns its send. Every message points back to a signal: "you finished the worksheet, here is the deployment lesson" beats "just bumping this to the top of your inbox" every time.

Exercise: trace one real journey

Create LEAD-JOURNEY.md. Pick one real path — a download, an inquiry, a trial — and trace it through all six stations plus every handoff.

# LEAD-JOURNEY.md — [Offer name]

## The six stations
- Source: ___ (page/link/event + what intent it carries)
- Offer: ___ (concrete value exchanged)
- Consented contact: ___ (what was promised, how often, how to leave)
- Useful next action: ___ (one invited step)
- Signals to watch: ___ / ___ / ___ (did it / stalled / left)
- Record: ___ (where each signal lands: stage, fields, notes)

## Handoffs (who or what acts at each step)
- Source→offer owner: ___ / tool: ___
- Contact→action owner: ___ / message: ___
- Signal→record owner: ___ / where logged: ___
- Signal→follow-up rule: if ___, then ___; if silent ___ days, then ___.

## Proof it is real
- One actual person (anonymized) walked: ___ → ___ → ___
- One handoff that currently drops signals: ___

Worked mini-example — Sonariq Research Desk: source (founder reads a sample report) → offer ("one free source-check on your market") → consent ("the check plus two method notes") → next action ("send us your three sources") → signals (sent sources / asked about price / silent) → record (CRM stage + analyst note). The silent path gets one useful nudge — the published method checklist — then stops.

Finish line: a LEAD-JOURNEY.md with all six stations, every handoff named, and one real walk-through.

Verify quickly: hand the file to a colleague. If they can say what happens when the person goes silent — without asking you — the journey is mapped. If not, the silent path is missing.

Common failure mode: the tool-first journey — five platforms connected, no named next action, no silent-path rule. Leads pile up, nobody is followed up, and the team blames the software for what was really an unmapped journey.

Check your understanding

1. Define lead, signal, conversion event, and attribution in your own words. 2. Why does consent belong inside the journey, not beside it? 3. What breaks when one campaign counts three different actions as "the conversion"?

Next

Journeys diverge: a Models reader and a deploying builder who downloaded the same worksheet need different next steps. Lesson 86.2 builds segments from real jobs and real signals — so each person gets the right next thing, and nobody gets everything.