An Idea Before Its Time
When Lew Cirne founded New Relic in 2008, he wasn't new to the game. He had already founded and sold a successful company, Wily Technology, in the same software monitoring space. His vision for New Relic was ambitious: a comprehensive, all-in-one platform
to monitor every layer of a company's tech stack, from servers to application code. The idea was to provide a holistic view of system health. It was a powerful concept, but it had a fatal flaw. The product was a solution in search of a problem that most of its potential customers didn't yet know they had, or at least couldn't easily justify solving with a complex, enterprise-level tool.
The Wrong Market, The Wrong Message
The initial product was too broad and unwieldy for the market that was most open to innovation at the time: small, agile teams of developers. In a 2011 post, Cirne explained his revised strategy of focusing squarely on the burgeoning Ruby on Rails community. This niche was growing fast but was too small to attract heavyweight competition. The first, all-encompassing product was a tough sell. It required significant setup and a top-down, enterprise buying decision. In contrast, developers in the trenches needed something they could adopt quickly, often without a manager's approval, to solve an immediate, painful problem. The first product was a powerful cannon aimed at a target that needed a laser pointer.
The Ruby on Rails Pivot
The turning point came when Cirne and his team recognized this disconnect. Instead of trying to sell their grand vision, they decided to solve one problem exceptionally well. They built a lightweight, easy-to-install agent specifically for performance monitoring Ruby on Rails applications. This was New Relic RPM (Ruby Performance Management), the product that would ultimately define the company. It was delivered as a Software-as-a-Service (SaaS) tool, which was a revolutionary approach at the time for application performance monitoring. Developers could sign up, install the agent in minutes, and immediately see where their code was slowing down. This solved a specific, acute pain point and created a groundswell of grassroots adoption.
The Power of a Painkiller
The initial product was a "vitamin"—a nice-to-have tool that promised general corporate wellness. The new product was a "painkiller." For developers struggling with slow applications and frustrated users, RPM was a direct cure. The success of this focused approach provided the traction and revenue New Relic needed to survive and grow. By winning the trust and loyalty of developers one project at a time, they built a massive user base. Only after establishing this strong foundation did the company begin to expand its offerings, gradually building out the comprehensive, multi-product observability platform that Cirne had originally envisioned. They eventually added monitoring for infrastructure, mobile apps, and user browsers, but each new feature was built on the success of the last.
