PXLnexus
Writer
Script and shot list from the brief. The first pass on paper, scene by scene, shot by shot.
Department: Script.
Every department.
Every tool. Connected.
AI production orchestrator, powered by 
The AI production orchestrator, from script to delivery, on your own servers.
Fourteen roles.
One orchestrator.
Every role reads the same show brain, and each is a Claude Code agent with its own skills. Select a role to see what it does; select the centre to see the brain.
reads the show brain
Bordered cards: AI agents, each a Claude Code agent with its own skills. Plain: people and apps
Select a department to see the role that runs it
Where the days go
AI is more than image making.
It finds where your show loses days.
Most conversations about AI start and end with the picture. For a studio, the images are becoming the cheap part.
The days go into the work around them: the bid, the setup, the handoffs, the notes, the tracker. This is how most shows still run.
PRE-PRODUCTION
PRODUCTION
POST-PRODUCTION
PROJECT MANAGEMENT
Script
Delivery
01The bid, by handTypical: weeks
02Show setup, rebuiltTypical: 2 to 5 days, every show
03Script to animaticTypical: 4 to 6 weeks
04Handoffs between departmentsTypical: 1 to 3 days lost per error found late
05Notes and versionsTypical: 1 to 2 days per review round
06The tracker, kept by handTypical: about a day a week of producer time, all show long
The traditional way, as most shows still run today. Timings are rough and typical, and change with the size of the show.
Select a box to see where the days go.
Even a studio with a pipeline runs a generic one, the same standard for every show. But every project has its own needs, and they can be read at the start, before the first day is lost. That is where PXLnexus begins.
The orchestrator
One brain for the show.
PXLnexus runs on Claude Code, and it works like a small team of specialist roles.
They all read from one show brain: the bible, the script and the shot list, the decisions, the time spent. So the shot list, the animatic, the bid and the tracker stay in step instead of drifting apart.
IN
THE SHOW BRAIN
THE ROLES
A PERSON
OUT
InputScriptthe story, page by page
InputBriefsclient, director, agency
InputShow specformat, length, delivery
One per showThe show brainThe bibleThe script and the shot listThe decisionsThe time spentAbout a hundred house methods, each written once as a skillbible · script and shot list · decisions · time
CrewWritingwriter, copywriter
CrewArt departmentart director, storyboard, previs
CrewProductionproducer, coordinator
CrewPost and revieweditor, colorist, sound, VFX sup
GateA person approvesevery pass
OutputA first version of everythingThe naming conventionsThe key decisionsThe show bibleThe presentationsThe onboarding pagesReviewed and corrected, never from a blank pagenaming · decisions · bible · presentations · onboarding
the brain feeds every roleSelect a box to see what it does
Select a box to see what it does.
Linked live
It drives the apps directly.
A person makes the call.
PXLnexus works inside the applications through MCP bridges: Maya, with mAIa doing the routine scene work, Unreal, ComfyUI, Premiere, DaVinci Resolve and ElevenLabs. It speeds up the regular process, not only the pictures.
WHERE IT ACTS, FROM THE SCRIPT TO DELIVERY
powered by 01PLANscript to plan
02MAKEthe shots
03TRACK + REVIEWthe record and the notes
04DELIVERYthe cut, the grade, the sound
linked live over MCPAI inside the app (mAIa in Maya)Select a stage or an app to see what runs there
Select a stage or an app to see what runs there.
Underneath
The bid becomes the production.
PXLnexus drives PXLsuite, the pipeline underneath. Every tool follows one production standard.
PLAN
TRACK + REVIEW
MAKE
Every tool follows one production standard; the core tools read it
Script to breakdown, bid and schedule.
The assets the bid calls for, waiting before anyone starts modelling.
The tracker, laid out from the bid.
Every version reviewed; the note goes straight back to the tracker.
Every application connects through it, on one standard.
The tools inside every application.One system, the whole production.
PXLnexus orchestrates PXLsuite, the ComfyUI workflows for image, video and 3D running on our own machines, and the partner tools from Reallusion, Faceform, 3D.sk, XGRIDS, Volinga, Dash and Lightcraft, each one removing a whole step. Tested on a full CG series and a Nike spec spot.
Set up at your studio
Built on site, around your pipeline.
I come in as a consultant and build the setup at your studio: your conventions, rates, departments and people fed in before the first show runs.
The setup is organised in three layers so the same method runs on your terms without touching what already works.
Your files and the brain stay on your servers. For NDA work the model runs on your studio’s own cloud account, so nothing ends up in a public tool. If you already have a tracker, it stays the system of record.
Results
Script to locked animatic in about 2 days, not 4 to 6 weeks.
Tested end to end on a 34 second Nike spec spot*. PXLbid broke the script into shots and assets, ComfyUI made the storyboard and the look frames, and Animatic Builder laid the cut out in Maya.
Days per department
0
2
4
6
8
days
Script + shot list
copywriter, director
Storyboard, 18 panels
storyboard artist
Look frames, environments
concept artist
Characters + kits
character designer
Animatic
editor
Sound: music, FX, voice, mix
composer, sound designer, voice
End card animation
motion designer
1.9days
so far, against 20 to 29 for a small conventional crew.
About 15 to 20 days
for the whole spot, projected, solo, against 83 to 122 for a crew.
Maya, Nuke, Unreal and Premiere are on both sides of the comparison. The gain is the pipeline.
Script
Storyboard
Look frames
Characters
Animatic
Sound
End card* Speculative test project
Built by Cristian Spagnuolo
VFX & CG Supervisor
Over twenty years in VFX and CG, with DNEG, MPC, Mill Film, Framestore and Pixomondo, among others. Former 3D Generalist, now also a pipeline consultant. I co-created Thresholds and am currently supervising it; PXLsuite is the pipeline I built to run it, and every tool is hardened on that show before it reaches anyone else.
- Autodesk Certified Professional
- Autodesk Approved Instructor
- Proud member of
- Clients and productions
- Studios I’ve worked at
...among others.- Thresholds partners
Partners of Thresholds, the CG series I co-created and am currently supervising.
How we start
- Feed inYour studio pack: conventions, rates, departments. Plug in your tracker.
- Run one showOne production through PXLnexus. Your people confirm every pass.
- MeasureThe days, against how you run it today.
- Roll outKeep what pays off, and take it to the next show.
Start with one show.
Everything I build starts from something I watched go wrong on a real show, and that’s how I’d start with a studio. I come in as a VFX & CG Supervisor, not only as the person with the tools. I read the show before I touch it, and I’m on it while it runs.
A conversation first. If it fits, a pilot on one of your shows.
Book a call
PXLbid
PXLflow