Systems in production
Not mockups — running systems. Each case study covers what we built, why it's shaped that way, and what it does every day.
A newsroom that files itself
In a regulated vertical with high source density and a tiny attentive audience, a deterministic pipeline we built and run files twenty-four articles a day without a human touching a single one.
read the case study →OutboundAn outbound system that grew up in production.
A no-code outbound stack rebuilt into one Python codebase, one cron schedule, one Airtable base, and an audit trail per lead. Two to five hundred personalized cold emails a day — drafted, sent, sequenced, and reconciled without anyone at the keyboard between the schedule and the recipient.
read the case study →AI infrastructureA private memory layer for a studio running many systems
Running a portfolio of live systems exceeds what anyone can hold in working memory. We built a private semantic index that turns years of project files, decisions, and operational notes into context any AI coding session can retrieve in under two seconds.
read the case study →Internal toolsA capture-management product for a vertical the horizontal tools never fit
In a procurement-heavy vertical where every opportunity runs through multi-stage proposals, compliance gates, and partner coordination, the real workflow always ends up in a spreadsheet. We built the product that replaces the spreadsheet.
read the case study →ProductA sibling-aware bedtime story app, shipped as a PWA
A bedtime story app we designed, built, and shipped ourselves: sibling-aware narration, a parent dashboard, push at bedtime, and a hard privacy boundary at the LLM call. Built for one family, architected for many.
read the case study →