Build Platforms, Not Apps: My Playbook to Delight Customers and Scale Product Strategy

I’ve been reflecting on the product lessons behind a career arc that has reshaped multiple industries. Adam Nash is the co-founder and CEO at Daffy, a platform that makes it easier to donate to charities and non-profits. Before Daffy, Adam was the President and CEO at Wealthfront, where he scaled the company’s assets under management from $100M to over $4B. Adam has also held leadership and technical roles at Dropbox, LinkedIn, eBay, and Apple. As a VP of Product Management, I see enduring patterns in these experiences that every product creator can apply. Over the last decade, many teams have felt that the world is less disruptive than expected. In my view, this “slowness” is less about a lack of innovation and more about the compounding dominance of distribution and platform effects. When platforms harden, apps struggle to break through. That’s why I coach my teams to design for platform leverage from day one—assume the game is about ecosystems, not just features—and to build product discovery loops that create new access, not just new interfaces. We’ve also tended to think about luck incorrectly. What looks like luck is often preparation meeting a catalyzing platform moment. The most resilient companies build the capacity to take advantage of inflection points when they arrive—technically, organizationally, and with a clear point of view on where customer value is migrating. This is product management leadership in practice: orchestrating readiness for the inevitable change while staying grounded in outcomes vs output OKRs. Consider how eBay survived the dot com bubble. The lesson I carry forward is simple but powerful: when your core product creates real network utility and trust, shocks can prune the market and strengthen your position. Liquidity, clear incentives, and disciplined execution make a marketplace anti-fragile. I’ve applied this mindset by prioritizing durability over novelty, especially in critical user flows where reliability trumps speed of iteration. Founders should build platforms, not apps. Platforms create compounding advantages: data network effects, extensibility, and a value surface that invites others to build with you. Apps often cap out at feature parity; platforms unlock a persistent widening of the moat. My test: if your roadmap doesn’t include APIs, a partner strategy, and a value-creation flywheel that improves with every user and contributor, you’re likely shipping an app. If it does, you’re on a platform path. What made LinkedIn successful offers a crisp strategy lesson: good company strategy = good product strategy. When the company’s mission, business model, and product bets align around a clear customer job-to-be-done, execution accelerates. Setting strategy isn’t a document; it’s a cascade of decisions that translates into what we ship, how we measure, and which trade-offs we make. In 2009, that meant focusing on the highest-leverage network use cases and aligning metrics with durable member and ecosystem value. Not every great idea finds its market on the first try. Why KaChing didn’t work and pivoting to Wealthfront underscores core product-market fit lessons: you can’t will a market into existence, but you can iterate into it if you listen to customer behavior, not just customer requests. One universal lesson on customer acquisition I’ve seen repeatedly: the most efficient growth happens when the product itself reduces anxiety and increases clarity at the precise moment of decision. That’s why I treat growth like a product problem—friction maps, value timing, and onboarding narratives are as strategic as any feature release. Leadership transitions are inevitable in growing companies. My advice on successful leadership transitions is to plan them early, be explicit about decision rights, and make “how we decide” a visible artifact across the org. How to delegate moral authority is just as critical as delegating operational authority; teams move faster when they understand not only what to do, but why it is the right thing to do for customers and the company. There’s a real problem with metrics and customer requests when they become the only signals that matter. Metrics are rear-view mirrors and customer requests are often local optima. The craft is to synthesize signals into convictions—and then to earn trust by shipping the right things. Apple’s approach to “delighting” customers is a reminder that delight is not random whimsy; it’s a disciplined practice of removing cognitive load and amplifying emotion at key moments. I use the 70/20/10 rule you’ve never heard about to balance roadmaps: 70% on core commitments, 20% on accelerants, 10% on bold, “delight” experiments. How Daffy ships “delight features” shows how even financial and charitable products can surprise and delight without sacrificing clarity or compliance. Here’s the playbook I carry forward: build platforms, not apps; align company strategy with product strategy; treat growth as a product problem; make leadership transitions a strength, not a risk; and systematize delight so it shows up predictably, not accidentally. Above all, keep your OKRs centered on outcomes, not outputs, and let product discovery be the engine that finds truth faster. Referenced resources I keep handy for deeper study: Andy Rachleff: https://www.linkedin.com/in/rachleff/ Bill Gates: https://www.linkedin.com/in/williamhgates/ Daffy: https://www.daffy.org/ Daffy’s 2023 Year in Review: https://www.daffy.org/resources/year-in-review-2023 eBay: https://www.ebay.com/ Jeff Weiner: https://www.linkedin.com/in/jeffweiner08/ Reid Hoffman: https://www.linkedin.com/in/reidhoffman/ Robinhood: https://robinhood.com/ Ryan Roslansky: https://www.linkedin.com/in/ryanroslansky/ The Innovator’s Dilemma: https://www.amazon.com/Innovators-Dilemma-Clayton-M-Christensen/dp/0062060244 Tim Cook: https://www.apple.com/leadership/tim-cook/ Wealthfront: https://www.wealthfront.com/

---