Arpeely · AI Builder Challenge

Same score.
Different room.

Google Search click on “free iq test” → account creation. KPI: CVR = account creations / page visits.

Part 1The funnel Ad click to account creation, mobile and desktop Part 2Three A/B tests One variable each, ranked by headroom Part 3Three creatives 320×50, 250×250, 1080×1920
Download everything · 1369 KB

All four builds run offline in one folder. No backend, no build step.

The argument
1

The number is the commodity. The comparison is the product.

Every competitor here can hand someone a score. Nobody remembers a score. What a stranger gives an address for is knowing who else is in the room.

2

Answers given freely beat answers taken.

Every question offers a way to stop. That costs conversion, and buys a signal worth having — plus a KPI that can't be inflated.

3

I didn’t build a funnel. I built a generator.

Four builds, one config object. A new variant is two lines.

PART 1 OF 3The product call

Why the flow is designed this way

Entry — the ad’s words, said back
Entry — the ad’s words, said back
One tap per screen, no typing
One tap per screen, no typing
A true pass rate, not a compliment
A true pass rate, not a compliment
The score, and a band that is useless on purpose
The score, and a band that is useless on purpose
The gate shows what it buys first
The gate shows what it buys first
Each answer draws another band
Each answer draws another band
Same number, three rooms
Same number, three rooms

The score is free. Resolution is sold.

Withholding the score is the obvious move. I rejected it. A withheld score turns the gate into a toll, and a tolled user either leaves or types a junk address — corrupting the exact metric we’re optimising.

So the score arrives immediately, stated as final: “That number is yours. It doesn’t change from here.”

Under it sits one comparison — everyone, every adult alive — deliberately worthless. The user holds something real and can see it tells them nothing about themselves.

That gap is where the gate goes. Not the most extractive spot. The only spot where what we want and what they want are the same thing.

Each answer pays out on the screen it’s asked on

Continent, country, city. Every answer draws a narrower distribution and stacks it under the last. Three profile questions read as a reward instead of a form.

The percentile falls as often as it rises

Berlin sits above the German mean, so a Berliner ranks lower among neighbours than among countrymen. A funnel where every answer flatters you is a compliment machine, and users work that out in two screens.

Movement is the product. Direction is the evidence it’s real.

Every screen offers a way out

“Show me what you have — you can stop at any level.”

Same logic at the gate: one field, no password, opened by a sign-in link. A password at the moment of maximum anticipation is the most expensive field in the funnel and buys nothing this product needs.

Desktop is a different composition, not a wider one

A 520px column centred in a desktop viewport is a phone screenshot with wallpaper around it — which is what most “responsive” funnels ship.

Rail carries where you are; stage carries what you do
Rail carries where you are; stage carries what you do
After the test the rail holds the score, so the stage is all payoff
After the test the rail holds the score, so the stage is all payoff

Reading measure is unchanged, so the device isn’t a confounder in the A/B tests.

Data quality is a design constraint, not a report

Or just click through it here

All four builds run inside this page — no backend, no build step. Switch the build, switch the device.

Open full screen →

Open the browser console while you click — every build logs the funnel events it would send.

PART 1 OF 3Scale, and where AI helped

How it was built, and with what

The division of labour

The model produced structure. I produced judgement and every fact.

One wrong answer in a test claiming to measure intelligence destroys every other item. So the bank is split by factual risk:

LayerProduced howRisk
Visual matricesGenerated from a transformation ruleNone — no fact to get wrong
Reasoning trapsCanonical puzzles, settled answersLow
Knowledge itemsAuthored, then verified individuallyManaged — and only here

What the automated checks caught

Checks run over the whole bank on every build, so adding 200 questions costs writing, not reviewing. They found:

Every one would have shipped unnoticed. None was visible in the code.

Where I didn’t let it decide

The central trade — give the score away, sell the comparison — is a judgement about what a stranger hands an address over for, and the whole funnel rests on it.

Same for the two calls that cost conversion on purpose: letting the percentile fall, and putting a way out on every screen. A model optimising for CVR removes both.

PART 2 OF 3A/B Test Ideation

The model, and three bets

Where the money leaks

No traffic exists yet, so I sized this from published quiz benchmarks — ~65% of starters complete, a well-framed gate captures 70–80% of completers. Per 100 visits:

StageRemainingLost
Lands, answers Q17030
Completes the test4525
Answers the narrowing questions387
Creates the account299

CVR ≈ 29%. Sanity check: 29 of 70 starters is 41% start-to-lead against a ~40% benchmark.

The funnel multiplies, so ten points anywhere is worth the same. What differs is headroom. The gate at 75% is near the 80% ceiling; completion at 65% is merely average and a short test can reach 80%.

That’s why my first bet is test length, not the gate.

Three A/B tests, ranked by headroom

1

Six questions instead of twelve

Funnel step: test completion — 25 of 100 lost here, the largest unclaimed headroom.
Bet

fewer chances to quit, and a cheaper promise on entry — “90 seconds” instead of “3 minutes”.

Risk

a six-item result is easier to dismiss as a toy.

Read

completion rate and CVR-among-completers, separately. They should move in opposite directions — that split is the finding.

One variable

the six items are a representative sample of the same blueprint. Taking the first six slots would have stripped every visual item and tested length and item type at once.

2

Show the payoff before question one

Funnel step: entry / first answer — 30 of 100 lost here, the largest leak.
Bet

the control assumes the visitor already knows what they’re getting. This opens on a sample band stack instead.

Risk

reintroduces the interstitial the control removed; a filled-in sample may read as fabricated.

Read

start rate. Everything downstream should be unchanged — if it isn’t, the variant is selecting a different visitor, not converting more of the same one.

3

Move the gate to the end

Funnel step: account creation — 9 of 100 lost here, the smallest leak but the sharpest question.
Bet

give everything away and let the account sell continuity. A user holding a finished result may reciprocate where one stopped mid-curiosity resents the ask.

Risk

by the end, the curiosity that carried them here is spent.

Read

CVR would mislead here, so guardrails decide it. If CVR rises while deliverability falls, the variant is buying inventory, not users — and I wouldn’t ship it on a CVR win alone.

How they’re built: one source, one CONFIG object, screen order derived from config. A diff against control is two to four lines.

Test 1   testLength: 6
Test 2   reveal.entry: 'payoff-first'
Test 3   gate.position: 'after-bands'

What I killed

  • A cognitive-decline angle. It converts, and Lumosity paid the FTC $2M for it. It also contradicts the keyword’s intent.
  • A literal world map. The obvious way to draw this, and decoration — the distributions carry the meaning.
  • Results delivered by email. Deferring gratification on mobile is an abandonment event.
  • A per-question timer. Adds credibility, adds abandonment. Better tested than assumed.
PART 3 OF 3Creative Design

Three creatives

Same score, different room. The ads don’t advertise a test. They advertise the mechanism, by showing the actual bands the user will earn.

320 × 50 creative
320 × 50 · Mobile banner

At 50px there’s room for one idea, so everything else is cut. Two shrinking distributions do in 60 pixels what copy would need a sentence for. A banner that explains loses to one that shows.

Download iqly-ad-320x50.png
250 × 250 creative
250 × 250 · Square

Two bands, the same column moving between them. The viewer sees the mechanism before clicking rather than a promise about it. CTA is “Find your place”, not “Take the test” — the test is the price, not the offer.

Download iqly-ad-250x250.png
1080 × 1920 creative
1080 × 1920 · Full-screen mobile

Three real bands, score constant, percentile moving, movement named. It runs downwards on purpose. An ad whose sample result flatters you is selling a compliment; one showing a score drop is selling a measurement. It is also the exact image Test 2 puts on the entry screen, so the two can be read against each other.

Download iqly-ad-1080x1920.png

Message match is a conversion argument and an auction one — Google scores landing-page experience, so a creative that oversells its destination raises CPC on the other side. The ad shows distributions. The landing screen shows distributions.

Not captured by this KPI
Arpeely already knows how to buy the click better than almost anyone. What that click becomes in the next three minutes is a different problem, and it’s the one I wanted to answer.