Case studies / Public scorecards / Railyard
This scorecard was produced independently as a methodology example, from the public railyard.run launch on Hacker News. ClawniLab is not affiliated with Railyard and no customer relationship exists. Findings are illustrative of our 10-point clarity methodology and do not constitute professional advice for the reviewed party.
CSPublic scorecard
Railyard — landing page clarity scorecard.
Scored the day Railyard launched on Hacker News (Show HN), straight off our public free score tool — same 10-point grid as a paid audit, no contact with the founder.
01Friction map
Three things to fix first
Ranked the same way every paid audit ranks issues — by what a stranger notices first.
Proof — 0/10
“What teams say” — the testimonial block is fetched by client-side JS and renders empty in the static HTML, so no visitor without JS sees any proof.
Fix: Server-render 2–3 named quotes (name, role, a usage number) directly in the HTML instead of behind a client fetch.
Audience — 3/10
“Building apps for clients? All your client apps on servers they own, one agency bill.” — the only named buyer is one line buried in the pricing section; the hero names nobody.
Fix: Add a line under the H1 naming the buyer, e.g. “Built for backend teams who want Heroku-style deploys on servers they control.”
Hero clarity — 7/10
“Ship your whole app to servers you own.” — states the product and outcome clearly but never says who it's for.
Fix: Add a sub-line directly under the H1 naming the audience.
02Strongest point
What Railyard already gets right
Consistency
“Deploy full-stack apps to servers in your own cloud account.” (footer) matches the hero promise and the Free-tier numbers repeated in the FAQ — no contradiction found anywhere on the page.
Want your page scored like this?
Free instant score, or a full clarity audit with friction map and hero rewrite in 48 hours.