For production companies and post houses

Practical AI systems for the work around the creative work.

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 seven-day build, we create one AI workflow in tools your team already uses, compare the first cycle against the baseline, then support the team for seven days after handoff.

Book a fit call See what the pilot includes

One workflow7 daysHuman stays in control$2,500

KaMeek Lucas Taitt monitoring a shot on a film set — On set

EMPIRE CITYCo-producer

PARAMOUNT PICTURESProduction experience

LOVE AND MONSTERSFeature film

NAUTILUSAMC television series

The work around the work

It matters. It also eats the day.

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.

The same work keeps coming back

A weekly process gets rebuilt from scratch because the steps, decisions, and context were never captured clearly.

One person carries the system

The process works until that person is busy, away, or trying to remember which loose end still needs attention.

AI becomes another thing to manage

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

One workflow, built and measured in one week.

AI handles the noise. Your project tool stays the record of truth. 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.

Workflow audit

A 60-minute working session and a clear map of the current process, its owner, the approved tools, and a baseline.

One workflow, built in your tools

Built inside the project tool your team already uses and has approved.

The noise turned into actions

Email, meeting notes, voice notes, and documents become clean tasks with an owner, a destination, and a date when needed.

Proposal-first checkpoints

The system proposes; a person approves before anything is created, sent, or scheduled.

One trusted record

Every entry is verified into the right place with the right owner and date, so the work lives in one place instead of five.

Handoff, measure, and support

A short operating guide, training for up to five people, the baseline-versus-first-cycle comparison, and seven days of support.

How it works

Small enough to judge honestly.

No open-ended transformation project. One owner, one workflow, one measure.

Days 1–2

Choose the right bottleneck

Map the current steps, the owner, the approved tools, the data boundary, and a baseline to measure against.

Days 3–5

Build and test

Create the workflow, put the human checkpoints in place, and test it with the person who owns the work.

Days 6–7

Measure and hand over

Compare the first cycle with the old process, train the team, document the system, and decide what happens next.

The trust part

Draw the line before we build.

The workflow should make the work easier without asking the team to relax its confidentiality or creative boundaries.

Inside the pilot

Approved existing tools
One named process owner
Human review and decision points
An agreed baseline and success measure

Outside the pilot

Confidential material in unapproved tools
Unattended external messages or production decisions
Creative judgment delegated to a model
Open-ended custom software or enterprise integration

What I already run

Real operating examples. Not invented client results.

I’ve run my own production work in Basecamp since 2017. That’s where this system was built and stress-tested. If your team runs on Asana, Notion, Monday, or Trello, the same pattern applies.

These are my own working systems. I’ll only add client numbers once there’s a baseline and permission to share them.

Project memoryAn AI collaborator that keeps approved context inside clear rules.

Task routingProject planning and follow-ups routed into Basecamp.

Meeting follow-upConversations turned into reviewed next steps.

Checked researchClaims distilled into decisions with sources reviewed.

Script supportAnalysis that sharpens judgment instead of replacing it.

YouTube planningResearch, scripting, and production planning kept in one flow.

Working solo?

The 90-minute AI Workflow Session is still available.

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.

Book the $350 session →

Straight answers

Questions you’re probably asking.

Will this replace our team or the creative work?

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.

What kind of workflow makes a good pilot?

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.

Do we need to change all our tools?

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.

Do we have to use Basecamp?

No. Mine runs on Basecamp and has since 2017, which is where I built and stress-tested this system. Your pilot gets built in whatever your team already uses and has approved.

What happens to confidential material?

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.

Is the result guaranteed?

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.

What happens after the seven days?

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

What keeps slowing your production office down?

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.

Book the fit call → Review the pilot