Visual summary of operating lessons from Abhinav Asthana.

Lessons from Abhinav Asthana

Abhinav Asthana is the co-founder and CEO of Postman, which he built in 2012 out of frustration with testing APIs using cURL. Today, Postman is the default platform for API development. This profile explores how to build infrastructure that scales from a single developer to massive organizations.

Part 1: The Founding of Postman

  1. On the origin: "Postman started because I hated cURL and needed a better way to test APIs while building a web app at Yahoo." — Source: Forbes
  2. On building for yourself: "When you solve a problem that annoys you daily, there is a high chance it annoys thousands of other developers too." — Source: First Round Review
  3. On early validation: "We released it as a simple Chrome extension, and it started growing entirely through word of mouth among developers." — Source: Code Story Podcast
  4. On finding co-founders: "I brought in Ankit and Abhijit because we had complementary strengths: I focused on product, Ankit on engineering scale, and Abhijit on architecture." — Source: Code Story Podcast
  5. On side projects: "The best side projects don't feel like startup ideas; they feel like necessary utilities you just have to build." — Source: First Round Review
  6. On early bootstrapping: "We focused on user growth and keeping the product stable before we even thought about raising money." — Source: SaaStr Podcast
  7. On transitioning out of the browser: "The $1M seed round allowed us to escape the technical constraints of the Chrome browser and build a standalone desktop app." — Source: First Round Review
  8. On ramen profitability: "You want to be in a position where you aren't desperate for funding, which means keeping your burn low early on." — Source: Heavybit DevGuild
  9. On ignoring the hype: "We didn't build Postman to follow a trend. We built it because working with APIs was genuinely painful at the time." — Source: First Round Review
  10. On taking the leap: "Transitioning from my previous startup to Postman full-time happened because the community pull was simply too strong to ignore." — Source: Code Story Podcast

Part 2: The API-First Philosophy

  1. On API abstraction: "APIs are both technical and business abstractions." — Source: Postman Blog
  2. On architecture: "An API-first approach means you design the contract before you write the underlying implementation." — Source: Stack Overflow Podcast
  3. On collaboration: "APIs act as the boundaries between teams, allowing them to work independently without stepping on each other's toes." — Source: Stack Overflow Podcast
  4. On business value: "If your APIs are poorly designed, your business logic is trapped. Good APIs unlock internal data for new revenue streams." — Source: SaaStr Podcast
  5. On standardizing: "We realized early on that developers needed a standard format to share API requests, which led to the concept of Postman Collections." — Source: First Round Review
  6. On testing: "Testing APIs shouldn't be an afterthought. It should be a continuous part of the development lifecycle." — Source: Heavybit DevGuild
  7. On microservices: "The shift to microservices made APIs the primary currency of software development." — Source: Stack Overflow Podcast
  8. On internal versus external APIs: "The standards you apply to public APIs should increasingly be applied to your internal ones, because internal complexity scales rapidly." — Source: Heavybit DevGuild
  9. On the network effect of APIs: "Once developers start sharing collections, the API becomes a living, collaborative entity rather than static documentation." — Source: First Round Review

Part 3: Building for Developers

  1. On developer experience: "Great APIs are defined by great developer experiences. Documentation and SDKs are necessary for API adoption." — Source: Pulse2
  2. On progressive complexity: "A developer tool should be simple enough to use in five seconds, but powerful enough to handle your most complex edge cases months later." — Source: First Round Review
  3. On UI design: "Developers care about aesthetics and usability just as much as consumers do. Clunky enterprise software is dead." — Source: Code Story Podcast
  4. On feedback loops: "You have to actively listen to your community, but also interpret what they are asking for versus what they actually need to solve the root problem." — Source: SaaStr Podcast
  5. On removing friction: "Every extra step a developer has to take to authenticate or format a request is a drop-off point. Remove them." — Source: Heavybit DevGuild
  6. On empathy: "Building for developers requires deep empathy for the moments when they are stuck, frustrated, and on a deadline." — Source: First Round Review
  7. On community support: "Before we had a massive support team, the developer community itself was our support structure." — Source: Code Story Podcast
  8. On non-developer users: "We realized product managers and QA teams were using Postman too, which forced us to rethink the platform's accessibility." — Source: First Round Review
  9. On open standards: "Embracing open standards rather than building walled gardens is how you earn developer trust." — Source: Stack Overflow Podcast
  10. On product updates: "Don't break a developer's workflow with an update unless the new workflow is undeniably faster." — Source: SaaStr Podcast

Part 4: Scaling the Company

  1. On team growth: "Scaling from three founders to over 400 people required a complete overhaul of how we communicate internally." — Source: Stack Overflow Podcast
  2. On hiring executives: "You need to hire leaders who have seen the next stage of growth, but who are also willing to get their hands dirty in the present." — Source: Heavybit DevGuild
  3. On global engineering: "Running distributed teams means writing things down. Asynchronous communication is a necessity, no longer an option." — Source: Code Story Podcast
  4. On maintaining culture: "Culture isn't a poster on a wall. It is the behavior you tolerate when things get stressful." — Source: First Round Review
  5. On early monetization: "We started with simple in-app purchases before realizing that a full SaaS model was necessary to support a growing organization." — Source: Heavybit DevGuild
  6. On letting go of code: "As a technical founder, stepping away from the codebase to focus on company building is the hardest, but most necessary, transition." — Source: Code Story Podcast
  7. On customer segmentation: "As we grew, we had to clearly define who was a free user, who was a pro user, and who needed enterprise compliance." — Source: Heavybit DevGuild
  8. On metric tracking: "Top-of-funnel metrics are the only reliable way to project future revenue plans when you operate a product-led growth model." — Source: SaaStr Podcast
  9. On focus: "There are a thousand features you could build. Scaling requires getting very good at saying no." — Source: First Round Review

Part 5: The Age of AI and Agents

  1. On the AI shift: "Agent Mode is a fundamental rethinking of how AI-native software gets built. It changes how systems interact at a structural level." — Source: Morningstar
  2. On agents as consumers: "As autonomous systems become primary consumers of software, model quality is only half the equation. The other half is whether your APIs are structured, governed, and discoverable enough for agents to use correctly." — Source: Daytona Compute Conference
  3. On AI enabling developers: "AI will clear out the tedious plumbing work so developers can focus on system architecture." — Source: Stack Overflow Podcast
  4. On API governance for AI: "You cannot let autonomous agents run wild on undocumented APIs. Governance is now a safety requirement." — Source: Today in Tech
  5. On LLM integration: "Large Language Models need tools to affect the physical and digital world. APIs are the hands and feet of AI." — Source: Stack Overflow Podcast
  6. On feedback synthesis: "We use AI internally to aggregate and summarize thousands of pieces of developer feedback, turning noise into actionable product insights." — Source: Stack Overflow Podcast
  7. On discoverability: "If an AI agent can't find and understand your API in seconds, it will bypass your service entirely." — Source: Daytona Compute Conference
  8. On prompt engineering: "Working with APIs and working with prompts require similar mindsets: you are constructing specific requests to get predictable outputs." — Source: Stack Overflow Podcast
  9. On the future of software: "We are moving from human-to-machine interfaces to machine-to-machine interfaces orchestrated by AI." — Source: Daytona Compute Conference
  10. On autonomous testing: "The next frontier is AI that writes your tests and continually adapts them as your API surface area changes." — Source: Stack Overflow Podcast

Part 6: Leadership and Engineering Culture

  1. On developer productivity: "Measuring lines of code is useless. Measure how quickly a developer can go from an idea to a deployed, testable service." — Source: Code Story Podcast
  2. On technical debt: "You have to accept a certain amount of technical debt to find product-market fit, but you must pay it down before trying to scale." — Source: Heavybit DevGuild
  3. On cross-functional teams: "Siloed engineering and product teams build disjointed products. They need to sit together, literally or figuratively." — Source: SaaStr Podcast
  4. On managing burnout: "Startup pacing is a marathon of sprints. If you don't enforce rest, your best engineers will break." — Source: First Round Review
  5. On the role of a CEO: "My job shifted from writing code to writing the organization that writes the code." — Source: Code Story Podcast
  6. On transparency: "When something breaks, conduct blameless post-mortems. Fear of failure kills engineering velocity." — Source: Stack Overflow Podcast
  7. On continuous learning: "The half-life of software engineering knowledge is shrinking. You have to hire for adaptability, rather than current stack expertise." — Source: First Round Review
  8. On setting technical vision: "The CEO doesn't need to choose the database, but they do need to set the boundaries of performance and reliability." — Source: Heavybit DevGuild
  9. On remote work: "We learned early that asynchronous tooling makes remote work possible, but deliberate culture-building makes it successful." — Source: Code Story Podcast

Part 7: The Product-Led Growth Engine

  1. On bottom-up adoption: "If you build something a developer loves, they will bring it to work. You don't always need to sell to the CIO first." — Source: SaaStr Podcast
  2. On the freemium model: "Free users act as a distribution network rather than a cost center." — Source: SaaStr Podcast
  3. On time-to-value: "The defining metric of product-led growth is how fast a new user experiences that initial moment of utility." — Source: First Round Review
  4. On onboarding: "Your onboarding flow is your most important feature. If it fails, nothing else you built matters." — Source: SaaStr Podcast
  5. On community as a moat: "Competitors can copy your features, but they cannot easily replicate a community of millions of active users sharing collections." — Source: First Round Review
  6. On user advocacy: "Our best salespeople were engineers who argued with their managers that they needed a Postman license to do their jobs properly." — Source: SaaStr Podcast
  7. On viral loops: "When a developer shares a workspace with a teammate, the product naturally expands its footprint within the organization." — Source: Heavybit DevGuild
  8. On defining usage: "We track active workspaces and API requests sent because logins alone do not equal value." — Source: First Round Review
  9. On balancing free and paid: "You have to give away enough value that the tool becomes indispensable, but reserve the features that solve organizational pain for the paid tiers." — Source: SaaStr Podcast

Part 8: Navigating the Enterprise Market

  1. On the enterprise shift: "Moving to the enterprise means shifting your focus from individual developer productivity to organizational security and compliance." — Source: Heavybit DevGuild
  2. On sales and PLG: "Sales teams in a product-led company should help existing heavy users navigate procurement instead of making cold calls." — Source: Heavybit DevGuild
  3. On security: "For enterprises, an API platform is a potential attack vector. Strict governance and role-based access are mandatory requirements." — Source: SaaStr Podcast
  4. On the buyer versus user: "In the enterprise, the person buying the software is rarely the person using it daily. You have to learn to speak to both." — Source: First Round Review
  5. On legacy systems: "Enterprise architecture is messy. Your tool needs to integrate cleanly with older on-premise systems as well as modern cloud infrastructure." — Source: Heavybit DevGuild
  6. On procurement: "Navigating enterprise procurement cycles requires patience and a completely different operational cadence than software development." — Source: First Round Review
  7. On data residency: "As you expand globally, understanding data residency and regional compliance laws becomes a core part of your engineering architecture." — Source: Heavybit DevGuild
  8. On API sprawl: "Large companies often fail to track how many APIs they have. Providing a central source of truth becomes a massive value proposition." — Source: Stack Overflow Podcast
  9. On long-term vision: "Our goal in the enterprise is to become the foundational infrastructure where all connected software is built and managed." — Source: Code Story Podcast