The same work keeps coming back
A weekly process gets rebuilt from scratch because the steps, decisions, and context were never captured clearly.
For production companies and post houses
I make movies for a living, and I’ve seen how much time production teams lose to the repetitive office work that keeps everyone on the same page. In a 14-day paid pilot, we build one AI workflow using tools your team already has, and measure whether it actually helps.
The work around the work
Meeting follow-ups. Research. Task routing. Status updates. None of it looks dramatic, but when it lives in five places and one person’s head, it keeps pulling attention away from the work only the team can do.
A weekly process gets rebuilt from scratch because the steps, decisions, and context were never captured clearly.
The process works until that person is busy, away, or trying to remember which loose end still needs attention.
Generic tools and demos create more tabs, not a workflow the team understands and trusts.
“If AI becomes another thing to manage, it’s failed.”
I’m a working film producer. I built these systems to survive real productions, and now I set them up for small teams. These days I’m co-producing EMPIRE CITY, starring Gerard Butler and Hayley Atwell.
I’m not a software company. I started building these systems because I needed an easier way to keep track of projects, turn meetings into next steps, check research, and stop carrying every loose end in my head.
The point isn’t to use more AI. It’s to make one recurring process easier, keep a human in control, and see whether the change actually helps.
Production Office Workflow Pilot
We start with a real office bottleneck, agree on the tools and data boundary, then build something the team can use without me.
The creative work stays with people. The pilot only improves one repetitive office workflow, and every output is reviewed.
A 60-minute working session and a clear map of the current process.
Built inside the tools the team already uses and has approved.
Clear moments where a person reviews, decides, or stops the process.
A short operating guide and training for up to five people.
One agreed metric: time per cycle, turnaround, missed handoffs, rework, or adoption.
A handoff session, then seven days of support while the team runs it without me.
How it works
No open-ended transformation project. One owner, one workflow, one measure.
Days 1–2
Map the current steps, the owner, the approved tools, the data boundary, and a baseline to measure against.
Days 3–10
Create the workflow, put human checkpoints in place, and test it with the person who owns the work.
Days 11–14
Compare it with the old process, train the team, document the system, and decide what happens next.
The trust part
The workflow should make the work easier without asking the team to relax its confidentiality or creative boundaries.
What I already run
These are my own working systems. I’ll only add client numbers once there’s a baseline and permission to share them.
Working solo?
Bring the busywork that keeps interrupting your week. We’ll map the bottlenecks, build three practical workflows, set the privacy boundary, and leave you with a 30-day plan.
Straight answers
No. The creative work stays with people. The pilot only improves one repetitive office workflow, and every output is reviewed. The goal is to give the team back time, not to remove anyone or hand creative judgment to a model.
A repeatable office process that happens at least weekly, has a clear owner, and can be measured. Meeting follow-ups, research, task routing, status collection, and handoffs are good examples.
No. The starting point is the tools the team already uses and has approved. If the process needs a new third-party service, that’s discussed and quoted before anything changes.
We agree on the data boundary first. Scripts, footage, client material, personnel information, financial records, or legal material stay out of any tool the company hasn’t approved.
No savings figure or business result is promised before a baseline exists. What I do promise: a bounded build, training, documentation, and an honest before-and-after measure.
The team keeps the documented workflow. If the result is useful, we can talk about additional workflows or ongoing support. If it isn’t, the measurement will make that clear too.
Start with one process
Bring the recurring work that keeps getting in the way. One short call will tell us whether it’s narrow and measurable enough for the pilot.