How Phil Libin built Evernote to 400 million users

Executive overview

Building for yourself removes the hardest question in product development: do people actually want this? Phil Libin's first two companies made products for customers he wasn't — retailers, banks, governments — and both times he felt the drag of guessing what others needed.

Evernote succeeded because Libin and his co-founder built a tool they wanted to exist. Early speed came from that clarity. Later challenges came from the same source: power-user assumptions that didn't scale.

Great products have a strong point of view — neutrality is a trap.

From consultant to product builder

• Engine 5 (1997) rode the dot-com wave building early e-commerce and shopping carts
• Sold to Vignette; learned that consulting money stops when you stop working
• Core Street was a deliberate pivot to product — but for a space no one cared about (government smart-card security)
• Lesson: building a product beats consulting, but the product must be for someone who actually cares

Why Evernote worked early

• Two teams merged in 2007 around the same idea: an external brain / cognitive prosthesis
• Neither team asked "will people want this?" — they were building for themselves
• Launched on the App Store on day one; became the default productivity app by being first and consistent
• Two genuine technical differentiators: seamless background sync across devices, and search inside images
• Background sync sounds trivial now — before Evernote it required manual FTP setup

The scaling trap

• Building for yourself gives speed early; it becomes a liability as the user base grows
• Evernote was optimised for power users with narrow use cases
• Had to actively re-learn what broader users wanted to make growth past that core viable
• The product that got you to one million users is not automatically right for ten million

Product philosophy: point of view over neutrality

• Products without a clear perspective are hard to make excellent
• Evernote was explicit about its philosophy of organisation and whose side it was on
• When company interests (who paid) conflicted with employee interests (who used it), Evernote always sided with the user
• "Don't try to be for everyone" is a feature, not a concession

Advice for first-time founders

• Build for yourself, or for a community you already understand deeply
• If you have to wonder whether people will want it, you don't know your users well enough yet
• Skip the demand-validation step by picking a problem you're already the world's expert on
• Finding people who already like your approach beats trying to convert sceptics
• "I've never taken someone from no to yes — I take people from yes to definitely"