Monetizing the Farewell Cycle — A 30/60/90 Playbook for Founder's Mammoth Goodbyes

The question

How does founder convert the 6+ warm farewells from Mammoth Growth seniors (Val, Aleks, Dimitar, Justin, Jim, Callie, Nate) into a future-inbound pipeline without burning the goodwill? The transactional-too-early failure mode is the load-bearing risk.

What we already know (from the vault)

[[06-reference/research/2026-05-11-naval-compounding-relationships-cadence.md]] — Already named the live members of the "compounding relationships" class: former phData colleagues, Mammoth Growth network, Sanity Check power-readers, Discord curiosity-readers. RDCO had a 0-touchpoint week problem when this brief filed; the farewell cycle is the natural correction.
[[01-projects/newsletter/rdco-article-no-consultant-prince-charming.md]] — Founder's own 2021 essay frames the post-engagement relationship: clients aren't being rescued, they're being equipped. The farewell narrative consistent with this framing converts naturally to "still rooting for you" rather than "selling to you."
[[06-reference/2026-04-15-commoncog-career-moats-confession.md]] — Cedric Chin frame: moats compound through reputation across employer-cycles. The farewell exchanges are exactly the moat-building moment.
[[01-projects/phdata/offer-negotiation-framework.md]] — The Mammoth contract was ~$200k/yr — these are seniors who controlled meaningful spend, not low-leverage relationships.
Velvet Noise side-doors piece (today) — warm-inbound as moat; adjacent rhetoric, directly relevant timing.

What the web says

Light-Touch Nurture Cadence is the industry consensus. Monthly or quarterly insight-sharing without a pitch. Most agencies assign account managers to a monthly/quarterly meeting; for solo operators the equivalent is a personal-note cadence. The 5-7x cost of new client acquisition vs retention is the load-bearing economic argument. (Skaled — Lead Follow-Up Cadence, Avoma — Agency-Client Relationships)
The "Always Be Useful" (ABU) principle replaces "Always Be Closing". Source after source converges on this — best relationship accelerator is value-first, not pitch-first. Get out of the digital realm; coffee, office visits, conferences beat email. (Haus Advisors — Human Outbound)
Re-engagement trigger checklist (concrete): 12+ months without engagement on active projects, new funding announcements, product/service launches, awards or press coverage, leadership changes (CEO/founder/promotions). Treat triggers as the natural reach-out moment — not the calendar. (Design Business Council — Reconnect with Past Clients)
Four reconnection tactics that work: (1) Coffee catch-up with sector-relevant research; (2) capability-update one-pager; (3) LinkedIn problem-focused case studies + targeted DM; (4) honest "we've evolved" outreach.
The failure-mode taxonomy is explicit: don't send generic newsletters, don't immediately pitch for work, don't apologize for lost contact, don't discount services to win them back. Each of these signals low-status and breaks the moat.
Solo-consultant exit literature emphasizes pipeline-as-asset. When exiting, the pipeline itself is what's monetized — meaning the work to maintain it is exactly the right investment. (Melisa Liberman — Solo Consultancy Exit)
Single-template that converged: "This reminded me of the challenges you mentioned last year — thought it might be relevant." Specific, not generic; about them, not about you; no ask.

Convergences and contradictions

Vault and web converge on the cadence shape: monthly/quarterly light-touch, trigger-driven reach-out. The Naval brief already calibrated this for RDCO; the web validates the calibration was right.
Vault adds a load-bearing nuance the generic web misses: for senior operators (the Mammoth seven), the touchpoint isn't insight-sharing — they have plenty of insight. It's signal of trajectory — they want to see you're building something interesting they could selectively engage with. The /process-newsletter discipline + Sanity Check publishing IS the trajectory signal for this audience.
Contradiction with naive playbook: generic "stay in touch" advice (monthly newsletter, periodic check-ins) is what breaks the moat for senior operators. They have 100 vendors trying that. The differentiator is non-transactional value delivery — sending a specific link / observation / intro that's clearly about them, not about you.
The 12-month re-engagement trigger is wrong for this specific situation. Founder is at zero days post-farewell. The right cadence is 30-60-90 day fresh-exit handling, then quarterly steady-state — not 12-month dormancy.

Synthesis for RDCO

The transactional-too-early failure mode is real. Avoid it via three rules.

Day 1-30 — only value-delivery, zero asks. No intro asks. No "would you like to chat about what I'm building." No referral asks. The only acceptable outbound: a specific link, observation, or intro for them that requires zero response. The Sanity Check newsletter is the perfect channel here — auto-add the 7 to the subscriber list if they're not already on it, send one personal note to each saying "you should be on this" (zero-ask reframing of "subscribe to my thing"). The newsletter itself does the trajectory-signaling for the next 60 days without founder doing additional outbound.
Day 30-60 — single individualized note per person, no group send. A short message specific to their current situation. Not "here's what I'm building" (status update, low-signal). Instead: "I've been thinking about [specific problem they own]. The [specific Sanity Check piece / vault concept] reframes it as [specific angle]. Curious whether you've hit this." This is a research-prompt to them, not a pitch. Half will respond substantively; the other half remembers you as the person who actually paid attention.
Day 60-90 — proactive intro, never an ask. Look for a triangulation opportunity: someone in founder's network the Mammoth person should meet for their benefit. Make the intro double-opt-in (founder's standard discipline anyway). This converts the relationship from "former vendor" to "useful node in their network" — which is the conversion that unlocks future inbound, not any direct ask.

Steady-state cadence after day 90: quarterly trigger-driven touchpoint. Founder maintains a contact-watch skill (already exists / candidate to formalize) that monitors LinkedIn / news for: new funding, leadership changes, product launches, conference appearances. On any trigger, a single specific note within 48 hours. No calendar-driven check-ins — those are the generic-newsletter failure mode.

Why founder's specific situation is unusually high-leverage:

Seven senior operators who controlled meaningful spend, who initiated the farewell exchange, in a 1-week window. That's an unusually concentrated reputational surface to harvest.
Founder's parallel build (phData W2 + RDCO + Sanity Check) is the exact trajectory signal this audience finds interesting — not "starting a competing consultancy" (zero-sum) but "operator who's compounding into something larger" (network-effect-relevant to them).
The Mammoth seven likely talk to each other. The reputation founder builds over the next 90 days across the group compounds within the group — not just one-on-one. This means consistency matters more than any single high-leverage touch.

Concrete deliverables for founder this week:

Friday 2026-05-22 (3 days): Personal note to each of the 7, individualized. Template: "Genuinely meant a lot — wanted to say one more specific thing about [specific moment / contribution]. The Sanity Check stuff I'm publishing tracks adjacent terrain to what you're working on; I've added you to the list (unsub anytime, no offense taken)." Time-box: 90 minutes total. 12-15 minutes per note. No group send.
Friday 2026-05-29 (10 days): Tag each in a personal contact note in vault with: their current focus area, what would actually be useful to flag for them, a 90-day re-touch trigger. This builds the substrate for the day-30 individualized notes.
Day 30 (~2026-06-19): Send the day-30 individualized "I've been thinking about X" notes. One per week so it doesn't look like a campaign.

What NOT to do (the moat-breakers):

Don't pitch RDCO consulting services to this group in 2026. Period. They know what you offer; if it's relevant they'll ask. The moment you pitch them, you collapse the relationship to a vendor-buyer dynamic and lose the network-effect upside.
Don't ask for intros for the next 90 days. The temptation to harvest the warm goodbye into a direct intro ask is the highest-EV-feeling move and also the highest goodwill-burn. Wait until the relationship has a non-transactional foundation re-established.
Don't apologize for the exit. Founder's narrative is "moving up the stack, still rooting for you" — not "sorry I left, here's how to keep working with me."

Strategic context for the Sanity Check + MAC roadmap:

This cycle is the first natural distribution moment for Sanity Check Vol II. The Mammoth seven are exactly the operator-tier reader profile MAC targets. If 5/7 actually open + read for 3 issues, that's the warm core of a launch list. Don't game this — but recognize that the 30-day "I've added you to the list" move is the highest-EV inbound activation founder will run this quarter, even though it doesn't feel like an outbound campaign.

Open follow-ups

Should founder write a piece explicitly about the farewell-cycle moment? Risk: too meta, group might feel surveilled. Reward: original reframe of an undertheorized operator moment, perfect Sanity Check material.
What's the contact-watch automation primitive? Today /sync-contacts handles last-touched and stub creation. Need: LinkedIn + news monitoring for specific tier-A contacts with trigger-on-event alerts.
How does this playbook generalize to future Mammoth-style exits? Should there be a ~/.claude/skills/farewell-cycle-handler skill that auto-fires when founder logs an employment/contract exit?
Are any of the 7 already on the Sanity Check list, and what's been their engagement pattern? Need to check before sending the day-30 note (asymmetric info matters).
What's the cost (in time/attention) ceiling for this kind of relationship maintenance? Naval brief's 0-touchpoint week was the alarm; what's the floor? 2 touchpoints/week with the tier-A class? Need explicit budget.

Sources

Vault:

[[06-reference/research/2026-05-11-naval-compounding-relationships-cadence.md]]
[[01-projects/newsletter/rdco-article-no-consultant-prince-charming.md]]
[[06-reference/2026-04-15-commoncog-career-moats-confession.md]]
[[01-projects/phdata/offer-negotiation-framework.md]]
[[06-reference/2026-04-03-selling-data-science.md]]

Web: