A paid map of where AI can take work off your team, and where it shouldn’t.
Read moreAI consulting & implementation
AI that ships, not AI that demos.
I work with one team at a time to find the workflow AI can actually take over. Then I build it, ship it into your stack and hand you the runbook. I also build the tools I wish my clients already had.
How an engagement runs
- Week 1MapEvery hand-off, every place someone retypes what a machine already knows.
- Weeks 2–5BuildOne workflow, into your stack, with evals.
- Week 6Hand overA runbook a non-engineer can follow.
- Day 30Check inWhat drifted, and what earned the next build.
Two ways in
Hire me, or use what I’ve built.
Same operator, same standards. Pick the one that fits how much of the work you want to own.
Services
I map your workflows, build the one that pays for the engagement, and hand it over. You own it when I leave.
Products
Software I run my own work on, opened up for agencies and operators who would rather drive themselves.
- ContentLoops: Content research and writing for agencies.
- BrittAI OS: Build AI workflows once, deploy them to every client workspace.
What I actually do
Three services. Always in this order.
Nobody starts with a build. The roadmap is what makes the build worth doing.
One workflow, built into your stack, handed over with a runbook.
Read moreI keep it running and add the next workflow when the last one has earned it.
Read moreThe approach
Six weeks, map to handover.
You get me, not a pod. Every week ends with something you can open, click and argue with.
Read the full approach- 1MapWeek 1
- 2BuildWeeks 2–5
- 3Hand overWeek 6
- 4Check inDay 30
What I hold to
Four rules I won’t trade away.
Evals before features
If I can’t measure it behaving, it doesn’t go near a customer.
One workflow at a time
A portfolio of half-built agents is worse than one that runs.
Handover is the deliverable
It isn’t done until someone on your team can run it without me.
Boring beats clever
Most of the value is in plumbing nobody wants to demo.
Insights
All insights
Notes from the work.
ApproachRoadmap
Why every engagement starts with a workflow map
The model is rarely the problem. Not knowing where the work actually gets stuck is.
Read itBuildEvals
Evals before features
Why I write the tests before I write the workflow, and what goes in them.
Read itNewsletter
One workflow, explained, when there’s one worth explaining.
Bring me the workflow that keeps breaking.
Forty-five minutes, no deck. If there’s nothing worth automating, I’ll say so.