Moxxie Meeting Battle Prep

plancompleted

Moxxie Meeting Battle Prep

Preparation guide for Thursday 10am PT meeting with Alex Roetter (GP at Moxxie Ventures, ex-VP Engineering at Twitter). Prateek (partner) already met, expressed interest.

Provenance

Ingested from Morphism/moxxie-battle-prep.md on 2026-03-28. Original meeting prep document.

60-Second Pitch (Core)

Every engineering team using AI coding assistants has the same experience. The first month is magic. The second month, someone notices a CI config was changed without review, a dependency was added without approval, a release went out with a policy violation.

The gap between observing what agents do and controlling what they ship — that's where governance drift lives.

Morphism is the control plane. One config defines your rules. Four surfaces enforce them — CLI, MCP server, CI pipeline, and shared dashboard. Every check produces a typed proof.

Install, init, validate. Under five minutes to first governance score. No account needed.

7 published npm packages, 26 MCP tools, 99% test coverage, onboarding pilot teams now. Raising pre-seed to hire first two engineers and reach 10 paying teams to Series A metrics.

Target: under 70 seconds.

Demo Flow (3 min max)

  1. Site walkthrough (30s) — morphism.systems hero → drift diagram → commands → dashboard preview
  2. Live terminal (60s) — morphism init && morphism score && morphism validate in test repo. Highlight: 12 governance categories, 125-point scoring, kappa/delta convergence.
  3. Dashboard (60s) — agents, assessments, governance score, activity feed, repo fleet drift percentages
  4. Close (30s) — back to deck slide 10, "Here's what we need to scale it"

5 Hardest Questions Prepared

  1. "How is this different from OPA / Snyk / Datadog?" — OPA checks infrastructure configs, Snyk scans dependencies, Datadog observes runtime. None enforce governance across the full agent delivery path (PR → CI → merge). Morphism is the cross-surface control plane.

  2. "Solo founder. Bus factor?" — System is open-source, modular standard stacks (Python engine, TS packages, Next.js dashboard). First two hires are engineer #1 + DevRel. Pre-seed runway specifically de-risks single-point-of-failure.

  3. "Zero revenue. When does that change?" — Pilot phase with design partners on free Pro tier. Pricing live: $29/seat Pro, $79/seat Team. Conversion trigger: team expansion at month 2-3. First paid conversions within 90 days of close.

  4. "Category theory — real or branding?" — Real and the moat. Engine maps governance rules onto functors, natural transformations, isomorphisms. Proves policy in CLI is structurally identical to policy in CI. Kappa/delta metrics are mathematical, not heuristic. Users just run commands and get scores.

  5. "Pipeline? Who's interested?" — Productive conversation with Prateek, early conversations with other funds. Product is live and installable today (ahead of most pre-seed).

Pre-Call Email Template

Subject: Morphism — deck + live product ahead of tomorrow

Includes: deck attachment, morphism.systems link, 2-line CLI install instructions (npm i -g @morphism-systems/cli && morphism init && morphism score).

Things NOT to Do

  • Don't show the 10-theme design system
  • Don't explain category theory unprompted
  • Don't apologize for being solo founder — frame as velocity
  • Don't fill silence after the ask slide
  • Don't read the slides — slides are evidence, voice is narrative

Execution Checklist

  1. Review deck (10 min)
  2. Practice 60s pitch 5x out loud (15 min)
  3. Set up demo terminal with test repo (10 min)
  4. Open all 5 tabs in order (2 min)
  5. Send pre-call email (5 min)
  6. Read Q&A once more (10 min)

Total active prep: ~52 minutes.