Mar 30, 2026 · 44m · product-market-fit
He launched a free product for enterprise customers—then grew to $12M ARR in 2 years. | Bhaskar S... · PMF Show
0:00 / 0:00
▶ Watch on YouTube →
gold bands on the timeline = statements, start to end. Hover to read, click to jump. CC turns on captions
In this episode of The Product Market Fit Show, host Pablo interviews Bhaskar Sunkara, co-founder of AppDynamics and Bicycle AI, on how AppDynamics redefined Application Performance Monitoring, scaled to $12M ARR in two years through innovative packaging and PLG strategies, and ultimately sold to Cisco for $3.7B before launching his next enterprise AI venture.
How this conversation actually went
Every chapter scored 0–10 on four independent dynamics. Hover any point for the reasoning behind the score. Pablo holds 13.9% of the talking time here. How this is scored →
Pablo as informed peer 2.6 Guest teaching 3.4 Guest disagreement 0.4 Pablo pushing back 0.9
speaking balance: gold is Pablo, purple is the guest (3 minute bins)
Sharpest disagreement ▶ 12:14 Bhaskar rejects building for developers
Bhaskar emphatically dismisses selling to developers because they give endless noisy feature feedback while lacking the enterprise purchasing budget of IT ops leaders.
Hardest push from Pablo ▶ 16:07 Pablo challenges the counter-intuitive production packagingPablo presses Bhaskar on why other monitoring tools bother selling non-production environments if uptime only truly matters in live production.
Biggest teaching moment ▶ 5:28 Bhaskar explains business transactions vs raw server metricsBhaskar breaks down why measuring CPU usage and low-level code methods creates noise, educating Pablo on why tracking constant business actions like checkouts transformed application monitoring.
Pablo holds their own ▶ 6:39 Pablo synthesizes the business transaction conceptPablo demonstrates understanding by immediately synthesizing Bhaskar's deep technical explanation into a clear, concise commercial takeaway around tying performance directly to discrete user actions.
the scores for every segment, with the reasoning behind each
| Chapter | Topic | Pablo as informed peer | Guest teaching | Guest disagreement | Pablo pushing back | Why |
|---|---|---|---|---|---|---|
| Defining Business Transactions and Targeting the Operations Persona | 2 | 5 | 1 | 1 | Pablo openly acknowledges he is non-technical and asks basic foundational questions to clarify how monitoring worked. Bhaskar educates him on how traditional profiling focused on isolated technical metrics like CPU and database queries, contrasting that with AppDynamics' business transaction abstraction. | |
| Navigating the 2008 Financial Crash by Targeting Critical Software | 3 | 3 | 0 | 1 | Pablo asks standard narrative-building questions about the 2008 financial crash, seed fundraising, and early customer ICP selection. Bhaskar outlines why mission-critical digital businesses like Netflix and Priceline benefited AppDynamics during downturns. | |
| Operational KPIs and Production-Only Packaging Strategy | 4 | 5 | 1 | 2 | Pablo pushes Bhaskar on why status-quo monitoring was so broken and questions why companies packaged software across multiple environments instead of just production. Bhaskar explains the lifecycle vs production dynamic and why enterprise budgets lived strictly in production monitoring. | |
| Product Strategy: Distributed Problems vs. Isolated Problems | 3 | 4 | 1 | 1 | Pablo asks whether the production-only packaging was internal focus or a sales driver. Bhaskar explains the architectural distinction between isolated problems like single-JVM memory leaks and complex distributed transaction failures. | |
| Mid-Show Channel Callout and The Low-Overhead Agent Advantage | 2 | 3 | 0 | 1 | Pablo inserts a mid-show channel promotion and then inquires about the target persona and messaging used in cold outreach. Bhaskar describes targeting IT ops leaders and pitching a sub-2% agent overhead. | |
| Executing Production POCs and the Netflix Performance Benchmark | 3 | 4 | 1 | 2 | Pablo asks practical questions about the operational risks of running agent POCs in live client environments. Bhaskar details running alongside Netflix's bare-metal data centers and proving zero detectable CPU degradation. | |
| Hypergrowth to $12M ARR and Launching AppDynamics Lite | 2 | 3 | 0 | 0 | Pablo asks about revenue milestones and the velocity of early growth. Bhaskar recounts scaling from $2M to $12M ARR and launching AppDynamics Lite as a lightweight self-serve acquisition channel. | |
| Multiproduct Expansion and the $3.7 Billion Cisco Acquisition | 2 | 2 | 0 | 0 | Pablo inquires about the $3.7B Cisco acquisition right on the eve of the planned NASDAQ IPO. Bhaskar explains how Cisco converted from customer to acquirer and how AppDynamics expanded into multi-product monitoring. | |
| Transitioning to Bicycle AI and the Evolution of Agentic Analytics | 3 | 3 | 0 | 1 | Pablo asks about the founding thesis for Bicycle AI and how the rise of generative AI shifted their product strategy. Bhaskar explains moving from purely technical signals to business-level agentic analytics that close the loop on enterprise actions. | |
| Bicycle AI Traction and Closed-Loop Enterprise Deployments | 2 | 2 | 0 | 0 | Pablo runs through the signature closing questions on PMF definitions, near-death moments, and hiring lessons. Bhaskar reflects on early POCs and diagnosing an existential IBM JVM performance bug at Netflix. |
Statements from this episode (14)
Monitoring must anchor on constant business transactions, not changing technical architectures.
“You need a unit of monitoring. You need to approach monitoring in a little bit of a different way where it represents something that is constant. So take Amazon, right? Like, let's just say take Amazon to a 15 year journey. And, you know, when they started off…”
AppDynamics brought deep-dive transaction profiling into production environments safely.
“And typically something like that would only happen in dev or test scenarios. We brought that into production saying, if you do it safely, if you do it with the right heuristics, you can actually go down to that type of level. And that's really what gave us th…”
Targeting mission-critical software helped AppDynamics survive the 2008 recession.
“Wherever the application or software is more critical to running the business, that's what we wanted to focus on. Cause you can't really afford to mess with it. And that was a good sentiment during that time. In hindsight, that helped us really, really well.”
AppDynamics launched exclusively for Java to win early enterprise customers.
“Second, we only wanted to build this for Java. Right. So there's obviously multiple languages, things like Ruby on Rails and all of that type of stuff was also very popular back then. But we saw that the core of the enterprise, you know, we wanted to really go…”
AppDynamics sold exclusively for production environments at a single price point.
“What we said was, let's only do production. Let's not even bother to have a dev version. Let's not even bother to have like a test version, et cetera. Let's only do production, and there's only one cost. So if you want to run it in development, we can give you…”
Netflix, Priceline, and Williams-Sonoma were early customers of AppDynamics.
“Netflix actually was one of the, you know, early ones. Priceline actually was one of the early ones. You know, Williams-Sonoma was one of the early ones.”
AppDynamics' monitoring agent added only 1% to 2% performance overhead.
“And second, it was the overhead part of it on, look, I mean, you barely add one to two percent and you can try this out.”
Offering proof-of-concept trials in production grabbed enterprise buyers' attention.
“And the third thing we said, which was, I think, surprising to a lot of people is that why don't we do a POC in production, right? That was the biggest thing that I would say got people to take notice because they're like, they're this sure of what they built.”
AppDynamics grew revenue from $2M to $12M in its second year.
“I think in the first year we started in oh eight, as you know, and it's been a while, but like just from my memory, the first year we did about a couple million, and then in the second year we did about 12. And the following year we doubled, the following year…”
A free product launch drove over 60% of AppDynamics' inbound leads.
“So that sort of really gave us that momentum because 60% plus of our leads you know, from then on started coming in from that.”
AppDynamics took Cisco's buyout offer over a projected $2B IPO valuation.
“And as we were getting closer to the IPO, then that's when we had the offer a little bit of back and forth here and there, and then eventually we're like, okay, let's, let's take this one, because we weren't going to float at probably around, around two bill, …”
AppDynamics sold over $1 billion in TCV before the Cisco acquisition.
“We just basically, by then, sold a billion in TCP. You know, I don't remember the exact sort of, like, Revenue number, but we had sold a billion in DCV.”
AppDynamics sold software to major banks like Goldman Sachs and JPMorgan.
“We sold to everyone in financial services as well, which is always hard, whether it's Goldman, JP Morgan, You know, we sold the Bank of America, we sold to everyone.”
A scary high-overhead bug during early Netflix testing was IBM's fault.
“Where we were coming up with, like, pretty high overhead, and this was actually at Netflix, and it took us about, you know, maybe a couple of weeks to resolve it, and it actually turned out to be a JVM bug because they were using IBM's JVM versus Sun's JVM, an…”