Shopify: a snowboard shop and a twenty-year compounding curve

The original problem. In 2004 Tobias Lütke, a German programmer who had moved to Ottawa, tried to build an online store to sell snowboards with his partners (Snowdevil). The available e-commerce software — Miva, osCommerce, Yahoo Stores — was bad enough that he decided to write his own.

Founder background. Lütke trained as a programmer through the German apprenticeship system rather than university. He was a Ruby contributor, and Shopify's internal framework work fed directly into the Rails ecosystem; he became a Rails core contributor. The relevant asset was deep craft plus membership in an open-source community, not business credentials.

The origin story caveat. "It started as a snowboard shop" is true and is also told in a way that implies accident. In fact Lütke and co-founder Scott Lake explicitly decided within about a year that the software, not the snowboards, was the business. The pivot was a deliberate strategic judgment, not serendipity.

Initial product and validation. Shopify launched publicly in 2006. Early validation was narrow and direct: other small merchants with the same problem. The API and, from 2009, the App Store turned the product into a platform, which is the decision that separates Shopify from the dozens of competing hosted-cart products of that era.

Funding history. Notably slow and late: bootstrapped and angel-funded for years, a $7M Series A from Bessemer in 2010 (six years after founding), $15M Series B in 2011, $100M Series C in 2013. IPO on the NYSE and TSX in May 2015 at $17/share, raising ~$131M at a ~$1.3B valuation.

Business model. Two revenue lines that compound differently: subscription (predictable, per-merchant) and merchant solutions (payments, shipping, capital, POS — scaling with merchant GMV). Over time merchant solutions became the larger and faster-growing line, which means Shopify's revenue is levered to its customers' success rather than just to its customer count. That is a structurally better position than pure SaaS.

Major turning points and mistakes.

• Shopify Payments (2013) converted Shopify from a software vendor into a payments business, which is where the economics actually are.
• The Amazon positioning. "Arming the rebels" gave Shopify a coherent enemy and a merchant-aligned identity.
• The logistics mistake. Shopify spent heavily building the Shopify Fulfillment Network, acquiring Deliverr for $2.1B in 2022, then sold the whole logistics business to Flexport in 2023 at a large loss and cut roughly 20% of staff. This is a well-documented, expensive strategic error: a software company with software margins tried to enter a capital-intensive, low-margin physical business during a demand spike it mistook for a permanent shift.
• The pandemic over-hire. Lütke's May 2023 memo stated plainly that the company had bet e-commerce's pandemic-era share gains were permanent, and that the bet was wrong.

Current status (September 2026). Public, and accelerating: Q2 2026 saw revenue up 34% year-over-year, with GMV, revenue, gross profit and free cash flow all growing more than 30%, and an 18% free cash flow margin (Shopify Q2 2026 results, August 5, 2026) [Verified — public filing]. Shopify moved its primary listing to Nasdaq in 2025 and is one of the few 20-year-old software companies growing faster than it did five years earlier.

Lessons that generalize.

1. Owning the payment flow is worth more than owning the software. Most SaaS businesses serving transacting customers eventually discover this; the ones that build for it early capture far more value.
2. Demand spikes are not trend changes. Shopify, Peloton, Zoom and dozens of others made the same error in 2020–2021 and paid for it in 2022–2023. The generalizable discipline is to ask what a spike would look like if it were temporary, and whether you could tell the difference in real time. Usually you cannot, which argues for reversible commitments.

---