Onboarding platform
Product · full-stack
An end-to-end onboarding platform, built hands-on with Claude Code and deployed on Vercel. A 19-screen CSM operations dashboard, with daily triage, an email approval queue, a pipeline board and live CRM and tenant sync, plus a magic-link customer portal for setup, document upload, training and live progress. Onboarding quality is the strongest churn predictor in the estate.
~41Klines TypeScript
165PRs merged
56API endpoints
12→5onboarding weeks
Next.jsPostgresVercelClaude Code
MCP server, permission-first
Platform · infrastructure
A production MCP server that lets AI agents read and safely write across the post-sales system, with the permission model designed first. Per-user bearer tokens, issued and revoked from settings and tied to a named identity. It fails closed: missing, unknown or revoked tokens get a 401 before any tool runs. Reads come from the same shared builders as the dashboard, so the agent and the UI cannot drift; writes replicate each route's full validation, logging and provenance.
No tool sends email, approves a draft, or moves a pipeline stage.
MCPOAuth + PKCEFail-closed authHuman-in-the-loop
Autonomous bug-fix agent
Autonomous agent
A scheduled agent that takes the newest reported bug each weekday, writes a fix on its own branch and opens a pull request for review. It can only propose: it never merges or pushes to main, and feature requests are never auto-built. They wait for a human by design.
GitHub ActionsClaudePropose-only
AI operating layer for post-sales
AI systems
The layer the CS team runs on. Call transcripts flow structured into the CRM, from Fathom to Claude to HubSpot. Churn risk is scored across the whole estate with tiered intervention sequences, and QBR decks, renewals workbooks, daily account briefings and health dashboards are generated rather than assembled.
950+accounts scored
days→15minto prep a QBR
Claude APIAgentsHubSpotRisk scoring
Multi-agent follow-up program
Multi-agent system
A designed multi-agent system with a separation of powers. Analysis observes the numbers, an orchestrator decides and sets priorities, workers act on accounts, a composer writes, and deterministic code enforces every guardrail. Compliance is encoded as data, not promised: kill switches that fail closed, recipient allowlists, frequency caps, and a written constitution of 20 testable rules. A composer validator checks each message before it sends: exactly one URL and it must be the account's own, and every figure must appear in the source facts.
Analysis observes, the orchestrator decides, workers act, the composer writes, code enforces.
Separation of powersGuardrails-as-codeDPO-gated
Agent governance & routines
Governance
Seven agent routines running in production, from daily summaries and meeting briefs to a Friday weekly wrap that reads across six systems, drafts replies and never sends them. Audits run report-only, with no automated writes. The standing rule is evidence or nothing: every action item must cite a source that actually appeared in a tool result, or it is dropped.
Report-onlyDrafts-onlyEvidence-cited