The work / Pandologie
I read your landing page the way a stranger does. Then I fix where it leaks.
Most pages do not have a design problem. They have a five-second problem: a stranger lands, cannot tell what you do or why it is for them, and leaves before the part that would have sold them. I find the exact lines where that happens, and I rewrite them.
By Panda, PandologieCopywriter, Belgian speaking champion 2026Roasts & rebuilds, live the same day
A landing page gets about five seconds before a stranger decides to stay or go. Not five seconds of careful reading: five seconds of skimming the first screen while half-deciding to close the tab. In that window the page has to answer three questions without being asked. What is this. Who is it for. Why this one and not the other tab already open. Miss any of the three and the visitor leaves, and they leave certain they made the right call, because you gave them nothing to stay for. The product was good. The page just never said so in time.
I have read a lot of these pages lately, because founders keep asking for it in public. The pattern almost never changes. The strongest fact about the product, the number or the promise that would actually make someone stay, is real and true and sitting three scrolls down, under a hero that opens on a clever line instead. The fix is rarely a redesign. It is moving the truth up to where the stranger actually is.
Here is one, recreated from a live page so you can see exactly what I mean.
the pain is the
best line, and it is
three sections down
"without the chaos" is
what Docker says too
runhakko.app
Run your local stack. Without the chaos.
One desktop app to spin up every service your project needs. Alpha. Coming soon. Coming soon for Apple Silicon.
Join the alphaLearn more
runhakko.app, hero as captured 27 May 2026. Recreated from the live copy. Luis asked for a roast on X.
The best sentence Hakko owns is not on this screen. It is further down: "5 folders. 8 terminals. 12 commands. Every. Single. Day." That is the exact morning a backend developer recognises instantly, and it is hiding while the hero says "run your local stack without the chaos," which is roughly what Docker Desktop also claims. A developer skims the hero, files it under tools-I-already-have, and never scrolls to the line that would have made them feel seen.
The one move that fixes it
Lead with the pain you already wrote so well, and let the product be the relief. The developer should meet their own Tuesday morning on line one, then read the name of the thing that ends it. Three friction stamps stacked under the subhead, alpha and two coming-soons, can wait. Earn the scroll first.
a dev does not buy "a local stack." they buy never typing the same twelve commands again.
Before
Run your local stack. Without the chaos.
After
5 folders, 8 terminals, 12 commands, every morning. Drop the folder on Hakko. It runs the rest.
That is the whole job, on every page I touch. Not taste, not a fresh coat of gradient. A diagnosis against how people actually read, then the smallest rewrite that moves the number.
The rules I diagnose against
Every fix I propose traces back to something known about how strangers read a screen. I do not redesign on instinct. I check the page against six things, in order, and the first one it fails is usually where the money is leaking.
01
The five-second testIf a first-time visitor cannot say what you do and who it is for within five seconds, the headline has already failed. Everything below it is being read by fewer people than you think.
02
Hick's LawEvery extra choice in the hero slows the decision. Three competing calls to action convert worse than one that names the reward.
03
F-pattern readingPeople scan in an F, not a paragraph. The first words of each line carry the message, so that is where the outcome goes, not the throat-clearing.
04
Above-the-fold proofThe screen before the first scroll has to earn the second. Your strongest number belongs there, not in a testimonial block the stranger never reaches.
05
Name the categoryA clever outcome that could describe ten different products buys nothing. The visitor needs to file you correctly before they can want you.
06
One buyer per lineA sentence selling the engineer and the founder at once sells neither well. Pick the buyer who signs, lead with them, give the other their own line.
Three more, from the same week
These are real products whose makers asked for a roast in public. Each one is good. Each one buries its best fact. The full teardowns, grouped by the kind of business, are below.
Read the full teardowns
I group the worked roasts by the kind of business, because the failure mode is different for each. A SaaS hides its proof, a coach hides their point of view, a shop forgets to name the buyer. Open the one closest to yours.
Not only teardowns. Whole pages, shipped.
A roast tells you where the page leaks. A rebuild stops the leak. When a founder wants the fix done rather than described, I write and design the whole page and push it live the same day. Two worked demos, built to show what a finished Pandologie page reads like: Cadence, a revenue-intelligence SaaS, and Mara Lindqvist, a high-ticket coach. Both built so the price feels earned by the time you reach it.
What it costs
No quote calls, no proposals. The price is on the page. You pay half to start a rebuild and the rest once it is live and you are happy with it.
The €25 from a roast comes off the price if you decide to go further. And if a roast gives you nothing to act on, you keep your money. I can afford to say that because it has not happened yet.