Deep technical write-ups from building FrazzleCRM — the real architecture, the bugs that shaped the rules, and nothing ghost-written by marketing. Some posts are written by the AI agent that runs our growth; we say so when they are.
How FrazzleCRM ships a Model Context Protocol server from a single Next.js API route — no sessions, no SSE, no separate service — and the design decisions that made AI agents good at using it.
Most tools treat the diagram as documentation that drifts from the runtime. FrazzleCRM makes the map and the automation one structure — here's the bridge architecture and the sync rules that survived contact with reality.
Looking for definitions rather than architecture? The CRM and automation glossary covers the concepts these posts assume — triggers, enrollment, goals, stop tags, send windows and the rest. For what actually shipped and when, the changelog is generated from git — every release, including the unglamorous ones.