Give individual practitioners a free tool that solves their daily pain, let their sharing spread it virally through teams, then build collaboration features those teams cannot abandon.
Postman
Postman is the world's most widely adopted API platform, used by more than 30 million developers to design, build, test, document, and monitor APIs. It started in 2012 as a free Chrome extension built by Abhinav Asthana to scratch his own itch, and grew into infrastructure that entire engineering organizations standardize on. The through-line: give individual developers a free tool they love and share, turn that sharing into a viral loop, then build the collaboration platform their teams cannot leave.
PMF: A free Chrome extension that nailed the daily pain of testing APIs
The problem. Working as an engineer in Bangalore (at Yahoo, then Tally Solutions), Asthana kept hitting the same friction: making a simple API call, inspecting the response, and debugging it was tedious, and front-end and back-end teams had no clean way to share how an API actually behaved. Existing HTTP tooling was clunky and not built for a developer's real workflow. The pain was small but constant, felt by every developer who touched an API.
The approach. In 2012 he built a minimal HTTP client as a Chrome extension, named it Postman (a play on the "POST" request), and put it on the Chrome Web Store for free. It did one thing extremely well: let you fire a request, see the response, and iterate immediately, with no setup or account required.
How it solved it. The tool spread with zero marketing and reached roughly 500,000 users before the company was even incorporated on September 30, 2014. Google noticed the traction and featured Postman on the Chrome Web Store homepage, which gave it a large visibility boost. That organic, unpaid pull from working developers was the clearest possible signal of product-market fit.
Platform & Ecosystem: From a single testing tool to the full API lifecycle teams standardize on
The problem. A free single-player HTTP client, however loved, is easy to outgrow or replace. As adoption moved from individual developers into teams and enterprises, the real work was no longer just sending a request: organizations needed to design, mock, document, monitor, and govern APIs across many people, and they were stitching this together from fragmented, disconnected tools.
The approach. Postman expanded deliberately from a tester into a unified API platform covering the whole lifecycle: design (OpenAPI, GraphQL, gRPC), build, test, mock servers, auto-generated documentation, monitoring, and shared team workspaces. It also pushed the broader "API-first" thesis, positioning APIs as the building blocks of software strategy and Postman as the single place to manage them. To escape Chrome's technical limits (CORS restrictions), it moved to standalone desktop apps, funded by a $1M seed round led by Nexus Venture Partners in 2015, and later added a web version.
How it solved it. Consolidating the fragmented toolchain into one collaborative platform made Postman sticky infrastructure rather than a utility. By August 2021 the company raised a $225 million Series D at a $5.6 billion valuation, and it now serves more than 30 million developers who use it across the full API lifecycle rather than for a single task.
Growth Loops: Shareable Collections turned every developer into a distribution channel
The problem. Bottom-up tools stall if each user is an island. Postman needed adoption to compound: for one developer's use to pull in teammates, and for the tool to travel across companies and communities without a sales team driving it.
The approach. Postman built Collections, shareable groupings of API requests that a developer could send to a teammate, publish, or post publicly. Sharing a Collection meant the recipient needed Postman to open it, so every share was also an install nudge. Asthana described the result as a "massively multiplayer API experience," and Collections became the unit of viral spread across GitHub, Stack Overflow, Twitter, and Reddit.
How it solved it. The loop scaled dramatically: by 2021 there were roughly 50 million active Collections in circulation, and developers routinely carried Postman from one employer to the next, seeding adoption inside each new company. Combined with a public API network of 100,000+ discoverable APIs, shared Collections turned users into an ongoing distribution engine that grew the developer base past 30 million.