The Twenty Minute VCGlen Coates: Why Shopify Will Dominate Amazon; How Microsoft Made Smartest Move of 2023 | E986
CHAPTERS
- 0:00 – 2:32
From game developer to building Handshake: a winding path into startups
Glen recounts his unconventional career arc—from computer science and video game development to running a warehouse for an eco-friendly bag business. That hands-on wholesale experience reveals a painful workflow at trade shows, which becomes the spark for building an iPhone app that later turns into Handshake.
- •Early career in game development and the mindset it builds
- •Moving to the US to run a warehouse and seeing commerce operations up close
- •Trade-show order-taking pain: paper order books and inefficiency
- •Decision to self-teach iOS dev and prototype the solution (Handshake)
- 2:32 – 3:47
Why game design produces resilient founders (and product builders)
Harry and Glen explore why gaming and game design correlate with strong founders. Glen frames it as repeated iteration under frustration—learning loops, competitiveness, and persistence that map closely to building products and companies.
- •Founding as repeated trial-and-error with small wins
- •Analytical + competitive mindset from games and chess-like thinking
- •Tolerance for frustration and long skill-building arcs
- •Reframing failure as part of the process
- 3:47 – 6:58
Shopify acquisition and the “Code Red” checkout mission
Glen fast-forwards through Handshake’s journey to Shopify’s acquisition and outlines his first roles post-acquisition. He then describes being asked by Tobi to run a “Code Red” effort on checkout—an all-hands, drop-everything escalation to fix foundational issues quickly.
- •Handshake acquisition rationale: Shopify expanding into wholesale
- •Glen’s role transitions: wholesale → checkout turnaround
- •Meaning of “Code Red”: overriding priority across the org
- •Checkout as a cross-cutting system that exposes org/coordination flaws
- 6:58 – 14:12
Glen’s product framework: Outcomes, Principles, Assumptions
Glen introduces a lightweight framework to reduce wasted work across many concurrent projects in Shopify Core. The method forces clarity early by documenting desired outcomes, the assumptions about reality driving decisions, and the principles that guide hard tradeoffs.
- •Framework goal: catch misalignment early and avoid trash-can work
- •Outcomes: define what “worth it” looks like after months of effort
- •Principles: pre-decide how to resolve predictable 51/49 forks
- •Assumptions: surface hidden beliefs that cause teams/leaders to talk past each other
- 14:12 – 18:59
Setting product goals without creating gameable metrics
They dig into what makes outcomes hard, especially in platform/core work where impact is indirect and attribution is messy. The conversation broadens into goal-setting failures—metrics that incentivize the wrong behavior across marketing, sales, and retention.
- •Not all outcomes are clean metrics; some are qualitative but must be explicit
- •Core/platform work has long dependency chains that obscure ROI attribution
- •Gameable goals produce perverse incentives (top-funnel vs retention)
- •Cross-functional misalignment shows up as ‘green’ metrics with bad business health
- 18:59 – 22:04
Simplicity at scale: progressive disclosure + app ecosystems
Glen explains how Shopify can serve everyone from tiny merchants to large enterprises without bloating the core product. The two main levers are progressive disclosure (show complexity only when needed) and a high-quality app ecosystem built on first-party-grade tooling.
- •“Stretch” challenge: serving very small through very large businesses
- •Progressive disclosure prevents ‘anti-features’ from adding premature complexity
- •App ecosystems act as a scalable extension layer for advanced needs
- •Ecosystem quality requires third-party builders to have first-party-grade tools
- 22:04 – 24:16
Hardest part of Shopify’s app ecosystem: running third-party logic safely (Functions + WebAssembly)
Harry asks what was most difficult in building the app ecosystem, and Glen points to Shopify Functions. He describes the historical SaaS extensibility tradeoff—security vs performance—and how WebAssembly enables safe, fast execution of third-party logic on Shopify’s servers.
- •Traditional problem: third-party logic can’t safely run on SaaS servers
- •Workaround (apps run on their own servers) creates latency/performance pain
- •Shopify Functions: compile to WebAssembly and run in secure sandboxes
- •Outcome: “best of both worlds” extensibility with hosted performance
- 24:16 – 30:55
Org design and team management: Dunbar numbers, escalation paths, and ‘senior aiming’
Glen describes restructuring Shopify Core after checkout coordination issues revealed org boundaries were blocking cross-team work. He argues that you can’t avoid org charts at scale; the fix is creating sane-sized teams with a leadership layer that actively resolves escalations, paired with strong directional leadership (“aiming”) to keep a product suite coherent.
- •Combining divisions didn’t eliminate the need to re-split into manageable units
- •Dunbar number constraints: why very large teams must be subdivided
- •Old escalation bottleneck: too many issues only met at the CEO level
- •New model: leadership layer handles conflicts quickly and explicitly
- •Leadership philosophy: ‘aim, assemble, achieve’ and the value of ‘senior aiming’
- 30:55 – 42:23
Exceptional storytelling & messaging: making people feel the why (and repeating it)
Glen shares how fundraising forced him to learn real storytelling—moving from process explanations to a relatable narrative anyone can repeat. They debate how to craft messaging that stays authentic while scaling to many personas, and why repetition plus memorable soundbites are essential.
- •Investor lesson: facts aren’t enough—stories must be felt and retold
- •Relatability: explain the problem through a concrete human experience
- •Authenticity matters; scripted messaging fails if you don’t believe it
- •Repetition is mandatory—people forget quickly, so choose a few sticky words
- •Brand tension at scale: broad messaging risks blandness; great brands build ‘armies’
- 42:23 – 45:31
Managing up with a founder-CEO head of product; platform + aggregator strategy; Shopify vs Amazon
Glen explains that Tobi is effectively Shopify’s head of product and discusses how to ‘manage up’ in that reality. He then outlines why Shopify is compelling as a hybrid: a core platform joined to an aggregator engine (Shop), and asserts that this combination makes Shopify a formidable competitor—even against Amazon.
- •Reality of founder-led product: CEO remains the product North Star
- •Managing up: working with (not around) the founder-product leader
- •Platform vs aggregator: different strategies that Shopify is combining
- •Shop reaching critical mass creates compounding value with the core platform
- •Competitive stance: Shopify already competes with Amazon and aims to scale further
- 45:31 – 48:44
Biggest product mistake: misreading the ‘arrow of progress’ and accruing permanent tech debt
Glen describes Handshake’s strategic mistake: building heavily around offline usage when connectivity was rapidly improving. What began as a killer differentiator became a long-term tax as the offline architecture created drag and complexity after the world changed.
- •2010 reality: unreliable connectivity made offline mode a killer feature
- •Architecture built around syncing and offline-first assumptions
- •Connectivity improved (LTE/5G/Wi‑Fi everywhere), reducing the feature’s value
- •Offline-first design became compounding technical debt that slowed innovation
- •Lesson: explicitly forecast where infrastructure trends are headed before hard-committing architecture
- 48:44 – 56:09
Quick fire: delight, CEO–VP product dynamics, Shopify strengths/weaknesses, and Microsoft’s AI bet
In rapid Q&A, Glen highlights a product that delighted him (Roland V-Drums), his views on founder-led product leadership, and Shopify’s strategic strengths and gaps. He closes by praising Microsoft’s OpenAI partnership and aggressive Bing/AI search strategy as an asymmetric bet against Google.
- •User delight example: high-fidelity electronic drums as product craft
- •CEO–VP product relationship: like bandmates (lead singer + drummer) in constant jam
- •Founders and product: if the founder is product-led, they remain ‘head of product’
- •Shopify strength: shipping velocity at scale + platform fused with buyer aggregation
- •Shopify weakness: not controlling top-of-funnel demand sources
- •Admired strategy: Microsoft’s AI search push as a high-upside, low-downside move
