role

Santiago — Project Manager JD

Santiago Perez Asis's Project Manager role definition: cadence, dependency tracking, risk register, and L10 scorecard ownership for MemberIntel inside the broader Caseproof portfolio.

Role: Project Manager, Cross-Caseproof — primary on MemberIntel
Incumbent: Santiago Perez Asis
Reports to: Blair Williams, CEO
Peers (also report to Blair): Seth Shoultes (Lead Architect, MemberIntel) · Product Lead, MemberIntel
Effective: May 2026
References: MemberIntel SPEC v1, decision-rights matrix, phased plan

Mission

Keep MemberIntel on cadence. The Project Manager is the operational metronome — sprint discipline, dependency mapping, risk visibility, and the connective tissue between MemberIntel and the rest of Caseproof’s initiatives.

You don’t decide what gets built (Blair) or how it gets built (Seth) or why it should ship a particular way (Product Lead). You decide when — through the rhythm — and surface anything that threatens the rhythm.

Authority structure

Project Manager (Santiago) holds:

Sprint cadence, ticket tracking, and dependency mapping
L10 scorecard for MemberIntel
Risk register maintenance and review cadence
Cross-rock coordination (MemberIntel ↔ MemberPress core ↔ MemberMouse legacy ↔ growth)
Status reporting to leadership across all Caseproof projects you cover
Project-management tooling decisions (Linear / Notion AI / etc.)
Meeting cadence and rhythm (standups, planning, retros, reviews)

Lead Architect (Seth) holds: sprint scope, engineering velocity, technical decisions
Product Lead holds: PRD content, customer-facing decisions, marketing/compliance/sales
CEO (Blair) holds: strategy, scope, pricing, material approvals

You are the third leg of the operational stool — a peer to Seth and the Product Lead, not a manager of either.

What you own

1. Sprint cadence

Run the MemberIntel sprint cycle (cadence TBD with Seth — likely 2-week sprints).
Sprint planning, mid-sprint check-ins, sprint review, and retrospective.
Capacity planning across the engineering team.
Burndown / velocity tracking — surface drift early.

2. Ticket and dependency tracking

All MemberIntel work tracked in Linear (or the team-agreed tool).
Dependencies mapped: MemberPress-core changes blocking MemberIntel features, MemberIntel features blocking marketing rollouts, etc.
Critical path always visible — what would slip GA if it slipped this week?
External dependencies tracked (privacy counsel, PR agency, third-party APIs).

3. Risk register

Maintain MemberIntel’s risk register per SPEC §14 (Anthropic dependency, content lead bottleneck, eval differentiation, compliance, Phase 2 calibration).
Review risks bi-weekly with Seth and the Product Lead.
Escalate hot risks to Blair within 48 hours of identification.
Track mitigation actions to close.

4. L10 scorecard for MemberIntel

Define the weekly numbers (signups, conversion, eval pass rate, cost-per-user, etc.) once telemetry exists.
Pre-launch: track readiness milestones (privacy counsel engaged, beta cohort onboarded, marketing site live, etc.).
Post-launch: track the metrics defined in SPEC §2.
Surface trends and outliers — don’t just collect numbers.

5. Cross-team coordination

Coordinate dependencies across:
- MemberPress core (Paul Carter) — data sync APIs, MP-side surface required for MemberIntel
- Growth (Curt Noble) — marketing site launch, paid acquisition timing
- Design (Russ + Meo) — design dependencies for engineering
- Operations (Danielle) — Senior AI Engineer hire and onboarding
- Payments (Ally) — Stripe integration and pricing logic
- CS (Wray) — support enablement before launch
Make sure no dependency is invisible to the Product Lead or Seth.

6. Status reporting

Weekly status snapshot to Blair (concise, traffic-light style: green/yellow/red on each rock).
L10 attendance with crisp scorecard read.
Quarterly: drive the architectural review check-in (per the quarterly-architecture-review-template) — keep agenda tight and timeboxed.
Cross-rock view for Caseproof leadership when MemberIntel timelines impact other initiatives.

7. Meeting rhythm

Daily standup or asynchronous equivalent with engineering.
Weekly sync with the Product Lead (30 min).
Bi-weekly sync with Seth (30 min).
Monthly leadership review with Blair, Seth, Product Lead.
Sprint reviews and retros at sprint cadence.
Quarterly architecture review (you facilitate; Seth and Product Lead attend; Blair joins).

What you do NOT own

Sprint scope decisions. Seth decides what fits in a sprint; you track whether it actually fits.
PRD content. Product Lead drafts; you track that it gets drafted on time.
Architectural decisions. Seth’s call.
Hiring decisions. Engineering hires are Seth’s; ops fit is Danielle’s; you don’t sit in the loop unless asked.
Cross-functional content decisions. Marketing, sales, support enablement — Product Lead’s domain.
Pricing or strategic calls. Blair.
Engineering management. You don’t direct engineers; you ask them to surface what’s blocking the work.

Critical role norms

Cadence over heroics. A predictable rhythm beats sporadic sprints of intensity. You enforce the rhythm.
Dependency-mapping is your superpower. When something slips, you know within 24 hours which downstream rock is affected.
Risks surfaced early are not failures. Treat early risk surfacing as a signal you’re doing the job well — the team should bring you problems before they’re crises.
Status reports are short and honest. Green/yellow/red, with the “why” in one sentence per item. No long narratives.
You don’t manage Seth’s people. You ask the engineers what they need; you don’t tell them what to do.
You can disagree with priorities. Bring concerns to Blair through the same 48-hour channel Seth and the Product Lead use.
Cross-rock visibility goes both ways. When Caseproof’s other initiatives could collide with MemberIntel timelines, you flag it before it’s a problem.

Success measures (12-month)

Measure	Target
Sprint completion rate	≥ 85% planned-vs-shipped, sustained
Velocity drift	≤ 15% sprint-over-sprint variance once stable
Risks surfaced ahead of impact	≥ 80% of register items flagged ≥ 1 sprint before they affect the critical path
Cross-team dependency surprises	≤ 1 per quarter (a “surprise” = unmapped dependency that delays a milestone)
L10 scorecard cadence	100% on-time weekly delivery
Status report on-time delivery	100%
Blair’s confidence in MemberIntel timeline	”I know what’s actually happening every week” — qualitative quarterly check

Reporting cadence

Cadence	Audience	Format
Daily	Engineering team	Standup or async digest
Weekly	Blair	Status snapshot (traffic-light + critical path)
Bi-weekly	Seth	Sprint sync (30 min)
Weekly	Product Lead	Coordination sync (30 min)
Monthly	Caseproof leadership	L10 scorecard
Quarterly	All leads + Blair	Architecture review (you facilitate)

What “good” looks like in this role

Blair gets predictable status reports — no surprises about MemberIntel’s actual state.
Seth focuses on architecture and code; he doesn’t have to think about cross-team dependencies because you’re tracking them.
The Product Lead can plan launch comms with confidence because the engineering timeline is real.
Risks surface 1–2 sprints before they become problems, not after.
Cross-rock collisions are anticipated — MemberIntel doesn’t blindside MemberPress core or growth.
The team enjoys the rhythm — they know when standups are, when planning is, when retros are. The cadence is reliable.
The L10 scorecard tells a story leadership can act on, not just a list of numbers.

Document version: Draft v1 — companion to the phased plan. Cadence and tooling specifics finalize once Seth and the Product Lead are operational on the project.

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

← Previous 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 9 of 9