News · Invideo AI assigns a different OpenAI model to each step of video production
Invideo AI assigns a different OpenAI model to each step of video production
The Indian startup's multi-agent system uses o3 as orchestrator and delegates scripting, research, moderation, imagery, and narration to distinct models — a case study in task-specific routing.
One model per job, not one model for everything
The most concrete detail in OpenAI's write-up of invideo AI is the division of labor. The company doesn't describe a single prompt-to-video pipeline. It describes a multi-agent system where each OpenAI model owns a specific stage of production.
OpenAI o3 acts as the planner and orchestrator, reasoning about a video's purpose, tone, and target platform, then selecting which models to use for each task. GPT-4.1 turns that plan into a script with structure and pacing. Search-augmented GPT models enrich scripts with timely context. The Moderation API reviews for tone and safety. gpt-image-1 produces backgrounds and branded assets. Text-to-speech models handle narration across languages.
That mapping is the actual architecture. The interesting engineering claim here isn't that AI makes videos faster — it's that invideo AI treats orchestration as a routing problem, where a reasoning model decides which downstream model is best suited to each subtask.
Why the co-founders frame model selection as the product
The invideo AI team is explicit that different models have different strengths, and that matching model to task is the core work.
Our job is to get the best creative outcome, and that means understanding which model excels at which task.Montana Labs
That quote from co-founder Anshul Khandelwal is worth sitting with. It reframes the value invideo AI adds: not the models themselves, which are available to anyone through the API, but the judgment about routing and coordination layered on top of them.
Platform-specific prompts trigger multi-model adjustments
The source gives a specific example of how orchestration surfaces to users. A prompt like "make this video hook work for TikTok" activates GPT-4.1 to adjust pacing and tone, text-to-speech to refine the voiceover, and gpt-image-1 to select high-conversion visuals.
For a headphone ad aimed at urban commuters, that resolves into calm music, a professional tone, and city-relevant imagery. A single natural-language instruction fans out into coordinated changes across three model types. That is the difference between a wrapper and a system.
The claims OpenAI attaches, and their limits
OpenAI reports that invideo AI serves over 50 million users producing more than 7 million videos each month across ads, explainers, and short-form content. It cites users spending 10x less time on production — cutting a day's work to 30 minutes or less — and says many have doubled their revenue.
These are numbers presented in a customer-story context, without methodology. The scale figures are specific; the outcome figures like doubled revenue are attributed loosely to "many" users. Read them as directional evidence of adoption, not as measured benchmarks.
What a roadmap pinned to model releases implies for builders
CEO Sanket Shah says invideo AI's roadmap evolves alongside OpenAI's, with the team revisiting capabilities on each new model release. That is a deliberate coupling: the product's ceiling rises when the underlying models improve.
The specific implication is that invideo AI has built its moat in the orchestration layer — the routing logic, the platform-optimization prompts, the moderation gating — rather than in any single model. When OpenAI ships a better text-to-speech or image model, the multi-agent design lets invideo AI slot it into the relevant stage without rebuilding the pipeline. For teams weighing whether to bet on one model or a coordinated set of them, this is a working example of the latter, with the orchestrator itself being a reasoning model.
Find this story relevant to you?
Contact us to find a unique solution
Need an AI engineering partner that can actually build?
We help businesses integrate AI, build AI-powered products, automate high-value workflows, and modernize the software systems behind them.
Related reading
More analysis around product delivery, operational AI, and the systems work that makes deployment hold up in reality.