What does it take to deliver and run multiple customer engagements at once, without losing signal?
Multi-project, multi-team customer engagements built to scale from one client to many. Each system in this domain ships with a Mermaid architecture diagram, a numbered implementation map, and a checkmark list of documented build phases. The original source document is kept per system.
| Reader | What to look at | Time |
|---|---|---|
| Recruiter | This README, badges | 10 sec |
| Hiring Manager | Systems list below, per-system Validation | 2 min |
| Engineer | Per-system Architecture + Implementation | 15 min |
| Learner | Per-system end-to-end source content | 30 min |
Engineering for the coordination of customer engagements across projects, teams, and stakeholders. Repeatable patterns for intake, scope, hand-off, status, and outcome reporting that hold under engagement growth.
What it isn't. A single-system point solution. A regulated-industry deliverable. A founder's zero-to-one build.
- 25 AI Agents: Excalidraw to Linear: 25-agent Excalidraw-to-Linear pipeline verified via MCP with a 98/100 triangulation score
- AI-Powered Executive Review System: MBR/QBR governance where a read-only reconciler flags every number before it reaches the room
- Multi-Team Sprint Delivery with Cursor Subagents: 25-agent sprint with 8-minute MTTR and 96% first-pass security-gate pass rate, recorded honestly.
- Cross-Program Capacity Planning: Capacity measured in competent hours, where headcount overstated capability by exactly 2x and an absence check only counts if it read every row