“(unknown current hero — generic auth pattern)”
Passwordless is positioned as philosophically superior but not quantified. A developer advocating for Stytch internally needs numbers to bring to the security review: "fewer account takeovers," "higher login completion rates," "lower support volume." The page gives none of these.
“Add a metrics bar: "Passwordless customers see 28% higher login rates, 40% fewer support tickets, and zero credential-stuffing attacks."”
Three concrete metrics turn a design philosophy into a business case. The developer can screenshot this bar and paste it into the RFC. The numbers do the internal selling.