We made 5,000 campaign ideas. Strategists kept the plain ones.

We asked an AI for 40 campaign ideas and got 14 — the rest were the same ideas re-worded. So we spent $110 testing every published fix, up to and including surgery on a 72-billion-parameter model's weights. What actually widened the ideas wasn't what anyone predicted.

The bottom line, up front

  1. Ask a frontier model for 40 ideas and you get about 14. One premise appeared seven times in a single batch. The collapse is baked into the model by preference training, not a settings problem.
  2. The settings don't work, but the way you ask does. Temperature and the other famous knobs still do nothing. Two simple changes do: ask for all forty ideas in one go instead of in small batches, or show the model its earlier ideas and ask for more. Each one buys you a third more ideas you haven't seen before. Neither makes the ideas any better.
  3. AI judges cannot score originality. Four frontier models agreed with a blind human read 43–55% of the time. Coin flips.
  4. A better brief gets you better ideas, not more of them. Naming the goal, allowing tangents and asking for a through-line didn't widen the set. It raised the share of ideas a strategist would actually run. Those are different jobs, and the brief does the second one.
  5. Different model lineages have different favorite ideas. Pooling four generators tripled the distinct viable ideas (21 → 64) with almost no overlap between sources. The widest swath comes from a portfolio, not a better prompt.
  6. The best thing we found: have one model write forty one-line idea seeds, then have a second model write each seed up properly. Our strategist would pitch 23 of those 40 ideas, and almost none of them were ideas we had seen before. No other method came close on both counts at once.

The basin is real, and deeper than you think

Every aligned language model has favorite ideas. Ask for 40 earned-media campaign concepts and 18% of them are the same idea — "humans vs. AI, blind test" — wearing different headlines. 57% sit in one emotional register. Clustered strictly for "same idea," a 40-idea batch holds roughly 14 actual ideas.

This isn't randomness failing you. Preference training teaches models that typical answers are good answers — researchers call it typicality bias — so the model learns to stay near the middle of everything it knows. The 2026 literature is close to unanimous that the collapse lives in the weights, and our measurements agree:

  • Temperature does nothing. Max versus low temperature on the same model: 17 vs 14 distinct ideas. Noise.
  • Verbalized sampling barely moves a frontier model. The paper-faithful version scored within noise of a random-constraints control, three replicates.
  • Self-rewording helps the count, not the reader. Spec-first decomposition — have the model write 40 maximally-different one-line specs, then render each — reliably doubled distinct ideas. It led our scoreboard for two full rounds. Then a human read the output.

Wider isn't better: the viability trap

We had a strategist blind-read whole 40-idea batches and tick every idea he'd actually take to a client. Plain prompt: 33 of 40 viable. The spec-first "winner": 22 of 40. Cluster the survivors and both land near 12 usable, distinct ideas. The diversity machinery bought its spread almost entirely with ideas a human throws out.

Almost every method that widened the set did it by escaping the brief instead of escaping the basin.

A "provocation" instruction — render each idea as the strangest version of itself — made the trap vivid: machine-scored originality soared while human-scored viability collapsed to a 0.28 win rate. Surprising and un-runnable is not a campaign.

Update (September 2026): seven more readers, one conclusion moves

Because this result carried so much weight, we re-ran it as a panel: seven Fractl strategists blind-read the same plain and spec-first batches on both briefs — same sheets, same tick-every-viable instruction, no knowledge of which set was which. The viable-rate gap replicated cleanly: plain wins on usable ideas everywhere (readers averaged 23 vs 20 of 40 on the main brief, 29 vs 22 on the second). The yield conclusion moved. Keep only the ideas a majority of the panel ticked, cluster the survivors:

Majority-vote survivors (7 readers)ViableDistinct & viable
Main brief — plain prompt25/4012
Main brief — spec-first18/4015
Second brief — plain prompt27/4010
Second brief — spec-first18/409
Majority = ticked by ≥4 of 7 readers (main brief) / ≥4 of 6 (second brief). Distinctness = strict same-idea clustering of the surviving ideas.

On the main brief, spec-first's survivors span 15 distinct ideas against plain's 12 — a modest real edge, not the wash a single reader saw, and it holds for six of the seven readers individually; on the second brief it's a wash. The mechanism is arithmetic, not taste: plain's 40 ideas only contain 14 distinct ideas to begin with, so its 25 survivors pile into the same clusters, while spec-first's 20 starting clusters survive a harsher cut with more of them still standing. Spec-first is still the wasteful way to widen a set — a quarter of its ideas die at review — but the spread that survives review is real spread. "Flat or worse" becomes "flat to modestly better."

The judges have their own basin

We tried to automate the human read. Four frontier models from three companies judged ~21,000 blind head-to-head pairs. Checked against 139 decisive blind human picks across two briefs:

Judge signalAgreement with human
Pairwise originality (Bradley-Terry, 4 judges)43–55%
Pairwise pitchability41–51%
Embedding nearest-neighbor novelty58%
Rubric quality score39% — anti-correlated
Agreement measured on decisive (non-tie) pairs only. 50% = coin flip.

The failure has a mechanism. Judges score pairs in isolation and never saturate: a human reading 60 pairs is tired of "the AI writes its own obituary" by pair 12; the judges rewarded it every single time. In one experiment, 13% of all judge-favored ideas on a moving-company brief were the same divorce-data premise. And the judges share the generators' training, so they share the generators' taste — a judge can't see its own blind spot.

One technique helped: showing the judge the candidate pool first and declaring its premises used up lifted originality agreement from ~50% to 63% — and to 77% on the pairs where two judge families agreed. Useful for triage; not good enough to replace a human. Every ranking in this study that matters was made by a person.

The $110 brain surgery

If collapse lives in the weights, edit the weights. Open-weight models ship in pairs — the raw pretrained "base" model (the whole distribution, unaligned) and the aligned "instruct" model — with identical architecture. So you can blend them, parameter by parameter. We interpolated Qwen2.5-72B at 30 / 50 / 70% base on a rented H200 and measured how many regions of idea-space each blend reached:

ConfigurationRegion reach (Hill number)
Instruct (0% base)8.1
30% base10–11
50% base9–12
70% base13–17
Plain Claude Sonnet, no tricks26.4

Withdrawn, October 2026: re-counted with the repaired judge, the 70%-base blend was no wider than the untouched model. The paragraph below is kept as first published; see "We ran it again" and corrections log item 7.

The dial is real. Every step toward base widened the ideas, monotonically, and the model still followed instructions at 70% base. It's a lever no API will ever expose. And it wasn't enough. The open model's basin was so much deeper than the frontier model's that maximum blend never caught a plain Sonnet prompt on the main brief.

Two more findings from the open-weights lane:

  • Division of labor beats either model alone. Let the blend emit raw one-line premises and a frontier model render each into a finished idea. This harvest-and-render pattern beat direct generation for every configuration — and on the second brief the 70%-base harvest (27.9) beat the best pure-frontier method (22.4).
  • You cannot predict which models are wide. One community model family is wide at 405B and collapsed at 70B; its successor is the exact reverse. Same lineage, opposite outcomes. Screening each candidate empirically costs about $1 with this instrument — guessing costs you the campaign.

We ran it again. Here's what survived.

After we found the counting problem (corrections log, item 6), we re-ran the open questions from this study from scratch, with the rules for calling a winner written down before we started. Eleven ways of generating ideas, each run several times against the same plain prompt, each batch counted by the repaired judge, and one full batch of forty from every method read blind by the same strategist, who marked each idea no, usable, or I'd pitch it.

Three things held up

Different models have different good ideas. Mix three unrelated models and you get about ten ideas per forty that none of our earlier runs had produced. Seven models, about the same. The catch is what the strategist saw: nearly every portfolio idea was usable, but only seven in forty were worth pitching. Mixing models buys range, not quality.

Seeds first, then write-ups. Ask a model for forty one-line seeds, hand each seed to a strong model and have it written up for the brief. With DeepSeek writing the seeds, almost every idea in the batch was new to us, and the strategist pitched 23 of 40. With Claude writing its own seeds, same pitch rate. Writing the seed up did not pull it back toward the usual ideas; we checked by writing the same seeds up two different ways and got the same spread.

You can't talk a model out of its habits by editing the brief. We hid our company name during generation and restored it afterwards: two or three new ideas per forty. We deleted the through-line requirement: no change at all, on either brief.

Two things moved

The "tensions" trick is a trap. Ask the model to name the five tensions in the brief, then to write seeds from the tensions, then to write them up. On paper it is the widest batch in the study. The strategist would run 29 of the 40 and pitch 2. More new ideas is not the goal; more ideas you'd pitch is. This is the cleanest example we have of why the last step of this pipeline is still a person.

The model-surgery result from August did not hold. When we re-counted the base-and-instruct blends with the repaired judge, the 70%-base blend was no wider than the untouched model. The lever may exist; our measurement can't show it. We've withdrawn the claim instead of defending it.

Cheap and real, but not enough on its own

If you change nothing else, change how you ask:

How you askIdeas you haven't seen before, per 40Strategist would pitch
Five small requests of eight (what most people do)about 2014
One request for all fortyabout 3210
Four rounds of ten, each shown the earlier roundsabout 3514

The pitch column is one blind read of one batch each, and the differences in it are inside the reader's own day-to-day swing; the new-ideas column is the finding.

Both changes gave us far more ideas we hadn't seen. Neither raised the share worth pitching. Use them as the plain arm of a portfolio, not as the answer.

What this still doesn't tell you

One brief for most of it, one strategist's reads, one sitting. The strategist's pitch calls moved on 4 of 20 cards when re-read a day later, always toward stricter, so small differences in pitch rate between methods mean nothing and we haven't called any. "New to us" means new against everything we generated in August, not new to the world.

How we checked

Second round, October 2026: 11 generation methods on the main brief, 3 to 6 runs of 40 each (95 batches); every batch counted by the repaired judge at a strict and a lenient setting, with wins called only when a method beat every plain run or passed an exact test at the pre-registered bar; 219 blind three-level reads by the original strategist; $288 in model calls. The pre-registration, every amendment and every score are on file; all model calls are cached and reproducible.

What to do with this on Monday

Everything above reduces to one working method. It costs about a dollar in model calls per brief and about twenty minutes of a strategist's time.

1. Fix the brief first (ten minutes). Three sentences: the goal, permission to be tangential, and the through-line rule ("a mention of the client should not feel out of place in the finished piece"). This is what moves the pitch rate; nothing below does.

2. Get your plain batch the better way (one call). Give your main model the brief and ask for all forty at once, as a list of title, two-sentence concept, and the proof point that makes it credible. If the model cuts off before forty, ask in four rounds of ten and paste the earlier rounds back in each time. Don't bother asking it to avoid a list of "ideas already used"; the memory alone does the work.

3. Get forty seeds from a different model (one call, cents). Pick a model from another company — DeepSeek was the best seed-writer we tested, and the point is that it has different habits, not that it is smarter. The prompt is short:

Here is the brief. List 40 one-line campaign premises — just the core concept of each, one sentence, no titles, no explanation. Cover as many different subjects, mechanisms and emotional registers as you can; do not repeat a premise in different words.

4. Have your main model write each seed up (forty small calls). One seed at a time:

Here is the brief, and a raw premise from a brainstorm. Turn it into one campaign idea for this brief. Keep what is surprising about the premise, but anchor it: shape it so a mention of the client would not feel out of place in the finished piece. If the premise can't be made to work for this brief, say so and skip it.

In our runs almost nothing got skipped, and the write-ups kept the seeds' spread.

5. Dedupe with a model, pick with a person. Clustering near-duplicates is the one judging job the models do reliably; ask your model to group the eighty ideas into "same idea" clusters and keep one from each. Then a strategist reads the survivors on three levels: no, usable, I'd pitch it. Forty ideas takes a few minutes. Keep the "I'd pitch it" pile; that is the deliverable.

What to expect. In our one blind read, the strategist pitched about one seeded idea in two, and almost none of them were ideas the plain batch already had. Expect twenty to thirty pitchable ideas per brief from the two batches together. (One reader, one batch each; the reader's own calls moved on one card in five between sittings, so treat the ratio as a guide, not a measurement.)

Measure the right thing. If you track this, count pitchable ideas per brief, not distinct ideas. Every method that looked best on "distinct" and worst in the room (the tensions trick, the heavy decomposition prompts) is a lesson in what happens when you optimise the wrong count.

Don't spend time on these. Temperature. Verbalized sampling. Persona and provocation prompts. Hiding your brand name from the model. Deleting the through-line sentence to "free it up". Asking for the tensions first. Blending open-weight models. Each one was tested; none earned its place.

Try it on your own brief: give us your brief and Fractl Agents writes both batches for you, then shows where each one spent its ideas. It is free, two runs a day.

The lever nobody was testing: the brief

Halfway through, our strategist said the wide-model ideas were "cool, but I'm not sure what they're trying to be about." Our brief said ideas "must be something the company could produce and pitch to journalists" — and every generator read that differently. So we rewrote it the way he actually judges: name the goal, license tangents explicitly, but require a through-line — a CTA or mention of the product must not feel out of place in the finished project.

Plain prompt, same modelViableDistinct & viable
Original brief33/40~12
Rewritten brief38/40~20

No new model. No technique. A clearer assignment nearly doubled the usable yield — more than anything else we tested, machinery included. A vague brief collapses the model into its safest cluster; a brief that names the goal and licenses tangents gives it permission to spread and a tether that keeps the spread useful.

No single generator wins. The portfolio does.

The final surprise. Under the rewritten brief, four very different generators each produced roughly 12–21 distinct viable ideas — call it a tie. Then we pooled everything the human had ticked viable and clustered the pool:

SourceAdds to the pool
Plain frontier prompt21 distinct viable ideas
+ Spec-first decomposition+15 new
+ 70%-base open-weights blend, anchored+14 new
+ De-aligned 70B harvest, anchored+15 new
Union64 distinct viable ideas — only 7 of 64 classes overlap

Different model lineages mine almost completely different veins of good ideas — same brief, same bar, near-zero overlap. Three times the swath of the best single method. The machinery earns its place not by beating the frontier model but by being uncorrelated with it.

The playbook

  • Fix the brief first. Name the goal. License tangents. Require a through-line. The highest-leverage twenty minutes in the pipeline.
  • Run a portfolio, not a prompt. Ask your main model for all forty at once (or in rounds that see each other), have one or two unrelated models write seeds, and have your main model write the seeds up. The API-only version costs about a dollar per brief.
  • Anchor everything. Render every raw premise for the brief with a frontier model — keep what's surprising, draw the through-line.
  • Dedupe the pool, then let a human pick. Clustering is the one job AI judges do reliably. Ranking originality is not — don't automate the last step.
  • Skip: temperature, verbalized sampling, personas, provocation instructions, the tensions trick (wide on paper, unpitchable in the room), and any judge that claims to score creativity.

First step, today: take your next ideation brief and add three sentences — the goal, permission to be tangential, and the through-line rule. Then ask two unrelated models, not one model twice.

Method & limits

Scale: two fixed briefs (our own AI platform; a national moving company) · 15 prompting conditions × 3 replicates × 40 ideas × 2 briefs in the main round, plus open-weight and de-aligned-model conditions (~5,000 generated ideas total) · ~21,000 head-to-head judge calls · 230+ blind human-labeled pairs and six whole-set human reads. The measurement grid (subject × mechanism × register) was declared before any generation. Spread measured by strict same-idea partitions under two judge families, grid Hill numbers, and embedding Vendi scores; where the judge families disagree we report the range. Open weights: Qwen2.5-72B base + instruct, linear weight interpolation, fp8 serving on a single H200; total GPU spend $9.50. Limits: two briefs in one broad vertical; viability is one senior strategist's blind judgment (the second reader round for findings 4 and 5 did not run; see corrections log (6)), not market outcome data; the blend's premises were harvested under an earlier brief wording than the hosted models' (the anchoring render mitigates this; noted). Panel read (added Sept 1): the plain-vs-spec-first viability result now rests on seven strategists' blind reads across both briefs (~1,040 idea-level viability labels; inter-reader agreement kappa .28–.56; majority vote for the reported numbers). Findings 4 and 5 remain single-reader; their distinct counts were re-measured in October 2026 (corrections log (6)).

Corrections log: (1) An early condition hard-coded one brief's subject into the other brief's prompt; regenerated and rescored. (2) Our first human-read sheet sampled judge-favored ideas — circular; resampled uniformly, re-read. (3) An early "86% judge agreement" figure came from 14 pairs and did not survive 139; retracted. (4) One model server returned identical "replicates" from a fixed seed; regenerated with per-request seeds. (5) Sept 1: v1 said spec-first's distinct-viable yield was "flat or worse" than a plain prompt, based on one reader. A seven-strategist panel replicated the viable-rate gap but moved the yield direction on the main brief — majority-vote survivors span 15 distinct ideas for spec-first vs 12 for plain (wash on the second brief). Softened to "flat to modestly better"; the waste finding stands. (6) October 2026 — the counting instrument, re-checked. We re-examined how this study counted "distinct ideas" and found things we should have caught before publishing:

  • The judge that did the counting merges too much. We asked the senior strategist who did the original reads to judge 40 pairs of ideas. Of the 20 pairs the counting model had called the same idea, he agreed with 3; of the 20 it had kept apart, he agreed with 17. The instruction "err toward merging" in our prompt did exactly that. We rebuilt the judge around his answers (a pairwise comparison on the full idea text, with a two-part test: same mechanism and same subject), and it now agrees with him on 36 of 40 pairs. A second, independent check on 99 new pairs from three other batches (chosen so that both judges' merges and the closest-looking unmerged pairs were all represented) came out the same way: the rebuilt judge agreed with him on 89 pairs, the old judge on 65, and of the 27 pairs only the old judge had merged he rejected 24. So the playbook line "clustering is the one job AI judges do reliably" held only once the judge had been checked against a person; the one that counted v1.1 was not reliable. The rebuilt judge is not him, and he is not a fixed ruler either: a same-or-different answer forces a line through pairs that are really "close, with one material difference", and he flagged those as his least certain calls; the 10 pairs where he and the rebuilt judge disagree are of that kind. The follow-up study therefore reports distinctness as a band, counting close variants as one idea and as two.
  • The headline count is too harsh. Counted by the rebuilt judge, the three plain-prompt batches behind "ask for 40 ideas and get 14" hold about 24 distinct ideas each (the published 14 was the lowest of three runs, 14, 21 and 18, by the old judge). On one of those batches the strategist's own pair answers merge a little more than the rebuilt judge does, so his own count would sit slightly under 24, nowhere near 14. The repeat problem is real; it is nearer four in ten than two in three.
  • Single counts wobble. One judging pass over a 40-idea batch moves by about 3 ideas on a re-run and by 9 or more one time in ten; we had published single passes as if they were exact. The counts in this entry are means of repeated passes where we have them; the October seven-model check is one pass and is marked as such. (The temperature comparison, 17 vs 14, was always inside that noise; "nothing" stands.)
  • "Spec-first reliably doubled distinct ideas" overstates it. Counted by the rebuilt judge, the spec-first batches hold 33 to 39 distinct ideas of 40 against 20 to 25 for the plain prompt: about half again as many, not double. The direction holds, and the viability cost the panel measured is untouched. The arithmetic in the panel section changes with it: plain starts from about 24 distinct ideas, not 14, and spec-first from about 35, not 20. We have not had the strategist check a spec-first batch pair by pair; on the one near-ceiling batch he did check (a region-planning prompt we tested but did not write up), he merged 2 of 36 pairs, in line with the rebuilt judge, and kept apart all 15 pairs the old judge had merged.
  • The portfolio table had arithmetic errors, and the overlap was understated. Its column summed to 65 while the total said 64 (the last source added 14, not 15), and the "7 overlapping classes" was 8 under our own definition. Counted by the rebuilt judge, the same pool holds 92 distinct ideas, not 64, and only 3 of them appear in more than one model family. The conclusion stands and strengthens: unrelated model families mine nearly disjoint veins. A fresh check with seven current models (October 2026, one judging pass, to be repeated in the follow-up) agrees: their first 40-idea runs together hold 124 distinct ideas, 86 of which come from exactly one model. Treat those as floors: on 20 pairs that set one model's ideas against the pool, the rebuilt judge merged nine pairs the strategist kept apart, so where this entry says another model adds new ideas, the true number is at least that.
  • The brief rewrite did not widen the set. We wrote that rewriting the brief nearly doubled the usable, distinct ideas. Re-measured with replicates, the rewrite did not change how many distinct ideas came out (24 vs 23–24). What it changed was how many the strategist would run (33 of 40 before, 38 of 40 after). The lever is real; it is a viability lever, not a spread lever.
  • Two claims we called findings were single runs. The "de-alignment adds width" result and the "12 → 20" yield were each one 40-idea run; both are below what a single run can resolve. They are now marked as unreplicated.

Method and all numbers for (6): Phase 0 of the follow-up study, on the lab's own files. All model calls, old and new, are cached and reproducible.

(7) October 2026, the follow-up study: the model-surgery dial ("every step toward base widened the ideas") is withdrawn. Re-counted by the repaired judge, the 70%-base blend of Qwen2.5-72B was no wider than the untouched instruct model, so the monotone widening in "The $110 brain surgery" is not supported by our measurement. The harvest-and-render pattern it led to did hold up, with frontier and unrelated-lineage seed writers (see "We ran it again").

Disclosure: Fractl is a marketing agency; the ideation layer this research informs runs inside Fractl Agents, which we build and sell. Weigh the piece knowing the interest exists; the method is open and the numbers are checkable.

Fractl Research · August 2026 · v1.3 (updated October 2026: the follow-up round folded in; one August claim withdrawn; corrections log (6) and (7)). Companion to What AI actually recommends.

Hand over your next job.

What we learn in these studies goes into how Fractl Agents works. Your team gets the same setup.

Hand over a jobAll Fractl studies