Alebuild · Ride-Along Sample
Perplexity
PerplexityThe InvisibleMeter
Why the paywall isn’t what lost them.
PerplexityWhy the paywall isn’t what lost them.
I spent a currency I couldn’t see, on work that never arrived.
Twenty-four minutes, one real research job, two surfaces and a paywall. What follows is what happened, in order, on the clock.
Most people put it at the paywall. Have a go before you scroll — it costs nothing and it’s more interesting if you commit.
Motivation is the thing you already paid to acquire. It’s finite, and every screen either spends it or refills it. Here is twenty-four minutes of it.
Peak 92. End 4. Four climbs, four falls, terminating on the floor. Both rises are worth pausing on: at beat 06 intent goes up because I thought I was getting something free, and at beat 11 because the Comet intro screen is genuinely lovely. Both were spent inside sixty seconds. A rise that isn’t converted is just a further fall arranged in advance.
The film runs in journey order, because that’s how your user meets the product. This runs in severity order, because that’s how you’ll schedule it.
| Severity | Quick win | Medium |
|---|---|---|
| Critical |
|
|
| Major |
|
|
| Minor |
|
|
All three are cheap, all three are indefensible once named, and none needs a designer.
“A typical research task costs 3–8 credits; your plan includes 50.” Ranges are fine. Refusing to estimate is not — right now the resource is formally unpriceable, so nobody can decide whether $20/month is worth it. One afternoon of writing. Beat 09.
The highest-value fix here, because it converts the worst moment in the product into a recoverable one. A user who loses a resource silently is gone. Beat 12.
A copy change that unlocks the most heavily promoted feature in the product — the one I refused to click because I couldn’t tell what it was. Beat 04.
Perplexity has already solved this problem once and hasn’t noticed. At 13:00 I watched an agent narrate its own work and said the word “nice” out loud — that’s the Labor Illusion, applied correctly, buying patience during a slow operation. Two minutes later I was reading circular documentation trying to find out what any of it cost. The product knows how to show its work. It just doesn’t show its price. Nearly every finding in the middle of this teardown is a version of that one gap.
The second thread isn’t really about Perplexity. On generative products, nobody owns the output. Length, density, failure states, cost variability — all of it is emitted by a model rather than decided by a person, so none of it gets designed. There was no meeting where someone chose to return three screens of prose. There was no spec for what happens when an agent fails. Those are the highest-leverage surfaces in the product and they are, structurally, unowned.
That’s the defining design problem of this product generation, and it’s why an AI company needs a design engineer rather than a designer. Half the fixes above are prompt-and-render decisions that live in a codebase, not in Figma. You can’t hand them off as a mockup, because the thing that needs designing is a constraint on a model, not a screen.
We ship the top three fixes together, in your codebase, plus a short retrospective on what moved.
I embed with your team two days a week. We ship continuously, and every quarter I run a fresh ride-along so you can watch the curve change.
Four per month. Free. Delivered in 48 hours.
Request your ride-along →