APIs provide a way to improve, change or add to your current business models. APIs are important if your goal is to create an internal and/or external platform. APIs can also help cut costs by re-using and sharing resources or to create a network effect in your business model.
Is API really a product or something else?
The modern way of thinking about APIs is often that API is a product. But is it really? As the previous business models imply, an API can be so many other things in a company's business model than just the product. But it should always be productized.
Applying product management thinking to APIs
By creating APIs the company or the team becomes an API provider. API provider needs to deliver value to internal and external customers and partners. Because of this, APIs need to be considered as products or productized digital services in their own right. APIs need to be designed and split according to what value propositions they offer.
Each API and each endpoint should be evaluated and designed based on:
What data or functionality is our customer willing to pay for?
What will make them more committed to engage with us and co-create with us?
What data or functionality should we expose to our partners?
What will make them engage with us more efficiently and be able to support us and our customers in a better way
What is the data or functionality most needed by our customers and partners or our own service development?
Which of those needs are easiest to implement and contains the lowest risk but highest potential
In broadest sense value proposition can be described as a formula where Value = Benefits - Cost (cost includes economic risk).
Developing a value proposition is based on a review and analysis of the benefits, costs, and value that our company can deliver to its customers, prospective customers and other members in the network of our company and within our company.
Treating APIs as digital products means they can be bought, sold and shared. Below is a useful list for assessing the business opportunity with APIs.
Assessing API opportunities:
Exactly what problem will this API or endpoint solve? (value proposition)
For whom do we solve that problem? (target market)
How big is the opportunity? (market size)
What are the alternatives out there? (competitive landscape)
Why are we best suited to pursue this? (our unique value proposition)
Why now? (market window)
How will we get this API product to market? (go-to-market strategy)
How will we measure success/make money from this product? (metrics/revenue strategy)
What factors are critical to success? (solution requirements)
Given the above, what’s the recommendation? (go or no-go)
Source: Marty Cagan, Silicon Valley and MindTheProduct -network guru of product management: http://svpg.com/assessing-product-opportunities/