Gig
8–$12/hour
20
Aug 4, 2026
LOCAL AI VIDEO PIPELINE DEVELOPER
ComfyUI, n8n, Python, FFmpeg, Windows 11, and NVIDIA GPU
ABOUT THE PROJECT
Wealth Crafted Futures LLC is building a completely local, automated AI short-video production system.
The finished system must allow a non-technical user to place a complete story or script into an input folder, select a few project options, and start production without manually operating multiple AI programs.
This is not a normal video-editing position. I need an experienced developer and systems integrator who can connect reliable existing open-source programs, repositories, and models into one working local pipeline.
The target computer runs Windows 11 with:
• NVIDIA RTX 5080 16 GB
• AMD Ryzen 9 5950X
• 96 GB RAM
• Multiple NVMe drives
• No paid cloud services or paid AI APIs
PRIMARY RESULT
I should be able to:
1. Add a complete story or script.
2. Select the desired language, voice mode, and production settings.
3. Click Start.
4. Have the system automatically create the project folders.
5. Break the story into episodes, scenes, and shots.
6. Generate the video segments.
7. Generate narration or individual character voices.
8. Generate accurately timed captions.
9. Add audio and assemble the segments.
10. Export completed vertical short-form videos.
11. Resume a job after an interruption without restarting completed work.
PIPELINE REQUIREMENTS
The finished pipeline must:
• Run locally on Windows 11.
• Be optimized for an NVIDIA RTX 5080 with 16 GB VRAM.
• Use only free and open-source local software.
• Have zero required paid APIs, cloud services, subscriptions,s or usage fees.
• Use existing reliable open-source repositories before building features from scratch.
• Verify that every selected repository works on Windows and the RTX 5080.
• Verify the license and commercial-use requirements of every dependency.
• Include n8n or another suitable local workflow orchestrator.
• Use Python for custom automation and integration where needed.
• Use FFmpeg for video and audio processing.
• Use ComfyUI or another proven local generative-video workflow system.
• Provide a simple local web interface or desktop interface for the user.
• Include logging, retries, checkpoints, and clear error messages.
PROJECT-FOLDER AUTOMATION
When a newscript is added, the system must automatically create a new project folder named after the story.
The project folder must contain organized subfolders for:
• Original script
• Story bible
• Character registry
• Character reference images
• Locations
• Props
• Scene breakdowns
• Shot plans
• Prompts
• Continuity information
• Generated images
• Generated video segments
• Narration and character voices
• Music and sound effects
• Captions
• Intermediate renders
• Completed episodes
• Quality-control reports
• Logs
• Project configuration
• Recovery checkpoints
STORAGE RULES
All permanent programs, repositories, models, project data, and completed outputs must be stored on the D: drive.
Temporary runtime processing must use:
E:\WCF_Short_Video_Temp
The E: drive is for active-job scratch data, extracted frames, temporary renders, caches, interpolation files, upscaling files and other transient processing.
Completed or required files must be moved back to the appropriate D: drive project folder.
VIDEO STRUCTURE
Each completed episode must be approximately one minute long.
Each one-minute episode will normally be created from four connected 15-second video segments.
The system must preserve:
• Character appearance
• Clothing
• Locations
• Props
• Story details
• Camera direction
• Voice assignment
• Visual style
• Continuity between segments
• Continuity between episodes
A normal series will contain 20 connected one-minute episodes with a real beginning, middle and ending.
The pipeline must also allow a series to be extended beyond 20 episodes when selected.
VOICE, LANGUAGE AND CAPTION OPTIONS
The user must be able to select:
• Narrator-only mode
• Individual character voices
• Narrator plus character voices
• Output language
• Caption language
• Burned-in captions
• Separate SRT or VTT caption files
Narration, character voices,s and captions must be generated locally.
The system should support adding more languages later without rebuilding the entire pipeline.
SCHEDULING AND JOB CONTROL
The pipeline must support a production schedule that can run from approximately 8:00 AM until 6:30 AM the following day, or stop after producing 20 completed one-minute episodes.
It must include:
• Start
• Pause
• Resume
• Stop after current step
• Retry failed step
• Skip an approved failed item
• Production queue
• Completed-job history
• Error log
• GPU-memory error handling
• Safe recovery after Windows restarts
USER INTERFACE
The user should not need to edit code or manually operate every underlying program.
The interface should include:
• Select or import script
• Project name
• Visual style
• Aspect ratio
• Resolution
• Number of episodes
• Narrator or character-voice mode
• Language selection
• Caption options
• Start, pause, and resume controls
• Current production stage
• Progress for each episode
• Error and warning display
• Preview and approval controls
• Open project folder button
DELIVERABLES
The developer must provide:
• Complete source code
• Git repository with organized commits
• All n8n workflows
• All ComfyUI workflows
• Python scripts
• Configuration files
• Dependency and model list
• License report for every major dependency
• Windows installation scripts
• Start and shutdown scripts
• Backup and recovery instructions
• User manual
• Developer documentation
• System architecture diagram
• Troubleshooting guide
• Test scripts
• Example project
• No hidden paid services or personal developer accounts
The system must not depend permanently on the developer’s computer, account, API key, cloud storage, or subscription.
MILESTONE DOCUMENTATION
At every stopping point or milestone, the developer must create or update a self-contained Markdown review file named PROJECT_REVIEW.md.
It must contain:
• Exact repository state
• Work completed
• Files created or changed
• Test results
• Failed tests
• Problems discovered
• Fixes applied
• Known limitations
• Current Git branch and commit
• Any authorization needed
• Exact recommended next action
ACCEPTANCE TEST FOR THE FIRST WORKING VERSION
The first working version will be accepted when it can:
1. Accept a sample script through the user interface or input folder.
2. Create the complete story project folder structure.
3. Break the script into scenes and four connected shots.
4. Generate or process four approximately 15-second segments.
5. Generate local narration or character voices.
6. Generate synchronized captions.
7. Join the four segments into one completed one-minute vertical MP4.
8. Save all permanent project files to the D: drive.
9. Use the E: drive for temporary processing.
10. Resume after an intentional interruption.
11. Produce logs explaining every completed or failed step.
12. Complete the process without a paid API or cloud-generation service.
REQUIRED EXPERIENCE
Applicants should have real hands-on experience with several of the following:
• Python
• n8n self-hosting and workflow development
• ComfyUI workflows and custom nodes
• FFmpeg
• Windows automation
• NVIDIA CUDA and VRAM optimization
• REST APIs and local APIs
• Git and GitHub
• Docker where appropriate
• Local text-to-speech
• Local transcription and caption generation
• Generative image or video models
• Queue systems, checkpoints and error recovery
HOW TO APPLY
Start your application with the exact words:
LOCAL-5080
Applications that do not begin with LOCAL-5080 may not be reviewed.
Please answer all of these questions:
1. Describe the most similar local AI or video-automation system you have personally built.
2. Provide a link, screenshot, or short screen recording showing a real ComfyUI, n8n, or Python automation you built.
3. Have you installed and optimized local AI software on Windows with an NVIDIA GPU?
4. What open-source tools would you initially evaluate for this project?
5. How would you prevent character and story continuity from being lost between video segments?
6. How would you make a failed production job resume without repeating completed work?
7. How would you verify software licenses and prevent required ongoing fees?
8. What would you build during the first paid milestone?
9. Estimate the hours required for the proof of concept and the first usable MVP.
10. State your hourly rate and weekly availability.
Do not send only a generic AI-generated cover letter. Specific technical answers and proof of previous work are required.
HIRING PROCESS
The hiring process will include:
• Portfolio and technical-answer review
• Short video interview
• Paid technical planning task
• Paid proof-of-concept milestone
• Full build divided into approved milestones
No applicant will be asked to complete custom production work for free.
This begins as a project-based position. Continued maintenance and future automation projects may be available for someone who produces reliable, documented work.