
- Client
- Internal · FANG Studio
- Year
- 2026
- Timeline
- 6 weeks · in daily use
- Role
- Product design, Agent architecture, Integrations
- Stack
- Next.js · Claude API · MCP · Google Workspace · Postgres

A studio's day is mostly admin nobody wants to click through.
Client notes, meeting follow-ups, files and calendar live in five tools. We built Squirrl for ourselves first: a single orb you talk to that knows every client, can read every doc and acts (schedules, files, drafts) with a human approving anything that leaves the building.
- ProblemContext scattered across five tools, re-typed daily
- BetVoice plus agents beats another dashboard
- ConstraintNothing sent or deleted without a human in the loop
What we built.
Squirrl in four parts, the pieces that carried the product, in the order we shipped them.
- (01)
The orb
Push-to-talk voice surface with streaming transcription; the whole interface is one conversation with memory per client.
- (02)
Agent + tools
Claude with MCP tools over calendar, docs, mail and CRM. Every write action is proposed first, executed on approval.
- (03)
Client memory
Per-client context built from notes, threads and docs, retrieved on demand, never stuffed into one prompt.
- (04)
Quiet UI
Cards for today, recent clients and documents surface only when relevant, the screen earns attention, it doesn't demand it.


What it did.
Numbers shared as ranges; specifics on request.
- (01)
Used daily by our own team
Runs FANG's client admin, scheduling, follow-ups, files, with a person approving every action.
Adoption - (02)
Zero unreviewed sends
Guardrails held: every outbound action approved by a person, logged and reversible.
Safety - (03)
Productised
Squirrl is now the reference build for our AI-workflow offers, see Automation on the Work page.
Offer
Build something that ships.
Start a project