retention-feedbacklisted

# Retention Feedback The loop that keeps the *post-sale* half of the motion connected to product — the half the funnel forgets. Sales→marketing is the loop everyone can see; this is its mirror on the right side of the bowtie. Field intelligence from onboarding, adoption, and renewal flows back to product and CS on a cadence, instead of dying in a QBR. This is the four-function version of the alignment thesis in [`docs/why-align.md`](../../../docs/why-align.md) — made concrete as a tagged line in the same shared log the `marketing-feedback` skill writes to. From a source — an onboarding note, a usage review, a support thread, a renewal call, a deal update: 1. **Scan for the four signal types:** - **Adoption friction** — where customers stall between signing and getting value (the workflow they never turned on, the setup step that blocks them). - **Churn risk** — the real leading indicator: usage trending down, a champion gone quiet, a single-threaded account after a reorg. - **Expansion blocker / signal** — a missing feature that's holding back a renewal or a second department; or, the opposite, a customer asking for more unprompted. - **Renewal-loss reason** — the real one, logged, not remembered (people misdiagnose why accounts leave as often as why deals are lost). 2. **Log each as a tagged line** in `ops/feedback-log.md` — the same single home marketing's tags use — so product and CS can act without a meeting: - `RETENTION-RISK: [account] — [the adoption/