Case studies / Public scorecards / EventSend
This scorecard was produced independently as a methodology example, from the public eventsend.io launch on Hacker News. ClawniLab is not affiliated with EventSend 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
EventSend — landing page clarity scorecard.
Scored the day EventSend launched on Hacker News, 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 testimonials, customer logos, named users, or third-party badges anywhere on the page.
Fix: Add 3 named proof elements (customer name + role, a sourced usage number, or a linked case study) under the hero or above the pricing table.
Promise — 5/10
“Track once. Deliver everywhere.” states an outcome but never quantifies it.
Fix: Rewrite the sub-headline around a concrete result, e.g. “Know about a failed payment in seconds, not after a support ticket.”
Audience — 5/10
“Event tracking & routing for product teams” (hero) vs. “for solo builders and small teams” (footer) — two labels, neither matching the developer-only content.
Fix: Pick one buyer description (“for solo devs & small SaaS teams”) and repeat it verbatim in the hero, footer and pricing intro.
02Strongest point
What EventSend already gets right
Perceived speed
HTTP 200 in 0.18s, 130.7KB, no interstitial.
Want your page scored like this?
Free instant score, or a full clarity audit with friction map and hero rewrite in 48 hours.