Ebook · Integration Marketplaces

The Definitive Guide to Building an In-App Marketplace

Introduction

Organizations are using more applications than ever.

With tens of thousands of applications to choose from, the average company is using 137 apps. This has only accelerated due to the pandemic and the resulting move to the cloud.

These applications are used and purchased by all departments, from sales, marketing, customer support, IT, human resources, to business operations.

While the software explosion has been a boon of functionality, it has also caused problems. Business users have to spend more time moving from one app to another, downloading and uploading data, and patching together their applications.

This process is frustrating and costly.

No matter what industry or vertical you operate in, your customers need to use your SaaS application with their other software - and they want to be able to do this without having to manually transfer their data, or persuade their IT department to build custom integrations.

The solution?

Build an in-app marketplace with embedded integrations. In-app marketplaces empower your customers to seamlessly connect to their other software without ever leaving your app. This integrated ecosystem around your core product significantly enhances the power and functionality of your app without requiring you to build more features.

In-app marketplaces are also known as app directories, app exchanges, or integration centers.

The Era of The In-App Marketplace

More and more, in-app marketplaces are becoming a requirement for SaaS companies.

The explosive growth of well-known SaaS companies like Salesforce, Shopify, Atlassian, BigCommerce, and HubSpot has occurred in large part because of the app marketplaces they offer their users.

91 percent of the Fortune 500 have installed an app from the Salesforce AppExchange, for example.

Salesforce generates over a billion dollars in revenue for their app partners every year.

These in-app marketplaces are only continuing to grow year over year.

Shopify app partners, for example, made more in 2020 than they did in 2018 and 2019 combined.

Credit: Shopify

137
Apps used by the average company
347
Median integrations at the 15 largest SaaS companies
63%
Of the 1000 fastest growing SaaS companies have a public integration marketplace

You can see the importance of integrations and integration marketplaces by looking at the 15 largest SaaS companies. Every single one has an integration marketplace. The median number of integrations at these companies is 347.

Number of Integrations & Extensions at the 15 Largest SaaS CompaniesOkta 7085, Shopify 5854, Atlassian 4000+, Salesforce 3860, Slack 2000+, Zoom 1320, ServiceNow 559, Datadog 485, DocuSign 347, RingCentral 266, Square 201, Twilio 176, Workday 119, Veeva 82, ZScaler 74. The median is 347; the median for the 1000 fastest growing SaaS companies is 15.Zoom1320Twilio176Atlassian4000+Square201ServiceNow559RingCentral266Shopify5854Workday119Slack2000+Salesforce3860Veeva82Datadog485DocuSign347ZScaler74Okta7085Number of Integrations &Extensions at the 15 LargestSaaS CompaniesThe median number of integrations at these companiesis 347. For comparison, the median number ofintegrations and extensions for the companies at the1000 fastest growing SaaS companies is 15.*Top 15 largest companies as identified by SaaStr

Number of integrations and extensions at the 15 largest SaaS companies, as identified by SaaStr.

But it is not just the largest SaaS companies.

In a study of the 1000 fastest growing SaaS companies, we found that 63% of the 1000 fastest growing SaaS companies have a public integration marketplace.

These companies also offer a median of 15 integrations. These SaaS companies are smaller and in an early stage of growth than the largest SaaS companies, but offering product integrations is a must have even at that point.

Companies who offer their customers seamless integrations are able to leverage an entire ecosystem of products and all the functionality that provides.

For example, if you sell an Applicant Tracking System, and want to offer your customers the ability to use AI in their video pre-assessments of applicants, you can either build your own pre-assessment platform that uses AI to analyze videos (not an easy task) or you can integrate with an existing one like HireVue.

Companies who fail to build an integrated ecosystem face an uphill battle trying to build more product features to compete with integrated SaaS apps.

In addition, it is challenging and often impossible to capture business users who are welded to other applications that need to be integrated with your product category.

For example, marketing automation platform Marketo offers a native integration with Salesforce.

If your new sales CRM doesn’t integrate with Marketo, it is going to be hard to persuade a company that is committed to using Marketo to switch to your CRM, even if you have a better UX.

Whether your customers need to integrate your app with 5 or 5,000 other solutions, building an in-app marketplace empowers your customers to have the seamless customer experience they are now looking for.

In-app marketplaces attract new leads, decrease customer churn, and increase upsells. As the number of B2B apps only continues to grow, SaaS companies that don’t build in-app marketplaces will quickly fall behind.

“Integrations are our biggest growth lever. They have brought us thousands of paid customers, raised our customer lifetime value, differentiated us in the market, and reduced churn.”

Casey Hill, Head of Growth at Bonjoro

So You Want to Launch an In-App Marketplace

Many different departments in your organization have a vested interest in building an in-app marketplace.

But even though an in-app marketplace is in many people’s interest, the project often does not fall under the purview of any one department.

It’s not uncommon for organizations to lack any employees who have experience building or launching one.

Those managing the initiative not only have to corral resources across departments, they need to learn best practices and set timelines.

We’ve created this playbook for those who want to build and launch an in-app marketplace. It offers guidance on how to get more resources internally and advice on how to build, market, and scale your marketplace. It lays out what to consider at every stage of the process, from idea to launch to scale.

Whether you’re a product manager, partnership leader, developer, or marketer, this playbook outlines the process and all the elements you need to consider when building, launching and scaling an in-app marketplace.

How Everyone Benefits from an In-App Marketplace

Product
Provides greater functionality to the product experience, reduces the need to build new product features
Engineering
More time to spend on developing core product and less time spent on bespoke integrations
Marketing
Generate more leads, reach more prospects, and access co-marketing resources
Sales
Generate more leads, reach more prospects, close more deals, and access co-selling resources
Partnerships
Happier partners, more shared resources and referrals, and generate more revenue from an integrated tech ecosystem
Customer Success
Decrease churn, increase upsells, happier customers, and more referrals
Chapter 1

What You Need Before Building a Marketplace

Almost all B2B SaaS companies should eventually have an integration marketplace. But you should ideally put a few things into place before building and launching one.

Keep in mind you need to build two integration marketplaces - one inside your app and one for your public website.

The content and style of these marketplaces may overlap heavily. The biggest difference is the in-app marketplace should enable customers to install and manage their integrations.

The public marketplace is a marketing asset and should be designed to explain how integrations work and excite prospects and customers about the possibilities.

Here are 6 things to accomplish before building your marketplace.

1. Product Market Fit

Successful integrations must move data between your product and other products in the right way. The reality is if your product changes significantly, your integrations will likely become outdated and have to be re-built.

If you’re still trying to find product market fit, then any integrations should likely be built to keystone software. Getting into the marketplaces of companies like Salesforce, AWS, or Slack should help you get leads and close customers.

But building your own marketplace is better left until when your product and integrations are relatively stable.

2. External API and API docs

Much like having product market fit, you want your external API to be mature enough to underpin the integrations you are going to offer your customers.

Even if your API isn’t yet publicly available, it should be battle tested by some partners and customers, and be relatively well-defined. And you should have documentation that your team and external developers can use to build integrations.

It is possible to build product integrations without an external API or with an API that only has basic functionality. But if your organization isn’t serious enough about integrations to have an API with at least moderate functionality, then it’s unlikely to be worth investing in building out a marketplace.

3. 5 Native Integrations

A marketplace is useful because it provides a place for customers to discover and manage integrations.

But if you have less than 5 native integrations, you can display the integrations in a simple list form, or place them in your product where the user would like to deploy them.

Once you have plans for 5 or more integrations, it makes sense to start thinking about building a marketplace for customers to sort and manage their integrations.

4. Technology partnerships manager

Building an in-app marketplace and overseeing and maintaining the integrations that are in the marketplace takes a lot of time, even if you are using infrastructure tools.

Once integrations are built, they still need to be maintained and supported. As products change, integrations must change with them.

In order to be successful, you need someone who owns this project and process.

This person could be a product manager or in partnerships, but you need to have a person dedicated to building and maintaining the marketplace and its contents.

5. Resources to build and manage the marketplace

You will need either a team of senior developers and/or a developer agency and/or an integration or marketplace platform to build and maintain your integration marketplace.

If you’re building everything in house, budget a team of senior engineers 12-18 months to build the in-app marketplace and its infrastructure.

This is not a small task and you should ensure you have the internal resources and budget to successfully build, launch, and maintain your marketplace and its integrations before starting.

(Chapter 5 on “Building Your Marketplace” covers the resources and costs of this in more detail.)

6. Strategic Goals for Technology Partnerships

In order to structure your marketplace and evaluate its success, it is important to understand what your strategic goals are for your technology partnerships.

Integration marketplaces can help achieve the following:

  • Improve customer satisfaction
  • Improve customer product adoption
  • Increase customer retention
  • Increase ACV
  • Send tech partners new leads and customers
  • Increase leads and customers coming from tech partners
  • Enable taking a revenue share from parters
  • Attract more tech partners willing to build integrations

Before you build and launch your marketplace you should understand which of these goals you are more focused on achieving. The goal can impact how and with what resources you launch your marketplace.

For example, if you are trying to improve customer satisfaction and reduce churn, you should enable a self-serve experience for customers and ensure that integrations are well-documented. Your marketplace should have an intuitive, modern UX that is easy to navigate and use.

If one of your primary goals, on the other hand, is to get more partners building into your product, then you should ensure you build a partner portal and have very good API documentation for partner developers.

Most organizations realize gains across the revenue funnel through their integration marketplace, but mapping out what is most important to you can help you to focus your limited resources and set expectations.

Evolution of Your Tech Partner Program and Building Your Marketplace

Below, you can see the early stages of a tech partner program mapped out, including the defining characteristics of each stage.

You can also see the approximate point where it makes sense to start building an in-app marketplace.

Building it earlier than this runs the risk of requiring a massive retooling if your product or your partners’ products change significantly. It can also mean that your integrations do not meet customers’ needs, and that partners have a poor experience building into your product.

Building a marketplace later on leaves revenue on the table in terms of customer satisfaction, partner referrals, and partner willingness to build into your app. It also can add significant developer expense in terms of unwinding whatever infrastructure was put in place to showcase, manage, and monitor integrations prior to building a marketplace.

When to Start Building an Integration Marketplace

Start building between Step 2 and Step 3

Step 1
Step 2
Step 3
API
No external APIEither API schema, endpoints, or authentication protocols are poorly designedAPI lacks functionality, might be read-only, and is difficult to access
API might be designed with minimal customer research or miss some technical best practicesAd hoc how external parties get access
Public instructions on how to access external APIAPI follows technical best practicesAPI may need more customer research to optimize design
Team
Poor communication across departments regarding integrationsNo one has KPIs designed to make tech partnerships succeed
A few official processes established across departments to communicate about integrationsSome employees might have one KPI around tech partnerships
A full time employee dedicated to technology partnershipsOfficial processes across different departments to communicateMultiple people have KPIs designed around tech partnershipsSome marketing and product support
Size
Less than 3 product integrations
Less than 5 product integrations
6-50 product integrations
Partner Support
Ad hoc supportNo dedicated employees or processes
Largely ad hoc supportEmployee dedicated to partnershipsContract negotiated with each partner
Standard contract with monetization terms and obligations for each partner, which is customized on an ad hoc basisPartner page on websiteSome resources for co-marketing and co-selling
Third Party Developer Support
Ad hoc supportNo API docs
Ad hoc supportAPI docs lack depth or clarity
Clear ways to access supportThorough API docsSome additional dev resources
CS
No visibility into integration errors or usageEntirely reactiveCustomer confusion over who to go to for support
Low visibility into errors or usageReactive support
CS admin dash showing integration errors, usageCS integration trainingProactively notify customers of issues
Tracking Results
Manual, ad hoc, or no tracking
Largely ad hoc tracking of resultsTracking one of: integration usage and installs, revenue, leads generated, brand equity, deals closed, retention, and customer satisfaction
Tracking revenue and integration usage and installsTrack up to two of: leads generated, brand equity, deals closed, retention, and customer satisfaction in data-driven manner
App Marketplace
None
No public marketplace or display onlyNo in-app marketplace or poorly designed
In-app marketplace and public marketplace with clickable tilesSearch, and filtering by product category
Integration UX and Configs
UI non-existent or clunky, requires customer support to install and useIntegrations not updated
UI non-existent or clunky, requires customer support to install and useIntegrations not updated regularly
Minimal support neededIntegrations maintained by monitoring new product features, partner API changes, and customer feedback
Chapter 2

Getting More Resources Internally

Sometimes leaders are on board with the value of an integration marketplace, but other times it may require persuading leadership of the business case to get enough resources.

The best way to approach this is to lay out the expected benefits of building an integration marketplace, keeping in mind the current strategic goal of your organization.

The more company and industry specific data you can provide, the more compelling your argument will be.

But here is an overview of what to include in a presentation to leadership.

Current Proof of ROI

You should already have at least a few integrations, and be able to show results. If you haven’t tracked these results, put mechanisms in place so you can show:

  • How many new customers came from your tech partners
  • How many deals integrations have influenced
  • Increase in retention, product adoption and satisfaction from customers using the integration
  • Co-marketing and co-selling resources from tech partners and their results

In addition to showing the benefits of your integrations, you should assess how long it took to build one integration and with how many resources.

A general rule of thumb is it takes a team of experienced engineers 3 months to build a deep integration. A simple, one way integration can take only a week or two.

You should also calculate the cost of ongoing maintenance, which includes supporting the integration and updating it as needed.

If your integrations were not built well or are going through a third party iPaaS, you can collect customer support tickets and articulate the current outcomes, but explain why a superior customer experience will bring in better results.

In addition, you should track how many customers are using integrations and expressed an interest in using integrations. Without an integration marketplace, your customers will often be unaware that certain integrations even exist.

Market Evidence

To show the ROI on an integration marketplace, you can point to evidence in the market.

Larger market trends strongly suggest that an integration marketplace is required for success in SaaS.

All of the 15 largest SaaS companies have an integration marketplace. And 63% of the 1000 fastest growing SaaS companies have one.

In addition, businesses have a strong need for integrations. The lack of integration amongst systems is a significant pain point that is causing businesses to lose revenue and expend resources on building custom integrations.

Companies report losing $250,000-$500,000 annually to poorly integrated systems. 90 percent of organizations say data silos and lack of integration is a challenge that is blocking digital transformation. And enterprises spend $3.5 million annually on integrating their systems.

If your organization can solve this problem for your customers, your customers will see real revenue gains and be willing to pay you more and churn off your product less.

Look for data on your specific product category to make an even stronger case. See what your competitors are doing, and find surveys of your target buyer that identify whether integration is a pain point.

In marketing technology, for example, organizations report that the ability to integrate is the single most important factor in selecting a vendor, even more so than price. And leading martech vendors like Salesforce and HubSpot are driving billions in revenue for their tech partners annually.

Use this data to show investing in a marketplace is now a required growth strategy.

$250K–500K
Lost annually to poorly integrated systems
90%
Of organizations say data silos and lack of integration is a challenge
$3.5M
Spent annually by enterprises on integrating their systems

Timeline, Resources and Expected Results

Using your organization’s data and market data, you should scope out the timeline and resources for building an integration marketplace.

Review Chapter 5 on “Building a Marketplace” to accurately assess what engineering resources you will need to invest.

You will also need go-to-market resources to share the marketplace with prospects and customers.

Identify which integrations you’d like to launch your marketplace with, and then assess the co-marketing and co-selling you can do with those partners.

In general, building an integration marketplace will take anywhere from 1 month (if you use an iMaaS) to 5-6 months (if you use an iPaaS or app marketplace) to 12-18 months if you build everything in house.

iMaaS

1 month

iPaaS or app marketplace

5-6 months

Everything in house

12-18 months

In terms of return on investment, you should predict how much an integration marketplace will increase integration adoption and partner-built integrations.

Getting your partners to build native integrations - in part because they see value in being in your marketplace - can significantly reduce the cost of investing in integrations.

Try to assess what the impact of the integration marketplace will be on:

  • Customer satisfaction
  • Customer retention
  • Partner engagement/number of partner-built integrations
  • Referrals sent by tech partners
  • Reduced need for customer support on integrations
  • Impact on close rate
  • Brand awareness

Making the Case

You know what your organization values most and where it most needs improvement. When preparing the tech partner plan, emphasize the value a marketplace can bring to those metrics. Explain what will happen if the organization does not invest, including time spent on custom integrations and integration support, prospects going with an integrated competitor, and customer churn.

Once you have flushed out all these elements, you should present it to your senior leadership in order to get them excited about investing the resources you need to build and launch your integration marketplace.

If you’re unable to make the case yourself, consider trying to get budget to hire a consultant who specializes in partnerships and ecosystems and who can validate the business value.

As you roll out your integrations and marketplace, it is important to put in place internal feedback loops for tracking and understanding the impact.

Sales, marketing, product, engineering, and customer support should all be providing feedback on integrations’ functionality and market demand, as well as tracking how they are fueling co-selling and co-marketing.

Depending on your organization, you may be using a CRM or a PRM, or both to engage with partners, and both can be utilized for reporting and tracking outcomes.

Here are the minimum elements you should track:

  • Integration requests and must have integrations from sales. This requires sales leadership’s agreement to track these requests and influencing factors as a separate field. Otherwise you will have to rely on surveying the sales team.
  • Marketing mentions. Marketing is monitoring your organization’s public reviews, industry reports, and engaging in conversations with prospects and customers. Ask marketing to synthesize the demand and reaction they are hearing on integrations.
  • Customer support and professional services issues. Customer support should have tickets on issues with current integrations, and professional services should be tracking how much time they are spending on integrating systems for your customers. CS and PS can also track the number of requests for new integrations.
  • Engineering resources. Engineering can report on how many resources are required for building and maintaining the marketplace and integrations. They can also explain what is possible for any particular integration given the APIs of two systems.
  • Revenue and influenced revenue. Track how many leads and referrals are being sent from tech partners, and results from co-marketing and co-selling activities. And track if a revenue share is being paid by your partners or by you, or other forms of monetization like a direct charge or upsell for integration access.

“There is tremendous value in creating an ecosystem of third-party technologies. That’s true whether you’re a platform or not.

I have seen a number of organizations stretch themselves thin over the years, trying to solve every need for every customer. It would be great if this were possible, but it’s hard to be an expert in every category. By leveraging third-party technology, you can provide your customers with options for best in class solutions.

At Omnisend, we have an incredible marketing automation platform for eCommerce. While our platform is extremely powerful on its own, our customers’ needs sometimes go beyond what we offer in our functionality. One of our integration partners, smile.io, for example, is a best-in-class application for running customer rewards programs. By integrating our two platforms together, it empowers our shared merchants to deliver even more personalized and targeted communications to consumers, which ultimately drives more revenue.

Leveraging third-party technologies through integration partnerships is often what is best for customers and their success.”

Jon Pruitt, VP of Partnerships at Omnisend

Chapter 3

Identifying Ideal Tech Partners

Once you are planning to build an integration marketplace, you should assess which integrations you want to launch with. Many of these you or a partner might already have built.

You will want to reach out to your current partners to get them invested in your marketplace launch and test the integration to ensure it is capable of meeting customers’ needs and has a good UX, even when used at scale.

Depending on how many integrations you already have, you should select more tech partners to participate in your marketplace launch.

With a marketplace launch, it’s ideal to have at least 10 integrations (whether built by you or your partners). You can build your marketplace while you manage building additional integrations as you’ll likely want to beta test your marketplace with select partners and customers.

At this point, you should develop a framework for identifying ideal tech partners that you can use to assess inbound requests and target your outbound.

While you don’t initially need to have a formal tech partner program, it is worth thinking about your program goals and how you plan to incentivize your partners. See Chapter 8 on “Scaling Your Marketplace” for more details on formalizing your tech partner program.

At an earlier stage, your relationships with tech partners will likely be more hands on. This helps to refine your ideal partner profiles and ensure your program management and incentives are working.

At the time you are launching a marketplace, you should also choose an initial monetization strategy.

If you are a keystone software in your ecosystem or have a truly distinct product that many partners want to be integrated with, you may want to charge a revenue share from your partners on the leads they get from your marketplace. This is usually between 10 and 20 percent of a first year contract.

If you aren’t getting a lot of inbound partner demand, you likely want to initially send your partners leads for free.

A typical way to monetize in the early days of a tech partner program is to require customers to be on higher paid plans to access some or all integrations.

“You want to find relationships that have mutual value where both parties are willing to work together. It’s a fine art to get this blend of aligned interests, but if you can get this formula to work, you will benefit yourself, your partner, and, most importantly, your customer.”

Ed Sullivan, Co-founder of PartnerReady

Mapping Out Your Ideal Tech Partner Profile

There are 4 criteria to consider when mapping out your ideal tech partner profile. We’ll cover each element, and you can use the resulting profile to vet and approach tech partners as well as evaluate your current partnerships.

Initially, it makes sense to rate partners as ‘higher’ and ‘lower’ on each element, and then, as you get more data, refine the assessment to have more granularity.

Knowing your strategic goals and needs as an organization can further help to weight these 4 factors. If you are looking to enhance your product experience, for example, then weigh the customer demand and how the integration will improve the customer UX more than a tech partner’s go-to-market contributions.

Customer Demand

A good starting point is to try to assess customer demand for a particular integration. To begin, ask sales, marketing, and customer support if they are getting any integration requests and how many for each system.

Next, you should try to map out your customers’ tech stacks. Market research and industry reports should make it easy to understand the different types of product categories your buyer is utilizing in their work.

You can survey your current customers about their current tech stack and use marketing tools like Builtwith to get a clearer picture.

It is important to understand not just what systems your customers are using but how they are using these systems. 70% of your buyers might be using team collaboration software, for example, but your product might be a security layer on checkouts and so have little need to be integrated with collaboration software.

Before getting into specific systems, map out your customers’ tech stacks and how they use them. For example, say that you work for Moxxy, a virtual events platform that targets marketers running conferences and events. Your buyer is a Director of Event Marketing and you sell to SMBs and enterprise customers. Mapping out your customers’ tech stack might look something like the graph below.

Percentage of Prospects Using Type of Tech

SMBEnterprise
Survey App
7%
18%
Video Software
28%
42%
Social Media SaaS
20%
45%
Email Automation
43%
61%
Event On-Site Management
32%
79%
Team Collab
62%
92%
CRM
95%
99%
Marketing Automation
45%
99%
Project Mngmt
56%
89%
Attribution SaaS
24%
87%
Personalized Video
18%
23%
BI Tools
17%
76%
Data Warehouse
17%
88%
Swag App
23%
52%

Once you understand what tech your customers are using, you should map out how they are using it, and how they would most likely wish to connect your system with the other systems.

You should be trying to understand the distribution of customers across different tech stacks and products, as well as the distribution of their workflows. For example, Moxxy might map the workflow of their typical SMB customer in the following way.

Example of a Typical Workflow

Moxxy’s Virtual Events
Director of Event Marketing, SMB
CRMEmail AutomationSurvey ToolForms ToolSwag AppTeam CollaborationProject ManagementAccounting App

You should be trying to understand the distribution of customers across different tech stacks and products, as well as the distribution of their workflows. Generally, you are trying to understand:

How many customers use product type + how much efficiency and improved performance would come from integrating your system with that product type

Once you have a strong sense of which product categories are most important to integrate with, you can map the individual systems. You might be able to partner account map with some potential partners and discover exactly how many of your customers and prospects are using that app.

In the case of Moxxy event software, for example, they might survey their customers, conduct market research, and partner account map to 1) find that integrating with CRMs (who most of their buyers are using) are key to efficiently inviting attendees, sending out info, and following up afterward, and 2) map out Moxxy’s prospects’ CRM vendors.

Customer CRM Usage

Salesforce
33%
HubSpot
29%
Microsoft Dynamics
13%
SugarCRM
7%
Zoho
3%
Pipedrive
2%
Other
13%

If you are targeting different prospects that have different value to your organization, whether it be by customer size or vertical or another criteria, you can map out the breakdown by that variable.

For example, let’s say Moxxy’s sells to SMBs and enterprises, but the enterprise customers drive 80 percent of their revenue. Mapping out what systems more valuable prospects are using can help to assess their value.

SMB and Enterprise CRM Usage

SMB CRM Usage
HubSpot
47%
SugarCRM
12%
Salesforce
8%
Zoho
8%
Pipedrive
8%
Microsoft Dynamics
2%
Other
16%
Enterprise CRM Usage
Salesforce
44%
Microsoft Dynamics
31%
HubSpot
5%
SugarCRM
5%
Zoho
1%
Pipedrive
0%
Other
14%

Once you have conducted this research, you should have a list of vendors that you will want to assess further. There are 3 additional variables that contribute to whether a particular integration will be worth the investment.

If you’re approached by a vendor who wants to build an integration with you, even if they are not on your initial list, you can conduct the analysis of these variables to see if an integration is worth supporting.

If a partner is interested in integrating with you, it will be easier to get them to provide the information on their current customers and to explain how the integration will benefit your customers’ workflows and business objectives.

Assess the Impact on Your Company’s Revenue

Ultimately, you want your in-app marketplace to deliver an exceptional ROI. When you’re first launching, it is important to hone in on the integrations that will deliver more leads and closed deals, and decrease customer churn.

You’ll want to estimate a particular integration’s impact on:

  • Your close rate - will it result in deals that close that would have otherwise been lost?
  • New leads and referrals - how many leads and referrals will be sent to you from your tech partner? What is the likely value of these leads?
  • Direct revenue - are you charging a rev share or charging customers to use the integration, putting it on a higher paid plan, and if so, how much do you anticipate earning?
  • Product adoption and customer retention - will this integration result in customers using your product more and churning off less?

Initially, you might not have enough data to precisely predict an integration’s impact, but we’ll cover some ways to assess each metric.

Before you try to assess these metrics, you should do some basic investigation into what the integration will look like and how it will work as described above. See Chapter 4 on “Developing User Stories” to understand how to do that in more detail. It is important to remember that not all integrations are created equally.

An email automation software may have a very simple integration with Salesforce, for example, that does not make a customer’s workflows much better. Or it can have a very complex one that enables the customer to save time and dramatically increases their marketing performance.

The impact a complex, highly useful integration will have on revenue will usually be much higher than the impact of a simple, one way integration. The cost to build and maintain a complex integration is higher (though this can be reduced with an iMaaS) so you should conduct a cost and benefit analysis of different types of integrations between the same systems.

Impact on Close Rate

One of the biggest ways to understand this is to track requests from sales and marketing, and sales’ closed lost analysis.

Surveying current customers on how valuable a particular integration is also helps illuminate how many potential customers might have went with another vendor because of a key missing integration. Part of this analysis can include account mapping to see how many of your customers are using a potential partner’s software.

Depending on how large and responsive your customer base is, you might have to rely more heavily on your understanding of your ideal customer to pick the integrations that are going to be the most popular and the most important to closing more business. Keep in mind that some integrations might be a popular, nice-to-have, while others will be less popular but essential to the customers using them.

“When it comes to tech integrations ‘build it and they will come’ is not a strategy. It helps to have data on what other applications your existing customers are using and asking for. A partner ecosystem platform like Crossbeam can help. Crossbeam reveals to you how many of your current customers are also customers of any possible tech partners without revealing the rest of your lists.

For example, Crossbeam can tell you that your CMS platform shares 7,000 customers with MailChimp but only 1,500 with Drip—making the former a much better investment for your next integration. Having this list of shared customers also means you can fully leverage any co-marketing endeavors, creating materials to notify your joint customers of the new integration. That means no more blindly emailing integrations to people who will never use them.”

Sean Blanda, Director of Content, Crossbeam

If the products you are competing with offer robust integrations to other software, especially keystone software, this increases the likelihood you’re losing customers because of a lack of integration(s).

Another advantage of having an integration marketplace is that it is easy to offer a ‘wait list’ feature for particular integrations, or a place for customers or prospects to select integrations that they would use and are interested in.

Once an integration is launched, one can continue to try to assess this impact by having sales and customer success track if it was mentioned as a reason for purchase, or if it results in a spike in sales.

Since you should be tracking who uses any particular integration and who visits the public and in-app page on the integration, this information can help assess whether new customers were impacted by the integration being available.

Merely using the integration or viewing the docs on it pre-purchase does not mean it influenced the closing of the deal; however, like any significant product feature, usage and pre-purchase interest are both indicators as to how important the integration is to prospects.

New Leads and Referrals

A potential tech partner might have an integration marketplace, both in their app and on their website, that will feature your app. A certain amount of their prospects and customers will discover your app there and consider purchasing it.

Account mapping with them to see how many of their customers and prospects fit your target customer profile can help you to predict how many leads you will receive.

If you’re not able to account map, you can use marketing and sales tools to assess their web traffic and size of their customer base.

You can also research existing integrations in your product category and the number of reviews to gauge how active your product category is and how competitive it will be for you to capture leads from their marketplace.

Larger marketplaces like Salesforce offer you the ability to follow up on leads that did not convert, which will increase the value of these leads as more will convert to customers.

If you map out the type of leads you expect to get and how many, you can use your normal conversion rate on that type of customer to predict the revenue you would expect to derive from these leads.

In addition to leads who find your app in your partner’s marketplace and website, you should receive referrals from your partners, either from the partnership or sales team. This requires finding out what is needed for the partner sales team to recommend your product, how frequently they will do this, and what opportunities you will have to educate and enable their sales team.

With larger partners, this is more established of a process. With medium and small partners, it is something you will usually have to discuss with their team.

Like with leads, you should predict the likely lifetime customer value, conversion rate, and strategic value of tech partner referrals.

Some partners might be able to facilitate your entry into new verticals or enterprise markets and that might have strategic value to your organization.

Referrals should have higher conversion than leads. And referrals from companies who have high brand loyalty and customer satisfaction will likely have higher conversion than companies with lower brand loyalty.

Direct Revenue

If you sell a keystone or truly distinct software, you may anticipate taking a revenue share from leads or purchases in your marketplace. In addition, you may plan to have your sales team send leads to your tech partner and charge a percentage of those closed deals.

For each partner, you should estimate how many new customers you will likely send them, and what that equates to in annual revenue.

If you intend to add an integration or a set of integrations to a higher paid plan, then try to assess how many customers will choose to upgrade to a higher paid plan for the integration(s).

Once an integration is launched, you can see how many current customers upgrade, and put an ‘Upgrade’ button next to an integration tile in the marketplace and see how many convert through it to refine this assessment.

Beyond that, you can use customer research and surveys to determine how many customers would likely upgrade for the integration(s).

Sometimes, companies sell integrations as an add-on, and this makes it easy to attribute revenue directly to a particular integration once it is available. Prior to launching, you can engage in market and customer research to assess how much customers would be willing to pay for a particular integration.

Adoption and Retention

In general, a customer using an integration versus not using an integration will boost retention by 15%. However, you can conduct a more specific analysis by determining how important a particular system is to your customer’s day-to-day workflow.

Once an integration is launched, you should track cohorts of customers using and not using the integration and compare their retention. Prior to launching, you should assess how many and how much customers will use this integration, how complex the integration will be, what alternatives exist to your product in integrating to the customer’s other system, and how much this particular integration is improving your customer’s objectives.

The complexity of your integration will increase the likelihood of retention. Complex integrations mean that your product is integrated into more of your customers’ workflows, which makes migrating off a more difficult task. They also tend to more significantly improve the user’s efficiency and business objectives.

In addition, you should track cohorts of customers using a different number of integrations and track their retention. You should expect the more integrations they use, the higher their retention.

Tying It All Together

By assessing these 4 factors, you have a framework for predicting which tech partners will bring your organization the most revenue in both the short and long term, and thus which partners you want to allocate your resources. As you grow and get more data, you can refine this assessment.

Assess the Cost to Build and Maintain

After you understand the potential return on an integration, you have to calculate the cost to build and maintain it.

In order to understand how much an integration will cost to build and maintain, you have to understand what the integration will look like and who will be supporting and updating it. Most companies build some integrations and their partners build others.

Usually, a company’s most important integrations will be built and maintained by the company. Keep in mind that the costs for an individual integration include engineering costs to build and maintain the integration, and marketing materials to explain what the integration does and how to use it.

The first step to assessing the costs is to map out what the customer experience will look like with any particular tech partner. You should understand what the integration does, if the customers’ access it from your product’s UI or from your partner’s, and how they install and manage it.

Even if your customers would love to have a particular integration, if the potential tech partner does not have an API or isn’t willing to give you access, you may not be able to move forward.

Have your tech team assess the potential tech partner’s API. Is it a public API? If it’s private, are they willing to give you access? Is there well-written documentation? Will it be easy or a challenge to work with? Do they conform to standard authentication protocols or did they create their own?

In addition, consider how long the company has been in business, how their tech works generally, and whether they have the resources to maintain and update their API. Ultimately, integrations require both parties to work, and your customer’s experience depends on your tech partner’s reliability and technical competence.

Try to find out how responsive their tech team is in updating their API and addressing any problems. Ultimately if the integration isn’t working or isn’t keeping with product evolutions on your side, it reflects poorly on your brand and your customers’ experience.

Even if you are building and maintaining the integration, if your partner’s API isn’t well-designed, is frequently down, or isn’t well-documented, your customers will end up having a compromised experience and your engineers will have to spend more time building and maintaining it.

Next, understand how the integration will be configured. For example, a CRM customer might want their marketing platform to automatically send names and emails to their CRM, and have a sales email sent out if someone clicks on a marketing landing page. All this functionality must be written into the integration. The more functionality, the more time will be spent building and maintaining.

These particular configuration options have to be flushed out by your and/or your partner’s team (see the next chapter on configuration best practices). Once you establish them, you have to ensure that you can build them through the tech partner’s API or they are willing to make changes to accommodate the configurations you need.

Assess Go-to-market Opportunities

Beyond the return on the integration itself, tech partners can contribute go-to-market resources that drive revenue for your organization. The partnership, marketing, and sales team can evaluate the go-to-market opportunities with any particular partner.

The first question to consider is whether this is a brand you want to be associated with. Ultimately, if they are featured in your marketplace, and especially if you co-market together, leads and customers will associate you with their brand. Is their messaging, visuals, and materials leaving a brand impression that aligns with yours?

Ensure, at a minimum, their brand avoids sending a message you actively don’t want to be associated with. Talk to their team, and ascertain if there are good opportunities for co-marketing.

Are they interested in promoting the integration and if so, how big is their audience, how much does it overlap with yours, and how many resources are they willing to put into marketing it?

Are they willing to send sales collateral to their leads and customers announcing the integration? How hands-on is their sales process, and are they willing to include your materials? Are they willing to feature the integration on their website or conferences they attend? How much traffic do they get to their partner page?

By answering these questions, you can evaluate how much additional marketing reach and sales help you would receive from a tech partnership.

Interview with Graham McCarthy, CTO and Co-founder of SoapBox

What’s your advice for how to identify the best tech partners?

When identifying a technology partner to integrate with you’ll want to assess two key factors: opportunity tradeoffs and reliability.

Opportunity tradeoffs: Is the cost of the development offset by the third-party integration? Will you increase signups with login integration? Will you increase activation numbers by pulling in data from their platform to yours? Will your customers trust your product more when they see top tier integrations on your marketing site?

Weigh both the time and cost of integrating with potential increases in acquisition and improvements to the overall product experience.

Reliability: It’s important to know how reliable the APIs from the third party integration are.

Do they upgrade them frequently pushing breaking changes?

Are they well documented for your engineering team to fully understand how to properly integrate the services?

These often go unnoticed or are considered minor concerns, but can add up in terms of unplanned work and accrued tech debt if they aren’t thought through properly.

What was SoapBox’s first external integration and why did you make that choice?

Like most tech companies, our employees have Slack open on their computers all day. Since SoapBox is built to help facilitate better communication between managers and their teams, it was a natural extension to integrate with the notification capabilities of Slack to prompt employees to perform SoapBox actions, instead of building out our own notification service.

At SoapBox, we chose to integrate with Slack as our first external integration as a way to capture basic employee information like name, avatar and email, as well as team structures. It offered users a frictionless way to get set up in our app, and provided us with the data we needed to onboard users properly.

In your experience, are there other elements to consider when choosing a tech partner?

When we learned that Microsoft was building a deep team collaboration tool, we knew we wanted to be a launch partner with them to increase the exposure of our app and be tied into Microsoft promotional efforts.

One of the drawbacks to consider when deciding to be a launch partner is weaker API documentation, and fast changing APIs. The one benefit of these drawbacks is becoming well connected to their core engineers and product teams to help craft their API design to better suit our needs.

“When identifying a technology partner to integrate with you’ll want to assess two key factors: opportunity tradeoffs and reliability.”

Graham McCarthy, CTO and Co-founder of SoapBox

Tying It All Together: Selecting Your Initial Tech Partners

Once you’ve assessed all the relevant elements, decide which potential tech partners will be the best initial partners.

Generally, larger partners tends to offer more predictable and programmatic supports, while smaller companies are less predictable but easier to win over. You’re likely to bring more value to smaller partners, and thus have a better opportunity for hands-on support and collaboration.

Most likely, your initial partners will be of varying sizes.

Evaluating what you can bring to the table for a particular partner can also help assess the likely long term success of the relationship. Are you likely to bring the partner a good number of new customers? Is integrating your app a huge value add for some of their existing customers?

The more this is true, the more the partner will likely continue to invest in the relationship over time.

You should use the rubric you’ve developed for determining an ideal partner to continue to seek and approve partners after your marketplace launch. As you get more data, you can refine what works and what doesn’t, and ensure you are best achieving your strategic goals.

Framework for Choosing Tech Partners

Customer Demand
  • Are customers and prospects requesting this integration?
  • Are customers and prospects using this system in great number and is there a need to have your system integrated with the partner system?
Anticipated Revenue
  • Close Lost Rate (deal influence)
  • Partner sent leads and referrals
  • Revenue share, upgrade, or direct charge
  • Adoption and Retention
Cost to Build and Maintain
  • Do you have to build and maintain the integration or will your partner?
  • If you, how much will it cost to build and maintain?
  • Does your partner’s API and your API enable an integration that meets customer needs?
  • Is the partner likely to maintain and update their API?
  • Is the partner’s API reliable and available?
  • Will the partner provide customer support when needed?
Go-to-market Opportunity
  • How invested will your partner be in go-to-market opportunities?
  • How likely will your partner be able to continue to invest over time?
  • How well do your brands and target customer base align?
  • Are there other, strategic opportunities with the partner?

Checklist

Selecting tech partners

By Sunir Shah, President, CSA, and CEO, AppBind

1
Common vision

Your partner and you should both share a common vision of how your companies can work together for the better service of customers, and thereby improve your marketability.

2
Identify target customers

Your customer bases overlap imperfectly; which customer types are you impacting?

3
Identify use cases

Roughly, what use cases are you going to be solving?

4
Assess market opportunity

What kind of marketing and sales will the partner do if you did an integration?

5
Assess hot to trotness

How excited and willing is the partner to do a deal?

6
Get technical documentation

Obtain API docs and other technical information you would need to build a spec.

Chapter 4

Developing User Stories

Once you identify the tech partners, you need to figure out in more detail how your customers want to use your app and your partners’ app together. This task usually falls to the product owner or manager, but you should gather input from sales, customer success, marketing, and the partnership team to best understand what your customers are looking for in an integration.

The basic form of a user story is “As a [role], I need to [task] in order to accomplish [goal]” and there is no reason to deviate from this model for integrations.

Once this big picture is established, you will need to get more granular in how these integrations will be used.

Sometimes these configurations will be simple. For example, a simple story might start, “As a marketer, I need my different membership groups from my CRM to sync with my audiences in Mailchimp so I can send and track my communications from one place.”

Flushing this out in more detail, you should specify that your marketing users want to be able to bi-directionally sync their different “lists” with “First Name, Last Name, Email” from your CRM with their different “audiences” with the same fields in Mailchimp. This configuration is relatively simple.

In other cases, depending on your app and your partner’s app, what some of your customers want will be much more complicated. The goal should be to identify these possible configurations so you can build a UI where your customers can self-serve.

Construct User Personas

Identifying who uses your software and understanding their needs and perspectives is key to figuring out what integration configurations they need.

Depending on your app, you may have different users. For example, a CRM might have a marketing user, a sales user, and a business dev user. An Applicant Tracking System might have a recruiter user, a HR executive user, a hiring manager user, and a benefits admin user.

It is important you identify all the major users of your product so you understand the different integrations that are needed.

Most likely, your product and marketing teams already have these user personas developed. You should also touch base with your tech partner to see if there is an additional user persona that they might bring to the table.

Writing The Stories

Once you have all the user personas, write out the different ways each user would want to use the integrations and why. Just like before launching any new key product feature, you will have to talk to your product, sales, customer success, and product marketing people to try to establish these stories.

Most likely, they will evolve post-launch as you get more customer feedback.

First write out all the high level stories in the form of “As a [role], I need to [task] in order to accomplish [goal.]”

Once these higher level stories are established, you should write out “acceptance criteria” for each one. Acceptance criteria simply spell out what needs to happen to make sure the user can accomplish their goal.

Here are some user stories and acceptance criteria for a marketer who is integrating their marketing automation platform with a CRM.

User stories
Acceptance criteria
As a marketer, I need to send my landing page leads to my sales people by having them entered in our CRM.
  • Automatically send my landing page leads to the CRM
  • Removing a lead or its duplicate updates the CRM list
  • Click to send different landing page leads to lists in the CRM
As a marketer, I need to send my rankings of my leads to my sales team by having the rankings entered into our CRM.
  • Click and select the fields and matching rankings I want to automatically send to the CRM
  • Rank a lead and have it automatically update in the CRM
As a marketer, I need the sales team’s intel on leads in my marketing automation platform so I can send out personalized and segmented emails.
  • Click and select the fields I want from sales to be added to my lists.
  • When a sales person adds new relevant intel, it automatically updates my lists
  • Click and remove CRM fields
As a marketer, I need to calculate the ROI on my marketing efforts by pulling in data from our CRM.
  • Click and select the fields from the numbers of the sales team’s funnel to automatically come in
  • Be able to tag deals in the sales funnel to marketing efforts

Sample user stories and acceptance criteria for a marketer integrating a marketing automation platform with a CRM.

Once all your user stories and acceptance criteria are written, you are ready to work with your engineering team to get them built.

Reconciling with APIs

Once you have all the user personas and stories, the technical team will have to reconcile them with the APIs.

The objective is to see how many of the user persona’s objectives can be reached within the APIs.

With larger partners, it is unlikely they will modify their API anytime soon. It is worth putting in a request, but don’t expect to see a change soon (unless it is already on their roadmap).

With smaller partners, however, they might be able to work with you to change their API in order to meet the needs of your joint customers.

You also might need to change your own methods of authentication or your API to meet your customers’ objectives.

Customer Beta Testing

After you or your partner build an integration, you should beta test it with customers. If your customers are larger businesses, this might be 3-5 customers; if your companies are smaller organizations, you might want to find 5-10 customers.

These customers should have stated an interest in the particular integrations, and you should have a good relationship with them.

You should give them 1-4 weeks to try out the integrations, depending on how complex the integrations are.

Track any problems, or inquiries during the experience, and then ask them for feedback on their experience installing, syncing, and running the integrations. You can also get feedback on whether they need different configurations options.

Chapter 5

Building the Marketplace

Many times, organizations embark on building an integration marketplace without having anyone on their team who has done it before. This chapter covers what goes into building an integration marketplace that works well and works at scale.

If you have already entered another company’s in-app marketplace, or built integrations for some of your customers, you are probably familiar with the fact that it can be a time consuming process. Often, companies do not have a dedicated team working on integrations, but pull developers off other projects related to the core product to build the integrations. It often becomes a drawn out, expensive process.

Here are the elements you should consider when deciding how to build your marketplace, and different platforms you can buy to make the process easier.

Build or Buy

The biggest decision to make from a technical perspective is whether you want to do everything in-house, use an integration platform (also known as an iPaaS), an app marketplace, or an iMaaS.

In most cases, it is going to be more affordable, quicker, easier, and deliver a better customer experience to use an iMaaS but it depends on what you have built so far, what your resources are, and what your goals are.

When making an honest assessment of this decision, consider all the elements that go into building integrations and a marketplace, and assess how much it would cost you in developer time (time that could be spent on other projects).

You should also ascertain how many of your developer hours can be devoted to the project on what timeframe, and see how that affects your timeline to launch.

In many cases, an iMaaS can speed the timeframe to launch up by 12 months, and an iPaaS or app marketplace by 4-6 months.

Realistically, building an integration marketplace takes a great deal of developer time if you plan to scale your marketplace to dozens of partners and hundreds or thousands of end users.

Building it all in house is similar to hosting your own servers or building your own CMS. Sometimes this makes sense, depending on your engineering expertise and need for bespoke architecture, but usually it is more expensive for infrastructure that does not work as well.

Below are the important technical elements of an in-app marketplace. If you’re thinking about building in house, calculate how long each element would take to build and maintain in line with your growth goals.

At the end of this chapter, you can also find Worksheets on Building vs Buying Your Integration Infrastructure to help further assess what approach makes the most sense for your organization and goals.

Tech Requirements for Building an In-App Marketplace

01Establish authentication protocols
02Configure the integrations
03Security
04Marketplace and integration UI
05Partner app and marketing submission
06New account provisioning
07Scheduling
08Hosting
09Maintaining servers
10Tracking and logging errors and analytics
11Responding to API updates
12Enable self-serve customer and partner UX

Platform Options

There are four basic options for platforms that can underpin your in-app marketplace: 1) an iPaaS which powers integrations between your app and other systems; 2) an app marketplace which can power the front-end of your marketplace; 3) an iMaaS, which can power your integrations and marketplace; 4) a PRM, which provides a place for your customers to submit their marketing materials for the marketplace.

We’ll cover what each type of platform offers and what you should think about when assessing it.

iPaaS

iPaaS’s were originally built for internal workflow automation. As a result, they aren’t the best fit for product integrations. But sometimes they might be the best option.

There are two different types of iPaaS’s: embedded iPaaS’s and non-embedded iPaaS’s that you direct your customers to use on their own.

Embedded iPaaS

Embedded iPaaS’s embed inside your product so that your customers can access it from within your app. Your customers should not have to create an account with iPaaS or go to their app.

Embedded iPaaS’s have preconfigured integrations so your app will be able to connect with them in pre-defined ways. They also do not usually come with customizable front-end marketplaces so your team will have to build this in addition and connect it with the infrastructure of the iPaaS.

The benefit of an embedded iPaaS is you can more quickly provide some connectivity for your customers to a high number of apps from within your app.

Unless your product and use case is relatively simple, however, iPaaS’s often do not have the exact configurations that your customers need. As a result, your developers will have to learn how to code around the iPaaS to create the configurations.

In addition, as other APIs and products are updated, you have to wait for the iPaaS to update the integration configurations in their connectors to reflect these changes. That means your integrations may cease to be useful (or your engineers will have to code around them).

You should also consider what goes into customer support and analytics for embedded iPaaS integrations. What kind of visibility does your team have into each integration and who is using it? Can your CS team see when a partner’s API is down, for example? Can they run or schedule syncs for a customer?

Embedded iPaaS Assessment

  • How well do the pre-set configurations between apps work for our customers? Do they offer the configurations are customers need?
  • How often are configurations updated? How likely is it our customers’ needs will be addressed promptly?
  • How will you connect this to a front-end marketplace and UI? What will the customer experience be of installing and managing integrations through the embedded iPaaS?
  • How will customers access integrations outside the embedded iPaaS that you or your partners have/will built?
  • What visibility will CS and marketing have into customer installation, usage, and errors? Will CS be able to troubleshoot?
  • How do your developers feel about coding around the embedded iPaaS? How much time would it take to learn the platform? Do they have to code in a particular language?
  • Will this help you develop relationships with the other apps on the embedded iPaaS?
  • Can you monetize integrations with an embedded iPaaS? Can you track when your customers are purchasing an app because they discovered it in your marketplace? Can you send tech partners leads of attempted installs?
  • Can you provide your tech partners with analytics on integrations through the iPaaS?
  • How will your tech partners communicate with you and submit marketing materials to you for their integration tile?

iPaaS

A regular iPaaS is a tool your customer uses to connect your app with other apps. For companies that serve SMBs, the most popular iPaaS is Zapier. When you build a connector to Zapier, your customer can then connect to other apps on Zapier.

Like with an embedded iPaaS, the configurations that are available will be dependent on Zapier and the other apps in their ecosystem. These may or may not meet your customers needs. The simpler your product and the simpler your need to be connected to other systems, the more likely an iPaaS will work well for your customers.

The downside of an iPaaS is that your customers have to make an account with the iPaaS, pay for that account, and leave your app to set up and manage their integrations. You lose a lot of control over the user experience, and your customer might be dissatisfied with the additional cost and UX.

An iPaaS does not have an integration marketplace front-end. In this case, you’d have to build a marketplace and then customers could click on a tile for an app and be re-directed to the iPaaS. (It’s best to disclose this upfront on the tile.)

The plus side of an iPaaS is that it may connect you to hundreds or thousands of apps, at least for basic and more common use cases.

iPaaS Assessment

  • How well do the pre-set configurations between apps work for your customers? Do they offer the configurations your customers need?
  • How often are configurations updated? How likely is it your customers’ needs will be addressed promptly?
  • How will we connect this to a front-end marketplace and UI?
  • What will the customer experience be of installing and managing integrations through the iPaaS? Is the iPaaS known for a good UX and customer support?
  • What visibility will CS and marketing have into customer installation, usage, and errors? Will CS be able to troubleshoot or does the customer have to go to the iPaaS? Is the iPaaS responsive?
  • Will this help you develop relationships with the other apps on the iPaaS?
  • How much will this cost your customers monthly on average? How much will super users of integrations have to pay?
  • Is there a way to monetize integrations on the iPaaS?
  • How technical are your customers? (The less technical, the more they will need help with the iPaaS.)

App Marketplace

An app marketplace is a front end UI for your integration marketplace. Some of these can be embedded in your app, and others are for a webpage and might be more difficult and expensive to embed.

App marketplaces are customizable so a non-developer at your company can make it look like your brand. They come with more advanced features like categories, filtering, search, and sometimes payment processing, and partner portals.

The challenge with app marketplaces is they do not run or host integrations so you will have to connect the integration install and management process for customers and partners to the front end marketplace.

App Marketplace Assessment

  • Can you embed the marketplace in your app or does it live outside your app?
  • If you are using it outside your app, can you sync data or materials with the marketplace you build in your app?
  • If it is embedded, how difficult is it to embed it in your app? What is the process for embedding?
  • Does the marketplace have search, filters, flags, and categories? Can you process payments?
  • What will the customer experience be of installing and managing integrations? How will you connect the marketplace to the installation and management of integrations for the customer?
  • What can tech partners see in terms of analytics? How will partners see the analytics on integration usage, adoption and errors?

iMaaS

An iMaaS offers integration connectors, a customizable front-end marketplace, and a partner portal where partners can submit their integrations and marketing materials and see integration analytics.

An iMaaS is designed to provide the end-to-end infrastructure for your integrations and your marketplace and it is only platform built specifically for powering SaaS product integrations.

Some iMaaS’s have thicker connectors that pre-configure the integration configurations, while other allow you to code those configurations yourself in any common language.

The latter approach means you can give your customers the exact configurations they need and update them as needed. You also develop a direct relationship with your tech partners. The former approach saves engineering time for use cases that are captured by the pre-set configurations.

iMaaS Assessment

  • How does the marketplace embed in your app?
  • Can you feature integrations you or your partners have already built?
  • Does the marketplace have search, filters, categories, and flags? Can you process payments?
  • If configurations are pre-set, how many meet your customers’ needs? If they aren’t pre-set, what does a developer have to do to set them?
  • What will the customer experience be of installing and managing integrations?
  • What can partners see in terms of analytics? How will partners see the analytics on integration usage, adoption and errors?
  • Can customer support see integration usage and analytics?
  • Can we track how many customers purchase a partner’s app after discovering it in the marketplace? Can we identify who attempted to install an integration?
  • Can partners submit integrations and marketing materials?
  • Does this enable me to develop a direct relationship with other apps?

PRM

PRMs are built for partner collaboration. When it comes to integration marketplaces, they can support marketplaces by providing a portal for partners to submit their marketing materials for their integration tile in the marketplace.

This usually requires your team to then upload the information to the actual marketplace, and it is not a place to submit the integration itself, though it can certainly be used to share documentation or communications with partner developers.

PRM Assessment

  • How can this streamline communications with tech partners who want to submit marketing materials?
  • Can this help partner developers get support on the integration and get information on our API? Can we accept or reject their integration?
  • Does this enable us to share analytics from our marketplace in any way? How would we build that functionality?

Overarching Considerations

As you work through whether you want to build your infrastructure in house or use a platform, or both, you should always assess a few variables and understand their relationship to business outcomes.

Below you can find these elements next to their differing business outcomes, followed by a worksheet for working through whether to build or buy.

Ultimately, whatever path you choose, you should form a realistic sense of project cost and the likely outcomes and timelines.

Worksheet

What to Consider In Planning an Integration Marketplace

Customer UX

What to ask
Options
Business outcome
  • Can customers easily search and filter the marketplace apps to find what they need?
  • Does the customer have to leave your app to install?
  • Can they install on their own and click to install?
  • Can they set their configurations on their own?
  • Can they run syncs and see their activity?
  • Can they uninstall integrations on their own?
  • Can they restrict who can install and uninstall apps?
  • Build - high cost, exceptional UX; low cost, poor UX
  • Embedded iPaaS - medium UX
  • iPaaS - medium to poor UX
  • App marketplace - good marketing UX; no integration UX
  • iMaaS - exceptional UX
  • Increased retention
  • Upsells
  • More customer referrals
  • More leads for partner apps as customers discover new apps in the marketplace and have a good UX with integrations

Partner UX

What to ask
Options
Business outcome
  • How will your partners submit an integration they built to your marketplace?
  • How will your partners submit marketing materials?
  • How will partners get developer support?
  • Will partners be able to get analytics from your marketplace with leads and integration usage?
  • Will partners be able to see integration usage and errors to provide customer support?
  • Build - high cost, exceptional UX; low cost, poor UX
  • Embedded iPaaS - no direct relationship with partners
  • iPaaS - no direct relationship with partners
  • App marketplace - good UX for marketing; none for integrations
  • iMaaS - good UX
  • More partners
  • More partner investment and loyalty
  • Better customer UX

Developer UX

What to ask
Options
Business outcome
  • Can partner developers get the information they need and contact support?
  • Can partner developers submit integrations for approval and see usage?
  • Do your developers have to learn a new system or platform to code the configurations that customers need?
  • Can your developers code in their preferred language?
  • Do your developers have visibility into integration usage and errors?
  • Build - high cost, exceptional UX; low cost, poor UX
  • Embedded iPaaS - medium to poor UX
  • iPaaS - medium to poor UX
  • App marketplace - none
  • iMaaS - good UX
  • Higher number of integrations
  • Get integrations to market faster
  • Better integrations with higher customer satisfaction
  • Fewer customer support issues

Customer Support

What to ask
Options
Business outcome
  • How often will your customers need customizations or additions to the integrations offered?
  • Will customers be able to self-install, see their integration activity, run syncs and uninstall?
  • Will customers be able to discover the integrations they need?
  • Will your customer support team be able to see all customers’ integration activity and usage, and run syncs?
  • Will your customer support team be alerted if there is a systemic failure on an integration?
  • Will your partners’ customer support team be able to see integration activity?
  • Build - high cost, exceptionally enabled CS; low cost, poorly enabled CS
  • Embedded iPaaS - medium to poor CS enablement
  • iPaaS - poor CS enablement
  • App marketplace - enables marketing materials for integrations
  • iMaaS - good CS enablement
  • Increase customer retention
  • Higher integration adoption and satisfaction
  • Reduced need for CS or developers

Build Costs And Timeline

What to ask
Options
Business outcome
  • How many engineers of what level of expertise would it take to build the infrastructure and marketplace that will meet our business goals?
  • How long will it take to launch the marketplace and with how many integrations?
  • How many integrations will be native, third party, or partner built?
  • Build - high cost, 12-24 months
  • Embedded iPaaS - medium cost, 4-8 months (plus in house front-end marketplace build)
  • iPaaS - low to medium cost, 2-4 months (plus in house front-end marketplace build)
  • App marketplace - low to high cost, 2-6 months (plus in house integration infrastructure and integrations)
  • iMaaS - medium cost, 1-4 months
  • Time to market
  • Engineering resources diverted from core product

Maintenance Costs

What to ask
Options
Business outcome
  • How often will your customers need customizations or additions to the integrations offered?
  • How hard will it be to update integrations in response to API and product changes?
  • How will you respond to scaling issues relating to usage and new customers and partners?
  • How easy is it to add new partners and partner-built integrations?
  • How hard is it to launch new native integrations?
  • Build - if high build cost, low to medium maintenance; if low build cost, extremely high maintenance costs
  • Embedded iPaaS - medium to high maintenance costs
  • iPaaS - medium to high maintenance costs
  • App marketplace - low maintenance costs for marketing materials, no coverage for integrations
  • iMaaS - low maintenance costs
  • Increase customer satisfaction
  • Time to market for new integrations
  • Reduced need for CS or developers

Worksheet

Should You Build or Buy Your Integration Infrastructure?

What it means
Build
Buy
Core Expertise
Is integrating data and systems a core part of your product?
Integrating data and systems is core to your product and value proposition. It’s a key part of your engineering team’s expertise.
This is not a core part of your product, and it is outside your team’s main expertise. Your engineers are currently focused on what makes your product differentiated in the market.
Internal Culture
Integration infrastructure is for developer and business users. Does your organization normally buy or build these tools?
Your engineers prefer to build as many tools as possible and have a strong culture of building dev and business tools in-house.
An iMaaS or an iPaaS is a dev tool, hosting, and, like a PRM or CRM, business software. Your organization normally buys those types of tools when it is cost effective and offers enhanced functionality.
Current Progress
Have you built an in-app marketplace, public marketplace, admin dashboard for customer support and marketers, and partner portal?
You have built a significant portion of this infra and it works or will work at scale.
You have only built part of this infrastructure or what you have built will not be able to provide customers and partners an excellent UX at scale.
Current Objectives
Advanced functionality enables a self-serve experience for customers and partners, drives revenue, and captures marketing leads and analytics. Does your organization aim to scale enough to want to provide customers and partners a self-serve UX? Does your organization seek to drive more revenue through tech partnerships?
Your objectives do not require any advanced functionality or scale, and you have the manpower to provide hands-on onboarding and management for your customers and partners.
You seek to have more than a dozen partners and hundreds of customers using integrations, and would like to continue to scale. Driving revenue is a priority.
Engineering Expertise
Do you have a senior engineer who has built integration infrastructure before, or can you hire one?
You have a senior engineer with experience who can and wants to lead this project full-time.
You do not have an engineer who has built integration infrastructure before and wants to take on this project.
Developer Resources
How many developer resources do you have to devote to building integration infrastructure and in what timeframe will they be available?
  • It usually takes a team of experienced engineers 6 months to build basic integration infrastructure from scratch. Plan for 12-18 months if you want advanced functionality.
  • Once the infrastructure is built, it must be maintained so ensure you will have continued access to developers dedicated to this task.
You do not have a devoted team of engineers to build the infrastructure for at least the next 6 months, as well as engineers who can maintain and update it.
Business Objectives
With an iMaaS, you can launch your integration infrastructure in a few weeks. Given your current progress, is the increased time to market, decreased functionality of an in-house build, and increased upfront costs outweighed by the benefits of customization and complete ownership?
  • You have distinct needs for your integration setup and highly value advanced customization that cannot be easily achieved with an iMaaS.
  • You do not like being dependent on a third-party vendor, and owning your infrastructure is more important than getting to market in the next 6-12 months. You can afford the high upfront labor costs of building in-house.
  • Launching 12-18 months early is of high value to your organization, as is the increased functionality of an iMaaS.
  • You do not need much customization beyond the integration configurations and the content and design of your marketplace.
  • Driving revenue through tech partnerships or attracting more partners is a top priority.

Rolling out the Marketplace

The next chapter “Marketing the Marketplace” covers the go-to-market side of the marketplace launch, but there are things to consider from a technical standpoint.

Once you have made a decision on how you want to build the marketplace, you should think about the rollout process from a technical standpoint. You should also carefully track your resources, timelines, and results as you may find that you were overly optimistic in your predictions and that you’d be better off switching to a platform from all in house (or vice versa).

Customer Beta Testing

Once there is a timeline for the front-end of the marketplace and the integrations themselves to be ready for launch, you should select a few customers to beta test the marketplace. If your customers are larger businesses, this might be 3-5 customers; if your companies are smaller organizations, you might want to find 5-15 customers.

These customers should have stated an interest in the particular integrations, and you should have a good relationship with them.

You should release the marketplace to the beta customers, and, depending on how complex your integrations are, give them 1-4 weeks to try out the integrations.

Track any problems, or inquiries during the experience, and then ask them for feedback on the marketplace UX, their experience installing, syncing, and running the integrations. You can also get feedback on whether they need different configurations options.

These customers can also become part of the Customer Advisory Panel you establish for the marketplace. After fixing any bugs or issues that are revealed during this period, your marketplace will be technically ready for launch, and you can establish your official launch date. (See the next section on marketing your marketplace.)

Monitoring Your Marketplace

Once you have launched, you should carefully monitor costs and engineering resources expended, customer usage of the marketplace and the integrations, as well as the partner and customer UX.

This information should be tracked and made visible to technical and non-technical users. Partnerships and business development teams - and company leadership - need to be able to see and understand the ROI on the integration marketplace.

Tracking integration usage and the customer and partner UX also helps you to refine the marketplace to better meet your customer needs.

As you refine your processes, establish a timeframe and workflow around the tech side of adding new integrations to your marketplace so that you can share this with partners as well as your marketing and sales departments.

In addition, as you grow, you must ensure that you can handle a large number of end users and accounts all using different integrations. (For more info about scaling your marketplace, see Chapter 8.)

Checklist

Quality assurance

By Sunir Shah, President, CSA, and CEO, AppBind

1
Personal smoke test

You should personally try the integration to make sure it works as you expected and you understand it.

2
Internal QA

Have someone else inside your company try the integration and look for problems.

3
Beta testers

Recruit actual customers, often those you talked to during customer research, to try it out and confirm it works.

4
Beta reviews and case studies

Get feedback, testimonial, reviews, and case studies from your beta customers you can use in your sales and marketing collateral.

5
Partner QA

Let your partner QA the integration.

Chapter 6

Marketing the Marketplace

Launching your marketplace should follow the same process as launching an important new feature of your product. Your product marketing team should have a template for this, though this chapter will cover the general strategy for rolling out a marketplace launch.

The main difference between a launch of an important product feature and a marketplace is you’ll need to create assets not just for customers, but for your partners. You need marketing assets that convince partners to invest in your relationship, and that empower them to co-market with you.

You should aim to attract and enable your partners before the marketplace launch so that your key partners are prepared to amplify your launch.

This chapter covers the marketing motions and assets you should implement before, during and after launch to ensure your marketplace reaches its full potential. The better co-marketing and co-selling motions you have in place before the launch, the more effective it will be.

Marketing To and Enabling Partners: Revenue Teams

Ultimately the most successful in-app marketplaces are those where tech partners are eager to build into your product, or at least happy to have an integration to your product. This requires getting other companies’ partnership and sales teams convinced of your tech ecosystem’s value.

Before you launch your marketplace, you want to ensure some of your partners’ marketing and sales teams are excited to promote it. Creating co-marketing cadences around existing integrations before your launch will help you hone in on the most effective tactics.

Marketing to your partners’ business development teams and empowering them with great materials on your app and ecosystem will ultimately lead to them contributing more marketing resources.

This should involve a mix of general marketing and product marketing.

Key ways you can market to and enable partners:

  • A web page specifically aimed at partnership teams
  • A sales deck and one sheet about your app
  • One sheets with the ROI partners can expect to see from an integration and your marketplace
  • Blog articles making the business case for being part of your in-app marketplace
  • Social posts with materials highlighting your successful tech partnerships
  • Events, webinars, and conferences for your current and potential partners
  • Compelling sales collateral for your partners’ sales teams to use

These campaigns should focus on the business value of joining your in-app marketplace. This can be done by highlighting:

  • The unique problem your product solves
  • How your product is particularly sticky, and integral to your users’ workflows
  • The number and type of users you have
  • How your users are using other software in their tech stacks
  • Why integrating with your product makes life easier for users
  • Any case studies or data on driving ROI for your tech partners through new leads, increasing conversions, reducing customer churn, or upsells
  • Why your users generally prefer integrated software
  • The perks of your partnership program, including any co-marketing and co-selling resources, and any favorable terms

Marketing to and Enabling Partners: Developers

Tech partnerships sit at the intersection of partnerships, product, and engineering. In order to promote and grow an in-app marketplace, getting third party developers on board is key. Excited developers result in more integrations built and maintained, and a better user experience for your customers.

Key ways you can to market to developers:

  • A web page for developers with clear documentation on your API and how to use it
  • Offering developer forums where questions can be asked and answered
  • Developer-specific blog or content
  • Hosting events for developers
  • Being active in online and in-person developer communities
  • Free developer sandboxes where developers can try building integrations and understand your product

These initiatives should extol benefits developers care about. This can be done by highlighting:

  • How clear and easy your API is to work with, including having the configuration options users will need
  • How well-supported and robust your API is
  • The cool stuff that can be created working with your API
  • Your tech team knows what it is doing and is available for troubleshooting

Marketing to Prospects and Customers

Marketing integrations to prospects and customers is essential to driving adoption and showing ROI. These campaigns should highlight individual integrations and, after the launch, the in-app marketplace itself. Test as many of these tactics as you can before planning your marketplace launch.

Key ways you can market to prospects and customers:

  • Email campaigns that are segmented to user profiles and share integrations of interest
  • Social posts highlighting your new or popular integrations
  • Social polls asking about favorite integrations or most desired integrations
  • Press releases
  • Ads targeted to users who are already using the other product
  • Ads targeted to your current customers broken down by user profile, and highlighting integrations they are most likely to use
  • Search ads for people looking for integrations to the tech partners’ products
  • Provide logo, elevator pitch for the product, and integration description, as well as any other materials, to all tech partners for their website, sales, and marketing campaigns
  • Webinars explaining one or a few important integrations and how they work
  • Recorded demo of integrations and how they work
  • Clear documentation on how to use the integrations, with a FAQ
  • If direct mail works for your product, include postcard or other materials about key integrations
  • Blog content on the value of using particular key integrations
  • Events targeted at particular user profiles that include information on integrations of interest
  • Promote integrations inside your application, either in the marketplace or where they might be used in a user’s workflow

This content should communicate to users why they should care about integrations. Specifically highlight:

  • Why integrations save the user time
  • Why integrations empower the user to be more efficient and successful at achieving their goals
  • How specific integrations work
  • What cool things the customer can do with the integrations
  • How easy the marketplace makes it to find what they need

Marketplace Launch

Once you have core marketing resources around integrations for partners and customers and have discovered some tactics that work well in your ecosystem, you can plan your launch of your integration marketplace.

This requires coordinating with partners and other invested parties to maximize your reach. The best approach should reflect your unique ecosystem, but this is a general launch plan that can be customized to the profile of your partners and customers.

Before the Launch

Customers and Prospect Outreach

The more you have involved beta customers in the marketplace build and rollout, the more they will amplify its official launch.

On launch day you want some kind of event, whether it is a larger conference your organization is holding or a webinar. During this event, you’ll want to showcase one or two beta customers. These customers should be as high profile and as enthused as possible.

You’ll want to start promoting this event two weeks out to prospects and customers. If possible, you should segment these communications to reflect which integrations the prospect will be most excited about.

A mix of emails, social, and ads (and any other channels you use to promote webinars) should be most effective. On social, tag and thank the beta customers who will participate in your event.

Beyond promoting the event where prospects and customers can learn about the marketplace and top integrations, you can try to create excitement by running polls on social media, asking your audience which integration is their favorite.

You might also want to offer lunch or some other prize for attendees of the webinar in order to increase interest.

Including some marketplace images and describing some important use cases in your marketing newsletter a couple weeks before launch can also lift the number of registrants.

If you own or participate in any communities on social media or Slack, announce the event in the weeks leading up to the launch.

Partner Outreach

You should have at least 10 integrations in your marketplace, and you will want to leverage all these partnerships in drawing attention to the launch.

You can include your top two partners in your event day webinar, and they can showcase their integrations and what customers can accomplish by using them.

Ensure that all the marketing materials submitted by partners (or written by your team) are clear, helpful, and easy to understand. You will likely have explanatory marketing materials inside your app as well as in your public marketplace.

Ask your partners to promote the webinar leading up to the launch, and to promote the marketplace on the day of the launch. For any partner that has relevant, strong website traffic, you should ask to write a guest blog on the marketplace and your integration that they can publish on launch day.

Ask to include 3-4 of your most important partners in a press release on the marketplace. This can amplify your news as each of their teams work to get it placed and shared.

If any of your partners own active communities, see if they will let you promote and announce your webinar in those communities.

Ahead of the launch, enable your partners’ sales teams with decks and info sheets on your product and the integration and encourage them to share it with relevant prospects.

General Prep

In addition to reaching out to prospects, customers, and tech partners, you should look for other opportunities to amplify. If you have agency or co-marketing partners, share the news with them and see if they can include it in their marketing activities.

Beyond a press release, try to identify industry specific journalists that might be interested in covering your launch. Industry specific communities and publications will be much more interested in your enhanced product functionality than general publications.

If you can’t get any publications or communities interested in your launch, consider doing paid sponsorships or paid posts on these sites.

If you have the budget, create a short product explainer video that you can share on social and on the landing page for the launch or public marketplace page.

Make sure that your sales, marketing, and customer support teams are all educated on the marketplace and integrations and have infosheets to give to prospects and customers.

Day of the Launch

For launch day, you should ensure customer support is prepared to help customers if they have any issues installing integrations or using the marketplace and integrations.

Other than that, you should be executing on all the marketing activities you have prepared.

Here is a basic checklist:

  • Share your press release and any news articles
  • Email customers and those on your newsletter announcing the marketplace - segment by role and industry if possible, highlighting the best fit integrations - and inviting them to the webinar
  • If you normally message your customers inside your app, consider messaging them about the marketplace launch
  • Promote on social media, highlighting the webinar and showcasing the explainer video
  • Tag beta customers, partners, and industry influencers
  • Promote guest blogs on partner sites and any tech partner produced materials
  • Digital ads featuring the marketplace, targeted to those searching for particular integrations in your product category
  • Share in relevant Slack and social media communities
  • Run the webinar showcasing beta customers and partners, with a way for customers or prospects to reach out with more questions

After the Launch

In the days after the launch, you will want to:

  • (One day after) send a thank you to beta customers and tech partners, and a gift to any who contributed significantly
  • (One day after) send a thank you and gift to any other partner or influencers who contributed significantly
  • (Two days after) send a thank you to all the webinar attendees and ask them for feedback
  • (Three days after) send a thank you to customers who checked out the marketplace and installed a new integration, and ask them if they had any issues
  • Continue to promote blogs and articles on the marketplace from other websites
  • Follow up with any leads

After the initial launch, you will want to continue to engage your prospects, customers and partners so that they use the marketplace and continue to provide feedback on the experience and how it can be improved. These types of activities were covered at the beginning of the chapter.

Ongoing marketing initiatives can include regular webinars on getting the most value out of the integrations, case studies featuring customers using integrations, and segmented suggestions for using the marketplace to accelerate business objectives.

After the launch, marketing initiatives can also move farther afield from the particular integrations to providing valuable information to your audience, or (when co-marketing) your shared audience.

For example, if you’re an e-commerce platform integrating with a shipping app, you can create joint content on how retailers can best ensure they meet customer demand during the busy holiday season.

Even though such content does not specifically address your integration, users who feel like you are providing them with helpful insights will likely check out your company and also develop a sense of trust in your relationship with your tech partner.

If you want to continue to scale your marketplace, you should also continue to create an active community around your tech partners, for both those working in business development and for developers.

Checklist

Pre-launch marketing

By Sunir Shah, President, CSA, and CEO, AppBind

1
Schedule

When are you going to “launch” the integration? Meaning, when is the marketing push?

2
Blog post

Will it include the elevator pitch and description, explainer video, screenshots, tracking links, case studies?

3
Landing page

Are you designing special landing pages for the integration?

4
App marketplace/directory listings

Do you have copy, screenshots, explainer videos, support contact information, tracking links, reviews from beta customers, and any case studies?

5
Social media mentions

What will be pushed on social media? The explainer video, screenshots, link to the landing page, or link to the blog post?

6
Webinars

Are you hosting a webinar for customers to talk through the integration?

7
Social media advertising

Are you buying social media ads for the integration? What’s the target? The landing page, blog, or webinar?

8
Newsletter

What is the newsletter copy? Will it include the elevator pitch, explainer video, screenshots, tracking links, case studies, link to the webinar?

9
In-app messaging

Will the integrations be announced in app, through notifications or, if decided in the spec, directly in the user interface?

10
Drip email

Are you designing a specialized drip campaign for new customers of the marketplace/specific integrations?

11
Press release

Are you putting out a joint press release with integration partners? Whose PR agency is coordinating? How much time do they need? What is the real story here?

Checklist

Pre-launch sales

By Sunir Shah, President, CSA, and CEO, AppBind

1
Elevator pitch for the in-app marketplace

In two sentences, what customer problem are you solving with the integrations and how? What is your unique value proposition?

2
Elevator pitch for your product

In two sentences, what customer problem are you solving with your company?

3
One pager

Do you have a one pager that answers most questions? Include any case studies from your beta customers. Social proof is key.

4
Explainer video

If prospects won’t read your one-pager, they will watch the explainer video.

5
Webinar (internal)

Do a webinar or video call to demo the integration for the sales team and explain how it will help them sell more.

6
Sales tracking

Will customers interested in the integration be tagged in the CRM?

Chapter 7

Marketplace Customer Support

A key element of a successful in-app marketplace is ensuring that customers have a good experience using the integrations. Minimize the need for customer support, and empower customer support agents with the tools they need to quickly help customers who can’t self serve.

Minimizing The Need For Customer Support

From a tech perspective, you should do everything you can to avoid customers needing to contact someone for support. Not only does this save you resources, customers find it more convenient.

The vast majority of customers prefer to self serve rather than have to contact your company for help.

If you’re not using an iMaaS designed for in-app marketplaces, you should build a marketplace with an intuitive UI that allows customers to discover the integrations they need, and select the configurations they want, sync their data, and see their logs without your assistance.

They should also be able to easily see all the integrations they have installed, and uninstall integrations.

One of the advantages of having an in-app marketplace instead of sending customers to third-party integration tools is you can control the customer experience, making it easier for customers to self-serve.

Providing easy to find help docs and explanations of what the integration does also helps to minimize the need for customer support.

You should ensure that you have high availability and reliable security practices so the integrations are running as needed, and your customers’ data remains secure. Make sure that your infrastructure will continue to work well even as you onboard dozens of partners and hundreds or thousands of customers.

In addition, a well-designed API and integrations that work as intended within your API and your partners’ APIs’ limits will avoid many customer support issues.

Enabling Good Customer Support

It is key that you write clear documentation of your API and for each integration for both users of your marketplace, and for your customer support team. This will ensure issues either do not occur or are resolved more quickly.

If you are using an iMaaS, you will have an Admin Dash for your customer support team to track errors with the integrations. If you are building everything in house or using an iPaaS, build a way for non-technical customer support to have complete visibility into integration usage and errors, as well as the power to troubleshoot for customers.

Like all tech, APIs sometimes experience issues that cause integration failures. If your customer support team can see a system wide error, they can proactively notify customers of the issue, and keep them updated as the issue is resolved. This ultimately reduces the burden on customer support and provides a better customer experience.

Empowering customer support with clear visibility into errors on both a system wide and individual level enables them to respond quickly to any inquiries from customers. If a particular customer thinks their integration isn’t working properly, customer support should be able to easily see the integration logs, and run syncs to ensure it is working properly.

Because integrations involve two different software, you should make it clear on your in-app marketplace pages and on your website who a customer should contact when they are having a problem with a particular integration.

This should come from clear agreements with your tech partners on who will be hosting, updating, and supporting the integration.

Don’t make customers chase down emails, or reach out to the wrong person at the wrong company, as that will only cause frustration and delay their ability to fix their problem.

Even if your partner built and is hosting and supporting the integration, your customer support team should be able to advise the customer on where to reach out if needed.

If you have customer reviews or customer forums, ensure that any complaints about integrations are addressed.

Finally, ensure that you have a process in place for updating integrations as products and APIs change. Make sure that whoever built the integration is notified when a product or API is changed and that they address the change in a reasonable time period.

Keep in mind an integration that no longer meets business objectives can be worse than no integration, and can reverse gains in customer retention and satisfaction. Integrations have to be updated as soon as underlying products and APIs change, and someone in your organization and your partner organizations has to be responsible for and able to do this.

To summarize, enabling good customer support for your marketplace and integrations requires:

  • Well-designed marketplace that allows customers to discover, install, and manage their integration on their own
  • Well-designed APIs and integrations that work as intended within the API limits
  • Infrastructure built to scale to dozens of partners and hundreds or thousands of customers
  • Secure data practices and high availability, even at scale
  • Clear customer-facing materials on using the marketplace and individual integrations
  • Clear materials and trainings for your customer support team, including who to reach out to for partner-supported integrations
  • Clear API docs and partner-facing materials on your product, API and integrations you built
  • Tech partner agreements on who will provide support for each integration and their timeframe to respond based on how critical the problem
  • Admin Dashboard providing non-technical customer support team with complete visibility into customer integration usage and errors, and the ability to run syncs and troubleshoot for customers

Checklist

Pre-launch support

By Sunir Shah, President, CSA, and CEO, AppBind

1
Support contact information

Exchange contact information between support teams. Share publicly with customers, and also a direct contact between support teams to escalate issues quickly.

2
Service level agreement

Is there a support service-level agreement? Which support team is responsible for what?

3
Help center article

Include the elevator pitch for the integration and the overall description. Explain how to enable and use the integration. Include the screenshots and the walk-through screencast.

4
Frequently asked questions

Address questions that came up during beta testing.

5
Webinar (internal)

Do a webinar or video call to demo the integration for the support teams.

Chapter 8

Scaling Your Marketplace

Scaling your marketplace involves technical and business aspects.

While scaling might seem far off, putting in place the technical infrastructure to do so can save a large amount of money and resources in the long run. Shifting infrastructure midstream is often significantly more burdensome than establishing the right scaffolding in the beginning.

Technical Scaling

From a technical perspective, one of the advantages of using an iMaaS is that it is built to accommodate a limitless number of integrations and end users. If you construct something in-house or with an iPaaS, ensure it also has this capacity.

Remember that it is manageable to provide hands-on customer service and partner support for every integration and account provisioning when you only have a few integrations and users.

But as you scale, you need to ensure that most of these processes can be automated and that customers and partners can self-serve - otherwise your marketplace will become unwieldy to maintain and provide a poor customer experience.

From a technical standpoint, you will likely want to implement many if not all of these items as you scale:

  • Marketplace search, categories, and flags
  • Marketplace reviews and payment processing
  • Your business users being able to manage marketing materials in the marketplace
  • Customer able to discover, install, manage, and uninstall integrations on their own
  • Permissions for customer accounts (so only some users on an account can install or uninstall integrations)
  • Partner portal for app and marketing materials submission, and partner-facing analytics and usage
  • Availability and performance at scale
  • Customer support Admin Dashboard
  • Alerting
  • Marketing analytics for you and your partners
  • API design that enables more use cases
  • Process for updating integrations
  • Technical requirements for integrations featured in the marketplace and to be labeled as premier/certified
  • Partner sandboxes or free developer accounts
  • An internal tech stack that optimizes results (check out our book “The Partner Tech Stack” to see how to do this and for info on 76 vendors)

Business Scaling

Scaling from the business side requires implementing a more sophisticated tech partner program and better customer and technical support.

For more details on how to scale your tech partner program, read our book, “An Analysis of the Top 50 Tech Partner Programs.”

Part of scaling is implementing tiers of partners so you can allocate your resources more efficiently and provide incentives for partners to invest more in the relationship.

Many in-app marketplaces have premier or certified app partners that must meet higher standards. Customers know they will get a certain level of support and reliability from these premier apps.

Shopify, for example, requires their Shopify Plus Certified Apps to have clear documentation in their listing, positive reviews from customers, exceptional customer support, a customer dashboard for status updates, and high standards for security, privacy and performance.

As your marketplace grows, creating tiers of partners allows you to offer your customers access to a greater number of apps while still giving them important information on what to expect from the experience.

Empowering customers to leave reviews on integrations can also give customers insights into each particular integration and how well it works.

In order to attract more quality tech partners with large audiences, you should incentivize partners to become part of your marketplace.

Having the right technical infrastructure and a large customer base goes a long way to attracting partners, but you can also incentivize partners by offering compensation for referrals or leads and providing co-marketing or co-selling opportunities.

You should also create a partnership community that fosters relationships and provides networking opportunities for all the partners as well as provide partner developers with the technical support they need.

At a high level, in order to scale your marketplace, you will need to implement:

  • Tech partner program tiers with business requirements for each tier - tier progression requires some level of revenue share, co-marketing activity, referrals, and strategic alignment and company size
  • Tech partner program with technical requirements for each tier - tier progressions requires a certain number of integrations or integration adoption, performance and security standards related to the integration, technical understanding of your product
  • Partner fee strategy - charging for ancillary services and/or requiring a program fee
  • Standards for marketplace marketing materials
  • Co-marketing and co-selling opportunities for higher tier partners
  • Technical opportunities, like increased access to the API and product roadmap and more developer accounts, for higher tier partners
  • Monetization strategy for integrations (see monetization options below)
  • Knowledge base for customers and partners, with forums
  • Developer community
  • Marketing materials and program information for partners and partner developers
  • An internal tech stack that optimizes results (check out our book “The Partner Tech Stack” to see how to do this and for info on 76 vendors)

Monetizing Your Marketplace

Model

Integrations free for all customers
Most used by: Smaller or midsize companies that want to grow, like Pipedrive or AWeber
Benefits: Increases usage of integrations
Drawbacks: No additional revenue

Model

Taking a percentage of tech partners’ revenue earned
Most used by: Larger marketplaces with many users, like Shopify and Salesforce
Benefits: Tech partners only pay if integrations are being used
Drawbacks: Partners only willing to pay if many users; partners can resent sharing revenue

Model

Integrations available in higher tier subscriptions
Most used by: Companies that already have tiered pricing, like Yesware, Drift and Evernote
Benefits: Can increase number of higher paid subscriptions, familiar model
Drawbacks: Less usage of integrations

Model

Charging the customer directly to use integrations
Most used by: Companies that want clear ROI, direct revenue, like SurveyMonkey
Benefits: Increases revenue, partners don’t have to pay
Drawbacks: Customers not used to paying directly, discourages usage

Showing ROI

All the calculations you made around costs and business outcomes when you launched your marketplace should continue to be tracked. The integration infrastructure you built should make it easier to track results for yourself and your partners.

Calculating the ongoing costs requires visibility into the developer and customer support resources that go into maintaining and growing your marketplace.

You should track the developer time spent on maintaining and updating the marketplace. In addition, track third-party costs (like your integration platform or any professional services) and the cost of hosting the marketplace if you are doing that yourself.

Finally, include any customer support and professional services hours spent responding to customer issues with their integrations or using the marketplace. If you used an iPaaS, for example, customers might routinely be requesting help or modifications to the integration configurations.

You should also calculate the engineering time spent assisting third party developers on building their integrations. From the partnership side, you should be aware of how much time is going into different partnerships.

Tracking results of your marketplace at scale can be tricky, and some elements are easier to prove than others. Here are the elements you should try to track.

Direct Revenue

If you charge a revenue share from your marketplace and process the payment, it will be easy to identify the direct revenue coming from the marketplace.

However, most integration marketplaces do not process payment for partner apps, even if they are charging a revenue share. This means implementing processes to track leads from your marketplace and sharing that data with your partners so you can collect the revenue share.

If you charge directly for integrations, that is also easy to calculate.

If you have some integrations on a higher plan, you should put an ‘Upgrade’ button in-app for customers looking into that integration to see how many upgrade after looking at the integration. You can also track this behavior through in-app analytics.

If you sell ancillary services to partners, you can calculate that revenue as well.

Influenced Revenue

Your organization might have a multi-attribution model that assigns a particular value to different types of activities that contribute to closing a deal. If it does, you can use that model here too.

Tracking whether integrations and the marketplace influenced deals can involve looking at whether the lead came from a tech partner’s marketing activities or website, or engaged with your public page on their integration or your marketing activities on the integrations.

Tracking leads sent from tech partners is straight forward as long as partners are willing to use identifying codes for any marketing leads sent from outside their websites.

Asking sales and customer success to track if integrations are mentioned as a must have or influencing factor in closing the sale can also help measure their impact.

Referrals

Referrals are direct introductions from tech partners. These are easy to track in a CRM, as is the amount of co-selling the tech partner is doing beyond an initial intro.

Your organization will have to assign a value to these introductions. You might also have to pay the tech partner 10 or 20 percent of the first year contract (or more) when these deals close.

Retention and Upsells

Regardless of how they are monetized, integrations, if they are chosen and designed well, should significantly decrease your customer churn rate and improve product adoption. Attracting new customers costs, on average, 6-7 times more than keeping current ones so reducing customer churn can be hugely profitable to your company’s bottom line.

Most SaaS companies are already tracking their churn rate. Like with any new key product feature, it is not easy to isolate the effect of your integration marketplace on your churn rate, but you can get a solid idea.

From a technical perspective, make sure you can easily track which customers are using which integrations and how frequently. If there is high marketplace and integration adoption rate, it is likely customers are staying in part because of this key feature.

You should also calculate your customer churn rate before and after you launch your marketplace, and compare the churn rate of customers who are using the integrations and marketplace with customers who are not. While these aren’t perfect metrics, they can establish a strong case that integrations are reducing churn.

In addition, customers who are using integrations might use your product more and upgrade and expand their plan. This should also be tracked with a cohort analysis.

You can supplement the numbers with qualitative intel by periodically surveying customers for feedback, including asking them how important integrations are to their continuing to use your product. In addition, look at whether marketplace and integration usage raises self-reported satisfaction with your product and customer experience.

Brand Equity

You can also track positive social and media mentions of the marketplace and integrations, which increase brand awareness and equity.

Conclusion

There are over 11,000 SaaS companies.

Businesses are overwhelmed trying to glue together these ever multiplying building blocks, and are demanding true connectivity from the companies that make them.

An in-app marketplace provides customers with the most seamless experience of integrated data and functionality.

Companies who do not leverage this ecosystem of tech partners will quickly be left behind by those that do.

For those ready to build and launch an in-app marketplace, this playbook can help align your organization behind the initiatives required to make your marketplace a success.

If you have any questions, thoughts, or feedback on this guide, we’d love to hear from you. You can also learn more about us and the iMaaS we’ve built here.