How Sentry Scaled DevTools to $100M ARR: My Playbook for PMF, B2D, and Packaging

I’m endlessly curious about how category-defining DevTools scale, cross chasms, and find product-market fit more than once. Few stories crystallize that arc better than Sentry’s recent momentum. The journey hits at the heart of what matters in product management leadership: developer obsession, disciplined packaging, and the courage to evolve your model as you scale. Milin Desai is the CEO at Sentry, an application monitoring tool for developers. Sentry has recently passed two key milestones: 100K customers and over $100M in ARR. Before Sentry, Milin was a GM at VMware and scaled their cloud networking into a billion-dollar business. Prior to stepping into leadership roles, Milin was a PM at Riverbed and a software engineer at Veritas. When I look at Sentry’s trajectory, I see two themes that separate enduring DevTools from the pack: Sentry’s developer-centric approach and the discipline to become the need, not the want. In practice, that means solving a daily, high-frequency pain with a crisp path to initial value, and then earning the right to expand by reducing toil, surfacing root cause faster, and integrating seamlessly into the developer workflow. This is also where “Sentry’s B2D model” shines. Developers don’t want to be sold to—they want tools that work with minimal friction, clear docs, and a pricing model that respects their usage patterns. The mantra to “Build for the many, not the few” pairs naturally with Building for the “Fortune 500,000”: design defaults and guardrails for the long tail, then let usage graduate into team and enterprise value. I’ve applied the same mindset in my own teams to unlock self-serve adoption without sacrificing governance or scale. From a go-to-market standpoint, the biggest unlock for me—and a lesson reinforced by VMware—is to Focus on packaging, not pricing. Lessons on pricing, packaging, and product from VMware translate directly to modern DevTools: segment by outcomes (workflow, team size, compliance) rather than by features alone; make upgrades obvious through natural usage thresholds; and tell a simple story that maps to how customers buy. Price becomes the byproduct of a clear packaging narrative. Leadership transitions matter, especially in founder-led companies. Joining Sentry as an external CEO can work brilliantly when the roles are explicit and the operating cadence is healthy. The CEO/founder relationship is strongest when there’s deep respect for the original product intuition and an equally strong mandate to scale what works. I’ve found that Forging successful relationships with founders starts with mutual clarity: who owns vision, who owns velocity, and how decisions get made when data is ambiguous. On product strategy, I resonated with the pragmatic stance on Open versus closed source product. What matters is trust, velocity, and fit with your distribution model. If open source accelerates awareness and credibility with developers, use it. If closed source is faster to iterate and aligns with customer security needs, do that. Either way, the bar is to keep Becoming the need, not the want by removing critical friction in the developer’s day. Scaling Sentry underscores a familiar pattern I coach teams on: instrument everything, shorten the feedback loop, and keep the “Hello, World!” moment under five minutes. The key ingredients to Sentry’s success translate broadly—tight product telemetry, opinionated defaults, and a packaging ladder that meets users where they are. These mechanics compound when supported by a crisp narrative that developers can explain to colleagues in one sentence. As products mature, The second product mindset becomes essential. After initial PMF, the next S-curve rarely arrives by piling on adjacent features. It comes from reframing the job-to-be-done for the broader team: moving from error monitoring to issues ownership, from signal to workflow, from tool to platform. That shift creates room for a Contrarian take on building for enterprise: earn enterprise by nailing the many. Enterprise credibility is the outcome of reliability, scale, and admin controls—not a separate product line too early. Here’s how I operationalize these lessons with my teams: start with developer-first onboarding; anchor packaging to outcomes and usage; harden governance and collaboration as natural upgrade paths; keep docs, SDKs, and integrations as product, not collateral; and measure time-to-value relentlessly. When we do that well, adoption expands organically, sales cycles compress, and customer love shows up in the metrics. In short, Sentry’s arc is a masterclass in disciplined, developer-led growth. For product leaders, the playbook is clear: build undeniable daily value, package it simply, and evolve your model as your users evolve. The rest is execution at every layer—product, pricing, platform, and people.

---