<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Nate Soffio on Medium]]></title>
        <description><![CDATA[Stories by Nate Soffio on Medium]]></description>
        <link>https://medium.com/@natesoffio?source=rss-9f3be0c685f2------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*fnuxJNEMrLaLu1T4RggAKQ.jpeg</url>
            <title>Stories by Nate Soffio on Medium</title>
            <link>https://medium.com/@natesoffio?source=rss-9f3be0c685f2------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 13:23:54 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@natesoffio/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[On APIs and SaaS Unit Economics]]></title>
            <link>https://medium.com/wharton-fintech/on-apis-and-saas-unit-economics-1de25bb2746d?source=rss-9f3be0c685f2------2</link>
            <guid isPermaLink="false">https://medium.com/p/1de25bb2746d</guid>
            <category><![CDATA[software]]></category>
            <category><![CDATA[fintech]]></category>
            <category><![CDATA[economics]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[api]]></category>
            <dc:creator><![CDATA[Nate Soffio]]></dc:creator>
            <pubDate>Tue, 09 Mar 2021 17:44:24 GMT</pubDate>
            <atom:updated>2021-03-09T19:51:18.507Z</atom:updated>
            <content:encoded><![CDATA[<p>In the first article in our seven-part series (<a href="https://www.qedinvestors.com/apis-are-everywhere-an-intentional-choice-being-api-first/">APIs are Everywhere An Intentional Choice: Being API First</a>), we detailed that while APIs are everywhere, the implications are under-appreciated. In discussing the strategic considerations of being API first, we answered key questions including, “What makes a good API?” and, “What does it mean to be an API-first company?”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*H1WcfW1kbQpfJMGEf7ECJQ.jpeg" /></figure><p>This article will comment on the role APIs play in SaaS unit economics and how these power dynamics have fundamentally altered the long-run view of customer experiences and buying expectations in financial services.</p><h3>RIP ASPs.</h3><p>Let’s start by pouring one out for the legacy application service providers of yore.</p><p>Gartner <a href="https://www.gartner.com/en/information-technology/glossary/asp-application-service-provider">defines</a> them as:</p><blockquote>An application service provider (ASP) is defined as an enterprise that delivers application functionality and associated services across a network to multiple customers using a rental or usage-based transaction-pricing model. Gartner defines the ASP market as the delivery of standardized application software via a network, though not particularly or exclusively the Internet, through an outsourcing contract predicated on usage-based transaction pricing. The ASP market is composed of a mix of service providers (Web hosting and IT outsourcing), independent software vendors and network/ telecommunications providers.</blockquote><p>These are your SAPs, NICEs etc. of the world — they’re still globally vital and play a role in many enterprise software deployments. But consider for a moment all the legacy tech deployment in banks<strong> that effectively create huge deadweight losses</strong> because they are too cumbersome to fill new whitespace as the world changes around them¹. Despite still having incumbent status all over the globe, these software products emerged in an era when the market sought 1:1 replacements for different parts of the customer value chain.</p><p>These ‘OG’ B2B vendors were synonymous with long, onerous implementations. They forced their customers to adapt to the vendor’s way of doing things and charged extra for services that were needed to ensure their software worked in the customer’s system.</p><p>The consumer suffers and the vendor lacks uniform repeatability at scale.</p><p>One of Amias’ friends was a salesperson at a SaaS company that was acquired by one of the giants. On his first day in the new company, his new boss sat down with him and asked, “OK, so how do we use your software to sell consulting and implementation services?” Shocked — <em>“the whole point of software as a service is that the product keeps improving and you don’t need to sell…services,”</em> — he thought as he politely nodded. Needless to say that he and the rest of the team left the giant to start a new company as soon as their earnouts were complete.</p><p>Meanwhile, the vast majority of fintech startups (both B2B and B2C) are gravitating toward ‘usage based/recurring revenue’ or subscription-based models — definitionally software-as-a-service (SaaS).</p><h3>SaaS Unit Economics, A Recap</h3><p>Banks need to remember this: the number one strategic imperative of every software company is to become a SaaS company. This sounds simple…every tech company is claiming to be a SaaS company anyway. But being a SaaS company is not just a fashionable label. It is an identifiable economic business model whose soaring valuation multiples appear to be sustainable judgments of their long-term economics, not just a faddish mania among investors.</p><p>One simple way to think about SaaS economics is a relationship between an hour of developer time and enterprise value. SaaS economics are characterized by gross margins of 60 percent to 80 percent, often higher, and the cost of revenue decreases since every line of code can be copied into the software of all customers. With lower R&amp;D costs coupled with greater deployment efficiency, SaaS companies ship greater marginal utility more quickly and can steadily increase fees without losing customers — a dollar of revenue today is worth more than a dollar a year from now. The impact? SaaS companies have the two properties that investors crave the most — diminishing marginal cost and extreme scalability. These two operational features drive SaaS valuations and are the holy grail for tech CEOs and the investors who back them.</p><p>The other wonderful thing about SaaS unit economics is revenue protection. Great SaaS companies force their customers to answer the following question: why incur switching costs if the current product works and gets better month-over-month, year-over-year? The deeper in the customer’s tech stack that a SaaS company can provide value, the higher the other downside risks become — training, hiring, security, switching etc. Stickiness plus lock-in equals negative churn.</p><h3>API-first unit economics — same but different</h3><p>To go back to an earlier metaphor, the broader fintech landscape is quickly morphing into an ecosystem of legos, where the market is continually calibrating between internally built or externally licensed products and services. But whether home-built or purchased, these services must be pluggable and interoperable to be worthwhile.</p><p>The customers’ desire for lego bricks and the SaaS companies’ desire to be embedded in infrastructure, combined, will continue to drive software providers to become API-first companies. But the APIs have to be monetized in a distinctly different way from most SaaS today.</p><p><strong>First, APIs should have lower switching cost than traditional SaaS.</strong> An API-first approach demands stronger standardization (see: Swagger, OAS etc.). In an era punctuated by support for new standard models like Open Banking and Open Healthcare and recent regulations like PSD2 (more on that later), the market itself has continued to apply pressure to software providers to adopt common standards that participating vendors and institutions can rely on to work with mutually intelligible input and output (more on that in Article 6 in our seven-part series). And historically, the highest switching cost in technology is training employees and developers — but APIs allow for a higher degree of decoupling across tools and business units, so “learning” new APIs is not strictly that difficult.</p><p><strong>Second, because APIs are inherently self-contained, the natural up-sell/cross-sell opportunities are more at the will of the customer than at the will of the vendor</strong>. Choosing to use any given API from a company does not strictly lock you into their entire ecosystem. Using legos grants architectural liberties, though that also includes ease of replacement, risk of churn, and overall revenue volatility. On balance, the strongest API-first companies are adept at creating complementary products (each with their own API endpoints) that make incremental adoption easy and painless. <strong>Nevertheless, these companies drive customer lock-in by choice, not by force, and therein lies another key distinction.</strong></p><p>Building and maintaining great APIs is a cost-effective strategy. But it’s cost-effective for all API-first players, so as API providers’ COGS gets cheaper, sellers lose pricing leverage and revenue protection as switching costs become lower. APIs have great COGS and the market knows it, so expectations around willingness to pay pressure API providers to price their baseline licenses lower than SaaS. <strong>Consequently, API-first approaches converge on competition at the product/utility and value level,</strong> not at the price level, giving API consumers a much larger degree of purchasing freedom than their SaaS-purchasing counterparts.</p><p>Traditional SaaS is priced on a per-user basis, so unless your customers grow or shrink significantly, SaaS deployments tend to have very predictable revenue. No seasonality, no surges and stops, just clean, predictable growth based on churn and upsells.</p><p>In contrast, APIs tend to be priced based on how much they’re actually used. Each time a user submits a request or extracts a unit of data, they pay a small toll. Like we said, this means that revenue can be much more volatile than classic SaaS.</p><p>But, there is broad recognition that these usage-based models can be just as powerful as traditional SaaS, though they must be managed and valued differently. Our friends at OpenView partners have an excellent overview of this trend in general tech <a href="https://openviewpartners.com/blog/usage-based-pricing-playbook/#.YDaH2S1h0Us">here</a>.</p><p>So the greater degree of difficulty for cross-sell, the higher risk of churn and greater revenue volatility means it’s looking likely that API-first companies will not fit the same economic model as a pure SaaS offering. Should those companies or their investors worry?</p><h3>API-first growth strategies — benevolent complementarity</h3><p>Because API-first offerings must be self-contained, API-first companies cannot ‘gotcha’ their customers into upsells and cross-sells. Instead, account growth is organic based on smart productization of complementary offerings. Here’s how it plays out.</p><p><strong>First, deployment repeatability gives API-first companies a unique economy of scale.</strong> Remember that SaaS economics are defined by constantly improving software; API-first economics also need to be defined by this constant improvement, but the improvement tends to be measured in more nuanced ways. Such companies shouldn’t change the fundamental inputs or outputs (you can’t change the shape of a lego block that’s in your Harry Potter castle!). This constraint forces hyper focus on the scalability of the product: the latency, reliability, resilience and scope of methods. Every business process will have bugs and exceptions; API-first companies compete by limiting the extent to which their deployed services ever appear as a root cause in those exception processes.</p><p><strong>Second, repeatability gives API-first companies the right to deploy new, closely related and complementary functions for their customers.</strong> “<em>Hey, we know that you’re using our API to get location data on your customer’s transaction, we now have the ability to give you device fingerprint data as well. Would you like that?”</em> This is the second key advantage that API-first companies should be able to build: speed to deploy and speed to link complementary services over time. Being API-first is hard work, but once some of the groundwork is down, the discipline of atomic thinking and the modularity inherent in the product tends to make launching new features and functions faster than others. Moreover, increasing the number of systems and number of functions that include your API creates a defensible feedback loop, so the long-term value of achieving a first-mover advantage is high.</p><p><strong>Third, API-first companies are ecosystem accelerants and increase the value of players both above them and below them in the tech stack</strong>. API-first companies are naturally symbiotic — they succeed when the companies around them in the ecosystem succeed. Whereas you can have a somewhat successful standalone SaaS solution, you cannot have a successful standalone API implementation; it defeats the point. So the greater the interoperability — a proxy for stickiness — the easier it will be for customers to invest and deploy new use cases building on top of API functionality with which they’re already familiar. <strong>The result? Great API-first companies will demonstrate both strong organic in-account adoption and gross retention.</strong></p><p>Fourth, as an API’s set of available functionality grows, the amount of value per unit added to the code <strong>increases as long as the API supplier has a sufficiently diversified customer base</strong> (horizontal growth) and can continue to roll out additional complementary features (vertical growth). <strong>TL;DR: grow horizontally first</strong> — <strong>as many customers as you can identify that need to function your API delivers, then vertically</strong> — <strong>finding the next adjacent function and trying to deliver that within the industry verticals you’ve penetrated.</strong></p><p><strong>Fifth, API-first strategies place a premium on distribution and channel utilization</strong>. So, while implementation costs shrink (users can basically implement it themselves), and repeatability increases, the reliance on partners and channels plays a greater overall role because the technology is highly portable. An API-first company will make money wherever it’s implemented by its own users — low cost, high repeatability.</p><p>Ask yourself this: can you count how many times this holiday season you bought something online and paid via paypal or stripe? And though these companies both have robust APIs, I bet you knew when you were paying with PayPal but not necessarily paying with Stripe.</p><p><strong>Finally, sufficiently-sophisticated APIs, when implemented, create hard-to-reproduce datasets (remember that thing about moats?).</strong> Most importantly, the robustness of an API, combined with its usage, is positively correlated with <em>data exhaust</em>, that wonderful byproduct that goes into creating value-add proprietary datasets. In fact, the strongest-performing API-first companies are masters of exploiting this trait — in macroeconomic terms, you might think of this as an <em>increasing</em> marginal product of capital. As a result, an API-first company is uniquely positioned to maximize their users’ chances of developing proprietary data sets and features — recommendations, modeling and predictions, risk scores, price transparency, process metadata etc.</p><p>In the next section we’ll walk through an example of how this has played out historically between vendor and buyer before turning to the practical impacts these forces have on traditional banks and nontraditional financial applications.</p><p>[1] One may consider this the external ramification of tech debt — rather than legacy tech holding back development, this is legacy tech holds back the capacity to clear a market.</p><p>**</p><p><strong><em>Amias Gerety</em></strong><em> is a partner at QED Investors, a leading fintech venture capital firm. His investing has focused largely on back office and infrastructure themes. Prior to QED, Amias was Acting Assistant Secretary for Financial Institutions in the Obama Administration.</em></p><p><strong><em>Nate Soffio</em></strong><em> is an MBA Candidate at Wharton focusing on fintech, regulation, and financial inclusion. There, is the co-chair of Wharton’s Fintech Conference taking place April 22–23. Hailing from Stamford, CT by way of Medellin, Colombia, he spent a decade building (and breaking) things in the infrastructure and regtech worlds with a focus on Know-Your-Customer and identity management. Before Wharton, he helped lead product at Arachnys, a London-based regtech and QED portfolio company. In his spare time you can find him road cycling, rock climbing, and cooking.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1de25bb2746d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/wharton-fintech/on-apis-and-saas-unit-economics-1de25bb2746d">On APIs and SaaS Unit Economics</a> was originally published in <a href="https://medium.com/wharton-fintech">Wharton FinTech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[APIs  Are Everywhere]]></title>
            <link>https://medium.com/wharton-fintech/apis-are-everywhere-b4645c562277?source=rss-9f3be0c685f2------2</link>
            <guid isPermaLink="false">https://medium.com/p/b4645c562277</guid>
            <category><![CDATA[investing]]></category>
            <category><![CDATA[fintech-app-development]]></category>
            <category><![CDATA[fintech]]></category>
            <category><![CDATA[api]]></category>
            <category><![CDATA[economics]]></category>
            <dc:creator><![CDATA[Nate Soffio]]></dc:creator>
            <pubDate>Tue, 02 Mar 2021 19:07:17 GMT</pubDate>
            <atom:updated>2021-03-02T19:56:24.739Z</atom:updated>
            <content:encoded><![CDATA[<p><em>A word of thanks: Amias and I met in late 2017 when I started at Arachnys and QED joined as an investor. Since then he’s become a friend and a mentor and I’m grateful we could collaborate on this miniseries.</em></p><p>APIs are everywhere, but the rise of <em>API-first companies </em>is still under-appreciated.</p><p>This is the first of 7 essays I’ve written in partnership with <a href="https://medium.com/u/a3bbd03cb722">Amias Moore Gerety</a> of QED Investors that walks through why every SaaS business must eventually become an API-first company to survive.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wixTiEwCKNNudJC_nASjgg.jpeg" /><figcaption>Great APIs beget great legos.</figcaption></figure><h3>An Intentional Choice: Being API First</h3><h3>Preamble</h3><p>Welcome to the first in a series of essays that lays out a guide to the next generation of SaaS. <strong>In no uncertain terms, in the modern software era, the API is the product</strong>. Every SaaS company must turn into an API-first company to survive.</p><p>A cursory search on Pitchbook for fintechs with ‘BaaS’ (banking as a service) or ‘API’ as keywords returns more than 2,000 hits worldwide. Since 2015, invested capital in platform- and API-led financial technology has more than quintupled, with 2020 clocking in at more than $80 billion USD invested worldwide, up from ~$15 billion in 2015.</p><p>It is already true that at the center of every financial SaaS company, every modern fintech infrastructure, every challenger bank, every anti-financial crime stack and every company pursuing financial inclusion is the humble API, or application programming interface.</p><p>But the prevalence and acceptance of APIs actually understates the current moment for SaaS companies and SaaS-investors. What we think of as the great SaaS companies have been built by mastering human-machine interaction, but the next generation of great SaaS companies will be based on machine-machine interaction.</p><p>APIs are everywhere, but still the implications are under-appreciated. The distinction between using APIs and <em>being</em> an API-first company is like the difference between companies trying to replicate their web offerings on a phone (remember m.facebook.com) and companies that actually built for mobile (Instagram).</p><p>Over the next few weeks, we will lay out the case that it is one thing to build with APIs, quite another to build an API-first company. We will explain why API-first approaches are the next logical stopping point for SaaS; and the essential element in fintech strategy. With our product management hat on, here is the roadmap of where this project is headed:</p><ul><li><strong>Part I:</strong> Our first three articles will step through the strategic considerations of being API-first and major market dynamics. Here we define the forces behind those who provide APIs, those who write to them, and who are likely to be simply out of luck³.</li><li><strong>Part II:</strong> Our next two articles will step through what API market forces mean for financial institutions, how banks’ API strategies will crystalize and what the maturation of the connective tissue between fintech apps and banks means for market activity.</li><li><strong>Part III: </strong>Our last two articles look to the future, first exploring open banking, standardized protocols and changes to central banking, then evaluating how the evolution of an API-first ecosystem will interact with the emerging boom in no-code and low-code solutions.</li></ul><p>We’ll offer a big-picture view why ultimately most banks will survive by being API-friendly, rather than by being API providers. Buying habits will change alongside technical prioritization; equilibrium will exist in tension as the largest banks have the resources to pass as tech companies where needed, whereas the vast majority will need to become adept buyers and integrators of API-first products.</p><p>Truly, APIs 👏🏼 Are 👏🏼 Everywhere 👏🏼.</p><ul><li><a href="https://www.ocrolus.com/">Ocrolus</a> (QED portfolio company) provides a set of machine vision and document processing APIs that automate and standardize how unstructured and semistructured content like loan applications and IDs are turned into clean data and analytics.</li><li><a href="https://treasuryprime.com/">Treasury Prime</a>¹ (QED portfolio company) has developed a full set of BaaS APIs that provide end-to-end financial account lifecycle management, and connectivity between payments rails, fintech apps and financial institutions.</li><li><a href="https://www.openpayd.com/">OpenPayd</a> recently<a href="https://thepaypers.com/e-invoicing-supply-chain-finance/openpayd-rolls-out-instantfx-to-offer-real-time-fx--1245370"> released</a> an API-based FX-as-a-Service product that allows clients to perform real-time trades and circumvent traditional batch processing.</li><li>Square recently<a href="https://thepaypers.com/online-payments/square-announces-terminal-api-for-new-contactless-solutions--1245183"> announced</a> its TerminalAPI that allows businesses to build contactless solutions between Square Terminal and any point-of-sale hardware. Here, the API circumvents the problem of hardware interoperability altogether.</li><li>Stripe’s launch of<a href="https://thehustle.co/12082020-stripe-treasury/"> Stripe Treasury</a> is a powerful move into modular BaaS across ecommerce accounts, payments, etc.</li><li><a href="https://www.arachnys.com/">Arachnys</a>²(QED portfolio company) has developed a unified data API that allows global institutions to plug in required and supporting KYC and AML data for virtually any jurisdiction.</li></ul><p>Core and non-core banking service digitization has rapidly mushroomed in the past 12 months due to the COVID-19 pandemic. There’s no shortage of coverage about how the pandemic has reduced<a href="https://thepaypers.com/online-payments/use-of-cash-has-decreased-while-paas-platforms-increase-during-the-covid-19-pandemic--1245369"> cash reliance while platform players have grown to fill the sudden need.</a> In fact, a report from<a href="https://www.grandviewresearch.com/"> Grand View Research</a> has revealed that the global payments as a service market size is expected to reach $25.7 billion USD by 2027.</p><p>But payments is just the tip of the iceberg. As digital disruption affects the global money transfer infrastructure, all the interrelated “plumbing” is being changed concomitantly. Much like Veruca Salt and the golden egg, consumers want their transactions and all the related data <em>now.</em> This means balances, financial health and wellness, lending, deposits, even onboarding and authentication — now, now, now. And we expect all the pieces to be able to talk to each other within or across borders.</p><p>This has led to two critical trends: first, individual offerings in the market are becoming increasingly atomic to meet the precise needs of each financial technology use case (Stripe succeeded early by abstracting away business problems with specific technical methods marketed to developers); second, because these offerings are atomic, they must be built specifically to be pluggable and interoperable, to “play nicely with others.” Consequently, APIs become essential to the growing consumer and commercial expectations that money — and the data exhaust around how we interact with money — needs to move instantaneously regardless of jurisdiction. To borrow from Dead Kennedys, <em>give me convenience or give me death.</em></p><p>On this ongoing quest toward modularity and interoperability, <strong>there will be three kinds of companies: those whose APIs are written to, those who write to others’ APIs, and those who are simply out of luck.</strong></p><h3>Good APIs and API-first Companies</h3><p><strong>So let’s back up a second</strong> — if APIs are the backbone of modern digital banking, what are they? What makes a good API? What does it mean to be an API-first company?</p><p>The API is a structured agreement between computer programs and systems to enable functionality based on predetermined inputs and outputs. In essence, APIs enable dialog between computers — call and response. They have their own grammar and syntax, and can be as expressive as needed for the situation.</p><p>Nick Gard at ITNEXT <a href="https://itnext.io/api-first-programming-on-the-front-end-4364c218ac60">provides an example</a> we all are familiar with: the archetypical API interaction between a data service, such Google Maps, and a website that sends it some data (e.g. two addresses) and receives data in return (e.g. a list of steps for getting from the first address to the second).</p><p>There is a widely held mantra <strong>the</strong> <strong>API is the product. We believe this to be true.</strong> But just as physical products and digital applications can be<a href="https://uxplanet.org/what-product-have-you-recently-seen-that-made-you-think-this-is-great-design-and-why-8cbb5f4b42c2"> well-designed</a> or<a href="https://www.youtube.com/watch?v=yY96hTb8WgI"> poorly-designed</a>, so too can APIs. Moreover, businesses can have strong design teams, be design-led, or both.</p><p>Lars Trieloff,<a href="https://medium.com/adobetech/three-principles-of-api-first-design-fa6666d9f694"> writing for Adobe</a>, notes that good APIs adhere to the following three principles.</p><p><strong>1. Your API is the first user interface of your application.</strong></p><p><strong>2. Your API comes first, then the implementation.</strong></p><p><strong>3. Your API is well-documented or self-described (in other words, it’s intelligible to us humans).</strong></p><p><strong>High-quality APIs are the way to square the circle between proliferation of SaaS solutions, the pressures of cross-system communication and market pressures to expand vertically or horizontally.</strong></p><p>From the perspective of a company consuming software from an API, great APIs make a vendor’s software functions <em>atomic</em> and make products and solutions highly consumable “off the shelf”. Said differently, <strong>APIs turn software into legos</strong>.</p><p>A major consequence: the battle for user engagement and user experience is now a completely separate battle from API competition. User-facing apps can compete for users’ attention on the merits of their interactions and design (mostly) regardless of which APIs are called in the background. In fact, we’d go so far as to say the strength and granularity of modern APIs has helped <a href="https://uxdesign.cc/creating-a-customer-obsessed-design-culture-validating-the-why-31f09539aa56">design-led culture</a> flourish while the competition to create the best connective tissue carries on elsewhere.</p><p>As a practical example, when Nate joined Arachnys and Amias joined the board in 2017, the company had a library of fairly beefy <em>internal </em>(non-open) APIs that powered a webapp sold through a SaaS model. Despite industry-leading data reach and indexing, we found that many potential clients were not interested in retraining their teams on new workflow tools or changing the way they conducted anti-money laundering investigations. Instead, they just wanted their existing tools to work better. Now, Arachnys relies on a full set of Open APIs and can as easily provide value through a pure-API sale, plugging its tools into the compliance stack of their choosing, as they can by consuming the original Arachnys product.</p><p>Even 10 years ago, it would have been out of the question to develop a SaaS company solely focused on one part of a data pipeline or transaction or interaction; and similarly, no one would have expected that the information from those transactions would become valuable proprietary data.</p><p>This is a fourth principle for good APIs, not articulated by Trieloff: APIs should structure and collect proprietary data from their use. There’s one thing to supply great standardized plumbing, but it’s another massively valuable thing for that plumbing to generate an additional layer of value-add data and metadata based on user-input content, logs, diagnostics and other signals generated from regular consumption and edge cases.</p><p>Worth noting that the question of whether it’s the API provider or API consumer who owns the data exhaust is an active battleground in fintech and other industries. As new advancements in cryptography, cloud storage and related fields roll into the market, vendors and consumers have more options about who owns what, when and under what conditions.</p><p>This is the alchemy of a great API, a property that gives great API-first companies their market power.</p><h3>So what does it mean to be API-first? What makes a great API-first company?</h3><p>In terms of what makes a great API, we’ve outlined some functional principles, but we still have the open question:<strong> is there a meaningful business distinction between being API-driven and being an API-first company?</strong></p><p>Yes. Being API-driven is a product development principle and a good <em>tactical</em> choice. Being API-driven allows companies to build extensible products faster, which decreases both time-to-market and time-to-patent where applicable. It forces your engineering team to build in a modular fashion and tends to more strongly align product and engineering teams to a customer-focus.</p><p>Being API-first requires a pure distillation of the “job to be done” framework. There is no visual design aesthetic or user-experience apart from interactions with the API. Your potential customers ask one question: what does each API endpoint allow me to do?</p><p>But being API-first takes these benefits further and becomes a good <em>strategic</em> choice.</p><p><strong>Why is this defensible strategy in the long run?</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*xzF1ElginkisS3mB" /><figcaption><em>If this crossed your mind, you’re not wrong. But you’re not quite right either.</em></figcaption></figure><p><a href="https://medium.com/yourapi/api-a-sustainable-competitive-advantage-through-connection-c966fc8895f7">Many</a>,<a href="https://www.marketwatch.com/story/moats-will-make-all-the-difference-for-cloud-companies-as-tech-costs-come-under-pressure-2020-07-08"> many</a>,<a href="http://reactionwheel.net/2019/09/a-taxonomy-of-moats.html"> many</a><a href="https://medium.com/eniacvc/compounding-economic-moats-for-technology-companies-f593a5d4688"> pieces</a> have been written about the nature of moats: user base and network effects, regulations, switching costs, and unique technology and related patents. So, to reiterate an earlier point, a focus on API-first design and productization often involves intentional choices around the proprietary data generated from its use, which, according to many, is where the maximum value of a moat sits.</p><p>Consequently, being API-first is a good <em>strategic</em> choice. Being API-first naturally forces the business to define differentiated user-facing processes and services earlier in company formation than traditional software development lifecycles.</p><p>In fact, <strong>being an “API-first company” is a strategic choice that:</strong></p><ul><li><strong>requires a company to focus on friendliness and interoperability; seeking lock-in through quality rather than switching costs.</strong></li><li><strong>requires the intentional creation of developer communities and an ecosystem of support; relying more on facilitating peer-to-peer virality than traditional sales methods.</strong></li><li><strong>tracks toward a long-term goal of having productized data derived from the APIs. (This might manifest as a productized data-generation capability, or bundled assets for complementary purposes).</strong></li><li><strong>commits the business to an early horizontal strategy — get a lock on one layer or atomic service in a particular stack (e.g. payment gateways or authentication). An API-first company will act in ways that make providers <em>above</em> and <em>below</em> you more valuable with your offering in the mix, rather than immediately seeking to displace players in an ecosystem.</strong></li><li><strong>recognizes the tradeoff between traditional SaaS margins and greater potential retention, lock-in, usage-based growth and up-sell potential.</strong></li><li><strong>plans for future <em>vertical</em> growth through the addition of complementary services over time.</strong></li></ul><p>As Chris Sperandio of Segment<a href="https://segment.com/blog/why-we-re-transitioning-to-api-first/"> rightfully pointed out in 2018</a>, the strength of (a) how well an offering can be integrated or (b) the value of its combination of integrations will provide the best customer journey. But this is challenging, and in Postman’s<a href="https://www.postman.com/state-of-api/"> most recent State of The API report</a> indicates that most respondents are somewhere in the middle of their journey.</p><p>In our next post, we’ll comment on the role APIs play in SaaS unit economics and how these power dynamics have fundamentally altered the long-run view of customer experiences and buying expectations in financial services.</p><p>From there, we will go in-depth on the mechanics of our market power thesis and begin to examine what this means for traditional financial institutions and how the rise of BaaS and neobanking puts API market power into practice.</p><p>[1] <em>Disclosure: Amias serves on the board of Treasury Prime, Ocrolus, and Arachnys. Nate is working with Treasury Prime this semester on a project facilitated through Wharton’s Stevens Center for Innovation in Finance)</em></p><p>[2] <em>Disclosure: Nate worked at Arachnys for the past 3 years. Shout out to David Buxton and team for tons of support and a great learning experience along the way.</em></p><p>[3] SOL, let’s be honest.</p><p><em>Amias Gerety is a partner at QED Investors, a leading fintech venture capital firm. His investing has focused largely on back office and infrastructure themes. Prior to QED, Amias was Acting Assistant Secretary for Financial Institutions in the Obama Administration.</em></p><p><em>Nate Soffio is an MBA Candidate at Wharton focusing on fintech, entrepreneurship, and financial inclusion. There, he is the co-chair of </em><a href="http://whartonfintechconference.com/"><em>Wharton’s Fintech Conference</em></a><em> taking place April 22–23. Hailing from Stamford, CT by way of Medellin, Colombia, he spent a decade building (and breaking) things in the infrastructure and regtech worlds with a focus on Know-Your-Customer and identity management. Before Wharton, he helped lead product at Arachnys, a London-based regtech and QED portfolio company. In his spare time you can find him road cycling, rock climbing, and cooking.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b4645c562277" width="1" height="1" alt=""><hr><p><a href="https://medium.com/wharton-fintech/apis-are-everywhere-b4645c562277">APIs 👏 Are 👏Everywhere</a> was originally published in <a href="https://medium.com/wharton-fintech">Wharton FinTech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>