thumbnail image

APIOps Cycles

  • HOME
  • PARTNERS
  • ABOUT
  • …  
    • HOME
    • PARTNERS
    • ABOUT
Join our Slack!

APIOps Cycles

  • HOME
  • PARTNERS
  • ABOUT
  • …  
    • HOME
    • PARTNERS
    • ABOUT
Join our Slack!
  • HOME
  • METHOD
    • API Canvas
    • Minimum Viable API Architecture
    • Build APIs
    • API Audit
    • Publish API
    • Developer Experience
    • Measure
    • Learn
  • RESOURCES
    • API Business models
    • API Canvas Instructions
    • Collecting requirements
    • Information architecture
    • Business Impact
    • Capacity
    • Local vs. Global
    • Identity and Access management
    • REST API Design Guide
  • PARTNERS
  • ABOUT
  • Search
    • API Business models

      Are you an API Consumer or an API Provider and how does that affect your business strategy?

      The business model covers all aspects of running a business or a product line, from customer segments, to channels, to operational activities, resources, and costs.

      Revenue model is part of the business model

      Revenue model, indirect or direct, only covers the way in which the company receives money or compensation from a product or service. What we need to consider is that APIs can play many roles in a company’s business model.

      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.

      These are all examples of APIs role in the business model from the book API Economy 101 (in Finnish, API-talous 101).

      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:

       

      1. Exactly what problem will this API or endpoint solve? (value proposition)

      2. For whom do we solve that problem? (target market)

      3. How big is the opportunity? (market size)

      4. What are the alternatives out there? (competitive landscape)

      5. Why are we best suited to pursue this? (our unique value proposition)

      6. Why now? (market window)

      7. How will we get this API product to market? (go-to-market strategy)

      8. How will we measure success/make money from this product? (metrics/revenue strategy)

      9. What factors are critical to success? (solution requirements)

      10. 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/

       

      Back to the cycle

    See contact info and follow us

     

    APIOps CyclesTM is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.

    The site is maintained by Osaango Ltd registered in Finland.

    Please let us know of any enhancement needs or derivative work. APIOps Cycles is registered trademark of Osaango Ltd. contributed to http://www.apiops.info community

     

    Graphical icons designed by Freepik from Flaticon

    Privacy Policy
      ×
      Privacy policy
      SECTION 1 - WHAT DO WE DO WITH YOUR INFORMATION?
      When you browse our website, we automatically receive your computer’s internet protocol (IP) address in order to provide us with information that helps us learn about your browser and operating system. 
      
      With your permission, we may send you emails about our site, new services, events and other updates.
      SECTION 2 - CONSENT
      How do you get my consent? 
      When you provide us with personal information to complete a transaction, verify your credit card, place an order, arrange for a delivery or return a purchase, we imply that you consent to our collecting it and using it for that specific reason only. 
      If we ask for your personal information for a secondary reason, like marketing, we will either ask you directly for your expressed consent, or provide you with an opportunity to say no.
      How do I withdraw my consent? 
      If after you opt-in, you change your mind, you may withdraw your consent for us to contact you, for the continued collection, use or disclosure of your information, at anytime, by contacting us at [email protected]
      SECTION 3 - DISCLOSURE
      We may disclose your personal information if we are required by law to do so or if you violate our Terms of Service.
      SECTION 4 – SERVICE PROVIDERS
      Our website is hosted on Strikingly Inc., a Delaware, US based company. They provide us with the website platform including the subscription and web form data you submit to us.
      Your data is stored through Strikingly’s data storage, databases and the general Strikingly application. They store your data on a secure server behind a firewall. More information can be optained from their Privacy policy https://support.strikingly.com/hc/en-us/articles/214364818 
      We use Google’s application suite for email, documents and calendar and Campaign monitor for sending email campaigns. We only allow dedicated personnel to get access to these systems. Emails sent to our general email [email protected] are also stored in PlanMill, our ERP system, for customer service and archiving.
      SECTION 5 - THIRD-PARTY SERVICES
      In general, the third-party providers used by us will only collect, use and disclose your information to the extent necessary to allow them to perform the services they provide to us. 
      However, certain third-party service providers, such as payment gateways and other payment transaction processors, have their own privacy policies in respect to the information we are required to provide to them for your purchase-related transactions. 
      For these providers, we recommend that you read their privacy policies so you can understand the manner in which your personal information will be handled by these providers. 
      In particular, remember that certain providers may be located in or have facilities that are located a different jurisdiction than either you or us. So if you elect to proceed with a transaction that involves the services of a third-party service provider, then your information may become subject to the laws of the jurisdiction(s) in which that service provider or its facilities are located. 
      
      Links 
      
      When you click on links on our store, they may direct you away from our site. We are not responsible for the privacy practices of other sites and encourage you to read their privacy statements.
      SECTION 6 - SECURITY
      To protect your personal information, we take reasonable precautions and follow industry best practices to make sure it is not inappropriately lost, misused, accessed, disclosed, altered or destroyed. 
      
      SECTION 7 - COOKIES
      You are asked separately for accepting cookies on the site.
      SECTION 8 - AGE OF CONSENT
      By using this site, you represent that you are at least the age of majority in your state or province of residence, or that you are the age of majority in your state or province of residence and you have given us your consent to allow any of your minor dependents to use this site.
      SECTION 9 - CHANGES TO THIS PRIVACY POLICY
      We reserve the right to modify this privacy policy at any time, so please review it frequently. Changes and clarifications will take effect immediately upon their posting on the website. If we make material changes to this policy, we will notify you here that it has been updated, so that you are aware of what information we collect, how we use it, and under what circumstances, if any, we use and/or disclose it. 
      If our store is acquired or merged with another company, your information may be transferred to the new owners so that we may continue to sell products to you.
      QUESTIONS AND CONTACT INFORMATION
      If you would like to: access, correct, amend or delete any personal information we have about you, register a complaint, or simply want more information contact our Privacy Compliance Officer at [email protected]
      -----
      Cookie Use
      We use cookies to ensure a smooth browsing experience. By continuing we assume you accept the use of cookies.
      Learn More