0% read
on this page
introwhy we built itbuild logproduct detailswhat shippedwhat i'd changemeta
Squadhouse connects a Next.js 16 customer platform, AI-assisted service delivery, and an internal CRM with a WhatsApp bridge and shared Supabase data contract.

product and operational engineering
decisions.md (squadhouse)
# challenge, architectural choices, and technical outcomes
focus platform · web
context: web
Build the customer-facing product on Next.js 16.
focus agents · six roles
context: six roles
Build scoped agents for the operating workflow.
focus evaluation · 19 checks
context: 19 checks
Test risky agent behavior like product code.
focus migration · cutover
context: cutover
Make the source-of-truth change explicit.
selected architecture · 1 deep dive
role / challenge / choices / outcomes
A Next.js customer experience connected to lead intake, AI-assisted delivery, and a WhatsApp-aware internal board.
My contribution: Full-product architecture and implementation across the public web experience, service flows, CRM, messaging integration, and migration runbook.
Platform
CRM board
Platform walkthrough
technical outcomes
6
scoped agents
19
agent eval assertions
3
CRM workspaces
human
outreach gate
retrospective.md
This work made operational details part of the product architecture. Lead identity, message history, migration order, backups, and the human workflow in the CRM determine whether the whole system is dependable.
← previous case
aiOS
04 / 04