role

Blair — CEO JD

Blair Williams's CEO role definition for MemberIntel: product owner, final decision-maker on strategy, pricing, and architecture material choices, executive sponsor across the company.

Role: CEO, MemberIntel / Caseproof
Incumbent: Blair Williams
Reports to: (top of org)
Direct reports for MemberIntel: Seth Shoultes (Lead Architect) · Product Lead (unfilled) · Santiago Perez Asis (Project Manager, Cross-Caseproof)
Effective: May 2026
References: MemberIntel SPEC v1, decision-rights matrix

Mission

Own MemberIntel as the executive product owner. Set the direction; approve the material choices; make the calls only the CEO can make; remove blockers the leads can’t remove themselves. Be the final voice on strategy, pricing, scope, and material architectural commitments — without dictating tactical execution.

The CEO posture is strategic and decisional, not operational. You direct what gets built and why. The leads execute how.

Authority structure

CEO (Blair) holds:

Product strategy, target customer, 18-month roadmap
Final say on PRDs (Product Lead drafts; Seth provides technical input; you approve)
Final say on product design (Product Lead coordinates; you approve at milestones)
Final say on architecture decisions for material choices (Seth proposes; you approve)
Pricing strategy and packaging decisions
Headcount and budget approvals
Vendor / partnership strategy at the company level
Go / no-go calls on launch readiness
Resolving peer disagreements (Seth ↔ Product Lead, escalated within 48 hours)
Cross-rock prioritization across the broader Caseproof portfolio

Lead Architect (Seth) holds:

Technical architecture and implementation
Engineering team direction and code quality
Sprint scope and engineering velocity
Engineering hiring decisions
Vendor / tooling decisions for the engineering stack

Product Lead holds:

PRD authoring and product execution
Customer discovery, beta program, marketing site, compliance, sales/support enablement
Free → Pro conversion mechanics
Cross-functional coordination across Caseproof

Project Manager (Santiago) holds:

Sprint cadence, ticket tracking, dependency mapping
L10 scorecard and risk register
Cross-rock and cross-team project coordination

What you own

1. Strategic direction

Set MemberIntel’s 18-month roadmap and reset it quarterly.
Define and update the target customer (initially: existing MemberPress site operators).
Decide what not to build — protect scope from creep.
Approve every material change to V1, V1.5, V2 scope.
Sign off on the eval-suite gating criteria (per architecture deep-dive).

2. Pricing & packaging

Set the Free / Pro split (currently $29/mo Pro, capped Free).
Approve pricing iterations based on post-launch data (Product Lead proposes).
Decide annual plans, Pro+ tiers, agency tiers, and any free-tier sunset before they ship.
Sign off on the launch discount strategy.

3. Architecture material choices

Approve high-impact technical commitments Seth proposes (hosting platform, brain isolation strategy, vendor lock-in).
Sign off on the Anthropic dependency and any plan to mitigate it.
Approve compliance-driven architecture (privacy counsel input).
Approve eval-suite content scope (the differentiation eval is a release gate).

4. Launch decisions

GA go / no-go call.
Beta-to-public-launch readiness sign-off (Product Lead proposes criteria).
Day-one launch comms approval.
Rollback authority if launch goes sideways.

5. Headcount & operating budget

Approve every MemberIntel hire (Senior AI Engineer, Product Lead, content lead, mid-level engineer).
Approve outside engagements (privacy counsel, PR agency, etc.).
Approve cost ceilings (per-call AI budget, free-tier cost-per-user target).

6. Conflict resolution

Resolve Seth ↔ Product Lead disagreements within 48 hours of escalation. No silent drift.
Resolve cross-team conflicts when Seth or the Product Lead can’t.
Mediate priority conflicts between MemberIntel and other Caseproof initiatives.

7. Executive review cadence

Weekly written status from the Product Lead — read and respond within 24 hours on blockers.
Bi-weekly architecture review with Seth (30-min sync; deeper dive monthly).
Quarterly architecture review (per the quarterly-architecture-review-template) — surface drift between SPEC and architectural reality.
Monthly L10 leadership attendance.
Quarterly outcome reviews with each direct report (90-min deep-dive).

What you do NOT own

Sprint-level execution. Seth and Santiago run the cadence.
PRD drafting. Product Lead drafts; you approve.
Engineering tactical decisions. Seth’s call (within material-choice boundaries).
Day-to-day cross-functional coordination. Product Lead handles.
Code review or technical debt cleanup. Engineering team’s domain.
Roadmap input collection. Product Lead gathers customer signal; you decide priorities.

Critical role norms

Decisions, not directives. Set direction at decision points; don’t redirect mid-sprint.
One escalation channel. Disagreements between leads come to you in writing within 48 hours, with each lead’s recommendation. You decide quickly.
No skipping the lead layer. When a customer or partner reaches you directly with a request, route it back to Seth or the Product Lead. You don’t take action commitments on behalf of the team.
Quarterly architecture honesty check. Surface friction points between the phased plan and architectural reality (per the quarterly review). Make calibration calls — don’t let drift accumulate.
Approve scope shrinks fast. If launch readiness is at risk, the right move is usually to cut scope, not extend timeline. You’re the only person who can make that call.
Compliance is a launch gate. If privacy counsel isn’t engaged by June 1, GA slips — and you make that call publicly so the team plans around it.

Success measures (12-month)

Measure	Target
MemberIntel V1 GA shipped on schedule	On or before mid-October 2026
Free tier adoption	≥ 10% of MP customer base within 6 months
Free → Pro conversion within 60 days	5% floor; goal 8–10%
Pro WAU	≥ 70%
Eval suite differentiation score	Beats baseline LLMs on MemberIntel-specific scenarios
Cost-per-free-user	≤ $1.10/mo
Cost-per-Pro-user	$6–12/mo range, profitable at $29/mo Pro
Launch readiness	All gating criteria met without scope-cut surprises in the final 30 days

Reporting cadence

Cadence	Audience	Format
Weekly	Caseproof leadership	L10 update on MemberIntel rock
Bi-weekly	Seth	Architecture sync (30 min)
Monthly	Product Lead, Seth, Santiago individually	1 (45 min)
Quarterly	All three leads + matrixed contributors	Outcome review (full afternoon)

What “good” looks like in this role

The leads feel decided, not micromanaged. Decisions land within 48 hours.
Scope debates resolve with clear rationales the team can repeat back.
Architecture and product stay aligned through V1 → V1.5 → V2 because material choices were approved with full context, not signed off in passing.
Cross-team coordination flows through the Product Lead and Santiago, not through your inbox.
Launch gates are honored — no scope cuts at the last minute, no compliance fire drills.
The team enjoys the executive cadence — predictable rhythm, honest feedback, fast unblocking.

Document version: Draft v1 — companion to the decision-rights matrix. Decision-rights table requires sign-off from Blair, the Product Lead, and Seth before operational rollout.

For: B Blair Williams S Seth Shoultes P Product Lead S Santiago Perez Asis

← Previous in role Seth — Lead Architect JD Next in role → Product Lead JD

Phase 1-2 Friction Points reference
A companion one-pager surfacing seven decisions where the May architectural commitments conflict with the v1 phased plan — each with a recommendation and named decider — designed to drive a 30–45 minute sign-off session before Rev 2 is approved.
Decision Rights Matrix reference
A binding contract defining who owns which decisions across engineering, product, compliance, and GTM — keeping Seth and the Product Lead unblocked as peers without escalating every disagreement to Blair.
Quarterly Architecture Review Template reference
A 90-minute fixed-agenda template for quarterly architectural health reviews — covering differentiation gap, cost-per-cohort, reliability, cross-pollination health, compliance posture, and a standing 'one thing that worried me' round — starting Q4 2026 post-GA.
Privacy Counsel Architecture Review Agenda reference
A 4-hour late-May working agenda for outside privacy counsel to review MemberIntel's per-tenant isolation, cross-pollination boundary, secrets management, and data lifecycle decisions — grounding counsel's June ToS and Privacy Policy drafting in the actual architecture.
Seth's Phase 1 Deliverable Checklist reference
Seth's operational working checklist for May 2026 — organized week-by-week with ADR drafts, GCP scaffolding, schema design, RLS prototype, hiring pipeline, and cross-functional coordination tasks required to unlock Phase 2 on June 1.
Product Lead's Phase 1 Deliverable Checklist reference
Product Lead operational working checklist for May 2026 — week-by-week milestones, PRD authoring, customer discovery, privacy counsel engagement, beta program scaffolding, cross-functional kickoffs, and the Phase 1 milestone gate criteria required to kick off Phase 2 on June 1.

This page is part of

Blair's Tour — Executive view — Step 8 of 9