Skip to content

Why should my CMO love APIs?

Jump to bottom Edit New page
Kristopher Kleva edited this page Jul 31, 2013 · 31 revisions

Convener

Kristopher Kleva (@klevland)

Attendees

Notes

APIs mean a lot of different things to different roles in the enterprise. This often exposes the question about who or why key business stakeholders should be on board with your API program.

Considering this I think of leadership at the c-level and how should ultimately have the most skin in the game.

The CIO? - Yes, of course this is a given.

But what about the CMO? What does he care about APIs. Why should they <3 them. This talk will prompt ideas and discussion on the best communications tools we have to communicate to executives.

  • Why should they care?

  • What key metrics are important to communicate?

  • How best to correlate the success of the API program to the success of the business?

  • When asked for a visual representation, what have you used?

  • Do's and Don't with communicating value?

  • Outcome:

Why should my CMO love APIs?

  1. They are the business of highlighting value. Apis provide value.
  2. Because there is nothing worse than missing out out on a trend.
  3. APIs (in some form or another) have historically enabled multiple distribution channels.
  4. Providing APIs can transition a traditional web site into a platform.
  5. They are in the business attracting new customers or leads.
  6. To bind or lock-in existing customers better providing service integration they are less likely to switch.
  7. API consumers are likely different than the rest of your customer base, but have a powerful multiplying effect.
  8. Because you don't want to get your lunch eaten by a competitor who did a fantastic job of reaching out to this segment and engaging them as customers.
  9. Because the value of your product and/or service increases with the number of tools people can use with it.
  10. The API is a means of building long-term customer relationships.
  11. Puts you on the radar of technical people by sponsoring hackathons, writing technical papers, producing technical content.
  12. Customers who integrated our APIs have stayed customers for longer on average and compared to non-integration customers.
  13. Building a community of developers around our API will function as a sales multiplier in our market.
  14. Creates a software halo around our core system that complements the out-of-the-box functionality.
  15. Enables collaboration with integration partners (who rely on our API) in niche markets that we would not address by ourselves cost/benefit-wise
  16. Provides marketing with a new target audience - the integration developer to market the product and/or service and the complementing API.
  17. Conveys a message to end customers that you are committed to meet their specific needs and are satisfied with a leading system and a smart integration

The impetus for creating APIs for an existing product can be entirely of a marketing nature (sometimes championed by engineering, but always from a marketing-as-perceived-by-engineering slant):

  • This would be useful?
  • People would use it and be happier?
  • People will pay for this, or buy our core product in greater numbers?

Do's and Don'ts when pitching APIs:

  1. Never tell anyone "they don't get it"… because they may understand the concepts using different nomenclature.

  2. Don't debate the value or impact to "The Brand" with marketing.

  3. Don't overdose on the technical terminology.

  4. Replace the API acronym with what it enables.

  5. API must not be solely the domain of the developer evangelist, CMO needs to be in on this, but your dev evangelist / API support team should be their shepherd

  6. Be aware of the customer segment actually consuming your APIs. But don't over do it

  7. Be aware of the customer segment actually building (or just using) the applications on top of or integrating with your API.

  8. Ideal use case is to provide a comprehensive product and/or service including an API, not just a pure API.

Use cases

  • Dropbox and Twitter (before it changed tactics) grew because of third-party integrations
  • Nike created Nike+ to prevent user for scraping content
  • IBM Rational Software creates API into products to extend functionality

Links

Add a custom footer
Add a custom sidebar
Clone this wiki locally