Postman is an API platform for building and using APIs. Postman simplifies each step of the API lifecycle and streamlines collaboration so you can create better APIs—faster with your team
Postman stands out among its competition with a clear head start and an already captured market. But just to name a few would be - mulesoft, stoplight & swagger hub
As a collaborative API platform postman offers the following benefits to the customer -
<aside> 📔 API repository
Easily store, catalog, and collaborate around all your API artifacts on one central platform. Postman can store and manage API specifications, documentation, workflow recipes, test cases and results, metrics, and everything else related to APIs.
</aside>
<aside> 🔨 Governance
Postman's full-lifecycle approach to governance lets adopters shift left their development practices, resulting in better-quality APIs, and fostering collaboration between developer teams and API design teams.
</aside>
<aside> 🔨 Tools
The Postman platform includes a comprehensive set of tools that help accelerate the API lifecycle—from design, testing, documentation, and mocking to the sharing and discoverability of your APIs.
</aside>
<aside> 💼 Workspaces
Postman workspaces help you organize your API work and collaborate across your organization or across the world. There are four different kinds of Postman workspaces for your different needs: personal, team, partner, and public workspaces.
</aside>
<aside> 🔌 Integrations
Postman integrates with the most important tools in your software development pipeline to enable API-first practices. The Postman platform is also extensible through the Postman API and through open source technologies.
</aside>
Classification done on the basis of the size of the organisation. To be short, these are going to be for profit internet based companies with internal development teams in place. Validations done via 5 user calls across all segments
Context related demographic information about our ICPs
| ICP features | Startups | SMBs | Enterprise |
|---|---|---|---|
| Industry type | Deep tech (AI) 🧠 | Fintech 💸 | Enterprise SaaS 💻 |
| Tech team size | 5-25 (developers + PMs) | 50-300 (developers + QA + PMs) | 250+ (Backend developers, frontend developers, QAs & PMs) |
| Company stage | Pre - PMF | Growth | Growth / Maturity |
| Postman plan | Basic | Professional / Enterprise | Enterprise |
| Power user in the team | CTO / backend developer | Product Manager | Quality Assurance (QA) engineer |
| No of daily API calls / power user | 30 - 60 | 50 - 80 | 100 - 300 |
Characteristics around product usage & the problems looking to be solved
| ICP features | Startups | SMBs | Enterprise |
|---|---|---|---|
| General problem statement | Need a tool to quickly check the response of newly developed APIs, to enable collaboration among budding team & ensure proper product functionality | Need a platform to verify the intended development among APIs, organise APIs for ease of use, solve API issues in case of customer dissatisfaction & check 3rd party APIs to scope out integrations | Looking for platform which enables automation to stress test our APIs, quickly verify intended development on exposed APIs & create a shareable API repository for 3rd party devs to interact with product |
| Present solution implemented (most use Postman but I’ll highlight out alternatives here) | IDEs like Visual Studio code & IntelliJ | IBM API connect or Mulesoft | Apache J meter, Gatling with IBM API connect |
| Other tools or services | • IDE - Visual Studio Code, IntelliJ IDE | ||
| • Deployment tool - AWS | |||
| • Documentation - Notion | • Documentation - Notion, Confluence | ||
| • Analytics - Google Analytics, Mixapanel, Amplitude | |||
| • Project management - JIRA, Clickup | • QA specific tools - Selelnium, Testsigma | ||
| • Documentation - Confluence | |||
| • Project management - JIRA | |||
| Point of discovery (for work related tools) | Search, dev community, product hunt & colleagues | Colleagues | Colleagues, Search |
Context related demographic information about our ICPs
Context related demographic information about our ICPs
Analysing how & on what the ICPs spend their money on
| ICP features | Startups | SMBs | Enterprise |
|---|---|---|---|
| Buying decision | Price sensitive but affordable plan available | Performance sensitive with a focus on collaboration | Performance sensitive with focus on safety & automations |
| Decision making structure | Few stakeholders, users directly decide on buying the subscription | More stakeholders, but postman value prop is strong, resulting in its selection | Many stakeholders, decision made by team head depending on the enterprise plan |
| Product retention | Really strong, due to most of the problems solved for the ICP with an affordable plan | Really strong, due to most of the problems solved for the ICP with an affordable plan | Moderate, although the best product for the purpose the enterprise plan need comes out as pricey & with low customization |
| Collaboration b/w Product buyer & user | Mostly same persona | Buyers have less interaction with users but feedback & suggestions can be exchanged easily | Buyers have low interaction with users. But, buyers analyse the performance wrt the price being paid |
Analysing how & on what the ICPs spend their money on
| ICP features | Startups | SMBs | Enterprise |
|---|---|---|---|
| Functional Goals | • Test out development | ||
| • Fast feedback on API design to fast track development | |||
| • To figure out errors obstructing product functionality | • Handling urgent customer facing issues | ||
| • Sanity check over new API developments | |||
| • Organising multiple APIs for easy collaboration | |||
| • Checking third party APIs to be integrated | • Security check on APIs via keys, so that new devs can | ||
| • Stress testing internal APIs for performance benefits via automations | |||
| • Ability to share APIs to customers & other actors | |||
| • Ability to consume APIs with proper cURL | |||
| Social Goals | NA | NA | NA |
| Personal Goals | NA | NA | NA |
| Financial Goals | NA | NA | NA |
