GoKawiilThe Customer Who Comes With a Checkbook and a Sledgehammer
Sometime in 2010, Airbnb was hemorrhaging money and growing slower than Brian Chesky had promised investors. The company had roughly $200 in revenue per week at one point. Into this vacuum walked a potential corporate client, the kind that could write a check large enough to solve all the immediate problems. The pitch was essentially: customize your platform for our needs, move toward corporate housing, and we’ll make you viable.
Chesky said no. Not politely declined. No.
That decision is easy to admire in retrospect, with Airbnb valued at over $70 billion. It is genuinely terrifying in the moment, when you have seven employees and can’t make payroll. And what makes it instructive isn’t the bravado of it. It’s that Chesky had a mental model clear enough to recognize that this customer, despite the money, was pointing toward a different company than the one he was trying to build.
Slack and Stripe have nearly identical versions of this story. So does almost every company that survived long enough to matter. The pattern is consistent enough that it deserves a name and an honest autopsy.
Why Early Enterprise Customers Are Especially Dangerous
There is a specific gravity that large customers exert on early-stage startups. It isn’t just the money, though the money is real and urgent. It’s that enterprise customers come with an implicit argument: we represent the real market. They have procurement processes, legal teams, integration requirements, and compliance needs. They seem like the grown-up version of your product’s future.
Stewart Butterfield has talked about the pressure Slack faced from large organizations in its early days wanting features that would have fundamentally changed what Slack was. The requests were reasonable on their face: more administrative controls, different permission structures, audit logging. Each one seemed like a logical extension. Taken together, they were a blueprint for a different product aimed at a different user. Butterfield’s team had to repeatedly decide what they were actually building.
The reason this is dangerous, specifically in year one, is that startups in their early phase are not stable enough to resist the gravitational pull of a paying customer. Your team will naturally start solving the customer’s problems. Your roadmap will quietly reorient. You will tell yourself you’re not changing direction, just serving the customer. And then one day you’ll look up and notice that the thing you originally set out to build no longer exists.
A coherent roadmap has a spine. Once you start accommodating misfit customers, the spine goes first.
... continue reading