← All stories
Clickpass· Summer 2007 (One of the first 5 YC cohorts — same batch as Disqus)

Clickpass

Two British engineers in one of the first five YC cohorts saw that internet login was broken, built an elegant fix on top of an open standard — and then watched the standard lose to Facebook and Google. What they built was the right product. What they learned was priceless.

Peter Nixey · 19 min read

Clickpass, YC Founder Story

Company: Clickpass Founders: Peter Nixey (CEO) & Immad Akhund (CTO) YC Batch: Summer 2007 (One of the first 5 YC cohorts, same batch as Disqus) Industry: Identity / Developer Infrastructure / Single Sign-On Founded: 2007 | Acquired: December 2008 (by Synthasite / Yola.com) Total Funding: $20K (YC seed round only) Status: Acqui-hired, Peter Nixey joined Synthasite team


⚠️ Why This Story Is Different, And Why That Makes It More Valuable

Most founder story collections only feature billion-dollar exits. That is a mistake.

Clickpass is the story of two sharp British engineers who got into one of the earliest YC cohorts, built something genuinely ahead of its time, earned TechCrunch coverage, attracted the chair of OpenID to their board, and then got acquired within 18 months for an undisclosed (small) sum.

The product worked. The founders were talented. The timing was right. But the platform they built on top of, OpenID, lost to a competitor the founders couldn't control: Facebook Login and Google OAuth.

This is the story that teaches you about platform risk. And it's one of the most important lessons in all of startup history.



The One-Line Summary

Two British engineers in one of the first five YC cohorts saw that internet login was broken, built an elegant fix on top of an open standard, and then watched the standard lose to Facebook and Google. What they built was the right product. What they learned was priceless.


Lens 1, The Before State

Who Were They Before YC?

Peter Nixey was a British software developer, practical, thoughtful, and deeply embedded in the early web development community. He was a regular contributor to Think Vitamin (one of the premier web developer blogs of the era) and had a reputation as someone who thought carefully about UX and developer experience, not just code.

Immad Akhund was studying for his Master's in Computer Science at the University of Cambridge, one of the world's top technical programmes. He was technically exceptional, deeply networked in the UK startup scene, and ambitious in a quiet, methodical way.

Neither of them was a celebrity founder. Neither had a prior exit. They were two talented British engineers who had moved to San Francisco specifically to do the thing that in 2007 felt mythological: build a startup and get into YC.

Peter later wrote openly about this moment: "Four years ago I upped sticks and left London to join YCombinator. My goals were clear, build a company, get to San Francisco and build big." He acknowledged that the plan was more aspiration than execution at that point. Revenue was an afterthought. The big story, the vision, was everything.

This honesty is rare and instructive. Most founders entering YC in 2007 were chasing the dream of what Silicon Valley represented, not the operational reality of building a durable business.

The Personal Pain They Were Living

The year is 2007. Every developer building a web app faces the same problem: users have to create a new username and password for every single service they use. It is fragmented, frustrating, and insecure. Password fatigue is real. Account abandonment on signup forms is epidemic.

At the same time, a promising open standard called OpenID had started gaining traction. The idea was elegant: one identity, usable everywhere. Major companies, AOL, LiveJournal, WordPress, had already implemented it. Thousands of websites accepted OpenID logins. Even the biggest players were signing up to issue IDs.

There was just one catastrophic problem: OpenID was technically correct and completely unusable.

To log in with OpenID, you needed to remember a URL, your OpenID identifier, something like https://yourname.myopenid.com. Most users had no idea what this meant, had never set one up, and found the redirect-based login flow deeply confusing. A beautiful standard was dying because no one had made it human.

Peter and Immad stared at this problem and saw it with developer clarity: the standard is sound, the interface is broken. We can fix the interface.

Why They Were an Unusual YC Bet

In 2007, YC was still in its infancy, this was one of the first five cohorts ever run. Paul Graham was accepting small batches of founders and betting on ideas that felt both technically interesting and socially important. Peter and Immad were British, not American. They had no prior exits. They were building on top of an open standard that they didn't control.

All three of these things were risk factors. What got them in was the clarity of the problem, the elegance of their proposed solution, and the fact that they were building in the exact moment when OpenID needed a consumer-friendly face.

Key Insight for Aspiring Founders

The absence of a good user experience around a technically correct standard is always a startup opportunity, but only if you ask: "What happens if a tech giant decides to solve this too?" Peter and Immad asked the first question brilliantly. The second question is what the story ultimately teaches.


Lens 2, The Idea Origin

How the Idea Was Actually Born

The idea came directly from frustration with the developer ecosystem Peter was already deeply embedded in. He was writing about OpenID for Think Vitamin in 2007, explaining how it worked, why it mattered, what it could mean for the web. While researching and writing, the gap became obvious: the technology was sound, but nobody had designed a product around it that normal humans could actually use.

Peter's contribution to the OpenID community wasn't just technical, it was UX-driven. His original Think Vitamin article on OpenID, published in November 2007, was described by Simon Willison (a web standards pioneer) as an "excellent introduction... with really nice analogies." Peter wasn't just a builder, he was a translator. He could explain hard things simply. That skill would become Clickpass's product.

The initial insight was this: what if you didn't have to remember your OpenID URL at all? What if clicking a single button on any site would log you in, without you having to know anything about the underlying standard? What if Clickpass managed all of that, stored your identity, generated unique OpenID URLs per service for privacy, and autofilled your profile data on new sites you joined?

That was the product: OpenID made invisible, login made human.

The First Version

Clickpass launched publicly on March 11, 2008, nearly a year after entering YC. That timeline tells you something: this was not a "ship in two weeks" startup. The launch partners were carefully assembled, Plaxo, GetSatisfaction, Pownce, and many other YC companies. The board included Scott Kveton, chair of the OpenID Foundation. The product was polished. The pitch was crisp.

TechCrunch covered the launch on day one. The headline was: "Clickpass Could Change the Way You Surf the Web." That was not a small thing in 2008.

The Signal That It Was Working

Within the YC community and developer circles, the reception was strong. Other YC founders adopted it. The OpenID community rallied behind it, finally, someone was making the standard accessible. TechCrunch's coverage was genuinely enthusiastic, not politely obligatory.

The challenge wasn't user enthusiasm among early adopters. The challenge was that the market Clickpass was trying to create, normalised OpenID usage among mainstream internet users, was never quite there.

The Pattern This Idea Follows

Clickpass fits a specific idea archetype that is both common and dangerous: "Fix the UX of an open standard."

This pattern has worked (Stripe fixed the UX of payment APIs). It has failed (Clickpass fixed the UX of OpenID, but OpenID lost). The difference is almost always the same: Stripe's underlying infrastructure (banks, card networks) had no competitive motive to replace Stripe. OpenID's underlying ecosystem (internet identity) had every competitive motive for Facebook and Google to replace it with their own proprietary versions.

Lesson: When you build on top of a standard, ask yourself whether the companies implementing that standard could also build your product, and whether they have an incentive to.


Lens 3, The Application Anatomy

What Made Their YC Application Work

Clickpass entered YC Summer 2007, a cohort so early that Paul Graham was still figuring out what YC should be. The batch included companies that would later become important (Disqus was in this cohort). The acceptance bar was different: Paul Graham was betting on founders as much as ideas, and the YC community itself was an early adopter of OpenID.

Their pitch had three things working for it:

1. Precise problem framing. They didn't say "we're building an identity platform." They said: "OpenID is broken for users. We're fixing it." That's a concrete, verifiable problem with a defined existing standard as context. YC partners could immediately understand both the problem and the proposed solution.

Founder Stories · Members Only

You've read your 5 free stories this month.

The next YC application you write could be the one that gets in. Don't stop learning from the founders who already did it.

$5/month

Cancel anytime. Less than one bad coffee.

Unlock Every Founder Story →
  • 1000+ deeply-researched YC founder stories
  • Unfiltered Lens breakdowns: what worked, what failed
  • 2 new founder deep-dives every week
  • Full Q&A library + application teardowns

Not ready? Keep exploring, free

More stories every week.

Get 2 free stories in your inbox each week.