11/22/2023 0 Comments Intuit api![]() ![]() To demonstrate that central platform's role in Intuit's ecosystem, and to assist with the visualization of ecosystem assembly, ProgrammableWeb has created a standard graphical template (see above) for mapping the layered features of API-driven ecosystems - one that visualizes not just the various entities within them, but also some extent to which they interact with one another to co-create different forms of value, different business models, and different channels for reaching customers. We believe we're going to be a platform-as-a-business." Speaking directly to that commitment in an interview with ProgrammableWeb, Alex Barnett, head of Intuit's Developer Group said "Platform thinking is central to the way we work. No matter the use case, there would be a single platform to serve all constituencies within its ecosystem. In other words, it started out knowing that once it got around to exposing APIs, that it didn't matter whether those APIs would be exposed to internal developers, external developers, or both (or for what reasons). Although 99% of the API-specific thinking should come later in the journey, there is one critical architectural decision that organizations should commit to early in the process the way Quickbooks did.Ī critical key to Intuit's ecosystem success - as well as that other organizations' ecosystems - is how Intuit envisioned its entire business as a single unified platform a business-as-a-platform (BaaP). The real-world example we'll be using for this article is Intuit provider of the globally popular small business accounting brand Quickbooks. Instead of leading off with a primer on ecosystem concepts and then using a real-world example to demonstrate those concepts in action, let's just dig right into a real-world example and identify the ecosystem concepts it exemplifies. ![]() In other words, how, with the right ecosystem design, a single API fabric can simultaneously enable multiple business opportunities involving new operational models, multiple channels, multiple business models, and new product/service offerings. The purpose of this paper is to use a real-world ecosystem example to demonstrate the subtle complexities of ecosystem design as well as to demonstrate how APIs (with the right ecosystem) are like opportunity multiplexers for businesses. Most people don't know what an ecosystem is, much less how to design one. They start by first establishing business objectives and priorities, conceptualizing the end-to-end customer experiences and business moments needed to support those objectives, and then they organize the necessary ecosystem - including the APIs - to launch the vision. Instead of putting the proverbial cart before the horse, the companies that have done best in the API economy are the ones that save the API details for later. At least not in the droves that you were hoping for. Unfortunately, unlike the mythical baseball diamond in the middle of an Iowa cornfield, if you just go ahead and build it, they (the consumers of your API) are not likely to come. In this follow up, we're revisiting Intuit as our test case and taking that visualization standard to a new level (version 2.0?) where we get into the details of what a successful API ecosystem looks like and how you should go about building yours.Ĭontrary to popular belief, succeeding in the API economy is not as simple as creating an API, tying it to a business model (eg: $ API calls), making the API publicly available on the Internet, and waiting for the money to roll in. ![]() Especially for the benefit of those hoping to learn from the successes of others. Believing that Intuit's journey could be truly instructional to other organizations hoping to join the API economy (and as can be seen from the illustrations in that article), we were inspired to artfully diagram the Quickbooks ecosystem in a way that accurately captured those subtleties.Īfter our initial attempt, we realized how these visualizations could not only serve as a valuable tool, we imagined that we could set a standard for how any organization's ecosystem could be captured, visualized and explained. It demonstrated the importance of putting end-to-end customer experiences and holistic platform thinking way ahead of the premature question "What should our API strategy be?" In the course of interviewing the head of the company's developer group Alex Barnett, we learned about the subtleties that make successful ecosystems tick. How Intuit Designed its API Ecosystem For Both Internal and External SuccessĮditor's Note: In December 2018, ProgrammableWeb published a case study involving Intuit's Quickbooks ecosystem. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |