Podcast, Interview
a16z Podcast | Product-Market SALES Fit (What Comes First?)
- Jyoti Bansal, founder of AppDynamics (acquired by Cisco for $3.7B), argues that engineering founders often misallocate focus by obsessing over technology rather than user adoption and sales fit during the pre-product market fit (PMF) phase.
- AppDynamics identified its initial market by starting with a broad aperture (interviewing startups, SMBs, and enterprises) before narrowing focus to medium-to-large enterprises building complex distributed Java applications.
- Bansal introduces the concept of "Product Market Sales Fit," asserting that true validation occurs only when a company has the right product, the right market, and a sales strategy that scales together.
- The journey to growth is segmented by revenue milestones: 0–$1M ARR focuses on PMF; $1M–$10M focuses on iterating the sales motion and aligning product features; $10M+ requires scaling sales organizations and potentially adding new product lines.
- Technical founders must break down barriers between engineering and sales; Bansal required engineers to join sales calls to directly understand customer pain points, buying motivations, and budget sources.
- AppDynamics adopted a "sandwich" sales motion (land-and-expand), starting with a freemium model to drive bottom-up developer adoption before leveraging "air cover" from executive leadership to close top-down enterprise deals.
- While services historically reduce margins for vendors, AppDynamics found a 10–15% services-to-software ratio increased overall profitability by accelerating customer adoption, reducing "shelfware," and enabling larger license deals ($1M–$10M).
- Successful expansion into adjacent markets (e.g., .NET, .NET monitoring) required a 2/3 to 1/3 engineering resource split: 2/3 on serving the existing Total Addressable Market (TAM) and 1/3 on expanding into new adjacent markets.
- Companies attempting to sell new products using an existing, mature sales force often fail; Bansal recommends treating new product launches as "startups within a startup" with dedicated "SWAT" teams to navigate the specific sales learning curve.
- The sales learning curve for new products is defined in three phases: founders/product team sell the first 25 customers; specialized sales take 26–100 customers; and the mature, broader sales force executes beyond 100 customers.
- AppDynamics utilized a "Path to 100 Million" and "Path to 1 Billion" strategic planning process to determine if growth required organic development or inorganic growth (M&A/licensing) to meet timelines.
- Pricing strategy should prioritize simplicity and measurability: Bansal's rule was that sales reps must be able to explain the pricing model in "half a sentence" and that the price must be tied to a measurable unit (e.g., production systems).
- Founders are advised to "price higher than they think they should" and rely on a strong Business Value Assessment (BVA) to justify premium pricing, rather than competing on low cost.
- A strong BVA process involves quantifying the customer's current cost of failure (e.g., engineer hours spent on outages) to demonstrate ROI, allowing sales teams to help internal champions justify the purchase to their own bosses.
- When a competitor offers a lower price, superior products should resist downward pricing pressure; Bansal argues that if a product is truly superior, the company should not charge less, as the market will eventually recognize the value.
- The ideal Product Manager profile requires three core skill sets: empathy for the customer, business acumen to align with sales and pricing, and execution capability to deliver the product roadmap.
- Bansal advises founders to focus exclusively on the competencies required for their current revenue stage (e.g., 0–$1M) rather than overthinking strategies needed for future stages (e.g., 75M+ or new product lines).