What do you like best?
This is an important spanner in the startup developer toolkit. They have added a lot of functionality over the last 3 years since we started using it and Postman proved useful enough that it was the first dev tool we paid for - and we were stingy back then.
The ability to create collections, put in multiple example requests+responses for each API and share them with the team is now a core part of our dev workflow.
What do you dislike?
The user interface could be dramatically better. The ability to share environments, templates, collections is confusing - it can be done from a few different places and the user interface isn't really conducive to building muscle memory of where to access which functionality.
Anytime I need to touch anything sharing/un-sharing related, I know I am going to click in a few different places before I get to what I really want to do.
The Collections cannot be ordered in the sidebar based on user's needs - and only supports automatic alpha sorting. Staring/unstaring collections also mysteriously reorders the collections. So good luck organizing them.
What business problems are you solving with the product? What benefits have you realized?
As a startup, communicating APIs through documentation - code or otherwise - is expensive and error prone - and frankly we don't have the time for it at the pace at which we move. It is much more preferable to have the API developers test using Postman and then progress those tests- and the variations of those tests into collections of API calls that serve as documentation of those service end points.
Postman has the ability to save snapshots of API calls for a given call - which serves the client developers well in that they are able to see the various ways to call the API, the error codes supported etc. Also since these collections can be published, it is great as API documentation.