Ebook

How to Track the Business Impact of Tech Partnerships

A practical guide to measuring brand equity, leads, referrals, sales enablement, integration usage and adoption, retention, and monetization across your ecosystem.

Introduction

Integrations are a requirement. Measuring them is not yet a practice.

There's no shortage of numbers showing how much integrations matter. 90% of B2B buyers agree that integration capabilities influence whether a vendor makes their shortlist. Over half say poor integration with their existing stack is a direct trigger to start looking for new vendors. Other studies show integrations are now a top three factor globally in software buying decisions, sitting just behind trust and sales.

Customers are willing to pay more for products with robust integrations and are significantly less likely to churn when integrations are in place. In one recent analysis, buyers with at least five integrations in place were willing to pay around 20% more for the same core product because it's better embedded in their workflows and data flows.

Despite recognizing the importance of integrations, organizations are still struggling with how to assess and track the business impact of integrated tech partnerships.

A hurdle for tech partnerships is that much of their business value is not directly sourced revenue. The easiest business impacts to track are those that are transactional.

While integrations can be directly monetized, either as product add-ons charged to the customer or by charging a revenue share from partners when their product is discovered through a marketplace, direct revenue only accounts for part (and sometimes a small part) of tech partnerships' business value.

Tech partnerships can also significantly impact 1) brand equity 2) sales close rate, time-to-close and ACV, and 3) product-related metrics, like retention, customer satisfaction and LTV.

When done right, tech partnerships will lift every stage of the revenue funnel, from awareness to customer loyalty and retention.

Organizations have long struggled to precisely measure the business value of impacts on the top of the funnel. Brand equity and pre-sales influence is trickier, in general, to measure than direct sales or impacts on retention.

Yet this type of influence is only growing in importance as businesses talk to a sales person later and later in their buying process, and with more of the buyer journey taking place online and increasingly mediated by AI search and LLMs.

Measuring the value of sales enablement can also be challenging. For example, if a tech partner gets on a sales call to explain how to use the product integration between your products, how much business value does that count for? That kind of assistance can certainly impact the speed of the sale and even change the outcome, but it is much tougher to assess what the exact impact was.

Multi-attribution models often define the value of defined marketing activities and sales enablement, but a tech partner may provide a different type of value (such as explaining an integration use case in detail) that doesn't fit in neatly with the existing categories. Or an organization may not even have an existing multi-attribution model that assigns values to different activities in the revenue funnel.

To some degree, tech partnerships has to work within existing revenue models of their organization. And marketing and sales enablement teams may already be using formulas that are useful for measuring tech partnerships' impact on earlier stages of the funnel.

But tech partnership teams can also advocate for creating a formula that recognizes the very real business value to the different types of influence they can exercise over brand equity and the sales funnel.

Measuring the more product-centric metrics, like tech partnerships' impact on retention, LTV, and customer satisfaction is complicated by 1) the disarray around integration usage analytics and 2) the challenge of isolating the impact of usage across a series of moving variables.

The need for product integrations has outpaced the infrastructure practices around integrations, and many companies are relatively mature before they start capturing detailed and organized usage analytics around their customers and integrations.

In the beginning, many organizations will be aware of the number of product integrations they have built and some of their partner-built integrations, but won't be tracking which customer is using which integration.

There will also often be many semi-custom integrations built by CS or professional services and third party integration tools, like Zapier, that do not provide details into customer usage.

Even when integration analytics are best in class, attributing their business impact can be challenging at scale.

Ultimately, many of the business impacts — on retention, LTV, product usage, and customer satisfaction — will be shown through cohort correlations around the number or types of integrations a customer is using.

These correlations do not prove causation but they can still be incredibly powerful evidence of the aggregate impact of tech partnerships on the customer experience.

As Scott Brinker, VP of Platform Ecosystem at HubSpot, put it, “Actually saying it is worth an exact amount is really, really hard. But when there are so many correlated metrics, in the aggregate it is clear the value is there.”

Most organizations, for example, find a significant increase in retention for customers using integrations, especially when the integrations are to business critical systems, like CRMs or ERPs.

By tracking these metrics as well as the impact on brand equity and sales, tech partnership teams can show their value to the organization and justify more investment.

Ultimately, organizations must decide whether to invest more money in partnerships, marketing, sales or another strategy, and having better data on tech partnerships can help guide that decision.

This book covers best practices on tracking the impact of tech partnerships across 1) brand equity 2) marketing leads 3) referrals 4) sales enablement and 5) retention, LTV, and customer satisfaction. It also visualizes data flows and the types of tools required to do this effectively.

“You're going to need to influence and persuade through data relationships in order to move your roadmap ahead and to really ship things that your customers need. And I think doing that is going to require understanding the lingo of the other person and the other company that you're partnering with, understanding what their incentives are and what's really driving them and how they're defining success in their own company.”

Biljana Pecelj, Principal Product Manager, Ledgy

Tracking the ROI of tech partnerships

The Integration Impact Measurement Model

To get the best insights into how tech partnerships are performing, they should be measured on two connected levels:

  • Business outcomes — pipeline, revenue, ACV, retention, expansion and LTV.
  • Integration program performance — adoption, activation, ongoing usage, reliability, support burden and time to value.

Commercial results without performance data are hard to explain; performance data without commercial context is hard to prioritize.

Measurement layer
What it answers
Example metrics
Commercial outcomes
Is the integration or tech partner program creating value?
Partner-influenced pipeline, win rate, sales-cycle length, ACV, retention, expansion, LTV
Customer adoption
Are the right customers discovering, installing, and activating integrations?
Marketplace views, install rate, activation rate, time to first successful sync, active accounts
Integration performance
Is the integration reliably delivering value after installation?
Successful runs, success rate, error rate, failed workflows, latency, connection health
Operational efficiency
Can the program scale profitably?
Support tickets per integration, time to resolution, maintenance effort, integration cost-to-serve
01

Tracking Brand Equity

With businesses doing 60-70 percent of their research before talking to vendors, having a compelling, well-known brand amongst your prospects has a strong business impact.

Tech partners can increase your brand equity in a variety of ways, from featuring you in their marketplace, mentioning you at events, or linking to your content.

Measuring this type of partner influence is very challenging and it cannot be fully captured. There is no way to capture every time your partner casually mentions your product to a prospect.

However, there are some ways to capture this influence and tech partner influence on brand equity can be compared to other types of influence, including other partner types, brand awareness marketing campaigns, customer advocacy, or community-driven influence.

01 · Brand equity

Here are some of the metrics you can track and show on a dashboard (you can utilize multi-attribution formulas if they already exist in your organization):

01Views of your brand in your partners' integration marketplaces
02Mentions on social media or online
03Earned media connected to tech partners
04Tech partner backlinks to your website
05If prospects or customers mention they have heard about you from a tech partner
06Your brand's appearance at partner events, on blogs or websites, in experiential campaigns, or in communities
07The strength of your tech partners' brands

Your marketing department may already be tracking the value of your brand and trying to assess the impact of different campaigns on the brand. You may be able to use much of their tooling and attribution formulas to track the impact of tech partners.

Keep in mind that the influence of tech partners on your brand cannot always be separated from other forms of influence.

The accuracy of brand equity measurements is undermined by the failure to capture many important forms of micro influence, like word-of-mouth referrals or mentions in a private Slack group.

But attributing lifts in brand to particular causes (like tech partners) can also be stymied by the inability to separate out the impact of changes that are occurring at the same time.

For example, your tech partner program may be scaling at the same time your company undergoes a re-brand and starts a customer advocacy program.

The best way to gauge the specific impact of tech partners is to identify their influence wherever possible.

1. Views and Traffic from Your Partners' Integration Marketplaces

A number of your tech partners will have integration marketplaces where your app is featured (whether you built the integration or the partner did).

A partner will usually have a public marketplace listing integrations as well as an in-app marketplace for customers. If your partner has a strong brand, then merely being in the marketplace can add value to your brand as customers create a tie between your company and the partner in their mind.

Being in a company's app marketplace is usually an implied endorsement. The exception to this might be if an app marketplace has thousands of listings of various qualities, including poorly written listings and apps. However, this is rarely the case with integration marketplaces today, as most have some level of vetting and require building an integration to be listed.

You can also track the traffic from all your tech partners' marketplaces. Google Analytics or similar tool can track the traffic coming as well as how long users coming from the marketplaces stay on your site.

If traffic from the marketplaces converts on your site, either for a trial, demo, or product signup, or content download, these may become marketing leads or even closed deals. Most tech stacks should show when a marketing lead or new signup came from a referring website or app.

If you can show that high value accounts are coming from your tech partners' marketplaces and spending significant time on the page, this makes a good case for influence.

For the traffic that does not convert and is not identifiable to the account, you can still use it to show influence. If your partner allows you to, you should create a unique URL link with UTM codes to list in their marketplace so that it is easier to track the traffic for whether it later converts.

If you can't provide a unique link to list in your tech partner's marketplace, then you can assess the value of the referral traffic that does not convert by looking at its bounce rate, number of page views, time on the page, and which pages they visit.

For example, if the traffic is focused on high intent pages, like a demo or pricing page, this traffic is more valuable to the organization.

You can also look at demographic information of the traffic as this may help you to identify whether the traffic aligns with your ideal customer profile.

Framework

Tracking Impact from Referral Traffic from Your Partners' Integration Marketplaces (Public and In-App)

What to track
How to track
Tools to use
Number of views and users
Ask partners for marketplace analytics if not provided by default; if partner won't supply, estimate based on traffic (public) and customer base (in-app) and placement in marketplace
Export in-app analytics from partners' Partner Portals, by API or by request; Ahrefs, Semrush for estimating views on public marketplaces
+
Bounce rate, number of interactions, length on site
Segment referral traffic from partner's marketplaces and use a tool like Google Analytics to see how it performs
Ask partner to use a unique URL or use a link from a tool like PartnerStack; Google Analytics or similar tool
+
How close audience is to ICP
Ask partner for information on their audience (for public marketplace) and customer base (for in-app); account share customer accounts
Obtain from partner or market research; tools like Crossbeam
+
Strength of your partner's brand with your ICP
Ascertain the strength of the partner's brand by their name recognition with your ICP, website authority, social media presence, brand mentions, and survey and review ratings of their product
Market research and customer surveys
=
Boost in brand awareness and equity
Your marketing team may have a specific formula for quantifying this type of influence. If not, make the case for the brand impact and look for ways to connect the influence by tracking mentions over time and prospects who mention discovering you through the tech partner
Multi-attribution formulas and visual BI dashboards

2. Social Mentions, Earned Media, and Other Mentions

Another way to track partner influence is to monitor all the mentions from tech partners on social media, online, and in the media.

Social listening tools like Sprout Social or Brandwatch can make this easier to track programmatically. If you don't have access to such tools, you can use data from social media management tools like Hootsuite, and tools like Google Alerts and Google Trends.

You can also have your partner marketers log mentions of your brand in target online communities or forums and log opportunities to present or mentions at live events that came from partners.

Backlinks from your tech partners' blogs and resources pages can also be tracked. Beyond sending traffic, backlinks from highly ranked, relevant sites increase your brand equity by increasing your website's domain authority and your SEO.

In order to evaluate the impact of these mentions, the authority, distribution, and positivity of the speakers have to be factored in.

On social media, the engagement on a post that mentions your brand, for example, is one indicator of its impact. How much your target audience respects or likes the brand mentioning you is another indicator.

To further see if a particular mention on social or opportunity (like a speaking opportunity) had an impact, check to see if it appeared to cause a spike in followers on social media or people searching your brand on Google.

Mentions of your brand on credible partner sites can also contribute to visibility in AI-assisted search experiences. Teams that are measuring brand presence in these channels can track which sources are cited in relevant category and brand queries, then compare those findings with partner mentions, backlinks, referral traffic, and branded-search trends.

Framework

Tracking Impact from Partner Social Media, Earned Media and Other Mentions

What to track
How to track
Tools to use
Partners mentioning your brand online
Social listening tools; or social media management tools for social and Google Alerts for other media; backlinks from blogs and resources pages; partner marketers logging mentions in closed communities
Tools like Sprout Social or Brandwatch for social listening, and tools like Hootsuite for social media management; Ahrefs for backlinks; Promptwatch or Profound for LLM citations
+
Partners mentioning or giving you opportunities at live events
Tracking the opportunities or mentions
Manually logging the event mentions
+
Partners mentioning you in the media
Media listening tools; or Google Alerts
Tools like Brandwatch, Meltwater, BuzzSumo or Google Alerts for press mentions
+
Strength of your partner's brand with your ICP
Ascertain the strength of the partner's brand and their reach on social or online with your ICP
Market research and customer surveys using tools like Wynter or Centiment; number of followers on social and engagement level from your ICP
=
Boost in brand awareness and equity
Your marketing team may have a specific formula for quantifying this type of influence. If not, look for spikes in searches for your brand, new engagement and followers on social, and increased brand awareness in customer surveys or among prospects
Google Search Console, social media management, and surveys of prospects; marketing may have relevant dashboards

3. Partner Brand Influence on Sales

Depending on your product, you may have a form or practice of asking prospects where they heard of your brand. If this is already in place, then you can use this data to determine how often partners are being mentioned as the original source of discovery.

More subtly, a prospect may mention a partner had said good things about your brand or mentioned your brand, even if the partner wasn't the original source of discovery. This indicates a positive brand influence from a partner.

If you use a sales conversational intelligence tool that records and transcribes conversations, like Gong or Fathom, it is easier to programmatically track when partners were mentioned as an influence.

Asking your sales team to log the influence or origin in the CRM may be better than having no data but it's often not very reliable as the sales team may have no motivation to record this relatively casual mention.

For current customers, it is possible to rely on customer surveys and conversations to assess whether partners mentioned your brand. However, customer surveys usually don't cover this question and in most organizations, one won't be able to get direct information on what customers have been specifically hearing from partners.

If you share account data with your partners, knowing how many customers are in a particular partner's audience can help you estimate exposure to any partner brand mentions and awareness campaigns.

Framework

Partner Brand Influence in Sales

What to track
How to track
Tools to use
Prospects and customers mentioning that a partner endorsed your brand
Analyzing transcriptions of sales calls for partner mentions. If not possible, ask account executives to log in the CRM. Customer mentions in surveys or by CS
Conversational intelligence tools like Gong; CRMs
+
How positive the endorsement was
Assess based on the transcript or survey
Conversational intelligence tools like Gong
+
Strength of the partner's brand with your ICP
Conduct customer overlap analysis
Market research and customer surveys; online reviews
=
Boost in brand in the sales process
If you have enough data, you can ascertain if deals that mentioned a partner endorsement close higher or faster. Aggregate the number of mentions over time and assess the brand boost
Conversational intelligence tools like Gong and BI tools
02

Marketing Leads

Tech partners can be a great source for marketing leads, which will often be entered into your CRM and marketing automation tools for your marketing or sales team to follow up on.

Here are the main ways you can get marketing leads from tech partners:

01Leads who come from partner links (including links in their app marketplaces) who do not purchase your product but engage with your content or events
02Some SaaS companies will send leads who interacted with your tile page on their app marketplace but did not purchase your app
03Leads who come from co-marketing campaigns and partner data sharing

02 · Marketing leads

1. Marketing Leads from Partner Links

Your tech partners will usually list your integration in their public and in-app marketplaces. Both these tiles will have links to your website, and if you have an affiliate agreement with tech partners, they will be affiliate links.

If you aren't using affiliate links, ask your tech partners to create unique links for their marketplaces so you can more easily track the conversions as a category (tech partners). This is as simple as adding UTM codes to the link.

If your partners do not use unique links, then you can use Google Analytics or similar tool to track when traffic from your partner's marketplace downloaded an asset on your website. Your CRM or marketing automation tool might also track this information.

If you're not engaging in formal co-marketing activities with your tech partners, you should still ask them to use a unique link whenever they link to your website, whether it is from their website, on social or in a private community, as part of onboarding the partner.

If partners do not use a unique link, you can still track the traffic they are sending from their website, but not from social or private communities.

When these leads download a piece of content or sign up for an event, they will often end up being partner sourced pipeline. In this case, this may be the “first touch” they had with your organization, which will depend in value predicated on how your organization weights that touch and, usually, how long and how many steps it took for them to convert to being a customer.

But some of the leads may already have been in your sales funnel, either as a marketing qualified lead or engaged in active sales discussions. In those cases, these new interactions would qualify as partner influence, whose value will be assessed by whatever multi-attribution model your organization uses.

Framework

Tracking Tech Partner Marketing Leads from Marketplaces and Other Links

What to track
How to track
Tools to use
Leads that came from partners' in-app and public integration marketplaces
Ask your partner to use a unique link for your site in their marketplaces, either an affiliate link or a link with UTM codes. Track with Google Analytics and/or your CRM and/or marketing automation
Google Analytics, UTM codes, affiliate links and software like PartnerStack; CRM or marketing automation
+
Leads that came from your partner posting a link to your site
Ask your partner to use a unique link for your site when they post it or share, either an affiliate link or a link with UTM codes. Track with Google Analytics and/or your CRM and/or marketing automation
Google Analytics, UTM codes, affiliate links and software like PartnerStack; CRM or marketing automation
+
Conversion rate on these leads and time to conversion
Track the leads through your entire sales funnel to determine how many convert to deals and how quickly
CRM, and any databases and visualization software your organization uses to analyze the revenue funnel; BI
=
Partner sourced and partner influenced revenue
Net new leads will likely be partner sourced; those that are already MQLs or in sales discussions will be partner influenced. Utilize your organization's existing dashboards for funnel tracking
CRM, and any databases and visualization software your organization uses to analyze the revenue funnel; BI

2. Marketing Leads who Interacted with Your Tile in an In-App Marketplace

Some large marketplaces, like the Salesforce AppExchange, will send leads who interacted with your tile page but did not purchase your app.

These leads are similar to leads that clicked to your website from the marketplace but some of them will be higher intent as they have tried to install the integration or watched a demo video (which the marketplace can tell you). You should enter these leads into your CRM as partner sourced (if they are net new) or partner influenced if you are already engaging them.

If you have your systems integrated with your partner's PRM or partner portal, these leads may be able to be automatically entered and tagged into your CRM or PRM. However, in some cases, you will have to export them and upload them into your own systems and tag the uploads as being partner sourced or partner influenced.

These leads should be followed up with by your marketing or sales teams, and tracked for conversion and time to conversion.

3. Marketing Leads from Co-Marketing Campaigns

Co-marketing with tech partners can include partner data sharing and actively running marketing campaigns together, which can run the gamut of marketing activities companies engage in, from social posts to events and product demos.

These campaigns can be run a variety of ways, each with their own tracking processes. The closer a partner is to a strategic partner, the more integrated your systems can be with partners and the more data you can share.

Here are different relationships you may have with tech partners and co-marketing campaigns that generate leads:

01One-off campaigns that may be run jointly or unilaterally — put UTM codes on URLs to track referral traffic that converts to marketing leads; for leads generated from live or virtual events, manually tag the source as the partner
02Ongoing marketing campaigns — you can use a PRM (like Channelscaler, Workspan or Impartner) or through-channel marketing automation software to run these campaigns together and share results; affiliate software like PartnerStack should also be used
03Ongoing partner data sharing — you can use a tool like Crossbeam to share data with partners, and integrate these tools with your CRM, databases, or marketing automation tools to track the impact of this sharing; it may be through data enrichment or having access to highly targeted lists that you run marketing campaigns to, either with your partner or separately

Framework

Tracking Tech Partner Marketing Leads from Ongoing Campaigns

What to track
How to track
Tools to use
Leads that came from partner campaigns or joint marketing campaigns
Use a PRM, through-channel marketing automation and/or affiliate software to collaborate on campaigns and share results. Leads from in-person events may need to be uploaded and tagged. Smaller programs may collaborate by manually sharing marketing assets and results of campaigns
PRM like Channelscaler or Impartner, through-channel automation software like Ansira Edge, affiliate/PRM software like PartnerStack
+
Conversion rate on these leads and time to conversion
Track the generated leads through your entire sales funnel to determine how many convert to deals and how quickly they convert
CRM, and any databases and visualization software your organization uses to analyze the revenue funnel
+
Cost of campaigns
Track the budget on these campaigns
Some PRMs or channel marketing automation software include MDF management, which can track budget received or given to partners
=
Partner sourced and partner influenced revenue
Net new leads will be partner sourced; those that are already MQLs or in sales discussions will be partner influenced. Utilize your organization's existing dashboards for funnel tracking
CRM, and any databases and visualization software your organization uses to analyze the revenue funnel

Framework

Tracking Tech Partner Marketing Leads from Partner Data Sharing

What to track
How to track
Tools to use
Leads that were enriched with partner provided data
Use a partner data sharing tool like Crossbeam. Smaller programs may collaborate by manually sharing data through spreadsheets that are uploaded to a CRM and marketing automation software
Data sharing tools like Crossbeam
+
Leads that were new and provided by partners
Track which are enriching existing accounts with new information and which are new prospect lists
Data sharing tools like Crossbeam
+
Conversion rate on these leads and time to conversion
Track whether these leads convert better than other data sources
CRM, and any databases and visualization software your organization uses to analyze the revenue funnel
+
Cost of other data enrichment and prospect lists
Data enrichment and prospect lists can replace other data sources
CRM, and any databases and visualization software your organization uses to analyze the revenue funnel
=
Value of lead lists and data enrichment
Utilize your organization's existing dashboards for funnel tracking to analyze whether these prospects are more qualified and convert better — this difference combined with the cost of other data sources can provide the business value
CRM, and any databases and visualization software your organization uses to analyze the revenue funnel
03

Referrals

Referrals from tech partners can be direct introductions from a tech partner or they can arrive from an integration marketplace or website when a prospect requests a demo or signs up for or purchases an account in a short timeframe.

Referrals have to be qualified but they are higher intent than marketing leads.

Especially in the case of direct partner introductions, referrals have a stronger propensity to close due to the partner recommendation. They also are likely to have a higher lifetime value.

Tracking direct introductions can be done through a tool like Crossbeam or some PRMs that enable deal registration; they can also be logged manually in a CRM (and may have to be if they are in-person, direct messaging via social media, or via a private community).

Prospects may come to your website from a partner's integration marketplace or other link and request a demo or sign up for an account — the difference between these accounts and marketing leads is marketing leads require additional outreach to start a sales conversation or purchase, while these leads are immediately entered into the sales process (or, if possible, immediately purchase).

03 · Referrals

1. Tracking Direct Referrals

You should be tracking whenever a partner directly recommends your product to a prospect and they then take a demo or purchase the product.

Tools like Crossbeam can not only increase the number of referrals by highlighting when a partner has customers who are good prospects, they can also create a record of this referral that enables it to be more easily tracked.

Most organizations will integrate these tools with their CRM, where records can be automatically appended to reflect the deal was partner sourced if the intro is made via email through the tool.

This is a much more accurate way than relying on people to manually log it in the CRM. However, if you are relying on manual logging, you should ensure whoever is logging has an incentive to do so.

In-person intros and intros via private communities or direct message on social media will usually have to be logged manually regardless, so cultivating an expectation and culture of tracking is important. Aligning sales and partner financial incentives can also help ensure the info is logged.

Partner managers may be more motivated than sales to log intros; though they may not have the necessary access to log the information depending on how your CRM is set up to log partner sourced deals and partner influence. They also may not be involved in every intro, depending on whether your partners interact directly with your sales team.

In addition to introductions that are made directly via email, in-person or via DM, partners may often recommend your product to their customers and prospects without notifying you.

With tech partners, these referrals may often be made from customer support or customer success as the integration may improve their customers' experience of their own product. Customer support teams will usually be even farther away from account mapping tools and the CRM.

In those cases, tracking the source is dependent on sales (or marketing via a demo request form) asking the prospect where they heard about the product.

If your organization asks this question generally and logs it in the CRM, it simply requires a process that systemizes partner data or that someone is reviewing and organizing this data.

Depending on how many partners you have, it may not always be easy for the sales person to log it specifically as “partner” sourced. They may not know all your partners so may just log the partner name. This might be resolved by a drop down field listing all partners or organizing the data after the fact.

Once you have logged the deals that were referred by partners, you will want to track their conversion rate, time to close, average contract value, and lifetime value as a customer.

Framework

Tracking Direct Referrals from Tech Partners

What to track
How to track
Tools to use
Direct intros to accounts from partners via email, phone, in-person or DM
Use a data sharing tool integrated with your CRM or a PRM integrated with your CRM to log written intros or partner-registered intros. Referrals from private communities, in-person events or via social DM may need to be tagged manually in the CRM. Smaller programs may manually tag all intros in the CRM
Partner data sharing tools like Crossbeam, PRM like Channelscaler or Impartner, CRM
+
Partners recommending your product without your knowledge, leading to a sales conversation
Ask prospects where they heard about the product, either in sales or via a request-a-demo form. Systematically analyze the information to tag as partner sourced
CRM and marketing or sales forms
+
Conversion rate on these leads and time to conversion; ACV and LTV of customer
Track the generated leads through your entire sales funnel to determine how many convert to deals and how quickly they convert
CRM, and any databases and visualization software your organization uses to analyze the revenue funnel
=
Partner sourced revenue
Net new leads will be partner sourced; those that are already in sales discussions may be partner influenced. Utilize your organization's existing dashboards for funnel tracking
CRM, and any databases and visualization software your organization uses to analyze the revenue funnel

2. Marketplace and Online Referrals

Referrals that come from partners' integration marketplaces and request a demo or sign up for an account in a short timeframe are notable because, other things being equal, they have a lower customer acquisition cost than marketing leads that need to be nurtured and followed up on.

This number is worth tracking separately from marketing leads but the process and technology for tracking it will be the same. Ask partners to use a unique link in their marketplace and other online mentions, preferably one for their marketplaces and one for other online mentions.

Track how many demo requests or account sign ups come from partners' links or sites and then track their progress in the sales funnel, their conversion rate, time to conversion, ACV and LTV. Tracking this by partner can help you decide which partners to invest more resources in.

Keep in mind as you scale this requires keeping a list of partners and their URLs and then tracking that as the source in a Google Analytics-like tool and/or your CRM. It may also involve marketing automation that powers the “request a demo” form on your site, for example.

Affiliate links can be centrally managed from a PRM like PartnerStack, but if you are not paying a rev share to partners, it likely does not make sense to use a specialized tool and partners may not use the specialized link without a financial motive to do so.

Alternatively, you may have a PRM or partner portal that provides unique links to partners, but without a rev share, you may have to track the provided link as well as traffic coming from their URL, as not all partners may use a provided link.

Between Product and Partnerships

Podcast · Interview

Beyond handshakes: structuring partner programs for success

Why a partnership is a connection of people — not a connection of APIs.

Martin Scholz

Partnerships Advisor, CEG Consult

Hosted by Cristina Flaschen

Interview · Martin Scholz, CEG Consult

Sales is transactional. Partnerships are collaborative.

Martin Scholz has spent more than 20 years in B2B partnerships, building partner programs for startups before becoming an advisor at CEG Consult. He now helps B2B SaaS companies make partnerships work. We talked about what actually makes a partnership valuable, why the biggest customer is rarely the right first integration, and the failure patterns he sees again and again.

How do you define a genuinely valuable partnership?

One of the challenges in our field is that we have no standing definition of what a partnership is. You've probably had someone say “let's do a partnership” when they actually wanted to sell you something. Sponsorships get called partnerships even though they're pretty transactional.

The common denominator is that two businesses team up to achieve a mutual goal that both benefit from — and very often there's a mutual customer in the middle. That's critical. Sales is transactional; partnerships are collaborative. That changes the dynamics, and a lot of people don't get it — they treat it as “you give me this, I give you that,” and that's usually not how it works.

A truly valuable partnership, for me, is alignment on a mutual goal where both parties win. I don't love saying it, but it's literally the cheesy one-plus-one-equals-three thing.

How should a company identify the right shared customer to build around?

The instinct is to reach for the one huge customer, but that's usually a big corporate — not flexible, responsive or agile, which are exactly the things you want for a product integration. And they often come with very specific, very custom requirements.

You might build something that perfectly fits that one elephant but isn't repeatable or scalable for anyone else. I'd look instead at your ICP and the common use cases customers share — and that massive key account often isn't actually your ICP.

What's the difference between a technical integration partner and a strategic one?

I'll quote my friend Justin Zimmerman: integrations are not partnerships. An integration is a connection of APIs; a partnership is a connection of people. That nails it. I can have a wonderful technical integration with a huge company — Google's API, HubSpot, the AWS marketplace — and that doesn't make me a partner.

You pull a number and you're startup 1,715 in line to connect to the API. That doesn't mean anyone there cares what you're doing. The partnership layer is when you manage to have a real business-driven conversation — how to market that integration and the value you create together.

I visited a client with a marketplace of 200-some integrations, all critical to their core product. They were focused only on technical quality. I asked, why don't you have a meaningful business conversation with these partners about the value you create for each other?

As for “strategic” — I dislike the term because it's overused. I reserve it as a quality bar: a partnership so critical to your success that you see it in your P&L, in the top or bottom line. Whether the other partner is large or small doesn't matter; it's the size of the impact. What a lot of startups call strategic is partnering with a big gun — it may be strategic for you, but you're most likely not strategic for them. That's a very unbalanced partnership.

“An integration is a connection of APIs. A partnership is a connection of people.”

Justin Zimmerman, quoted by Martin Scholz

On the danger of betting everything on one big strategic partner?

It's a bet. Put everything on one number in roulette and you may win or lose it all; distribute it and you have more chances to succeed. It's nice to have a relationship with a partner manager, but that person usually doesn't execute the partnership — they own the relationship.

For a technical integration you need the product team. To promote it you need marketing, sales or CS. If you hope the integration generates leads one day, the partner manager won't give you those — they're not customer-facing. That's where the whole thing very often dies.

How do you get into all those teams at a large partner?

It depends on the size of your company and your role, but I always pushed my teams on QBRs. A quarterly business review isn't you and your partner manager — that's the weeklies. The QBR needs the strategic-alignment component.

Bring your plus-one, maybe your founder or a C-level, especially as a smaller startup, to get attention on the other side. And require the same back — not just the partner manager but their boss, as high up as you can responsibly ask.

For me a QBR is maybe 15–20% reviewing the past and 80% about the next three, six, nine, twelve months. It should always open with: are we still strategically aligned? If the partnership isn't paying into their business goals, they won't prioritize it — no amount of wine and dine changes that.

Which team is the best way in — and how do you earn their time?

Don't try to connect with the other company's salespeople first. They have a narrow focus and anything you ask is a distraction, so they're less responsive early on. Point yourself at the CS team instead. They have a deeper relationship with customers, hear the pains and wishes regularly, and are far better positioned to mention your integration — no sales rep will bring it up unless it helps them close.

Where I'd push back is on “give to get.” I used that phrase for years, then thought: wait, if it's a collaborative relationship, both sides should be equally committed. It should be like two people in a restaurant both reaching for the bill.

Companies convince themselves they must give first and expect nothing, and they end up giving and giving until it's 80–20. If you give 80% to get 20% back, that's a toxic relationship — and you walk away from toxic relationships. A partnership leader once told me: 51–49 is enough. If it's 80–20, walk.

So what counts as a healthy give?

A give with real reciprocity built in — offering to write a blog post where you get their audience in return, for instance. What's toxic is constant chasing, flights and meetings with no skin in the game coming back. There's a natural power dynamic in almost every partnership: someone has the bigger customer base or the data. It's easy to become the 80% without noticing.

When two large companies partner, who builds and pays for the integration?

When neither is the clear bigger fish, both agree it would be great to have — and then nobody moves. In the early days it was a question of who had an API, and the other developed against it. As service-based architectures became standard, everyone had one, so that tiebreaker disappeared.

What resolved it was pragmatism. One develops, the other pays 50% of the non-recurring engineering cost — you split the bill, because it's usually a resource constraint, not a lack of will.

More than once we did this: if neither side had the capacity on the roadmap, we each put in 5K, hired an external developer to build it, and shared the IP. It wasn't that nobody wanted it — it was literally resource constraints on both ends.

Is that a technical problem or a relationship problem?

It's rarely technical — the APIs exist these days, and building the integration is such a small part of the bigger exercise. The real question is what you both want to do as a long-term partner.

And there are many ways to share the load beyond splitting the build: one company builds while the other takes a higher revenue share, for example. Once those connections are made — especially in enterprise, where customers stay five-plus years — you're genuinely in bed with that other company, so it pays to be a good partner while still doing the dance.

What are the most common failure patterns you see in partner programs?

Across both technology partnerships and core channel, the same thing recurs: the order to start partnerships comes from one small part of the leadership team and isn't aligned with the others. You end up working in a silo, and partnerships always touch every team sooner or later.

Even when it comes from broader leadership, the “why are we doing this” is often totally unclear. I met startups who'd integrated with Salesforce or Adobe with no use case — because an investor wanted a logo on a slide. Investors are smart in some areas, but too often they don't bother to understand the product; they see the integration everyone else built and ask why you don't have it too. Building into a company like Salesforce blind is enormous work — rigorous approval, multi-threaded — for no value if there's no need behind it.

And the vanity-metric trap on the marketplace side?

A senior director bragged to me about 1,650 apps in their marketplace. I asked how many are active — actually used. It was a vanity number. It looked good in marketing, but I'd guess 1,400 of those companies wasted their time, effort and hopes, many expecting business that never came.

Often the marketplace owner doesn't even know which are used — ecosystems built ten years ago never instrumented installs, so it takes real database work to answer. It comes back to measuring partnerships on sheer number of integrations instead of whether they're meaningful and used.

Any advice for partner managers heading into the age of AI and MCP?

Double down on the fact that partnerships keep becoming more relevant. There's a huge hype on the tech side about MCP and agentic tooling, and I think people underestimate the maintenance it requires. “I vibe-coded my own thing and connected it” is fine when you're a solopreneur doing it for yourself. Assume a midsize company will rebuild and then run and maintain all of it with limited resources? That doesn't hold.

So don't panic that MCP will kill your job. It's a way for software companies to develop more efficiently — not a world where everyone builds their own solutions. The hype is already dying in places: AI-driven outreach is fading because nobody wants hyper-personalized spam. Anthropic is hiring SDRs and SDR leaders — the AI company apparently doesn't trust AI to replace those jobs.

We've seen this movie before, migrating everyone from homegrown custom software to SaaS. There's a reason the industry moved away from bespoke builds; now the cycle is circling back. It took 20 years — it'll be interesting to keep watching.

Three takeaways

1

Partner to your ICP, not your biggest logo. Build around the shared, repeatable use case — the elephant's custom needs rarely scale.

2

Keep the balance honest. 51–49 is enough; 80–20 is toxic. Reciprocity, not endless giving, sustains a partnership.

3

Measure what's used, not what's listed. A marketplace count is a vanity metric — track active integrations and real business impact.

04

Sales Enablement

Sales enablement is a form of partner influence. With tech partners, it is often product focused, and can span from providing a one sheet on an integration to actively co-selling together.

Organizations often struggle to assign a business value to this type of influence but it can have a significant business impact and increase the close rate, contract size, and speed the time to close.

Even if your organization does not assign a specific value to different types of influence, you should make sure it is being tracked. If you get enough data, you can make the case that certain types of partner influence lead to better outcomes.

Here are the main types of sales enablement you should be tracking:

01Partner introduces you to a key decision maker on an account you are already selling to
04Partner provides sales enablement materials, like one sheets, videos or FAQs on the integration to your product
02Partner gives you data or information about an account that helps you close the deal
05Partner joins a sales call to explain how to use the integration and why it would benefit the account
03Partner recommends or endorses you to an account you are already selling to
06Partner is actively co-selling with you and both your sales teams are trying to persuade an account to buy both of your tools at the same time

04 · Sales enablement

Processes to Track Partner Enablement on Sales

Regardless of the type of partner influence on the sales process, it will likely need to be tracked in a similar way. When evaluating a PRM or partner data sharing tool it is important to look at not only how it improves collaboration and workflows, but how it enables you to track results.

For tracking, you should evaluate what the tool itself reports, how robust its integration is with your CRM, and how robust its external API is.

Tracking partner influence will be easier if the type of influence (whether it was an intro to a key decision maker, actionable intel, or joining a demo) was logged in a PRM or partner data sharing tool that is integrated with your CRM.

It can also be integrated directly with a BI tool or database for tracking purposes. However, a CRM integration has the added benefit of integrating with where sales is usually tracking and visualizing their own goals. Being present there reinforces the value of partnerships.

Some tools keep track of the partner sourced and influenced revenue inside the PRM or partner data sharing tool. This data can capture the revenue driven and influenced from partners using that tool or portal.

This data can be utilized but will likely have to be merged with other data as it is unlikely all your partners will be using one particular partner data sharing tool or portal/PRM.

Many organizations use their CRM to report on their revenue funnel so beyond the importance of account executives seeing the impact of partnerships on their accounts, it usually makes sense to have partner influence logged in your CRM, even if it is also logged elsewhere (for example, in a partner portal where you and your partners can both see it).

It is best to have a process and tech stack that ensures the Opportunities (Salesforce) or Deals (HubSpot) in your CRM are tagged with partner influence, and preferably the particular type of influence.

The best way to do this will often be to create a custom object for Partner accounts. This custom object can identify each partner and include information on it, like contacts, names, and company information fields. It can then be associated with particular deals.

Salesforce has built-in functionality for managing partner relationships, but the basic capabilities are relatively limited. Its Experience Cloud, which includes partner accounts and portal functionality, offers more robust partner management, though it has traditionally been geared toward channel partnerships. Salesforce has expanded its capabilities with Partner Cloud, making it more viable for technology partnerships, but it may still be more infrastructure than you need if your primary focus is managing tech partners.

In addition to associating a particular partner account with opportunities/deals, you can also put a custom field on the Opportunity/Deal that specifies the type of partner influence that occurred. (And if you have no Partner account object, a custom field that identifies which partner exercised the influence.)

This should be set up so that an Opportunity/Deal can have more than one Partner associated with it, and more than one type of partner influence, even per partner account.

Once you set this up, you need to ensure that the information is actually logged. A partner manager may be able to associate Partners with Opportunities/Deals if they are involved in the process. For example, if they are using a partner data sharing tool and they are the ones requesting intros to key decision makers from partners, as long as they have the permissions, they can log this in the CRM.

From there, depending on your CRM, you may be able to require an account executive to fill out the partner influence field to move it to closed (whether won or lost).

Partners and their sales teams may have a direct line of communication to your sales team, in which case the influence and association has to be logged programmatically or by the sales team.

Out-of-the-box integrations to PRMs and partner account sharing software may enable the Opportunity/Deal record to automatically show the email intro or a request that was made via Slack.

This type of record does not fill out a custom field but it does enable a partner manager to see when influence was exerted and then manually ensure that its influence was logged. However, if partner managers are responsible for dozens or more partners, checking this manually can become time consuming.

Account executives should be asked to log this influence, and note when prospects mention partners exercised influence or served as a reference. Some organizations incentivize this logging by rewarding AEs for working with partners.

As the deal unfolds, partners may actively co-sell by jumping on calls, giving demos, or following up on prospects to move them down the funnel. This type of influence can be impactful, and should be logged as well.

As an organization, you have to come to an opinion on how much these different types of influence are worth, but the first step is logging the influence.

Then, you can start to get data and try to run analyses to find strong correlations and impacts. For example, partner co-selling may speed the time to close, enable the AE to close more deals per quarter, increase the average contract size, and increase the conversion rate.

Framework

Tracking Partner Enablement in Sales

What to track
How to track
Tools to use
Intros to key decision makers in active deal
Requests may be made in a partner data sharing tool or PRM; integrating these tools with your CRM to append the record; alternatively, logging in the CRM
Tools like Crossbeam; PRMs like Channelscaler or Workspan; CRMs
+
Critical data relevant to the sale
Tracking in a data sharing tool and/or CRM
Data sharing tool and/or CRM
+
Endorsement to account in active deal
Logging in the CRM
CRMs
+
Sales enablement materials
Tracking in a PRM, channel marketing tool, deal room software and/or CRM
PRMs, through-channel marketing automation, deal room software, CRMs
+
Engaging in co-selling activities, like calls and emails
Logging this in a CRM, on a Partner object and the Deal/Opportunity
CRM
=
Partner influence on sales
Your organization may have a specific formula for quantifying this type of influence. If not, look for the impact on close rate, time to close, average contract size, and AEs' ability to close more deals
Databases, analytics and visualization software, CRM and partner technology
05

Retention and LTV

Technology partnerships are based on a product integration that can significantly improve the product experience, as well as reduce churn by integrating an app more deeply into customers' workflows.

Tracking this requires tracking which integrations customers have installed and how often they are using them.

Best practice is to track customers in cohorts based on timing and important characteristics like size and industry, and comparing their retention rates and other key metrics by cohorts of how many and what types of integrations they have installed.

You should also track customer satisfaction and uninstall rates around integrations. Bad integrations can decrease retention so identifying if some integrations are poorly designed can help to disentangle whether other integrations are having a positive impact.

Integration installation data should be compared to:

1. Retention rate2. Customer satisfaction rates3. Product adoption4. Average contract size5. Lifetime value of customers

05 · Retention and LTV

Tracking Integration Installs and Usage

The first step to showing the significant influence tech partnerships can have on retention and lifetime customer value is to put the infrastructure in place to know which integrations your customers are using and how they are using them.

This requires authentication protocols for your API that track who the end user is as opposed to just showing who the partner app is. If you and your partner are using OAuth 2 protocol, then the logs should show the end users (however they are identified in the system).

Companies that do not follow OAuth may have other authentication protocols that do not reveal who the end user is, but may only identify the partner app's unique keys. This can give you a sense of how much an integration is used, but not by who or how many different customers.

In some cases, you will be reliant on your partner to get usage data; if, for example, you build an app that uses their unique components and framework and doesn't follow the usual OAuth protocol, you may need to get usage information from your partner.

Utilizing a centralized dashboard where you can see integration usage by integration and by customer is key to tracking.

Tools like Pandium can help you track integration usage, adoption, engagement and activity across your integration ecosystem. They also allow you to share partner-specific views with tech partners so that you're all working from the same data set.

Tracking Customer Retention and Satisfaction

This is likely data your organization is already collecting. The additional factor is implementing a clean process for comparing product analytics around integration usage per customer with the retention, LTV and satisfaction data per customer.

That means implementing an effective way to accurately identify customer users of integrations and compare it with their customer account data. Most likely, your organization has already done this for product usage analytics; partner-built integrations may make this somewhat more complicated, depending on their and your technical setup.

Centralizing your integration infrastructure, whether building in-house or through a tool like Pandium, helps to ensure that integration usage analytics are able to be cleanly aligned with revenue analytics around retention, LTV, and customer satisfaction.

Framework

Tracking Partner Impact on Retention and LTV

What to track
How to track
Tools to use
Integration usage by customer
Product analytics and partner provided data
Tools like Pandium and product analytics tools
+
Integration customer satisfaction
Reviews; partner reported data; customer support tickets; churn rates off the integration; customer surveys
Marketplace, customer support software, product analytics
+
Customer retention rates
Revenue analytics
CRM, BI tools
+
Customer satisfaction
Customer surveys; product analytics around product usage
Survey software, product analytics
+
Customer LTV
Revenue analytics
CRM, BI tools
=
Partner impact on retention and LTV
Correlate integration usage analytics in customer cohorts who have similar key properties (like start date, size and business vertical) with retention, satisfaction, LTV, and product usage
Databases, analytics and visualization software
06

Measuring Integration Program Performance

Tracking the business impact of technology partnerships requires measuring more than partner-sourced pipeline, influenced revenue, or the number of integrations you have launched. These commercial measures are important, but they do not show whether customers are actually getting value from the integrations after they are built.

An integration can look successful on paper because it has been launched, promoted in a marketplace, or installed by a number of customers. But if customers are unable to connect it, do not complete a first successful workflow, encounter frequent errors, or stop using it shortly after installation, the integration is unlikely to deliver its full value to the customer or the business.

This is why organizations should pair traditional commercial measures with integration program performance metrics. Commercial metrics show whether integrations are associated with stronger revenue, retention, expansion, and customer lifetime value. Integration performance metrics show what is happening within the integration program itself: which integrations customers are adopting, whether they are activating successfully, how reliably they are operating, and where customers may be experiencing friction.

06 · Measuring integration program performance

Tracking Integration Adoption and Activation

The number of integrations you have launched is not the same as the number of integrations your customers are using. Similarly, an installed integration is not necessarily an integration that is delivering value.

For tracking purposes, organizations should distinguish between the following stages:

Stage
Definition
Discovered
A customer has viewed or interacted with an integration in your marketplace, on your website, or in another product surface
Installed
A customer has selected, added, or authorized an integration
Activated
The integration has completed its first meaningful successful action
Active
The integration continues to perform successful actions over a defined period
Healthy
The integration is operating reliably, without unresolved connection issues or repeated failures

This distinction is important because raw installation counts can overstate the value of an integration program. A customer may install an integration with the intent to use it, but then abandon the setup process due to a difficult authentication flow, an unclear configuration experience, missing permissions, or an error in the integration itself.

The most useful adoption and activation metrics include:

01The number of customer accounts that have installed each integration
02Install rate by integration, partner, customer segment, industry, plan, or account tier
03The percentage of installed integrations that achieve a first successful action
04Median time from installation to first successful action
05The percentage of activated integrations that remain active after 30, 60, or 90 days
06The number of customers who use one integration versus multiple integrations
07Adoption of business-critical integrations, such as CRM, ERP, communications, or data-warehouse integrations

Tracking activation is particularly important because it represents the point at which an integration moves from a customer intention to an actual product outcome. If an integration has strong marketplace interest and a high install rate but a weak activation rate, the problem may not be demand. It may be friction in the customer experience, documentation, onboarding, authentication, configuration, or integration design.

Organizations should track these stages in a centralized platform or dashboard, rather than relying only on API logs or individual partner portals. Pandium can provide visibility into integration installs and activity, which helps SaaS companies identify where customers are succeeding and where they are dropping off. That visibility is useful both for improving the integration experience and for demonstrating the impact of integrations on adoption, retention, and expansion.

Tracking Ongoing Usage and Customer Value

After an integration has been installed and activated, the next question is whether it is becoming part of the customer's regular workflow. The strongest indication that an integration is creating value is not that it has been installed once, but that it is being used successfully over time. Ongoing activity can indicate that the integration is helping the customer move data, automate a business process, reduce manual work, or connect your product more deeply to the rest of their technology stack.

Here are some of the metrics organizations can track:

01Number of active customer accounts using an integration
02Number of successful integration actions, workflows, or data syncs
03Frequency of successful activity by account
04Active usage by customer cohort, industry, plan, or account size
05Repeat-use rate after activation
06Integration usage among strategic or high-value customer accounts
07Number and type of integrations used by retained, expanded, or churned customers
08Use of integrations that connect to business-critical systems

This data becomes more meaningful when it is compared with broader customer metrics. For example, organizations can compare customers who have never installed an integration with customers who have installed but never activated one, customers with an active and healthy integration, and customers whose integrations are generating repeated errors.

The goal is not to claim that an integration directly caused a customer to renew, upgrade, or expand their account. There are usually many factors involved in a customer outcome. But cohort analysis can reveal strong correlations that help organizations understand where integrations appear to be contributing to customer value.

Tracking Reliability and Integration Health

An integration is part of the customer experience. If it works reliably, it can make your product more valuable and more embedded in a customer's workflow. If it fails frequently, it can create frustration, support tickets, and doubt about both your product and your partner relationship.

Reliability should therefore be measured alongside adoption and commercial outcomes. This is especially important as an integration program scales and the organization is supporting integrations built in-house, integrations built by partners, and integrations that depend on changing APIs, authentication protocols, permissions, and third-party systems.

The following metrics can help organizations understand integration health:

01Successful activity volume by integration
02Success rate and error rate over time
03Number of failed workflows, syncs, or actions
04Error type, such as authentication, permissions, API changes, rate limits, configuration, data mapping, or partner-side errors
05Number of integrations requiring reauthentication or reconnection
06Time to detect and resolve integration issues
07Number of customer support tickets related to each integration
08Uninstall, inactivity, or abandonment rates after an error occurs

Not every error has the same business impact. A temporary issue affecting a low-use integration may be less consequential than recurring failures in an integration used by enterprise customers to connect a business-critical system. Organizations should therefore segment performance data by customer importance, integration strategic value, activity volume, and the type of workflow being supported.

Tracking Operational Efficiency and Support Burden

Integrations create value, but they also require ongoing investment. The total cost of an integration includes more than the initial build. Organizations need to account for maintenance, customer support, monitoring, documentation, marketplace management, partner coordination, and the work required when either company changes its product or API.

Some integrations may have modest adoption but be strategically important for closing enterprise deals or retaining key accounts. Others may drive broad customer adoption with relatively little maintenance. Still others may generate many support tickets or engineering requests without creating enough customer or commercial value to justify continued investment.

To understand the efficiency of the integration program, organizations can track:

01Customer support tickets by integration
02Support hours or time to resolution by integration
03Engineering maintenance effort by integration
04Frequency and impact of incidents or partner API changes
05Cost to support an active integration account
06Cost to maintain an integration relative to adoption and activity
07Adoption-to-support ratio by integration
08Active use, reliability, and commercial influence compared with build and maintenance cost

This analysis helps organizations make better portfolio decisions. It can reveal which integrations should receive more marketing and sales support, which need investment in reliability or onboarding, which integrations should be improved with a partner, and which may no longer justify ongoing maintenance.

Framework

Tracking Integration Performance

What to track
How to track
Tools to use
Installs, activation rate, time to first successful action, and active accounts
Track the customer account, integration, installation date, activation event, and ongoing successful activity. Segment by customer size, plan, industry, and strategic account tier
Pandium, product analytics, CRM, BI dashboards
Successful activity, workflow volume, and repeat usage
Track successful actions over a defined period, such as 30, 60, or 90 days. Compare active and inactive integration cohorts
Pandium, product analytics, data warehouse, BI tools
Error rate, failure type, connection health, and reauthentication
Centralize integration events and errors. Categorize the source of errors and identify recurring patterns by integration and customer segment
Pandium, monitoring and logging tools, customer support software
Support burden and time to resolution
Associate support tickets, issue type, and resolution time with the relevant integration and customer account
Customer support software, CRM, Pandium, BI tools
Integration cost and portfolio value
Combine build, maintenance, support, and infrastructure costs with adoption, reliability, and commercial-impact data
Finance systems, project-management tools, engineering records, CRM, BI tools

By tracking commercial outcomes alongside the actual performance of integrations, organizations can move beyond reporting on the number of integrations they have built. They can make better product, engineering, partnerships, customer-success, and go-to-market decisions, and demonstrate how an integration program contributes to the broader performance of the business.

Between Product and Partnerships

Podcast · Interview

How to build integrations with platforms bigger than you

Without getting stuck at the bottom of the queue.

Biljana Pecelj

Principal Product Manager, Ledgy

Hosted by Cristina Flaschen

Interview · Biljana Pecelj, Ledgy

A relationship job that happens to run on APIs

Biljana Pecelj has spent most of her career on integration products and APIs — at Hootsuite through the rise of Instagram Business and TikTok, and now as Principal Product Manager at Ledgy in Munich. We talked about what changes when the platform on the other side of the API is far larger than you, and how to keep your roadmap moving anyway.

You've built both regular products and integration products. What makes integration work different?

The mental models from product stay the same, but the part that gets really interesting is that you usually have a little less control. You have to wield things through influence and persuasion a lot more.

You're typically working with partners whose roadmap you don't control, so you need to work much more on collaboration and building the human relationships that keep everyone aligned.

It also takes a creative muscle. Sometimes you have to work around things outside your control — say you're working with an API that has no webhook, so you build a polling system to accomplish what your product needs.

That's what drew me to integrations at Hootsuite. It's a bit like working with one hand tied behind your back.

What did your time at Hootsuite look like?

I started in 2019 and was there until I moved to Germany. Instagram Business was a super hot network — I got a few grey hairs from that integration. It was an acquisition from Facebook, so you were working with one partner but really several backends underneath.

TikTok was rising by the time I left, so I worked on that integration too. I had a fabulous partnership team, and it was the first job where I worked closely with legal — you learn quickly what it takes to do contracts with really large partners.

What's your advice when you're the smaller fish — when you don't get to dictate the rules, commercially or technically?

At Hootsuite the model was interesting: you built an entire business on a set of free APIs, and when you're not paying for something you have less influence from that angle too.

Twitter — I still call them by the old name — was the first to develop a paid API. That was a very different negotiation, because at that point you're a customer, not just a partner. You have different levers depending on the contractual relationship: is there a paid component, or are you offering something valuable like feedback from big logos in their beta?

In essence, being the small fish is about acknowledging the asymmetry from the get-go and adapting to it. Every partner has slightly different interests and motivations — you learn each one individually, and you build relationships along the way.

What kind of data have you been able to bring partners to earn their attention?

Partners are really responsive to data that helps their business. Instead of “my network disconnected,” help them with root-cause analysis: here's the error code we got from your system, here's when it started, here are specific customer IDs affected.

That takes solid observability. It makes them trust you, and it moves your other issues to the front of the line, because you're also helping them troubleshoot their own product. Auth issues especially — monitoring lets you be proactive instead of caught on the back foot.

“Being the small fish is about acknowledging the asymmetry right from the get-go — and learning what each partner is actually motivated by.”

Biljana Pecelj, Principal Product Manager, Ledgy

M&A is everywhere right now. How does it show up in integration work?

With any acquisition, marketing updates first — you rebrand the product — but the tech is much harder to integrate, so the backend lingers behind the branding.

Instagram had been acquired by Facebook years earlier and rebranded to Meta, one cohesive unit on the surface. But to set up an Instagram Business account, customers had to move between two interfaces — steps in Instagram, then steps in Facebook — before they ever reached us. It blocked people from integrating.

A wonderful designer built a friendly carousel walking through each piece. Investing in user guidance and education can go the distance when the tech itself isn't as integrated as you'd assume.

A lot of that awkwardness comes from M&A being driven purely from the commercial side, with the tech side not along for the ride. There's little due diligence on how the systems will actually fit — and the patterns linger for decades.

How do you get resources for an infrastructure team without being seen as a cost center?

Being branded an infrastructure team is a double-edged sword — everyone needs things from you, but you can be viewed as a cost center. The key is to rebrand what the team does and tie your wins to customer outcomes, whether they come directly from what you ship or indirectly through the teams that depend on you.

Integration roles take collaboration to another degree — PMs, designers and engineers on other teams, plus legal when you're speccing contracts, and a partnership team close enough to the ground to hear a beta is coming and say yes fast.

How do you handle the roadmap conversation when a new integration lands mid-year?

It's a negotiation. Onboarding to a beta with no webhooks means building polling infrastructure — if one team is bogged down, another may have the capacity. It's a lot of trade-off conversations: if you say yes to one thing, what comes off?

You can always predict the calendar of API deprecations — that's easy to prioritize six months out. What's unpredictable is whether a new feature ships, takes off with your customers, and gets an API endpoint. That's where a strong partnership team's spidey sense helps you pre-plan two versions of the roadmap.

We're in a moment obsessed with agents and automation. Where do humans fit?

I'm a big AI nerd and I love the efficiencies. But the people who buy our products are humans, and the people who build them are humans. A partner manager tipping you off that a beta is coming — that doesn't come through a chatbot. So much of this is still done offline, palm to palm.

One piece of advice for your early self?

You'll walk into a job you expect to be about APIs and specs, and find it's fundamentally a relationship job. Learn the other company's lingo, understand their incentives and how they define success, and use relationship-building as your strategic leverage. Be proactive with communication — it reduces escalations and builds the trust that accelerates everything else.

“It's a cross-section of humans aligning with other humans — with technology doing a lot of the work under the hood.”

Biljana Pecelj, Principal Product Manager, Ledgy

07

Monetization

Tracking monetization of integrations is mostly straightforward and is the easiest business impact to measure.

Organizations monetize their tech partnerships in different ways:

01Charging directly for integrations
02Charging or receiving a revenue share from partner apps that are sold or discovered in your app marketplace
03Restricting integrations to higher paid subscription plans and tracking when customers upgrade for the integration
04Charging partners program fees

Most SaaS companies do not charge directly for their integrations, though some do sell them as add-ons. The downside of this approach is most customers are not used to paying for integrations. The plus side is it can give you a strong indication of what integrations are worth to customers and how much value they perceive in integrations.

More commonly, SaaS companies either do not charge for integrations or they reserve integrations, particularly complex integrations, for higher paid plans.

Charging partners program fees is relatively common at larger companies; however, these fees are usually a very small percentage of revenues, and aimed mostly at covering some of the administration costs for the program and as a way to vet out partners who aren't that invested in the relationship.

07 · Monetization

Tracking Direct Charges for Integrations

Charging customers directly for integrations is easy to track and simply requires collecting the data on how many integrations customers purchased and at what price. If you're selling the integration from a partner's marketplace, a revenue share may be taken out of the price the customer pays, while if you sell it directly to your customer, you will receive the full amount.

Tracking Revenue Share You Take From Partners

If you have an integration marketplace, you may take a revenue share from your partner, either for their integration or their app, for customers who discover these apps in your marketplace.

You may also take a revenue share when your sales or customer support team recommends the partner app.

If you're selling the integrations and/or partner software in your marketplace and remitting the payment minus the revenue share, this is also straightforward to track.

If your marketplace is not transactional, then you need to include unique or affiliate links in your marketplace so your partners can identify when a customer discovered their app in your marketplace. This requires an agreement with the partner and that they track the customer after they arrive on their website.

While this method results in lost rev shares (when customers aren't tracked successfully from marketplace to purchase) it is relatively straightforward to track the amount of revenue that is being collected.

Tracking Integration-based Upgrades

It is common to put integrations on higher paid plans. Often you won't be able to track if a person upgraded solely for the integration.

But there are ways to identify how much this is occurring. One way is to have an in-app integration marketplace with an “Upgrade” button next to the integrations that require moving to a higher plan. From there, you can track when customers clicked on the “Upgrade” button and then upgraded their account.

The other way is for sales or customer support to ask customers why they selected the higher paid plan, and see how frequently the integration was cited as the reason.

It depends heavily on how complex your plans are and your product category as to whether integration-based upgrades can be directly attributable to the integration. Often, it will just be one factor amongst many that prompted a customer to upgrade.

Tracking Program Fees

Partner program fees are usually not substantial amounts of money. However, they can easily and should be tracked as part of the overall picture around tech partnerships' business value. Depending on your ecosystem, you may also be receiving market development funds from partners. For most, this will not be a significant amount of money, but should also be tracked.

Framework

Tracking Direct Revenue from Tech Partners

What to track
How to track
Tools to use
Direct charges for integrations or upgrades due to integrations
Track price and amount customers are paying directly for integrations. Have an “Upgrade” button in-app next to integrations, track conversions. Ask sales and CS to note when customers upgrade for an integration
Integration marketplaces like Pandium; CRM; customer support software; revenue analytics
+
Revenue shares taken from tech partners
Track revenue coming from tech partners via revenue share, whether through a transactional marketplace or affiliate link or referral
Marketplace software, affiliate software, CRM, revenue analytics
+
Partner program fees and MDF
Track the total fees obtained from partners for security reviews or program tier fees, and any MDF from partners
Partner portal, revenue analytics
=
Partner driven revenue
Utilize your organization's existing methodology for revenue analytics
Revenue analytics
Between Product and Partnerships

Podcast · Interview

How to price your SaaS product in the age of AI

When the marginal cost to serve a customer is no longer zero, every pricing assumption is back on the table.

Roee Hartuv

Pricing & Packaging Advisor, Willingness to Pay

Hosted by Cristina Flaschen

Interview · Roee Hartuv, Willingness to Pay

Why AI just broke the economics of SaaS pricing

Roee Hartuv started in software sales, moved into go-to-market advising, and now works exclusively on what he calls the number one growth lever a software company has: pricing and packaging. He works with companies from tens of millions in ARR up to a billion. We talked about what AI changes about monetization — and why nearly everyone he meets still can't answer a basic question about their own product.

What changes about SaaS pricing once AI is in the mix?

All of a sudden the cost to serve a customer is no longer almost zero. In SaaS, the marginal cost to serve the hundredth customer or the ten-thousandth is basically the same, and in most cases close to nothing. That's the game of SaaS: you develop one piece of software and everyone gets access to the same platform.

AI comes with a cost, and that completely changes how companies define their monetization strategy. Some say it averages 50% — the numbers keep changing and AI is getting cheaper — but it's a dramatic cost.

And unlike SaaS, where every customer's cost to serve was pretty much the same, with AI you might have superusers running the product 10, 20, 50 times more than the average. That changes how you have to think about pricing altogether.

Where do companies start with unit economics in that world?

The point is they need to start thinking about unit economics at all. When I come in and ask what it costs to serve a customer or a segment, usually they don't know. In some cases they can extract the cost of the CSM team from finance, but it's never done at a customer level.

So first, understand the unit economics. Then measure it at the account level, and in a lot of cases the user level — often in real time, because eventually you need to price on it. The companies doing this best are AI-native: they have it baked in. The challenge is for SaaS companies adding AI who never had to think this way.

Who should own pricing strategy?

Everybody — and of course when you say everybody, that means nobody, so somebody needs to own it. It doesn't matter whether that person sits under finance, commercial, product, or product marketing. Pricing and packaging touches everything, so you need inputs from all of them.

It touches how product is built and how they measure usage. Commercial needs to understand the value and how to sell it. Finance needs it to forecast revenue. Marketing traditionally owned pricing, and that still holds at companies with strong product marketing. Everybody comes to the same table and makes the decision together.

Do fixed, multi-year contracts still have a place when cost and consumption are both variable?

First look at whether your cost is variable. With AI it usually is — it changes by user, by time of year. In that case you need to tie pricing to cost, so fixed or per-seat models often no longer hold.

I'd go with a hybrid: some fixed component that gives you forecasting, plus a variable piece that moves up and down with usage.

On duration — putting my pricing hat on, not my sales hat — I advise against multi-year right now. Sales loves it because it locks in the customer, but everyone is still learning: we don't know the cost, the usage patterns, or who the power users are. Leave room to change pricing, and maybe the model, each period rather than locking into a deal that loses money for two or three years.

“Everyone is still learning. Leave room to change your pricing — and maybe your model — every contract period.”

Roee Hartuv, Willingness to Pay

How do you distinguish value-based pricing from outcome-based pricing?

You can have one without the other, or both. Outcome-based is the holy grail: as a customer, I pay only for outcomes, not for all the inputs it takes to get there. But in real life it's very difficult, because what is an outcome?

Take an AI agent that supports tickets. A ticket closed — fine. But what if it reopens? What if it's closed and the customer isn't satisfied? There are a lot of caveats to watch for.

Take OpenAI — they can't do outcome-based pricing. It's flat, per seat. Myself and my mother are an extreme example: I use it for financial forecasting and deep Excel work that would've taken an analyst a week. My mother uses it to check Italian recipes. The value and the outcome are completely different, so how do you price on outcome when it varies that much?

Value-based, though, is doable in a lot of cases — it's aligning how you price and package to what the customer actually considers valuable. That's what companies should try to do.

How should companies price on efficiency gains, when those are so hard to prove?

It's tough, especially when the gain isn't clearly understood by the client. Like risk reduction, it's hard to quantify and hard to sell — you have to educate the prospect with examples of others in their situation.

This is where I run a willingness-to-pay analysis. With one manufacturing-floor management customer, machine uptime rose by a real amount versus their old Excel process, but customers struggled to connect that uptime to the software. It took a lot of interviews to capture it. That's the only way — talk to your customers, narrow the gain down to dollars, and price on that.

Are we past peak AI hype on efficiency?

I think we're at a pivotal moment. Some companies are realizing the hype has passed and asking what the real efficiencies are. Uber's CEO said a few weeks ago that they'd used AI across the company and hadn't really seen efficiency gains yet.

That's a great example: companies are starting to realize they spent enormous amounts on AI and didn't hit the ROI they were promised or targeted.

When you look at it from the top — the CFO or CEO level, with enough data — you can make the call. How much did we spend on AI over this period? How many new products, what time to market, how many more features? If it barely moved, you can see that clearly at a high level.

Why is that measurement so hard for most teams?

Uber can do it because they've been around a while and stayed relatively consistent — the core value of the product hasn't changed much, so year-over-year comparisons hold. Most companies can't compare quarter to quarter: the people change, the tech changes, the market changes. And AI gives you a fast dopamine hit — it does something immediately — but the real downstream impact can take months or years to show up, all while you're spending to use it.

“Companies are realizing they spent enormous amounts on AI and didn't hit the ROI they targeted.”

Roee Hartuv, Willingness to Pay

Platforms like HubSpot, ServiceNow and Workday are starting to meter agent access. Will more follow?

Obviously there's value there, and they're trying to see what else they can extract from it. We'll see more and more companies do this with API gateways — there's value to capture, and that's why they're doing it.

The use case I see is: you don't have to use our interface or our AI — bring your own agents, the ones you've built for your organization, and hook them up to our services and to your data in our platforms. It's the same idea as charging for API access, capturing value instead of forcing people through your UI. From a customer's perspective, it sounds fair.

Take Salesforce. The reason they're doing this is they understand the traditional seat-based model is threatened — AI will replace some seats. So they're finding ways to keep the revenue they get from customers. More will follow.

How should companies price the integrations themselves — bundle, premium tier, or free?

Monetize as much as you can — but some connectors sound silly to charge for. I work with a marketing automation platform that has to connect to your CRM; there's no way around it. Charging $500 a month for the Salesforce connection would be absurd, so they give it away.

Anything commoditized and basic, you give — assuming there's no custom adaptation or heavy maintenance, because everyone connects to Salesforce now. But SAP is the opposite: mission-critical, a 99.99% SLA to maintain, real adaptation per customer. That one I'd almost always charge premium for.

How does willingness to pay change the connector question?

The same connector can be free or premium depending entirely on the customer. A small company doesn't expect to pay for integrations, so you probably give it away. Sell to enterprises who expect to pay — where it's common practice — and of course you charge.

The value isn't always tied to the effort. Sometimes an integration is genuinely hard, like SAP. But sometimes the specialization is the value even when the build isn't that heavy — the customers in that segment are simply used to paying for it.

That's what we call customers' willingness to pay — it's the name of our company. At the end of the day, you want to price based on how much different customers are willing to pay. You can price on cost, do cost-plus and protect a margin. Or you price on willingness to pay: some customers you charge more even though the cost is the same, because they'll pay more. That's how you build a more intelligent pricing and packaging strategy.

What about freemium and PLG?

Freemium has a real cost to the company, so the question is how much you're willing to bear, and whether your paying customers generate enough to justify subsidizing the free ones. Same bucket as connectors: what does it cost to maintain the API, and can you justify the free-to-paid conversion? At some point you reserve certain features for paid — and my gut, across most use cases, is that integrations usually justify a monthly charge.

The through-line: measure before you monetize.

AI ended the era where every customer cost roughly the same to serve. The companies that adapt are the ones that can answer, at the account and user level, what a customer actually costs and what they're actually willing to pay — then build a hybrid model that keeps some fixed revenue for forecasting while letting the variable piece move with usage.

The same discipline applies to integrations. Commodity connectors get bundled; specialized, mission-critical ones earn a premium — and the deciding factor is less the engineering effort than the customer's willingness to pay.

Three takeaways

1

Know your unit economics. Measure cost to serve at the account — and often user — level, in real time where you can.

2

Go hybrid, stay flexible. Pair a fixed base with usage-based variable pricing, and avoid locking into multi-year terms while the market is still learning.

3

Price on willingness to pay. The same feature or connector can be free or premium — let the segment, not the build effort, set the number.

08

Tracking the ROI: Costs

Tracking the costs and spend on tech partnerships is easier than tracking the impact because doing so does not require the participation of external stakeholders, nor does it require tracking “influence,” which cannot be completely tracked due to technical limitations and privacy concerns.

The challenge around tracking the amount of money that goes into tech partnerships is how cross-functional they are. Those working on tech partnerships may report to other departments and only spend part of their time and budget on tech partnerships. This may not be cleanly demarcated or even officially noted.

In addition, tech partnerships may significantly utilize the work of other departments, whether it is marketing's messaging or engineering's infrastructure building. This other work may be necessary to the success of tech partnerships even though it was completed for another department and for another business objective.

Tracking the costs should focus on a few key elements:

01Salaries for those in technology partnerships and other employees who are working on tech partnerships
02Budget for a tech stack, whether for additional seats in a CRM or partner technology
03Budget for go-to-market activities and campaigns, including revenue shares, MDF, and partner program fees
04Cost of building and supporting integrations
05Cost of building and supporting integration infrastructure, including an integration marketplace, hosting, logging, and product analytics

08 · Costs

Tracking Salaries

Large ecosystems may have a “Platform” or “Ecosystem” department with cross-functional employees all on one team. This simplifies the calculation of salaries going into tech partnerships.

But for mid-market or smaller companies, there will often be only a half dozen people working exclusively on tech partnerships, and many employees may be contributing significantly part time.

Understanding the bigger picture on ROI requires trying to achieve clarity over how much employee time is supporting tech partnerships, whether from a go-to-market or product side.

Tech Stack Budget

Tech partnerships may have partner specific technology subscriptions, like a PRM, embedded marketplaces, partner account mapping software, or affiliate software. They may also be a user on tech your organization is already using, like a CRM, Slack, or productivity software.

Go-to-Market Budget

Go-to-market budget will include marketing to partners and with partners, as well as customer and prospect marketing around integrations.

Marketing to partners includes outbound to attract new partners and partner engagement activities, like gifts and events.

Marketing with partners includes a wide swath of activities, as well as marketing to prospects and customers about the marketplace and individual integrations.

Building and Supporting Integrations

Almost all SaaS companies, even very large ones, build and support certain integrations. Usually these are integrations that are important to their customers and the organization wants more control over.

Budgeting the build for an integration is straightforward, but supporting it over time is tougher to predict. It will depend on how deep the initial integration was and how quickly your product/API and your partner's product/API is updated. The more quickly it is updated, the more the integration itself will have to be updated.

The design of the integration will also impact how much support it will entail. A well-designed integration with an intuitive UI will require much less support than one that is not designed with the customers' business objectives in mind or has a complex UI.

Building and Maintaining Integration Infrastructure

To successfully show the impact of tech partnerships and to scale your program, you need strong infrastructure for your marketplace, partners, and customers. This infrastructure is necessary to tracking, partner UX, and customer UX.

This entails building an in-app marketplace with analytics and tracking customer installs and usage and having a simple process for all stakeholders to access the information relevant to them, from customers to partners.

Without this infrastructure, you won't be able to show integrations' impact on retention, LTV, or customer satisfaction, and partners and customers will have a subpar experience interacting with your organization.

Whether you use an embedded iPaaS like Pandium or build everything in-house, you need to estimate the cost of building and maintaining the infrastructure at scale, and understand the different costs that go into this endeavor.

Summary

Tracking Costs of Tech Partnerships

1

Salaries. Except in very large organizations, employees supporting technology partnerships are most likely reporting to many different departments.

2

Tech stack. This is likely a combination of partner technology and general technology with additional users, like a CRM seat.

3

Go-to-market budget. Includes marketing to and with partners, customer and prospect marketing, revenue shares, and partner program fees.

4

Building and supporting integrations. The cost of building and supporting integrations to your tech partners.

5

Integration infrastructure. Building and maintaining integration infrastructure that enables tracking of usage analytics, and a satisfactory partner and customer UX.

09

Tools and Workflows

One of the major challenges around tracking the impact of interoperable tech partnerships is the sheer number of internal AND external stakeholders needed to participate.

Understanding what most organizations need from internal and external stakeholders in order to effectively track the impact of tech partnerships can help you advocate for the right processes, tech stack, trainings, and incentives.

Below, you can see the primary tools each relevant user may be using in your organization and partner organizations to effectively track the impact. Each phase indicates the next stage in development — as tech partner programs grow and scale, they adopt more tech to monitor the impact.

Diagram

Primary Tech Used by Role Supporting Tech Partnerships

Each phase indicates the next stage in development. As programs grow and scale, they adopt more tech to monitor the impact.

Role
Phase 1
Phase 2
Phase 3
Your Sales Team
Phase 1CRMSlack
Phase 2Partner Account Mapping
Partner Sales Team
Phase 1CRMSlack
Phase 2Partner Account Mapping
Your Partner Team
Phase 1CRMPRMSlack
Phase 2PRMPartner Account MappingAffiliate Software
Phase 3Integration AnalyticsMarketplace Analytics
Partner's Partner Team
Phase 1CRMPRMSlack
Phase 2PRMPartner Account MappingAffiliate Software
Phase 3Integration AnalyticsMarketplace Analytics
Product and Dev Team
Phase 1Product ManagementProduct AnalyticsSlack
Phase 2Integration AnalyticsMarketplace AnalyticsDeveloper Portal
Partner's Product and Dev Team
Phase 1Product ManagementProduct AnalyticsSlack
Phase 2Integration AnalyticsMarketplace AnalyticsDeveloper Portal

Categories of partner technology for tracking

CRMPRMPartner Account MappingAffiliate SoftwareThrough-Channel Marketing AutomationIntegration AnalyticsMarketplace AnalyticsDeveloper Portal

Other relevant technology

SlackProduct AnalyticsMarketing AutomationDatabase & VisualizationCustomer Support Software

Workflows

Data has to move across the organization in order to track and show the impact of tech partnerships. The two diagrams below show the workflows centered around the Partnerships Team and the Sales Team.

With larger organizations, this data will go into databases and business insights visualization software at various points, depending on how the company's tech stack is set up.

Sometimes there will be direct integrations between, say, a PRM and CRM, and other times, the data will be extracted, transformed and then loaded into the other system by an intermediary tool.

Or, depending on the use case, data may be taken from those systems and visualized in a BI tool where both partnership leaders and other executives can assess it, without being passed to the other tool.

For reporting purposes, data does not necessarily need to be viewed inside a PRM. But, in other cases, where one wants to show partners the results of their referrals, for example, the CRM data will need to be sent back to the PRM.

A process should be defined that optimizes individual workflows, unpacks new functionality and opportunities, and tracks results. Once a process is mapped out, you can ensure that the data is consistent, accurate and updated when and where it needs to be.

Diagram

Sample Data Flows From Your Partner Team

Your Partner Team

CRMPRMPartner Account MappingSlack

May work primarily in CRM and/or PRM, and collab tool. Partner data sharing tools are also important.

Event updates and requests sent to and from a collab tool.

Counterparty and systems
What moves
→
Your Partner's App Marketplace
Marketplace Analytics → Your Partner Marketing Team (Marketing Automation)
Leads from marketplace tile interactions
→
Your Partner Marketing Team
Marketing Automation
Logging leads to show revenue attributed to marketplace leads
→
Your Sales Team
CRM
Sales team may request intros or search for shared accounts. Your sales team will log into your CRM and may log partner referrals or influence
↔
Partner's Partnerships Teams
PRM, Marketplace Analytics
Your partner team will likely log in to some partners' portals to collab on co-marketing and get reports on marketplace activity from partners
↔
Partner's Partnerships Teams
PRM, CRM
Partner shares account data and gets notifications and results of collaborations
↔
Your Partner Marketing Team
Through-Channel Marketing Automation, Marketing Automation, Affiliate Software — Partner's Partnerships and Marketing Teams log in
Partners may co-market out of through-channel marketing automation or a PRM. Earlier on, they may use their own marketing automation and CRMs to run campaigns and share data by sending CSV or Excel files or through unique links
→
Your Product and Dev Team
Integration Analytics
Provide data on integration installs, uninstalls, and usage
→
Your Customer Success Team
Customer Support Software
Provide data on integration tickets and satisfaction
→
Your Integration Marketplace
Marketplace Analytics
Data on which integrations customers are exploring and most interested in
Integration installs, uninstalls, usage can be compared to customer retention and ACV; support tickets and satisfaction surveys can help inform this analysis.
Larger organizations will use internal iPaaS's, databases, and visualization tools that may sit “between” some of these integrations, processing the data before passing it on to the next software. Smaller organizations may use off-the-shelf iPaaS's like Zapier to connect these systems.

→ Data movement from one system to another     ↔ User logging into a system

Diagram

Sample Data Flows From Your Sales Team

Your Sales Team

CRMSlack

Works primarily in CRM and team collab tool.

Integrations to Slack or other collab tools enable easier, faster collaboration while also creating a record of partner influence; Slack messages can be added to CRM records.

Counterparty and systems
What moves
→
Your Partner's App Marketplace
Marketplace Analytics → Your Partner Marketing Team (Marketing Automation)
Leads from marketplace tile interactions
→
Your Partner Marketing Team
Marketing Automation
SQLs
↔
Your Partner Marketing Team
Affiliate Software — integrated with your CRM so leads that come through affiliate links are automatically attributed to the right partner
Leads from affiliate partners in; deal results from affiliate partners back out
↔
Partner's Partnerships and Marketing Teams
Log in to Affiliate Software
Leads from affiliates entered into system and results and payouts accessed
→
Your Partner Team
Partner Account Mapping, PRM — integrated with your CRM so intros and influence are automatically attributed to the right partner
Intros to leads from partners; partner sales enablement activity; lead data; results from partner collaboration
←
Your Partner Team
Partner Account Mapping, PRM
Results from intros and partner influence; status of deals
↔
Your Partner Team
via Slack
Find leads, and request intros and data; send messages to partner managers. Partner data; notifications of new data and partner messages come back
→
Your Partner Marketing Team
Affiliate Software → Slack
Notifications of new leads and messages; find data and requests to partner managers
↔
Partner's Partnerships Teams
CRM, PRM — with Your Partner Team
Partner's partnerships team sends partner data to partner account mapping and PRM software. Some partners may use your partner portal; in other cases, your partner team will use the partner's portal. Usually, both the partner and your partnership team will use the account mapping software
Larger organizations will use internal iPaaS's, databases, and visualization tools that may sit “between” some of these integrations, processing the data before passing it on to the next software.

→ Data movement from one system to another     ↔ User logging into a system