— DISPATCH · LIVE TEST · 04
v0.app is a polished surface with a confident pricing card and a free tier. It also lost every SaaS buyer we pointed at it. The exit was quiet, not angry — the page simply never answered the question they walked in with.
Strong product, wrong room. The page never met the buyer it was shown to.
Would click
0%
Scroll or leave
0%
Brand
V0
Audience
SaaS Buyer (B2B)
To decision
0s
Synthetic users
0+
The SaaS Buyer panel arrives with a job to do: evaluate a tool, justify a line item, map features to a workflow. They read pricing pages like contracts and landing pages like briefs.
v0.app's surface assumes a different reader — one who already knows what a deployment is, what tokens cost, and why cache layers matter. For the buyer panel, that framing reads as a closed door.
0% clicked. 100% left. Why?
Same surface. Different reads. The minority who clicked — and the majority who didn't.
Pricing opacity killed the justification.
“$30 per user per month, and after digging through every FAQ I still can't tell you how many actual builds that covers. I have to justify every line item. This pricing model is designed to obscure cost, not explain it.”
Billing copy reads developer, not finance.
“I reconcile client ledgers daily, so I need billing records I can actually read line-by-line. The invoice tracker dumps me straight into developer jargon — deployment costs, API usage — when I just need itemized charges matched to my statement.”
Came for workflow software, found token economics.
“My team just got budget approval for a new planning platform, so I clicked in expecting workflows or data management. Instead it's all token pricing and cache layers — nothing about how this helps someone managing city datasets or zoning.”
No translation from developer surface to her job.
“Seven messages a day on the free tier — I file more source follow-ups than that before noon. The whole thing is built around app development and UI generation. Nothing on this page tells me what I'd actually use it for.”
Credit where it lands: the visual hierarchy is clean, the free tier is surfaced early, and the $30/user/month anchor is unambiguous. Nobody got lost in navigation. The page is well-built. It just isn't built for the person reading it.
Pricing opacity was the loudest break. $30 per user per month buys… how many builds? How many messages beyond the seven-a-day free cap translate into what monthly spend? The FAQ doesn't resolve it, and a buyer who has to defend the line item to finance won't guess.
The second break is audience fit. Accountants want itemized charges they can reconcile against a statement, not deployment costs and API usage. Analysts, administrators, planners, and journalists all hit the same wall: the vocabulary on the page is engineering-native, and nothing translates the product into their workflow.
$30 per user per month, and after digging through every FAQ I still can't tell you how many actual builds that covers. This pricing model is designed to obscure cost, not explain it.
— VERDICT
The one fix that moves the most
Add a usage translator above the pricing card. Show what $30/month actually buys in concrete units — builds, messages, projects — with at least one worked example a non-developer can read. The free tier's seven-messages-a-day cap is honest; extend that honesty to the paid plan.
Then decide who the page is for. If v0.app is a developer tool, say so in the first line and stop spending impressions on SaaS buyers. If it's broader, the homepage needs a non-developer use case — one paragraph, one screenshot, one outcome — before the token economics.
1,800+ synthetic users browsed v0.app. Decision arrived in 273 seconds. That's the cadence: a real panel, a real surface, a real timer — and a verdict before the kettle boils.
Live Test runs weekly. Same protocol, different surface, no retakes. If you want to see your page read out loud by the buyer you're targeting, the queue is open.