Visual summary of operating lessons from Jyoti Bansal.

Lessons from Jyoti Bansal

Jyoti Bansal founded AppDynamics and later co-founded Harness and Traceable. This profile examines his customer-discovery, product-roadmap, go-to-market, and internal product-line methods. — Bansal's Harness Merger Essay.

Part 1: Identifying the Right Problem

  1. Experience before founding: Bansal advises engineering students without a compelling problem to gain industry experience first, learn where businesses struggle, and build around a problem they care about. — Don't Rush Into Entrepreneurship.
  2. A frustration worth solving: He describes a recurring frustration that he feels compelled to fix as a useful signal for when to build a company. — Don't Rush Into Entrepreneurship.
  3. Problems beyond the classroom: Bansal cautions that student experience can miss the complex operating problems found inside industries; work experience can expose those problems. — Don't Rush Into Entrepreneurship.
  4. Validate painful problems: In customer discovery, Bansal tests whether a buyer has enough pain to buy anything, enough urgency to buy now, and enough differentiation to buy his product. — Unusual Startup Field Guide.
  5. How AppDynamics began: While working with increasingly distributed applications, Bansal saw that existing monitoring tools would not adequately serve the teams responsible for keeping them running. — Unusual AppDynamics Field Guide.
  6. Motivation from hard problems: Bansal says the chance to build something from scratch and solve a hard, consequential problem motivates him more than money or fame. — FactorDaily Interview.
  7. Customer value over competitor chasing: At Harness, Bansal watches competitors without obsessing over them and uses customer value and willingness to pay as the main guide to what to build. — First Round Interview.

Part 2: Product-Market-Sales Fit

  1. Talk to prospective buyers: Bansal recommends repeated direct conversations with real prospects before narrowing a startup's target customer and pitch. — Unusual Startup Field Guide.
  2. Iterate cold outreach: For AppDynamics, Bansal built a prospect list on LinkedIn, tested outreach messages, studied which company sizes and job titles responded, and refined his targeting. — Unusual AppDynamics Field Guide.
  3. Test the business case: Bansal asks prospective buyers how they would justify a purchase to their boss, using their answer to test whether the product's value can be expressed in business terms. — a16z Podcast Transcript.
  4. Challenge initial assumptions: Harness's customer discovery overturned its initial large-enterprise focus when Bansal found more urgent early demand among mid-sized companies. — Unusual Startup Field Guide.
  5. Cold conversations: Bansal recommends roughly 50 conversations with prospects beyond a founder's friendly network so the feedback is candid and patterns emerge. — Unusual Startup Field Guide.
  6. Product-market-sales fit: Bansal argues that enterprise product-market fit includes a workable way to sell and deliver value; if a useful product cannot be sold repeatably, the product or sales motion may need revision. — First Round Interview.
  7. Founder selling for new modules: For new Harness product lines, the product owner leads early selling with help from account teams until roughly 20–25 customers have received value, then salespeople can take over a repeatable motion. — First Round Interview.
  8. A binary differentiator: Before launching into a crowded market, Bansal wants enough core capabilities to compete and at least one clear capability that distinguishes the new product. — First Round Interview.
  9. Pricing around business value: Bansal favors a pricing model salespeople can explain simply, customers can measure, and the buyer can justify through the value delivered. — a16z Podcast Transcript.
  10. Delivered value before sales scale: Bansal asks how many customers have actually achieved the promised result; a handful of sales without successful outcomes may indicate an immature product rather than weak distribution. — First Round Interview.

Part 3: The Four Lists Framework

  1. The Four Lists roadmap: Bansal organizes product-roadmap input into four lists: current customers, sales opportunity gaps, engineering technical debt, and the product's longer-term vision. A product leader consciously balances them. — The Four Lists.
  2. Current customers: The first list captures needs of existing customers and power users; ignoring important gaps can leave them dissatisfied and less likely to renew. — The Four Lists.
  3. Sales opportunity gaps: The second list records missing capabilities that salespeople identify when a competitor wins a deal, so product leaders can weigh those gaps against other priorities. — The Four Lists.
  4. Engineering technical debt: The third list gives engineering a voice on technical debt and product quality, which Bansal says can suffer when feature work crowds out maintenance. — The Four Lists.
  5. Product vision: The fourth list asks what new capabilities support the product's vision, revenue goals, and potential market expansion. — The Four Lists.
  6. Fund new products in stages: At Harness, Bansal says an internal product line can start with a product manager and roughly five or six people on shared infrastructure, gaining more resources as it proves customer and revenue traction. — First Round Interview.

Part 4: The Startup Within a Startup Model

  1. Startups within a startup: Harness gives new product lines small, semi-independent teams so they can retain ownership and speed while operating within a larger company. — First Round Interview.
  2. Modular product lines: Bansal organizes Harness as separate product-line teams on one shared platform, with each module expected to stand on its own merits rather than ride in a bundle. — First Round Interview.
  3. Dedicated product ownership: Each new module has an owner acting like a startup CEO, responsible not only for product work but also for early customer discovery and selling. — First Round Interview.
  4. Independent teams, integrated platform: The product teams have autonomy, but their modules use shared infrastructure and appear to customers as one integrated platform. — First Round Interview.
  5. Launch multiple modules over time: Bansal says Harness has launched about three new internal product lines a year, allowing the revenue of several maturing modules to compound. — First Round Interview.
  6. Why Harness and Traceable merged: Bansal says Harness and Traceable began with different buyers, then merged as software delivery and application-security needs converged; the merger was a strategic choice, not an automatic result of modular architecture. — Bansal's Harness Merger Essay.
  7. Former founders inside product lines: Bansal says roughly half of Harness's internal product-line leaders had founded companies before; he values that experience but does not make it a requirement. — First Round Interview.
  8. Limit the cost of experiments: Bansal says a new Harness module can begin with a small team; if it cannot find a path to roughly $1 million in revenue, the company can pivot or stop it at comparatively low cost. — First Round Interview.
  9. Scaled autonomy: Bansal seeks enough shared structure and checks to coordinate a large company while letting product teams operate without constant micromanagement. — First Round Interview.

Part 5: Hiring and Talent Density

  1. Hire expertise you lack: Bansal says a founder who lacks sales expertise should recruit a strong sales leader who can build that function, then learn from that person rather than pretending to know the job already. — Sramana Mitra Interview.
  2. Interview for sales mechanics: When assessing sales leaders, Bansal asks them to explain why they missed or exceeded targets and how they built a repeatable process, not just recount a deal they won. — First Round Interview.
  3. Learn through candidate interviews: Bansal says repeated interviews with senior marketing candidates can teach a founder how a function is structured if the founder asks each candidate the same substantive question. — FactorDaily Interview.
  4. India as a product-development center: Bansal said in a 2024 interview that most Harness and Traceable product development happened in India and described the engineering talent there as central to building highly technical products. — Economic Times Interview.
  5. Develop people skills: In his four-dimensions framework, Bansal calls hiring, inspiring, managing, and leading people a skill technical founders must deliberately develop. — SaaStr Talk Transcript.
  6. Challenge with trust: For Bansal, a healthy board challenges management's reasoning and provides oversight while trusting the executives who work in the domain every day to make operating decisions. — First Round Interview.
  7. Sales needs change with scale: Bansal describes the first $1 million as proving product-market fit, $1 million–$10 million as building a repeatable sales model, and later growth as scaling the organization; leadership needs evolve with each stage. — Sramana Mitra Interview.
  8. Delay sales scale until value is proved: Bansal warns that hiring a large sales team before validating product-market fit and the right buyer can rapidly burn cash on an assumption that has not held up. — Unusual Traceable Interview.
  9. Hire for an owner mindset: Bansal looks for people eager to build, act quickly, and take accountability, then tries to remove blockers rather than micromanage them. — Jyoti Bansal Owner-Mindset Post.

Part 6: Navigating the Early Days

  1. Product excellence needs go-to-market excellence: Bansal recalls assuming AppDynamics' superior product would sell itself; after early growth, he learned that scale required equal strength in go-to-market execution. — First Round Interview.
  2. Make advisor time actionable: Early at AppDynamics, Bansal became selective about advisor meetings, prioritizing people who could help bring a customer, employee, or concrete advice on an immediate operating problem. — FactorDaily Interview.
  3. Founder isolation: Bansal describes lonely and difficult founder periods and says having someone to talk to mattered; his first hire became a de facto co-founder in that respect. — FactorDaily Interview.
  4. A downturn sharpened revenue focus: After AppDynamics raised its first round in 2008, the financial crisis constrained further funding; Bansal says that forced his small team to focus tightly on customers and revenue. — First Round Interview.
  5. Assumptions change in discovery: Even as a repeat founder, Bansal says Traceable initially misread its product, target buyer, and sales model and changed all three through customer discovery. — Unusual Traceable Interview.
  6. The green-card constraint: Bansal says his H-1B status delayed his ability to start a company; he worked in startups while waiting for a green card and has argued that those rules should be reformed. — SaaStr Talk Transcript.
  7. Execution over idea novelty: Bansal says recognizing an opportunity is only a small part of company building; the larger work is executing product and distribution faster and better than others who see the same opening. — First Round Interview.
  8. Find urgent buyer pain: In Bansal's customer-discovery framework, a startup must establish that the buyer's pain is pressing enough to buy now, not merely that the product idea sounds interesting. — Unusual Traceable Interview.
  9. Adapt to real feedback: Bansal says founders should be brutally honest when their initial assumptions fail and change the product, buyer, or go-to-market model accordingly. — Unusual Traceable Interview.

Part 7: Transitioning to Enterprise

  1. Build a repeatable go-to-market engine: Bansal says a scalable sales organization needs a model for leads, demos, conversion, seller ramp, and capacity—not an assumption that good products or a few heroic deals will carry growth. — First Round Interview.
  2. Mid-market and enterprise need different motions: Bansal contrasts high-velocity, often PLG and inside-sales-led mid-market selling with longer, more sales-led enterprise cycles, partners, and different product requirements. — First Round Interview.
  3. Let a marquee customer go when the trade-off is wrong: Bansal says AppDynamics let Netflix go after its requests consumed engineering capacity needed for the broader customer base. — First Round Interview.
  4. Plan around ramped sales capacity: At scale, Bansal models how many sellers are hired, how long they take to ramp, and what leads and bookings that capacity should produce. — First Round Interview.
  5. AI shifts pressure after coding: Bansal argues that faster AI-assisted code creation increases the importance of testing, security, deployment verification, and governance in the software-delivery pipeline. — WorkOS HumanX Interview.
  6. Do not reuse the first founder playbook blindly: Bansal says repeat founders should not assume a successful first-company approach will transfer unchanged; Traceable's initial buyer and sales assumptions had to be corrected. — Unusual Traceable Interview.

Part 8: The Founder's Journey

  1. Four founder-development skills: Bansal names technology, business, people, and sales savviness as four dimensions technical founders need to develop deliberately. — SaaStr Talk Transcript.
  2. Sales as a founder skill: Bansal calls the founder's job continuous selling—to recruits, investors, and customers—and suggests thinking of it as inspiring people to join the mission. — SaaStr Talk Transcript.
  3. Engineer to CEO is learned gradually: Bansal says his transition from engineer to CEO came through many small learnings and struggles, especially building business and people leadership skills. — FactorDaily Interview.
  4. Ask specific people for specific help: Instead of collecting generic advisors, Bansal seeks people who have solved the particular operating problem in front of him and asks them for focused advice. — FactorDaily Interview.
  5. Manage for impact, not hours: Bansal says he allocates attention by where he can make the greatest difference—product, hiring, financing, or go-to-market—rather than by a fixed percentage of time. — The Stack Interview.
  6. Stay close to customers as a repeat founder: When starting Harness, Bansal deliberately avoided management layers and worked directly with early sales reps and customers so his prior CEO experience would not distance him from the problem. — First Round Interview.
  7. A difficult pre-IPO sale: Bansal says Cisco's offer days before AppDynamics' planned IPO led to difficult board debate over shareholder outcomes and execution risk; board misalignment was also a factor in selling. — First Round Interview.
  8. Continuous improvement as culture: Bansal says he emphasizes steady improvement and delivered customer value over a demand for perfection, while balancing team autonomy with shared operating structure. — First Round Interview.