M MemberIntel KB

reference

Decision Rights Matrix

A binding contract defining who owns which decisions across engineering, product, compliance, and GTM — keeping Seth and Cindy unblocked as peers without escalating every disagreement to Blair.

Drafted: April 30, 2026
Status: Draft v1 — requires sign-off from Blair, Cindy, and Seth before MemberIntel work begins
Owner: Blair Williams, CEO


Why this matrix exists

Cindy and Seth are peers, both reporting directly to Blair. Without a written matrix, peer-to-peer collaboration on a complex product launch degrades into Blair adjudicating tactical disputes. This document is the contract that prevents that.

The rule for anything not in this matrix: if Cindy and Seth disagree on a decision not explicitly covered here, the disagreement goes to Blair within 48 hours. No silent escalation drift.


Roles

  • Blair Williams — CEO, MemberIntel. Strategy and final approval on material product decisions.
  • Seth Shoultes — Lead Architect, MemberIntel. Technical product owner.
  • Cindy Thoennessen — Product Lead, MemberIntel. Operational and execution lead.
  • Santiago Perez Asis — Project Manager, Cross-Caseproof. Sprint cadence and dependency tracking.

Decision Rights Tables

A. Engineering & Technical Decisions

DecisionOwnerInput fromEscalation path
Technical architecture and implementation (brain design, data pipelines, AI/ML approach)Seth (Blair final say on material choices)Cindy (delivery dependencies), Mahmoud ad hocBlair
Vendor / tooling decisions (hosting, vector store, AI providers, observability)SethCindy (cost / contract terms)Blair
Engineering hiring decisionsSethDanielle (cultural / operational fit interviews + onboarding logistics)Blair
Sprint scope and engineering velocitySeth (tracked by Santiago)Cindy (delivery dependencies)Blair
Code quality standardsSeth (with Ronald enforcing baseline; Senior AI Engineer once ramped)Blair
Engineering team prioritization between MemberIntel internal needs and cross-team requestsSethCindy (launch dependencies), Paul Carter (MemberCore impact)Blair
Tool surface design (query_customer_metrics, analyze_site, etc.)SethCindy (PRD requirements)Blair
Entitlement layer designSethCindy (tier-feature matrix)Blair
AI model routing rules (Sonnet/Haiku tier-gating)SethCindy (cost implications)Blair
Prompt versioning and AI eval suiteSethCindy (acceptance criteria)Blair
Per-tenant data isolation architectureSethoutside privacy counsel (compliance constraints)Blair
Cost controls and token budget capsSethCindy (impact on customer experience)Blair
Performance and scalability targetsSethBlair
ADR (Architectural Decision Records) authoringSethBlair

B. Product & Business Decisions

DecisionOwnerInput fromEscalation path
Product strategy, target customer, 18-month roadmapBlairSeth (technical feasibility), Cindy (market / customer feedback)Final
Pricing model and packaging ($29/mo Pro, Free tier scope)BlairCindy (rollout plan), Curt (sales enablement)Final
Free vs Pro entitlement matrix (every feature × every tier)Cindy proposes; Blair approvesSeth (technical feasibility)Blair
Product Requirement Documents (PRDs)Cindy drafts; Blair approvesSeth (technical input)Blair
Product design (visual + UX)Cindy coordinates; Blair approvesRuss + Meo executeBlair
Launch timing (closed beta, public GA)Joint: Cindy + Seth + BlairSantiago (delivery confidence)Blair makes final call if disagreement
Quality bar / “ship or hold” gateCindy holds the gateSeth (technical readiness)Blair on appeal
Brand identity (logo, color, voice, working name → final name)Cindy proposes; Blair approvesRuss (visual direction)Blair
Marketing positioning and messagingCindy + Curt (joint); Blair approvesSeth (product accuracy)Blair
Beta cohort selection criteriaCindy proposes; Blair approvesCurt (customer signal), Seth (usage requirements)Blair
Beta-to-public-launch readiness criteriaCindy proposes; Blair approvesSeth (technical readiness), Wray (CS readiness)Blair
memberintel.com design and copyCindyRuss + Meo (design), Sarah (copy), Curt (brand consistency)Blair
Pricing page designCindyRuss + Meo, CurtBlair
In-MP-admin banner / menu integration designCindySeth (technical), Paul Carter (MP integration)Blair
Sales enablement materials and trainingCindy + Curt’s teamSeth (product accuracy)Blair
Support enablement materials and trainingCindy + Wray’s teamSeth (product accuracy)Blair
Customer support model for Free users (docs / AI-first / human escalation)Cindy proposes; Wray operatesBlair approvesBlair
Customer onboarding flow designCindySeth (technical constraints), Wray (CS readiness)Blair
Free → Pro upgrade-moment surfaces (chat cap, insight cliffhanger, etc.)CindySeth (technical), Curt (conversion best practices)Blair
A/B testing plan for upgrade copyCindy + CurtBlair
Pricing iteration based on launch data (post-Q4)Cindy proposes; Blair approvesSeth (cost implications)Blair
Educational content scope (videos, FAQs, knowledge base)Cindy directs scopeCarl Jessee (production), Sarah (written content)Blair
Roadmap input collection (post-launch)Cindy aggregatesAll customer-facing teamsBlair + Seth (joint on what gets prioritized)
DecisionOwnerInput fromEscalation path
Outside privacy counsel selection and engagementCindyBlair (budget approval)Blair
ToS / Privacy Policy / DPA draftingCindy + outside counselSeth (data architecture), Blair (final approval)Blair
Cross-pollination opt-out mechanism designCindy proposes; Seth implementsoutside counselBlair
Customer-side data deletion pathwayCindy proposes; Seth implementsoutside counselBlair
Consent flow at signupCindy proposes; Seth implementsoutside counselBlair
Data classification (anonymous telemetry vs personally identifying)Cindy + Seth (joint)outside counselBlair
GDPR / CCPA compliance postureCindyoutside counsel, Seth (technical implementation)Blair

D. Project Management Decisions

DecisionOwnerInput fromEscalation path
Sprint cadence, ticket tracking infrastructureSantiagoSeth (technical needs), Cindy (visibility needs)Blair
Cross-rock dependency trackingSantiagoAll rock ownersBlair
Risk register and L10 scorecardSantiagoAll teamsBlair
Status reporting cadence to BlairSantiago (data) + Cindy (MemberIntel narrative)Blair
Phase milestone gating (e.g., Phase 1 → Phase 2)Joint: Cindy + Seth + BlairSantiago (delivery confidence)Blair makes final call
Resource allocation (when does Meo / Kalpesh / Sarah start their dedicated phases?)Blair (with Cindy + Seth input)Russ, Thomas, Katelyn (home managers)Blair

E. Marketing, GTM, and Launch Coordination

DecisionOwnerInput fromEscalation path
Internal-PR vs outside-agency engagementCindy proposes; Blair approvesCurtBlair
Outside PR agency selection (if engaged)CindyCurtBlair
Press release content + embargo strategyCindy + PR agencySeth (product accuracy), Blair (messaging)Blair
Launch-day comms planCindyCurt, Wray, SantiagoBlair
Paid-acquisition campaign budget and channelsCurt (Cindy provides positioning + product input)Blair (budget approval)Blair
GA4 / Meta Pixel / analytics setupCurt’s team (Cindy provides product event spec)Seth (technical)Blair
Email campaigns to existing MP customer baseCindy + Curt’s team (joint)Blair
Social media launch planCurt + Katelyn’s content teamCindy (positioning)Blair
Launch event (Huddle webinar, etc.)Cindy + CurtCarl Jessee (video content)Blair
AEO content strategy for MemberIntelCurt (Rock 1 owner)Cindy (product positioning)Blair

F. People & Org Decisions

DecisionOwnerInput fromEscalation path
Strategic dissent on product direction (Cindy or Seth disagrees with Blair’s strategy)Cindy or Seth raises directly to BlairBlair (final)
Compensation / role decisions for Innovations teamBlairSeth (engineering), Cindy (operational fit)Final
Adding scope to MemberIntel V1Joint: Cindy + Seth + BlairSantiago (impact analysis)Blair
Cutting scope to hold timelineCindy proposes; Seth + Blair approveSantiago (impact analysis)Blair
Pulling matrixed contributors (Meo, Kalpesh, Sarah) back early to home teamsJoint: Blair + home manager (Russ / Thomas / Katelyn)Cindy (impact on launch)Blair
External partner relationships (Stripe, Anthropic, vendors)Cindy (Seth on technical vendors)Blair (when strategic)Blair

Norms (not decisions, but binding)

  1. Cindy doesn’t manage Seth’s people. She doesn’t direct engineers. She works through Seth or Santiago.
  2. Seth doesn’t direct content / marketing / website work. He works through Cindy.
  3. When Seth and Cindy disagree on something not in this matrix, they take it to Blair within 48 hours. No silent escalation drift.
  4. Strategic dissent goes to Blair, not into the workflow. If Cindy or Seth disagrees with a strategic direction, raise it directly with Blair. Don’t reroute through team workflows.
  5. AI tooling is the default workflow for Cindy. Notion AI / Linear AI for project management. AI for first-pass copy drafting. AI for synthesizing customer feedback.
  6. Citations are non-negotiable for Seth. Every AI response must cite the data it references (per SPEC §8.4).
  7. Server-side enforcement of model routing. Free users always route to Haiku; never user-configurable, never accidentally Sonnet.
  8. No fine-tuning of LLM weights in V1. All learning happens through brain content + retrieval.
  9. Honesty in marketing copy is non-negotiable. Per SPEC §4 — never imply non-MemberIntel customers’ data is used.
  10. MM/AA/WL legacy work is not part of MemberIntel. Cindy does not retain dual-product responsibility.

What this matrix does NOT cover

This matrix covers MemberIntel-specific decisions. It does NOT govern:

  • Cross-Caseproof org rocks (Rocks 1, 2, 4, 5, 6, 7) — those have their own owners
  • MemberCore platform decisions outside MemberIntel scope — Paul Carter’s domain
  • Other Innovations work outside MemberIntel — handled within Seth’s broader Innovations team mandate
  • MM/AA/WL legacy product decisions — handled per the dissolution / stable-operations plan

If a decision spans MemberIntel and another org rock, default to Santiago surfacing it as a cross-rock dependency at L10, with Blair as final tiebreaker.


Sign-off

SignatureDate
Blair Williams (CEO)_____________
Cindy Thoennessen (Product Lead)_____________
Seth Shoultes (Lead Architect)_____________

This matrix is binding once signed. Changes require all three signatories to agree. Re-review at the end of Phase 3 (July 31) and Phase 5 (mid-October post-launch).


Document version: Draft v1 — derived from MemberIntel SPEC v1 plus role discussions.

For: S Seth Shoultes C Cindy Thoennessen B Blair Williams S Santiago Perez Asis