We generated 150 video ideas across five frontier models and measured them against every reel we have published. The experiment contradicted the assumption it was built on.
Aditya Bhatt··18 min read
A creator publishing a reel most days needs a continuous supply of ideas, and the supply is the bottleneck — not the filming, not the editing. So we tested the question underneath it: is it better to think hard once, or to sample widely and select? We drew 150 ideas, one per call, across five frontier models, and measured what came back against every reel the creator had already published.
What follows is the whole experiment, including the part where it contradicted the assumption it was built on. We measured how varied the ideas were and how far they sat from work already published. We did not measure whether they are any good — nobody has shot them yet, and that limitation is load-bearing enough that it gets its own section.
This is the write-up. The paper it comes from — the same run, set out formally, with the reference list, the silhouette selection and the interactive figures — reads in full here.
150 / 150
calls that returned a usable idea. None failed to parse.
37
distinct themes in the pool, 23 of them reached by more than one model.
0.392
how close an idea sits to the nearest reel already posted — where his own reels sit at 0.5267.
+17.6
themes bought by taking 5× the draws, against +3.2 for spreading them over five vendors.
01Why run this at all
The creator we ran this for posts a teaching reel most days, to an Indian audience learning AI and data science. A companion analysis of 35 reels found a median of 1,039 views against two breakouts at 34,405 and 58,264. The breakouts shared a shape: they reframed a job title the viewer already holds, and attached a one-word comment keyword to a real deliverable. The floor shared a different shape — eight reels between 458 and 672 views, five of which took exactly zero comments, each explaining a term or reporting a model launch without asking the viewer to decide anything.
That gives an unusually well-specified problem. We know what the target looks like. We know the dominant failure mode. And we have a labelled corpus of prior attempts to measure novelty against. The open question is procedural, and it is the one every person using these tools actually faces: think hard once, or sample widely and select?
02Method
The prompt
One prompt, roughly 5,700 characters, holding the creator’s mission, the measured performance of all 35 prior reels with real view counts, and the rules distilled from them. Two choices in it are load-bearing. It leads with the losers’ shared mechanic rather than the winners’, because “five of the eight worst reels took zero comments” is a more correctable instruction than “career topics win”. And it explicitly retires the winning sentence: the 58k reel’s construction is named as used up, so the models reuse the mechanism underneath it instead of producing 150 variants of one headline.
Sampling
One idea per call, not a list of ten. A model asked for ten ideas optimises the set — it pads after the first strong entry. One idea per call makes each draw independent, which is what makes the 150 rows comparable and the saturation analysis meaningful.
Thirty identical prompts at temperature 1.0 do not explore a space. Models have strong modes and re-sample around them, so the draws collapse onto a handful of ideas in different words. Each call therefore enters through one of 20 rotating lenses — a required angle of attack: the failure mode, the verification problem, the career door outside software, the thing a senior will not tell a junior. Call n uses lens n mod 20, so every model covers the full set at least once.
Models and parameters
We ran five models through OpenRouter, 30 draws each, at temperature 1.0, reasoning enabled, structured JSON output with a parse retry. Two configuration details cost real debugging and are worth recording. Setting provider.require_parameters, the pattern used elsewhere in this codebase to pin routing to schema-honouring providers, removes every viable endpoint for some vendors — Claude Opus 5 returned a 400 for unsupported structured outputs, and GPT-5.6 Sol a 404 for no endpoints found. And reasoning tokens bill against max_tokens, so an initial ceiling of 1,200 was consumed entirely by DeepSeek’s reasoning, returning empty content that looks exactly like a parse bug. The ceiling went to 6,000 after measuring Grok at 3,958 tokens on this prompt.
Measurement
All 150 ideas and all 34 recoverable prior reels were embedded with text-embedding-3-large at 3,072 dimensions, then row-normalised so a dot product is cosine similarity. Ideas were clustered with agglomerative clustering on cosine distance, average linkage, the cluster count chosen by silhouette. Cluster labels come from one model call per cluster; exemplars are medoids, meaning a real idea nearest the cluster centre rather than a synthesised description. Every random component takes a fixed seed (20260802).
03Results
Yield
150 of 150 calls returned a parseable, non-empty idea. No draw was wasted, and no vendor needed a second attempt beyond the parse retry that never fired.
Thematic structure
Silhouette selected 37 clusters. The peak is shallow — 0.1142, with neighbouring values within 0.004 — which is normal for short-text embeddings and means the exact count should be read as “roughly this many themes”, not as a discovered constant. Of these, 23 contain ideas from more than one model and 9 are singletons: one idea no other draw came near.
Generated ideas (150)
Reels already posted (34)
Figure 1.A two-dimensional projection of all 184 embedded texts. Hover anything to read it. The two populations are close to disjoint — the posted reels hold a compact region, and the generated ideas largely sit outside it. That is the visual form of the novelty result below. Two cautions: a 2D projection distorts distance and is shown for orientation only, since every statistic here is computed in the full 3,072 dimensions where these two flat components carry just 11.7% of the variance. And the two populations differ in text form as well as origin — a posted reel is embedded as its topic plus hook, an idea as a single sentence — so some of this separation may be style rather than substance. The baseline test in the next section is what rules that out, not this picture.
GPT-5.6 Sol19 themes
DeepSeek V4 Flash18 themes
Claude Opus 515 themes
Gemini 3.6 Flash15 themes
Grok 4.2014 themes
Figure 2.The same projection, one panel per model, each model’s own 30 draws lifted out of the full pool behind them. Read it for lean, not for territory: no model owns a region, but each has a visible tilt. That mild, real separation is the picture of the within-model versus across-model gap below (0.3856 against 0.3464), and it is the mechanism behind the modest mixture gain — a second vendor lands somewhere slightly different from where a 31st draw of the first would have.
Novelty against the back catalogue
For each generated idea we took the cosine similarity to its nearest prior reel. The mean is 0.392, the maximum 0.5498, the minimum 0.22.
That number is meaningless on its own. A similarity of 0.392 could be far or near depending on how this embedding model scores any two texts from one narrow niche. The reference that matters is how similar the creator’s own reels are to each other.
A posted reel’s nearest neighbour among the other posted reels scores 0.5267. A generated idea’s nearest posted reel scores only 0.392. The generator is therefore working outside the creator’s existing territory, by a margin larger than the territory’s own internal spread. That is the result the raw number was trying to claim, and it survives the control.
The same table carries a caution the headline hides. Generated ideas are more similar to each other (0.6375) than posted reels are to each other (0.5267). The pool is novel with respect to prior work while being internally tighter than the creator’s real range. That is a predictable consequence of the prompt: 20 lenses all pointed at agentic systems, so the output is concentrated on-mission rather than spanning everything he actually posts about. Read it as a deep seam next to the existing catalogue, not a wider catalogue.
Table 1.Nearest-neighbour cosine similarity within and between the two populations. The first row is the baseline that makes the third interpretable.
Nearest-neighbour similarity
Mean
A posted reel, to its nearest other posted reel
0.5267
A generated idea, to its nearest other generated idea
0.6375
A generated idea, to its nearest posted reel
0.392
Figure 3.Distribution of each generated idea’s similarity to its nearest of 34 posted reels. The whole mass sits between 0.22 and 0.5498, well below the ~0.8 region where two texts read as restatements of each other — and mostly below the line marking how alike the creator’s own reels are.
Saturation, and whether 30 draws was the right number
This is the result the experiment was run to get. Resampling the draw order 400 times gives the expected number of distinct themes found after n draws.
All five models pooled
A single model, meaned over the five
Figure 4.Expected distinct themes after n draws, averaged over 400 random draw orders. The upper curve pools all five models; the lower is the mean of the five single-model curves, which is what 30 draws against one model actually buys. The gap at 30 is the entire case for using more than one vendor. The pooled curve is still rising at 150, but see the limitation below: sampling without replacement from a finite pool forces it to terminate at the true total, so the shape of the tail is partly an artifact and only the early slope should be read as a rate.
The marginal return falls sharply and legibly. The first 30 draws yield 19.4 themes, about 0.65 per draw. Draws 31 to 75 add 10.7 more, about 0.24 per draw. Draws 76 to 150 add 6.9, about 0.09 per draw. A run half this size would have found roughly 81% of the themes.
Read the two curves as answering different questions. The gap at 30 draws (3.2 themes) is what mixing vendors buys at a fixed budget. The rise along the pooled curve is what buying more draws buys. The second is much larger than the first, which is the opposite of what this experiment was set up expecting.
Which model contributed what
Within-model similarity (0.3856) exceeds across-model similarity (0.3464). The margin is small but consistent, and it means each model has a recognisable signature: its own draws resemble each other more than they resemble another vendor’s. That is the mechanism behind the mixture gain.
Figure 5.Distinct themes each model reached in its own 30 draws. The spread between best (19) and worst (14) is five themes, so model choice moves coverage far less than budget does. These counts are each from 30 draws and are not comparable to the 37 the pool reached, which came from 150; they compare models to each other, not models to the pool.
Table 2.Per-model contribution. Each model drew 30 ideas, so the theme counts are comparable to each other but not to the 37 found by the pooled 150 draws.
Model
Themes reached
Internal similarity
Similarity to prior work
GPT-5.6 Sol
19
0.3586
0.3437
DeepSeek V4 Flash
18
0.363
0.4092
Claude Opus 5
15
0.4005
0.4002
Gemini 3.6 Flash
15
0.3956
0.3921
Grok 4.20
14
0.4103
0.4148
One asymmetry in that table is worth naming. The least expensive model in the set reached 18 themes; the most expensive reached 15. On this task, at this sample size, price bought no coverage whatsoever. If this is repeated, the efficient configuration is to scale draws on a cheap model and keep one expensive model in the mix for contrast, rather than to spread a budget evenly across vendors.
The themes
Sizes are uneven by a factor of ten. The head of the distribution is where several models converged on the same territory; the tail is where a single draw found something on its own. Both ends are useful for different reasons — the head as consensus, the tail as reach. The 15 themes above the median hold 71% of all ideas, and the 9 singletons at the bottom are where a wide sample earns its keep over a deep one.
Figure 6.Ideas per theme, largest first. Hover a bar for its exemplar and how many models reached it. Every theme is listed in full in the table below.
Table 3.All 37 themes recovered by clustering, ordered by size. "Models" is the number of distinct models that reached the theme; the exemplar is the medoid — the real idea closest to the cluster centre, not a summary of it.
#
Theme
Ideas
Models
Exemplar (medoid)
1
Agentic AI Interview Skills
10
3
Data engineering interviewers are now rejecting candidates who list basic SQL but cannot explain how an AI agent handles tool-call retries during a pipeline failure.
2
ChatGPT Agentic Tool Loops
9
4
If you copy-paste error messages back into ChatGPT until your code works, you are acting as a manual ReAct loop, and you can automate it using a simple 10-line Python agent.
3
Preventing AI Agent Loops
9
3
Watch an AI agent burn 10 dollars in two minutes stuck in an infinite loop over a syntax error, and learn the three-line loop guard that stops it.
4
AI agent loop analogies
8
5
Teach the agent reasoning loop using the non-technical analogy of a cricket captain who observes the pitch and score then decides the next bowler or field change in a continuous cycle until the team wins.
5
Agentic MIS Automation
8
2
Month-end MIS report: pehle 3 ghante VLOOKUP aur copy-paste, ab ek agent loop 4 minute mein banata hai, aur aapka kaam report banana nahi, report ko galat sabit karne ki koshish karna ban gaya hai
6
Agentic Portfolio Projects
8
4
Data science freshers can build one simple ReAct agent that cleans a messy dataset on its own and explains every decision as their first portfolio piece.
7
AI Data Literacy
7
5
Bust the claim that you don't need to learn SQL because AI writes it. The real skill is auditing AI-generated queries.
8
Agent Evaluation Careers
7
3
Audit 50 live Indian agent-evaluation jobs, show their salary range, then teach QA testers to build one tool-failure test as a portfolio sample.
9
Agentic Data Career Upskilling
7
3
Compare the 6 LPA salary cap of traditional SQL data engineers with the 14 LPA average for agentic pipeline builders, showing the exact 3-week skill path to make the jump.
10
Auditing Agent Data Outputs
7
3
Agent ne SQL likha, number plausible laga, revenue 3x inflate ho gaya: teach the 30-second maker-checker audit (COUNT(*) before vs after JOIN, plus COUNT(DISTINCT order_id)) on agent output.
11
AI Agent Decision Checks
6
4
Stop pushing AI-generated Python scripts blindly: here is the three-step audit loop every junior developer must run to verify agent code before shipping.
12
AI Tool Schema Design
5
3
The quietly mandatory skill of writing precise tool descriptions so AI agents pick the right data functions that most people are missing with one before-after example.
13
Agentic Data Analysis Loops
5
1
Your repeated cycle of inspecting a messy dataset running a fix then validating the output again is an agentic loop you have been running without the name and here is how to hand it to an AI agent.
14
Agentic Loops for Beginners
5
1
An agent is just a while loop with a goal. Collapse the entire buzzword into: while (not done) { do something }. Once a beginner sees that, they can debug any agent, build one themselves, and stop being intimidated.
15
Human Audited Data Agents
5
2
Show how cleaning a messy 10,000-row Excel file shifted from writing manual Pandas scripts to writing validation rules for an agent, turning a 3-hour cleanup into a 5-minute audit.
16
AI Agent Failure Loops
4
3
Watch a data agent fail by repeating the exact same invalid SQL query in a visible loop on your screen because it skips its own error output
17
AI Reframing Analytics Roles
4
3
Reframe the MIS Analyst role. Agents now automate the entire report generation workflow, from pulling data to formatting. The human job shifts to defining the business question and validating the output. The reel shows a before and after of a typical week, then teaches the one skill that matters: writing clear instructions for an agent and double-checking its work. Comment MISSHIFT to get a prompt template for automating your weekly MIS report.
18
Agent Failure Debugging Skills
4
2
500 log apply karte hain, 1 select hota hai: luck nahi, ek capability hai. Working agent demo ab free hai, so interviewer sirf ek cheez pooch raha hai: tera agent kahan toota aur tu ne kaise pakda. Banao ek 3-entry failure log.
19
Resume Worthy AI Agents
4
3
How to upgrade a basic college Python project into a tool-calling AI agent that actually gets a fresher resume shortlisted.
20
Idempotent Agent Operations
3
2
Idempotency ka matlab ek line mein: agar aapka script do baar chala aur table mein data double ho gaya, to koi agent use nahi kar sakta. Fix: INSERT ko key-based MERGE banao.
21
AI Agent Output Auditing
2
2
QA Engineer ka agent-era test: final answer nahi, uske tool calls check karo, kyunki correct output ke peeche unsafe action chhup sakta hai.
22
AI Agent Runtime Visibility
2
1
Jupyter notebook ka hidden state: kernel me variables zinda hote hain jo .ipynb file me dikhte hi nahi, isliye AI agent aapka notebook padh kar galat code likhta hai. Fix: Restart and Run All se pehle agent ko mat bulao.
23
AI Agents Reshape ETL Roles
2
2
How agents reshape the ETL Developer job by handling pipeline logic in reasoning loops leaving you to define success metrics and intervene on failures.
24
AI Logistics Exception Agents
2
2
Build a logistics exception agent that checks delayed shipments, calls weather and tracking tools, then reroutes or escalates to a human.
25
Agent Tool Description Design
2
1
Freshers ka entry point agent banana nahi hai, agent ke liye tool likhna hai: dikhao ki ek function ka docstring badalne se agent sahi ya galat tool uthata hai, phir 5-tool repo banwao.
26
Agentic Pipeline Guardrails
2
2
Senior engineers know but do not tell juniors that agentic data pipelines fail from unchecked loops on uncertain results so set explicit confidence thresholds to force a stop.
27
GitHub Copilot coding context
2
1
Why GitHub Copilot copies your outdated coding patterns: open files become context, so close stale tabs and open one correct example before asking it to code.
28
Human Approved SQL Agent
2
2
Build a 'SafeSQL Agent' – a natural language to SQL tool that asks your permission before running any destructive query (DELETE, UPDATE, DROP).
29
AI Agent Contracts
1
1
An agent is a house contractor, not a genie. Here is the contract you must write.
30
AI Driven Software Testing
1
1
Senior developers are not writing functions anymore, they write automated test cases to check if AI agents generated correct code, and juniors must learn LLM evals to stay relevant.
31
AI SQL Cost Risks
1
1
Agent-written SQL runs fine and still bankrupts you: put EXPLAIN in front of one AI-generated query and read the rows-scanned number, because the planner, not your query, decides cost.
32
AI agent cost accounting
1
1
Agent har loop mein poori chat dobara bhejta hai, so 10 steps ka bill 10x nahi lagbhag 40x hota hai; isliye apne project ke README mein likho: rupaye per completed task.
33
Agent Loop Termination
1
1
In interviews, they now ask: How do you stop your agent from running forever? Here's the answer that shows you're not a beginner.
34
Agent Readable Metric Contracts
1
1
BI Developer ka new edge dashboards nahi, agent-readable metric contracts hain: har KPI ke source, filters, formula aur edge cases clearly define karo.
35
Agent loops and verification
1
1
Explain an agent’s loop through a Swiggy rider who checks the map after every turn, then show why a precise delivery pin is the agent’s verifiable finish line.
36
Database Migration Validation
1
1
Before and after: the database migration check
37
LLM Context Truncation
1
1
Explain the mechanism of context truncation in LLMs like ChatGPT and how it changes where you should place the most important instruction in a prompt.
04What it means
Separating scale from mixture
The design confounds two variables, and the tempting summary — “one model reached 16 themes, five models reached 37” — silently compares 30 draws against 150. The honest accounting is less dramatic than that sentence.
Mixture, at fixed budget. 30 draws spread across five models find 19.4 themes; 30 draws on one model find 16.2 on average. Pooling buys 3.2 themes, about 20% more coverage for the same money. Real, worth having, not transformative.
Scale, at fixed mixture. Going from 30 draws to 150 takes coverage from 19.4 to 37.0 themes. That is the larger effect by a wide margin.
So the headline is that scale mattered more than model choice, with mixture a secondary bonus. This inverts the intuition the experiment was designed around. If a budget is fixed and something must give, take more draws before taking more vendors. The practical caveat is that mixture is nearly free to add — it is a list of model ids — while scale is linear in cost, so there is no reason to give up the 20%.
The lens rotation did its job
Mode collapse was the expected failure of this design, and it did not occur. A companion word-overlap analysis of the same 150 rows found zero cases of a model repeating itself, and all 20 lenses were represented in the output. The cost of that insurance was writing 20 lines of prompt.
Where the models did converge is informative rather than embarrassing. Two themes were reached independently by all five vendors: AI agent loop analogies (8 ideas) and AI Data Literacy (7 ideas). All five vendors landing separately on the same ground suggests those are optima of the evidence itself rather than a quirk of one model’s training. Against that, 14 of the 37 themes came from a single model — which is the clearest argument in the run for not standardising on one vendor.
05What this does not show
We measured diversity and novelty, not quality. This is the important one. Nothing here shows these ideas will perform. Distinctness in embedding space is a necessary condition for a useful idea pool and nowhere near a sufficient one. The honest test is to shoot several and compare against the 1,039-view median, which has not been done.
The cluster count is soft. A silhouette peak of 0.1142 is weak in absolute terms and the neighbouring candidates are within 0.004 of it. Read 37 as an order of magnitude for the thematic range, not a measured constant. Every downstream count inherits that softness.
The saturation tail is partly an artifact. The curve resamples a finite pool without replacement, so it is forced to reach exactly the true total at n=150. Real additional draws would keep finding new themes at some low rate past that point. Only the early slope is a trustworthy rate; the flattening is real in direction but overstated in degree.
One prompt, one topic, one day. All 150 draws share a single prompt on a single niche, run in one session. Nothing here establishes that the pooling advantage generalises to another domain, another prompt, or these same models next month.
The pool is narrower than the creator’s actual range. Generated ideas cluster more tightly around each other (0.6375) than his posted reels do (0.5267). A run intended to broaden topical range needs a different lens set, and this experiment says nothing about how that would perform.
Embedding similarity is a proxy for sameness, not a definition of it. Two ideas with different wording and the same underlying premise can land far apart; two with shared vocabulary and different intent can land close. The clusters were spot-checked and read sensibly, but no human labelled all 150.
Prior work is 34 reels, not 35. One posted reel had no matched script and therefore no topic text to embed, so it is absent from every novelty comparison.
06Conclusion
The question was whether to think hard once or sample widely and select. On this task the answer is sample widely, with two corrections to the naive version of that advice.
The width that matters is draws, not vendors. The experiment was built on the assumption that mixing five frontier models was the lever. It is not. At a fixed budget of 30 draws, mixing buys 3.2 extra themes over a single model — roughly 20%. Multiplying the draws fivefold buys 17.6. Both are real; they are not the same size. Mixture survives as a recommendation only because it is nearly free to add, while draws cost money linearly.
The sampling needs structure or it does not scale. Thirty identical prompts at temperature 1 re-sample one region. The 20 rotating lenses cost twenty lines of prompt and produced zero within-model repetition across 150 draws, with every lens represented. Without that, this experiment would have measured the cost of rediscovering the same four ideas thirty times. Any attempt to replicate the yield reported here without a diversification scheme should expect a fraction of it.
What the pool is. 37 distinct themes, sitting genuinely outside the creator’s existing work: an idea is further from its nearest posted reel (0.392) than his reels are from each other (0.5267). It is a deep seam rather than a wider catalogue, because all 20 lenses point at agentic systems. For zero failed calls out of 150, that is a favourable trade against the alternative — a creator staring at a blank page.
Every measurement here is of the pool’s shape, not its worth. Distinctness and novelty are necessary conditions for a useful idea, and neither is sufficient. The next run is the one that shoots a handful of these and puts real view counts against them, and that is the number that will settle whether any of this mattered.