Lab
The tools we built for ourselves.
Most studios talk about AI. This is the part of ours you can actually look at: internal tools we run every day, shown in full, including the places we deliberately stopped the automation and put a person back in.
We build our own tooling because the routine work of running a studio, watching search, chasing enquiries, keeping records straight, is exactly the kind of work worth handing off. Everything here is in daily use. Nothing here is a prototype or a concept, and if we stop running something we will take it down rather than leave it up as decoration.
-
01 / Internal tool, in daily use
SEO Workbench
A read-only Search Console workbench that briefs an AI agent, ranks the work, and keeps a person in the loop.
Look inside it- Source files
- 71
- Lines of code
- 7,961
- OAuth scope
- read-only
- Third-party services
- none
-
02 / Internal tool, in daily use
Content Control Room
A content operating system that drafts with Claude, gates the output, and refuses to publish on its own.
Look inside it- Source files
- 82
- Lines of code
- 21,033
- Model
- claude-sonnet-5
- Autonomous actions
- zero
-
03 / Internal tool, in daily use
Studio CRM
A local client pipeline that answers one question in two seconds: who needs chasing today.
Look inside it- Source files
- 30
- Lines of code
- 2,822
- AI features
- none
- Cloud services
- none
Start a project
Got routine work worth handing off?
Tell us what eats the most time in your week. We'll tell you honestly whether it's worth automating, and what we'd build first. You'll hear back from Jake directly.
Three questions · about a minute
See the work