Case studies / Public scorecards / Droneship
This scorecard was produced independently as a methodology example, from the public droneship.run launch on Hacker News. ClawniLab is not affiliated with Droneship 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
Droneship — landing page clarity scorecard.
Scored the day Droneship 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
No named customer, logo, usage number, or case study anywhere on the page — only third-party security research cited (Anthropic, Pillar Security, METR).
Fix: Add 3 named proof elements (an early user name + role, a usage number, or a linked workspace example) under the hero demo.
Audience — 3/10
“Launch Claude Code or Codex…on an isolated cloud machine with one command” — the buyer is only inferable from CLI and git vocabulary, never named.
Fix: Add a line naming the buyer directly, e.g. “Built for engineers who run Claude Code or Codex on real repos.”
CTA — 5/10
“Console” (nav + hero) — a single primary button, but the label is generic and sets no expectation of what happens, how long, or whether it's free.
Fix: Relabel to “Start free — no card” and keep the install terminal visible as the low-friction alternative.
02Strongest point
What Droneship already gets right
Perceived speed
HTTP 200 in 0.066s, 36.1KB, no interstitial found in the static HTML.
Want your page scored like this?
Free instant score, or a full clarity audit with friction map and hero rewrite in 48 hours.