Episode Summary
Executive Summary: The episode argues that enterprise startups should think beyond product-market fit to "product-market-sales fit": product design, pricing, services, and sales motion must evolve together. Jyoti Bunsel explains how AppDynamics used a broad-to-narrow market search, freemium plus enterprise sales, services at the right level, and staged product launches to scale from early customers to large enterprise revenue.
Main Topics: Product-market-sales fit vs. product-market fit (Priority: 5/5): The discussion reframes fit as a combined product and go-to-market problem, where the product must support the intended sales motion and customer buying process. Finding the right market before narrowing (Priority: 5/5): For pre-PMF companies, founders should start broad, interview multiple segments, and then focus on the market with the strongest pain and willingness to pay. Matching sales motion to product and customer (Priority: 5/5): The speakers compare bottoms-up, self-serve, inside sales, and field sales motions, emphasizing that the right model depends on complexity, buyer count, and enterprise buying behavior. Services as an adoption and revenue lever (Priority: 4/5): Services are presented not as margin destruction but as a way to drive adoption, reduce shelfware, and unlock larger software deals and renewals. Pricing and packaging discipline (Priority: 5/5): Pricing should be simple, measurable, and tied to business value; founders should price higher than they think and use ROI to justify premium pricing. Product roadmap and startup-within-a-startup (Priority: 4/5): As companies grow, they must balance core roadmap work with adjacent market expansion and often create a separate motion for new products so mature sales teams do not stall innovation. Stage-specific company building milestones (Priority: 5/5): Bunsel outlines how priorities change by revenue stage: first finding PMF, then sales fit, then scaling sales, and only later building multiple products or buying growth via M&A.
Key Arguments: Technical founders often over-focus on features; enterprise success requires building the go-to-market motion in parallel with product development. The first phase of product-market fit is figuring out where the pain is most acute by interviewing broad market segments before narrowing the target buyer. Product features should inherit the sales motion: if the company is freemium, lend-and-expand, or direct sales, the product must be designed to support that path. Enterprise companies often need both bottoms-up and tops-down selling; AppDynamics used a "sandwich strategy" that started with developers and DevOps and then expanded upward. Services can improve adoption and increase blended economics when they help customers realize value on large software purchases; a small services attach can enable much larger license deals. Pricing should be understandable in one sentence and measurable before and after sale; otherwise sales and customers cannot plan or justify the purchase. Founders should not price low to win deals; if the product delivers superior value, the company should capture that value and discount only when necessary. New products need a new sales learning curve; mature reps may fail on immature products, so companies may need evangelists or startup-like teams for first customers. As companies scale, they should keep most engineering resources on the current TAM while dedicating a portion to adjacent markets to expand revenue over time. Company priorities should change by stage, so founders should focus on the skill required for the next milestone rather than trying to solve every future problem too early.
Data Points: AppDynamics acquisition value: $3.7 billion - Cisco acquired AppDynamics the night before its planned IPO. Pre-PMF revenue range: $0 to $1 million ARR - Bunsel described this stage as where the company validates a real product and initial customer pain. Sales-fit revenue range: $1 million to $10 million ARR - Used as the stage where go-to-market strategy and product alignment are refined. Scale threshold: $10 million ARR - Bunsel said reaching this level indicates product-market-sales fit is in place. Engineering allocation rule: 2/3 existing TAM, 1/3 new TAM - AppDynamics used this rough rule to balance core product improvement and adjacent market expansion. Services attach rate: 10% to 15% - Bunsel said this was the balance where services improved adoption without overly hurting margins. First-year services example: $100,000 services on $1,000,000 software - Illustrative example used to explain how services can support large software purchases. Early customer phase: First 25 customers - Bunsel described this as the initiation phase where founders or product management must sell like a startup. Product maturity phase: After 100 customers - At this point, the broader sales force can sell the product effectively. New-product launch support: 8 months - A SWOT team at AppDynamics worked for about eight months to create the motion for a fourth product line. Adjacent revenue target: 40% of revenue from new adjacent products - Bunsel estimated this mix would be needed to grow from $100 million to $1 billion in about 6-7 years. AppDynamics first four years: 0 services - The company initially avoided services until larger enterprise deals required them. Time saved by acquisition: 2-3 years to about half - Bunsel noted acquiring technology could materially accelerate product development versus building from scratch.
Pivotal Quotes: "We should call it product market sales fit." — Jyoti Bunsel: He introduced this as the more accurate framing for enterprise go-to-market. "If you can understand the business value of your product, that's when you know." — Jyoti Bunsel: He offered this as his practical definition of product-market fit. "Don't overthink too far ahead in many cases as well." — Jyoti Bunsel: His parting advice was to focus on the milestone and skills needed for the current revenue stage.
Implications: Enterprise founders should design product, pricing, services, and sales together from day one. As the company scales, they need stage-appropriate motions, disciplined focus, and separate launch teams for new products to avoid stalling growth.
About The a16z Podcast
The a16z Podcast discusses tech and culture trends, news, and the future – especially as ‘software eats the world’. It features industry experts, business leaders, and other interesting thinkers and voices from around the world. This podcast is produced by Andreessen Horowitz (aka “a16z”), a Silicon Valley-based venture capital firm. Multiple episodes are released every week; visit a16z.com for more details and to sign up for our newsletters and other content as well!