Chapter 10: The Ecosystem of Complements

The App That Made the Store Too Valuable to Leave

A merchant logs into the backend of an online store. The store runs on a popular ecommerce platform, and the merchant has been selling handmade candles for about a year. Sales are steady but unspectacular. The merchant opens the platform's app marketplace, a directory of add-ons and integrations that extend the core functionality of the store. There are apps for email marketing, for loyalty programs, for shipping labels, for product reviews, for upsell pop-ups, for abandoned cart recovery. The merchant scrolls through the categories, reading descriptions and reviews. One app promises to add a "frequently bought together" widget to the product page. Another promises to suggest complementary scents during checkout based on the candle the customer selected. A third offers a subscription box builder, turning one-time candle buyers into monthly subscribers. The merchant installs all three. Each app charges a monthly fee, paid to the app developer, not to the ecommerce platform. But the platform benefits anyway. The merchant's store becomes more capable, more sticky, and more revenue-generating. The merchant is now more deeply embedded in the platform's ecosystem — migrating to a competing platform would mean abandoning not just the store's design, but the entire layer of third-party functionality that now powers the customer experience. The platform, without selling a single additional feature of its own, has increased its customer's lifetime value and reduced its churn risk. The upsell was not a product. It was an ecosystem.

Shift to a different screen, a different industry. A sales manager at a mid-sized company logs into the customer relationship management system. The core CRM handles contacts, deals, and pipeline tracking. But the sales team's workflow extends beyond the core. They use a third-party integration that connects the CRM to a proposal generation tool, built by an independent software vendor and listed on the CRM platform's marketplace. When a deal reaches the negotiation stage, the integration pulls the contact and product data from the CRM and auto-populates a professional proposal, complete with pricing tables and e-signature. The sales manager pays the integration vendor a per-user fee, separate from the CRM subscription. But the integration increases the sales team's reliance on the CRM. Without it, the proposal workflow would break. The CRM platform has not upsold the customer directly; it has provided the marketplace through which an ecosystem of complementary tools does the upselling on its behalf. The platform becomes more valuable not because its own feature set expanded, but because its ecosystem made it the hub of a workflow that no single application could serve alone.

A third scene, in the realm of hardware. A customer buys a smartphone. The purchase is a one-time transaction, but it initiates a cascade of potential upsells that the manufacturer has carefully architected. The phone prompts the customer to buy a case, a screen protector, and wireless earbuds during the checkout process. These are first-party accessories, designed and sold by the manufacturer. But the ecosystem extends further. The phone's operating system includes an app store, populated by millions of third-party applications. The manufacturer takes a commission — typically fifteen to thirty percent — on every app sale, every in-app purchase, every subscription initiated through the store. The customer who buys a phone and then spends years buying apps, games, and services is generating a stream of post-purchase revenue that, over the device's lifespan, can exceed the original hardware purchase price. The upsell is not a single accessory. It is the entire economy of software and services that the device enables. The manufacturer's most profitable upsell is not a product it sells. It is the marketplace it owns.

These scenes converge on a principle that extends the logic of upselling beyond the boundaries of a single product or a single company. The most scalable form of upselling does not occur on the core product page, nor in the post-purchase email, nor in the cancellation flow. It occurs in the ecosystem of complementary goods, services, apps, and integrations that surround the core product and draw both customers and third-party providers into a self-reinforcing commercial orbit. The platform becomes the marketplace, and the marketplace becomes the upsell engine. This chapter examines that transformation: how companies like Salesforce and Shopify have built ecosystems that generate more revenue from complements than from the core product, and how the architecture of a platform marketplace can be applied at scales far smaller than a global enterprise.

Why the Most Profitable Upsell Is One You Didn’t Build

An ecosystem of complements is a network of products and services that enhance the value of a core offering, sold by a variety of providers but connected through a common platform. The core product might be a software application, a physical device, or a marketplace that matches supply with demand. The complements are the add-ons, extensions, integrations, accessories, and services that make the core product more useful, more customized, and harder to leave. The platform does not necessarily build these complements itself. In fact, the most vibrant ecosystems are those where the majority of complements are built and sold by third parties, and the platform's role is to provide the infrastructure, the distribution, and the governance that make the ecosystem trustworthy and efficient.

The economic logic of the ecosystem is grounded in the theory of complementary goods, a concept that has been central to industrial organization economics for decades. A complement is a good whose consumption increases the value of another good. Hot dogs and mustard are complements. Printers and ink cartridges are complements. In the digital domain, a CRM and a proposal generator are complements; an ecommerce platform and a subscription box app are complements; a smartphone and a meditation app are complements. The key strategic insight is that the demand for the core product is a function of the availability and quality of its complements. A CRM with a thousand integrations is more valuable than a CRM with ten, even if the core features are identical. An ecommerce platform with a rich app store is more valuable than one with a closed architecture. The complements sell the core product, and the core product sells the complements. The relationship is a flywheel.

The flywheel effect is amplified by network effects, the phenomenon by which a product becomes more valuable as more people use it. In a marketplace ecosystem, two types of network effects operate simultaneously. The first is the user-side network effect: more merchants using an ecommerce platform attract more app developers, which produces more apps, which attracts more merchants. The second is the data network effect: as more transactions flow through the platform, the platform accumulates data that improves the relevance of app recommendations, the accuracy of upsell offers, and the efficiency of the matching between customer needs and complementary products. The platform that reaches critical mass in its ecosystem becomes increasingly difficult to displace, not because its core product is unbeatable, but because the cost of abandoning the ecosystem — the integrations, the data, the trained workflows, the app subscriptions — is too high for a rational customer to bear.

The monetization of the ecosystem can take several forms, and the choice of model shapes the incentives of all participants. The most common model in software marketplaces is the revenue share: the platform takes a percentage of every transaction between the third-party developer and the customer. Apple's App Store and Google Play are the most visible examples, with commission rates that have been the subject of regulatory scrutiny and developer protest. Salesforce AppExchange, by contrast, does not take a direct revenue share on third-party app subscriptions; instead, it monetizes indirectly by increasing the value of the Salesforce platform and reducing customer churn, which drives renewal and expansion of core Salesforce licenses. Shopify's App Store takes a revenue share on app sales, but the larger strategic benefit is the increased gross merchandise volume that flows through Shopify-powered stores, on which Shopify earns transaction fees. The monetization model is not a fixed choice; it is a design decision that reflects the platform's strategic priorities and its relationship with its developer community.

The design of an ecosystem marketplace involves trade-offs at every level. The first trade-off is openness versus quality. An open marketplace that allows any developer to list an app maximizes the quantity of complements, but it risks a degraded customer experience if low-quality or malicious apps proliferate. A curated marketplace that vets every submission maintains quality but limits the speed and diversity of ecosystem growth. Salesforce AppExchange has historically leaned toward curation, with a review process that checks for security, performance, and integration quality. Apple's App Store has oscillated between openness and restriction, facing ongoing criticism from developers over the opacity and inconsistency of its review guidelines. The platform that gets this balance right builds trust with customers, who feel safe installing third-party tools, and with developers, who feel that the rules are fair and stable. The platform that gets it wrong either suffers from a trust deficit that suppresses complement adoption or from a developer exodus that starves the ecosystem of innovation.

The second trade-off is competition versus cooperation. When a platform identifies a particularly successful complement — an app category that generates high revenue or high engagement — the platform faces a choice. It can allow the third-party developer to continue capturing that value, preserving the ecosystem's health but potentially leaving money on the table. Or it can build a first-party version of the same complement, leveraging its access to platform data and its ability to bundle the feature into the core product. This decision, often called "sherlocking" after Apple's historical practice of incorporating third-party app functionality into its operating systems, carries significant risk. Developers who fear that the platform will compete with their most successful products will reduce their investment in the ecosystem, slowing innovation and reducing the diversity of complements. Shopify, in its public communications to developers, has emphasized that it views its role as providing the "primitives" — the basic building blocks — while allowing developers to build specialized solutions on top. When Shopify does expand into a category previously served by third parties, it often does so with features that are broadly applicable, leaving room for developers to build more niche or advanced versions. The platform that manages this boundary well keeps its ecosystem vibrant; the platform that ignores it may find itself with an app store full of abandoned, unmaintained tools and a developer community that has moved to a more trustworthy host.

The third trade-off is the allocation of upsell economics between the platform and the complement provider. When a merchant installs an app from the Shopify App Store that increases the merchant's average order value, who captures the value? The app developer captures the monthly subscription fee. Shopify captures the transaction fees on the increased order volume, plus the indirect benefit of a merchant who is now more successful and less likely to churn. The upsell is co-created. The platform provides the customer relationship and the transaction infrastructure; the developer provides the specific capability that triggers the upsell. The alignment of incentives — both parties benefit from the merchant's success — is what makes the ecosystem upsell so resilient. It is not a zero-sum extraction of value from the customer. It is a positive-sum expansion of the total value available, with the platform and the developer splitting the increase according to their respective contributions and their pre-agreed commercial terms.

The next section examines Salesforce AppExchange as the primary case of a B2B software ecosystem that transformed enterprise software distribution and generated billions in ecosystem revenue. A secondary case, Shopify's App Store, illustrates how an ecommerce platform has built a developer economy that generates significant revenue while increasing the stickiness of the core subscription.

Salesforce’s AppExchange and Shopify’s Developer Economy

Salesforce, in the early 2000s, faced a problem that was, in retrospect, a luxury. The company had pioneered cloud-based customer relationship management, convincing skeptical enterprises that their most sensitive sales data could live safely outside the corporate firewall. By 2005, Salesforce was growing rapidly, but its growth was constrained by a structural reality that affects every enterprise software vendor. Large customers, the kind that sign multi-year, multi-million-dollar contracts, inevitably demand features that are specific to their industry, their workflow, or their internal politics. A pharmaceutical company wants integration with a prescription drug database. A manufacturing firm wants a shop-floor scheduling module. A financial services company wants compliance reporting tailored to a specific regulatory regime. No single vendor, no matter how well-funded, can build all of these features. Attempting to do so would turn the product into an unmanageable monolith and starve the core development team of focus. But failing to address these demands would cap the company's growth, leaving money on the table and opening the door for niche competitors to pick off high-value accounts.

The solution, announced with the launch of AppExchange in 2005, was to turn Salesforce into a platform. Instead of building every feature a customer might want, Salesforce would build a set of robust application programming interfaces, a development toolkit, and a marketplace where third-party software vendors could list, sell, and distribute applications that extended the Salesforce core. Customers would get the industry-specific functionality they needed. Independent software vendors would get access to a rapidly growing base of enterprise customers, with distribution, billing, and trust already handled by the platform. Salesforce would get a more valuable core product, a share of the ecosystem revenue through various monetization mechanisms, and a deepening of customer relationships that made churn increasingly unthinkable. Marc Benioff, the company's CEO, described the vision at the launch event as "the end of software as we know it," a phrase that was hyperbolic but, in the narrow context of enterprise software distribution, proved to be largely accurate.

The architecture of AppExchange was built on trust. Enterprise customers, particularly in regulated industries, do not install third-party software lightly. A poorly written integration can corrupt data, open security vulnerabilities, or degrade system performance. Salesforce addressed this by implementing a rigorous security review process for every application listed on the marketplace. Developers were required to adhere to strict coding standards, pass penetration tests, and submit to ongoing monitoring. The review process was, and remains, a significant investment for both Salesforce and the developer, but it created a seal of approval that gave enterprise buyers the confidence to adopt third-party applications at a pace that would have been impossible in the pre-cloud era of on-premise software. A customer who might spend six months vetting a standalone vendor could install an AppExchange application in an afternoon, because the trust was transferred from the vendor to the platform.

The results of this ecosystem strategy are measured in the billions and have become a standard case study in platform economics. By 2023, Salesforce's annual revenue exceeded $31 billion, and while the company does not break out AppExchange revenue as a separate line item, industry analysts at IDC and Forrester have estimated that the ecosystem of partners, developers, and applications surrounding Salesforce generates several times more economic activity than the company captures directly. An IDC study commissioned by Salesforce in 2021 projected that the Salesforce ecosystem would create 9.3 million new jobs and $1.6 trillion in new business revenue worldwide by 2026. These numbers, while promotional, are directionally indicative of the scale that a mature software ecosystem can achieve. The AppExchange itself lists thousands of applications, ranging from small utilities built by solo developers to enterprise suites from publicly traded companies, and the number of installs — cumulative app downloads by Salesforce customers — runs into the tens of millions.

The upsell mechanism within AppExchange is not a single prompt or a pop-up. It is the persistent availability of complementary capabilities that are contextually relevant to the user's current task. A sales representative viewing a lead record in Salesforce might see a sidebar widget from a data enrichment app, auto-populating the lead's company size and industry from a third-party database. The widget was installed by the sales operations team, paid for through the AppExchange billing system, and delivered by the third-party vendor's infrastructure, all within the Salesforce interface. The sales representative experiences the upsell not as a commercial offer but as a seamless enhancement of their workflow. The company that purchased the app experiences the upsell as a natural expansion of their Salesforce investment. The platform has turned the core product into a distribution channel for a universe of complements, and every complement that a customer adopts increases the switching cost and the lifetime value associated with the platform. The upsell, in this ecosystem, is not an event. It is the permanent, ambient state of the product.

The lesson from Salesforce AppExchange is not that every company should aspire to build a $1.6 trillion ecosystem. It is that the most defensible form of upselling is the one that makes the core product more central to the customer's operations with every additional complement that the customer adopts. The platform does not need to own the complements. It needs to own the relationship, the data layer, and the trust infrastructure through which the complements are delivered. If those three elements are in place, the ecosystem will produce upsells that are initiated by the customer — searching for a solution to a specific problem — rather than pushed by the vendor. The customer's own need becomes the upsell trigger, and the marketplace provides the answer.

A secondary case, drawn from the ecommerce sector, reinforces the ecosystem principle while demonstrating its application at a scale that is accessible to smaller merchants and developers. Shopify, founded in 2006 in Ottawa, Canada, began as a tool for selling snowboards online. Its pivot to a general-purpose ecommerce platform was driven by a recognition that the internet was lowering the barriers to starting a business, but the tools for building and managing an online store remained fragmented and technically demanding. Shopify's core product — a hosted shopping cart with customizable templates, payment processing, and order management — solved the fragmentation problem for store owners. But store owners, as a species, are insatiably inventive. As soon as one problem is solved, they discover ten more. They need to run email campaigns, print shipping labels, offer loyalty points, upsell at checkout, translate their store into three languages, and integrate with the accounting software their bookkeeper insists upon. Shopify, like Salesforce, faced the impossible feature demand problem.

The company's response, launched in 2009 and significantly expanded thereafter, was the Shopify App Store. Developers could build applications that extended Shopify's functionality, list them in a directory that merchants could browse from within their store admin, and charge a recurring subscription fee. Shopify would take a commission on each app sale — initially twenty percent, later reduced to fifteen percent for most categories — and would provide the APIs, the documentation, the billing infrastructure, and the distribution channel. The model aligned incentives cleanly: developers were motivated to build apps that solved real merchant problems and generated positive reviews, because revenue followed directly from merchant adoption. Shopify was motivated to maintain the health of the platform and to grow the merchant base, because its commission revenue and its core subscription revenue both scaled with merchant success.

The results of the Shopify App Store strategy are quantitatively striking. By 2023, Shopify reported in its annual filings that it powered over 4 million online stores across more than 175 countries. The App Store listed over 8,000 applications, and the cumulative number of app installs by merchants exceeded hundreds of millions. A 2022 economic impact report commissioned by Shopify and prepared by Deloitte estimated that the company's ecosystem of partners, developers, and merchants generated over $400 billion in global economic activity since Shopify's founding. The App Store itself does not rival the App Store of Apple or Google in revenue, because the total addressable market of ecommerce merchants is smaller than the market of smartphone users. But the strategic impact on Shopify's business is disproportionate. Merchants who install multiple apps are significantly less likely to migrate to a competing platform, because migration would mean not just redesigning a store but rebuilding an entire operational stack of third-party tools. The apps increase the merchant's switching cost while simultaneously increasing the merchant's revenue, a combination that produces the kind of negative churn — revenue expansion from existing customers exceeding revenue lost to churn — that subscription businesses covet.

The Shopify App Store is also a powerful upsell engine for the apps themselves. A merchant who installs a free app to add a "you might also like" widget to product pages may later upgrade to the app's paid tier, which offers an AI-driven recommendation engine trained on the merchant's own sales data. That upsell happens between the merchant and the app developer, with Shopify taking its commission on the higher subscription fee. The platform does not design the upsell offer or time its presentation. It provides the environment in which the app developer can build a relationship with the merchant, demonstrate value over time, and present the upgrade at the moment of maximum relevance. The ecosystem multiplies the number of people who are working to increase the merchant's lifetime value — every app developer, every theme designer, every integration partner becomes an extension of Shopify's own retention and expansion efforts. The platform's ability to scale its upsell capacity is unbounded, because it is not limited by the company's own product development headcount. It is limited only by the size and creativity of the developer community it can attract and retain.

The combined lesson from Salesforce and Shopify is that the ecosystem of complements is not a feature that can be added to a mature product. It is a product strategy that must be embedded from the early stages of platform design. The APIs must be clean, well-documented, and stable. The developer experience must be respected; the terms of the marketplace must be seen as fair. The customer experience must be curated enough to maintain trust but open enough to invite innovation. The upsells that emerge from such an ecosystem are not interruptions. They are solutions to problems the customer has already identified, delivered through a channel the customer already trusts, at a moment the customer has already chosen. That is the architecture of the upsell at its most scalable, and it is the architecture that the businesses discussed in this chapter have built.

Growing an Ecosystem Before It Deserves the Name

The Salesforce AppExchange and the Shopify App Store are separated by industry, customer profile, and product category. One serves enterprise sales teams with a platform that can cost hundreds of thousands of dollars per year. The other serves solo entrepreneurs launching a first online store with a monthly subscription that costs less than a streaming service. Yet the structural logic that makes both ecosystems valuable is the same. A core product, no matter how well-designed, can only address a finite set of customer needs. The needs that fall outside that set — the niche integrations, the industry-specific workflows, the personal productivity enhancements — represent a vast, distributed demand that no single product team can satisfy. The platform that opens its architecture to third-party developers transforms that unmet demand from a liability into an asset. Every app, integration, and add-on that a developer builds fills a gap, and every gap filled makes the core product more complete, more tailored, and more entrenched in the customer's operations.

The economic mechanism that drives the ecosystem is the flywheel of complementary value. A customer adopts the core product. The customer discovers a complement that enhances the core product's utility. The complement increases the customer's success with the core product, which increases the customer's willingness to invest further in both the core product and additional complements. The cycle reinforces itself. The platform's role is to reduce the friction at every step: to make the core product easy to adopt, to make complements easy to discover and install, to make the integration between the core product and the complements reliable and secure, and to make the billing and administration of the entire stack manageable from a single interface. When the platform succeeds at reducing this friction, the ecosystem grows, and the platform's own revenue grows as a byproduct of its customers' and developers' success.

This logic can be applied at scales far smaller than a Salesforce or a Shopify. The necessary conditions are not a billion-dollar valuation or a global developer conference. They are a product with a defined set of core capabilities, a customer base with needs that extend beyond those capabilities, and an architecture — even a simple one — that allows external parties to build and deliver solutions that integrate with the core product. The architecture might be a set of REST APIs, a webhook system, an embeddable widget framework, or a manual integration guide. The marketplace might be a curated directory on a website, an in-app listing page, or a partner program with referral fees. The scale can be modest; the principle is scale-invariant.

For a small ecommerce business, the ecosystem logic often begins with a single integration that transforms the customer experience. A merchant selling custom-made furniture on a platform like Shopify or WooCommerce might discover that no single app solves the problem of offering customers a 3D product configurator that shows exactly how the fabric, wood finish, and dimensions will look together. The merchant could commission a freelance developer to build a custom integration that connects the store's product data to a 3D rendering engine. That integration, once built, becomes a complement to the store. It increases the store's conversion rate and average order value. If the merchant later packages that integration as an app and lists it on the platform's marketplace, the complement becomes a product in its own right, generating a new revenue stream. The ecosystem has turned a cost center — custom development — into a potential profit center. The upsell is not an offer from the merchant to the customer; it is the merchant's entire business becoming more capable and more differentiated through complements that the platform's core functionality alone could not provide.

For a B2B SaaS company that is too small to attract third-party developers organically, the ecosystem can start as a partner integration program. The company identifies the five other SaaS products that its customers most frequently use alongside its own — the CRM, the accounting tool, the project management app — and builds deep, native integrations with each of them. These integrations are complements, and they increase the value of the core product by embedding it in the customer's existing workflow. The company then offers these integrations as part of a higher-tier plan, effectively upselling customers to the tier that includes the integrations they need. The ecosystem here is not a marketplace of third-party apps; it is a curated set of partnerships that the company builds and maintains. Over time, as the customer base grows, the company can open its APIs and invite external developers to build integrations, but the initial flywheel can be hand-cranked with a small number of high-value complements that address the most common customer pain points.

The ecosystem of complements also applies to physical product businesses that have embraced digital service models. A company that sells smart home devices — thermostats, lights, locks — sells each device as a one-time hardware purchase. But the device is useless without a companion app, and the app becomes more valuable when it integrates with other devices and services. The company that opens its platform to third-party developers — allowing a security company to integrate with the smart lock, allowing an energy utility to integrate with the smart thermostat — creates an ecosystem of complements that increases the value of every device the company sells. The upsell is not an additional device. It is the expanding capability of the device the customer already owns, enabled by software and service complements that the company may not build or sell directly, but from which it benefits through increased hardware sales, subscription revenue, and customer retention.

The most important operational lesson from the Salesforce and Shopify cases is that the ecosystem strategy requires patience and restraint. Salesforce launched AppExchange in 2005, years after the core CRM product had achieved product-market fit. Shopify launched its App Store in 2009, three years after the platform's founding. In both cases, the company had first established a base of customers who were actively using the core product and generating demand for extensions. Building a marketplace before the core product has a viable, engaged user base is a common mistake. Developers will not invest time in building for a platform that cannot deliver customers. Customers will not visit a marketplace that has no apps. The ecosystem flywheel cannot start from a standstill; it requires an initial push of core product adoption and a small number of high-quality complements — often built by the platform company itself or in close partnership with a few developers — to demonstrate the value of the ecosystem to both sides.

Once the flywheel is spinning, the platform's governance choices determine whether it accelerates or stalls. The governance includes the review process for new apps, the commission structure, the policies around data access and security, the handling of disputes between customers and developers, and the platform's own decisions about when to build features that compete with popular third-party apps. The companies that govern their ecosystems with transparency, consistency, and a genuine commitment to developer success — even when that means forgoing short-term revenue opportunities — build durable ecosystems that compound over decades. The companies that treat their ecosystems as extractive resources, changing the rules to capture more value after developers have committed, find their ecosystems withering. Developers talk to each other, and a platform's reputation in the developer community is a hard currency that takes years to earn and can be lost in a single policy change.

The ecosystem upsell, at its most mature, becomes indistinguishable from the product itself. A Salesforce user does not think of the AppExchange widget in the sidebar as an upsell; it is simply part of the tool they use to do their job. A Shopify merchant does not think of the email marketing app as an upsell; it is the way they communicate with customers. When the complements are deeply integrated, the boundary between the core product and the ecosystem dissolves. The customer's relationship is with the outcome — the closed deal, the shipped order, the automated campaign — and the platform and its developers share the credit. The upsell is not a pitch; it is the customer's own next step, made visible and accessible by an ecosystem that was designed to make the next step inevitable.

What Could Surround Your Product That You Haven’t Built Yet?

For the small business owner, the first question is an invitation to look beyond the boundaries of the current product. If the core product is a physical good, what digital complements — an app, a subscription content library, a configuration tool, a community platform — could surround it and increase its value in the customer's life? If the core product is a service, what tools, templates, or integrations could make the service easier to buy, easier to use, or easier to combine with other services the customer already uses? The answer may not be a full marketplace. It may be a single, focused complement that addresses the most frequently requested capability the business currently lacks. The second question is about the existing customer base: if a small group of the most engaged customers were asked to describe the one thing that would make the product ten times more valuable to them, what patterns would emerge in their answers? The business owner who conducts even five of these conversations often discovers that the complements customers want are not the features the business had planned to build next. The ecosystem approach shifts the product roadmap from internal prioritization to external demand, and the shift, while uncomfortable, is where scalable upsell opportunities are found.

For the consultant or strategist, the questions are about the architecture of the ecosystem before it exists. First, when advising a client who is considering opening a platform to third-party developers, what are the minimum technical and legal infrastructures that must be in place before the first external developer can be onboarded? The answer includes stable APIs with versioning, clear documentation, a sandbox environment for testing, a developer agreement that protects both parties, a billing mechanism, and a review process that does not create an administrative bottleneck. The consultant who can lay out this checklist with specific, actionable items is providing a roadmap that prevents the most common cause of ecosystem failure: launching a marketplace that is not ready for the developers it hopes to attract. Second, how does the consultant help a client assess whether the core product's adoption is sufficient to sustain a marketplace, and if not, what interim steps can be taken to build toward one? The interim steps might include a partner directory with manually negotiated integration deals, a referral program that incentivizes external developers to build on the platform without a full marketplace, or a set of "first-party" complements built by the client's own team that serve as proofs of concept and seeds for future third-party development. The consultant who understands that ecosystems are grown, not launched, helps the client avoid the costly mistake of building an empty mall and waiting for tenants who never arrive.

The practical implication for a reader who wants to act within a week is to inventory the complements that already surround the business, whether or not they are recognized as such. Make a list of every third-party tool, service, integration, or add-on that customers use alongside the core product. Interview three customers and ask them what other products they use to fill gaps the core product leaves. The list that emerges is the raw material for an ecosystem strategy. The reader can then take one of those complements — the one that seems most aligned with customer demand — and explore what it would take to build a deeper integration with it, to partner with its provider, or to build a simple version of it as a first-party complement. The first step is not a developer conference or an API launch. It is the recognition that the core product is already part of a larger commercial system, and that the business's next upsell opportunity may not be a feature of the product at all, but a connection between the product and something else the customer already values. The ecosystem of complements is not a destination reached only by the Salesforces and Shopifys of the world. It is a lens through which any business can see its customers' unmet needs more clearly, and in seeing them, find the upsells that were always there, waiting to be built.