AI built around how your business runs.
I’m James. I find the repetitive work costing your business time, then build AI to handle it without replacing the software you already use. A month later, I come back and check it is still working.
20+ years in operations, including 3 at Meta. You work directly with me.
Reply from me, not a bot. Within a business day.
A request and approval process I rebuilt at Meta.
Read what changed →What this has changed
Results from the work, not the demo.
10 days to 2
Procurement request and approval time at Meta.
5+ hours back per operator, every week
One Meta project, used by 75+ operators.
30+ tools down to 3
Across three teams and 350+ people.
Where I look first
The work your team should not still be doing by hand.
Intake and queues
The inbox or ticket queue your team has to sort before work starts.
Approvals
Requests waiting while the same checks happen by hand.
Recurring reports
The numbers somebody still assembles every Friday.
Follow-ups
Work that moves only when one person remembers to chase it.
Want to see the small version first? The email brief and Friday report are free to build from the guides.
How I work
Find the hours that leak.
Scope, test, and number, agreed first.
Built in your accounts. You own it.
It stuck, or you don’t pay.
A bit about me
One person from the first look to the finished build.
I’ve spent more than twenty years in operations, helping companies grow from $100K to $250M+ and running operations through a $350M sale. The last three years were at Meta.
I find the work, write the code, ship it with your team, and come back to check it is still being used. The plan and the build never change hands.
A note on this site
The AI system I run built it. I made the calls.
That story is useful proof that I build with AI myself, but it comes after the operating results because those are the work you are here to judge.
What’s the one thing you’d want handled by Friday?
Not sure where AI fits yet? Finding it is the first step, and if it doesn’t stick, you don’t pay.