MAC pivot: retainer-consulting framing killed; info-product shape confirmed

Why this is in the vault

Closes off a competing product-shape framing that had been sitting in the Notion board as a stale "Productize MAC + Client Reporting as RDCO services" ticket since 2026-04-16. Founder explicitly archived it on 2026-05-11 13:14 ET via the new HQ click-back rail (first real round-trip on that system) with the reasoning that a client retainer is too time-intensive AND directly competitive with his phData work. The MAC product-shape stays exactly where the 2026-05-04 decision-log put it: executable info product, $300-2k range, scales without marginal labor.

What got killed

• "RDCO offers MAC as a managed/retainer client engagement" — DEAD
• Any future framing of MAC as a $2-5k/mo consulting service — DEAD
• "Client Reporting" as a productized RDCO service line — DEAD (was always paired with MAC in the same ticket)

What stays exactly as it was

• MAC as an executable course / info product sold as a .claude plugin via Anthropic marketplace + Stripe paywall ([[01-projects/mac/2026-05-04-mac-product-shape-decisions]]).
• $300-2k price band.
• 8-phase agent playbook architecture (portable Layer 1 IP + Claude skill Layer 2 wrapper).
• Sanity Check distribution funnel + drip-essay anchor article positioning.

Why retainer was dead in the water

Two compounding reasons, only one of which I'd been tracking:

1. Time intensity (was visible) — retainer-shaped work doesn't scale with the founder's available hours; MAC info-product scales without marginal labor.
2. phData competition (was NOT visible to me) — founder's day-job at phData IS mid-market data-platform consulting. Selling RDCO retainers in the same buyer + same problem space is a direct conflict-of-interest. An info product is differentiated enough to coexist: it ships ideas the buyer installs and runs themselves, not labor the founder sells to compete with phData's hours.

The phData conflict is the load-bearing reason. Time intensity alone might have been workable; the conflict is what makes retainer un-shippable, period.

Implications for downstream work

• Sanity Check positioning can keep MAC as the anchor product without softening (info product, not retainer — the Sanity Check funnel converts to the info-product spine cleanly).
• MAC anchor essay drip (the "Confession" video + drip sequence) keeps its current framing — it sells the info product, not a consulting engagement.
• Productize Client Reporting as a standalone offering is now off the board; if it returns it would need to be re-framed (e.g. as a SaaS / self-serve dashboard product, not consulting).
• Notion Task Board entry 344f7d49-36d1-8102-b6ad-c0b1c0bd140f archived with this doc linked from its Notes.
• /decisions/2026-05-11-board-backfill-mac-warm-network-pick.html marked decided/archived in _decisions.json.

Process-meta (first real click-back loop)

This was the first end-to-end validation of the HQ-as-decision-surface architecture shipped earlier today ([[06-reference/concepts/2026-05-11-hq-as-decision-surface-notion-as-data-store]]). The loop ran cleanly:

1. /check-board surfaced the ticket as Both-owned (founder warm-network names + moonlighting check needed).
2. Backfill subagent generated the /decisions/<slug>.html page with the 4-option click-back rail.
3. Founder opened the page on iPhone, tapped ARCHIVE + typed a sentence of context.
4. iMessage came back to Ray with the structured wire body DECISION:<slug>:ARCHIVE || <context>.
5. Ray archived the Notion ticket and filed this vault note within ~5 min of the click.

End-to-end latency from /decisions click → vault-canonical decision-log: ~3 minutes. The system works.

Related

• [[01-projects/mac/2026-05-04-mac-product-shape-decisions]] — the canonical product-shape brief; this doc closes off the retainer alternative that was still alive in the Notion board.
• [[06-reference/concepts/2026-05-11-hq-as-decision-surface-notion-as-data-store]] — the architecture this loop validated.
• [[~/.claude/projects/-Users-ray/memory/feedback_imessage_as_generative_ui_return_channel]] — the wire-format pattern that powered the click-back.