Article
|
11
 minutes
A Lack of GTM Support for ELG Could Cost You Millions in Revenue
Article
|
13
 minutes
A hiring manager’s guide to partnerships roles and job titles
Article
|
4
 minutes
How Typeform went from 30 integrations to 100+ in just one year
Article
|
4
 minutes
Expanding to a new persona or market? Your partners can help you dive in with grace
Video
|
4
 minutes
How to Source and Convert Pipeline in HubSpot | Connector Summit 2022
Article
|
8
 minutes
Confessions of a GSI: Here's What GSIs Look for in an ISV Partner
Article
|
8
 minutes
Confessions of an ISV: How to Be a Good Channel Partner
Article
|
3
 minutes
Sales Leadership and Partner Enablement: Part 3
Article
|
15
 minutes
The Partner Tiers Cheat Sheet: Benefits, Drawbacks, and Checklists
Article
|
5
 minutes
Reflections on 'The Age of Connected Work'
Article
|
1
 minutes
Is ELG right for me? Find out with the ELG Readiness matrix
Article
|
4
 minutes
Sales Leadership and Partner Enablement: Part 1
Article
|
2
 minutes
The growing importance of partner attach across the buying cycle
Video
|
3
 minutes
Getting Primed for Account Mapping with Partners in Crossbeam | Connector Summit 2022
Video
|
3
 minutes
Crossbeam Product Drop Webinar: New Features Worth Buzzing About
Article
|
4
 minutes
How to Become the Beyoncé of Your Ecosystem
Video
|
51
 minutes
Nearbound Podcast #057: What Your Agency Partners Won't Tell You
Article
|
8
 minutes
How to be a customer-obsessed partner manager
Article
|
1
 minutes
SAS Gets IPO Ready via Partnerships
Video
|
45
 minutes
Nearbound Podcast #055: The Partner Manager Playbook — Managing the Front Lines
Article
|
7
 minutes
Partnerships 101: What is partner marketing
Video
|
45
 minutes
Partnership Secrets: Enable Sales Teams and Hit Revenue Goals
Article
|
6
 minutes
SaaS reseller partnerships: What they Are & How They Work
Article
|
26
 minutes
Partnerships 101: ISVs, VARs, SIs, MSPs, and the Glue that Holds them Together
Article
|
7
 minutes
Partnerships 101: What is cross-selling?
Article
|
7
 minutes
Partnerships 101: Strategic Alliances Explained (Finally!) Plus Examples
Article
|
3
 minutes
What Partner Ecosystem Maturity is and Why it Matters
Article
|
10
 minutes
The nearbound.com manifesto: Trust is the new data
Article
|
6
 minutes
How RingCentral built an internal culture of partnerships
Article
|
11
 minutes
It’s happening! Crossbeam and Reveal are joining forces to disrupt go-to-market strategy as we know it.
Article
|
14
 minutes
The Beginner’s Guide to SaaS Tech Partnerships
Video
|
53
 minutes
Nearbound Podcast #051: Day Zero Mentality - How Rob Brewster Went from Partner Chief to Company Chief
Article
|
8
 minutes
Navigating Partnership Ecosystems: Channel, Tech, & Strategic
eBook
2022 State of the Partner Ecosystem Report
Video
|
38
 minutes
Nearbound Podcast #048: The Fear & Greed Index - Right Now Every Partner Pro Needs to Stand Tall
Article
|
25
 minutes
25 Articles Showing the Business Impact of Partnerships (Bring These to Your CEO)
Article
|
8
 minutes
Don’t Fall Behind: Get Your Partner Data in Your Data Warehouse (Part 1 of 2)
Video
|
43
 minutes
Secrets to Building a High-Impact Partner Program
Article
|
46
 minutes
How to Ensure Accurate Ecosystem Data
Article
|
7
 minutes
A recommended ecosystem AI strategy: Take an integrated rather than a top-down approach
Article
|
17
 minutes
Your Guide to Preparing for Your Next Partner Pitch Meeting
Article
|
6
 minutes
How to Guide: Partnership Alignment with Internal Stakeholders
Article
|
45
 minutes
How to measure and attribute nearbound impact
Article
|
5
 minutes
Balancing AI, automation, and the human touch in partner management in 2024
Video
|
18
 minutes
The Inside Track: How to Accelerate Crossbeam Onboarding for Your Partners
Article
|
8
 minutes
You Have Dormant Partners. Here’s How to Get Their Interest
Article
|
4
 minutes
How to nail co-marketing events in 2024 with nearbound
Video
|
12
 minutes
How to Gain Internal Buy-in to Build New Integrations | Connector Summit 2022
Article
|
3
 minutes
Track churn and you’re 3.6x more likely to have dedicated budget for integrations
Video
|
54
 minutes
The State of the Partner Ecosystem 2022 Webinar
Video
|
3
 minutes
Crossbeam Explains: What are System Integrators?
Article
|
9
 minutes
The Awkward Dance: Should You or Your Partner Build the Integration?
Article
|
16
 minutes
Building the Flywheel Starts with Your Partners
Article
|
8
 minutes
4 Signs it’s Time to Expand Your API Docs
Article
|
9
 minutes
7 tips for co-selling like a supernode
Video
|
48
 minutes
Nearbound Podcast #039: Dancing with Elephants — The Art of Strategic Partnering
Article
|
8
 minutes
Tech ecosystem maturity: How to level up your co-marketing motions
Article
|
14
 minutes
20+ Interview Questions for Hiring Your First Tech Partner Manager
Article
|
7
 minutes
3 Reasons to Get Certified in Your Partners’ Tech and Become Indispensable to Your Team
Article
|
8
 minutes
Partnerships 101: What is a PRM and should I use one?
Article
|
7
 minutes
Tech ecosystem maturity: How to level up your “better together” messaging
Video
|
36
 minutes
Partner Ecosystems 101
Video
|
1
 minutes
Dave Goldstein: Ecosystem-Led Sales for the Enterprise: How Braze Leveraged Alliances to Fuel Robust Growth | Supernode 2023
Article
|
11
 minutes
8 Times a Partnership Impacted an “Exit Event” (And Why Acquisitions are on The Rise)
Article
|
5
 minutes
How VC firms are using Crossbeam to grow their portfolio companies at scale
Article
|
9
 minutes
5 Signs Your Tech Partner's About to Get Acquired (And How to Prepare for Change)
Article
|
12
 minutes
Tech Ecosystem Maturity: How to Level Up Your Integrations Team
Video
|
18
 minutes
The Inside Track: Crossbeam Security 101 with CISO Chris Castaldo
Article
|
8
 minutes
6 tips for expanding internationally using channel partners
Article
|
6
 minutes
10 steps to develop a co-marketing strategy
Article
|
6
 minutes
How Typeform improved their revenue by 40% with ELG and PLG
Article
|
6
 minutes
Partnerships 101: What is co-selling?
Article
|
6
 minutes
Partnerships 101: Inbound vs Outbound Integrations and Why They Matter for Your Partnerships
Article
|
11
 minutes
How to Communicate Effectively With Your Entire GTM Team and The C-Suite
Video
|
20
 minutes
The Inside Track: Get to know the Crossbeam Salesforce App
Article
|
18
 minutes
The 7 Metrics That Prove the Business Impact of Your Tech Integrations
Article
|
5
 minutes
How to learn your customer’s tech stack and increase integration adoption by 17%
Article
|
7
 minutes
8 times sales reps won the deal by co-selling with partners
Article
|
9
 minutes
6 ways sales professionals can use partnerships to get promoted
Article
|
6
 minutes
How Co-Selling & Co-Marketing Build Revenue
Article
|
8
 minutes
The Intersection of Partnerships and Product Development with Pandium’s Cristina Flaschen
Video
|
37
 minutes
The 4 Levels of Tech Ecosystem Maturity
Article
|
12
 minutes
8 Tips for Surfacing the Business Impact of Partnerships and Driving Partner-Sourced Revenue Earlier
Article
|
7
 minutes
Tech ecosystem maturity: How to level up your co-selling workflows
Article
|
31
 minutes
Despite The Economy, Gartner Projects Double-Digit Growth As Companies Find Ways to Do More with Less
Article
|
14
 minutes
Crawl, walk, run: The co-marketing framework that will keep you sane
Article
|
11
 minutes
The 5 Things to Do in Your First 90 Days as a Partnership Leader
Article
|
4
 minutes
Ecosystem Ops 101: 6 Ways to Drive Efficiency and Maximize the ROI of Your Partner Program
Article
|
7
 minutes
Vetting 100s of channel partners? Use this 4-criteria checklist to speed up the process
Article
|
6
 minutes
8 ways to treat your co-selling partners with R-E-S-P-E-C-T
Video
|
42
 minutes
Nearbound Podcast #026: Building Trust in Channel Partnerships
Article
|
12
 minutes
Partnership KPIs For Marketing, Sales, Customer Success + More
Video
|
44
 minutes
No more silos: 4 new ways to use partner data
Article
|
13
 minutes
15+ questions to help your sales reps master their co-selling motions
Article
|
23
 minutes
How We Foster Collaboration Remotely at Crossbeam
Article
|
7
 minutes
21 Partnerships People You Should Follow on LinkedIn
Article
|
12
 minutes
How to use CRM data & automation to nurture your co-selling relationships
Article
|
7
 minutes
How CallRail increased integration adoption by 167% through strategic partnership with HubSpot and Reveal
Article
|
7
 minutes
3-step strategy for partnership managers
Video
|
5
 minutes
How to Execute an Effective Nearbound Channel Strategy
Why Co-innovation Between Tech Partners Is So Hard
by
Ryan Lunka
SHARE THIS

Building software products is hard. Building cross-product user experiences, where two otherwise separate software products combine to provide a joint solution, is really hard.

by
Ryan Lunka
SHARE THIS

In this article

Join the movement

Subscribe to ELG Insider to get the latest content delivered to your inbox weekly.

Building software products is hard. Building cross-product user experiences, where two otherwise separate software products combine to provide a joint solution, is really hard.


Yet, this is what’s required in the era of ecosystems.


You do need to build an exceptional software product to be successful. That’s always been a minimum requirement, but the minimum is no longer sufficient.


There’s massive potential for co-innovating with technology partners to jointly solve really hard problems for users. Doing this hasn’t always been “a given,” and now it’s one of your biggest opportunities for growth.


But, this opportunity does not come without challenges. This is an unfamiliar motion for most software teams. Even among those who have been successful with co-innovation, it’s rare to have scaled that success.


In this post, I want to talk about why and what can be done about it.



Reason one: Software products tend to be built behind closed doors

You raise some money. You hire a few developers. They set up a private Git repository, and they start coding.

From day one, most software teams build in private.


There are many valid reasons for this. Most products aren’t open source, nor does open source fit their business model. Building in private protects intellectual property, which can easily be ripped off, even with proper documentation in place. See Silicon Valley for details.


Plus, if you’re building SaaS, who outside cares what the code looks like?


Yet this perfectly reasonable idea behind building in private is exactly what causes friction when you try to build some parts of the product (e.g. integrations) with someone else.


Product and engineering teams who operate as a black box, often leaving the partnership teams on both sides to be the messengers, put themselves at a disadvantage. They don’t allow some of the smartest people in their respective rooms to come together and co-create, which is exactly what’s required to build truly innovative joint solutions.



What to do about it

Your product may not be open source nor may the concept play any part in your overall business strategy. However, your team (partners, product, and engineering) should learn open-source principles. You should be intentional about where you can include the OS operating model in your tech partnership program.


The tools and workflows your product and engineering teams already use are likely already derived from open-source motions. This philosophy is built into the DNA of the web, and its best practices tend to work their way into the DNA of commercial companies, especially those who aren’t big legacy enterprises.


It’s because building software in public with people from all over the world who rarely if ever actually meet one another is a challenging governance problem. Thus, really good software development practices have emerged that now get used even when the team sits in a room together. The best engineering teams adopt such practices.


Think about what parts of your product development process can be partially opened up to your partners’ product teams. Operate “kind of open source” to allow those teams to work more closely together.


This will help you to use the principles of open-source software and understand how it is built for joint solutions with tech partners.



Reason two: Separate fiduciary responsibilities

Tech partnerships are about two or more companies coming together to jointly solve a customer’s problems more effectively than they could do individually. But, the reality is that partnerships are made of separate companies, with separate investors, separate boards, and ideally somewhat aligned but ultimately separate goals.


In more technical terms, each of those companies has separate fiduciary responsibilities to its shareholders and to its individual relationships with customers.


This immutable fact can cause friction between partners. Often it shows up when determining investments to be made by both or when navigating separate but connected relationships with customers.


Here’s a classic example: A small upstart forms a tech partnership with an established ecosystem hub product because they are able to expand that product’s capabilities in a specific way. After years of a solid partnership, the larger company decides to build its own feature that renders the smaller company’s solution mostly unnecessary.


Can you blame the bigger company? Strictly speaking, if they assessed that building it themselves was best for their business, they kind of have the right and responsibility to do it. It’s not an easy conversation, but it’s a common one.


The bottom line is, even in the most successful partnerships, separate companies will do what’s best for them. As long as the partnership aligns with those interests, it will continue successfully. If it no longer aligns, things will change.



What to do about it

You can’t change the fact that partnerships are fundamentally made up of separate companies, but you can acknowledge and plan for it.


When assessing a new tech partner opportunity, try to be as upfront as you can about your intentions. What do you hope the joint solution will do now? What about in the future? Do you plan to provide your own function that will replace it?


You may not be able to provide 100% transparency, but the more you can, the better. It’s not in either party’s favor to invest in a partnership that has an unexpectedly abrupt end.


That said, it’s quite alright to view a partnership as a temporary relationship. You aren’t fusing yourselves together for all time. If this is a “few years” thing, then be clear about it upfront.


Additionally, when you set up your partner agreement (formally or informally) try to design balanced incentives. Incorporate checks and balances with how you decide to operate together, so you’ve both got enough skin in the game.


Setting up a situation where you jointly invest time and resources in building the joint solution (my first point) is a good way to start. It prevents one side from putting too many eggs in the basket at the outset.



Reason three: Risk aversion

Tech partnerships, like all business decisions, are about balancing risk and potential reward. You can never know for sure that a partnership will work out.


You have finite time and finite resources. Your partnership, product, and engineering leaders must be discerning about where they make investments. Building a joint solution with a tech partner is no exception.


Making matters harder, despite today’s growing enthusiasm for partner-led strategies, many partnership teams are fighting for budget and are constantly required to prove their worth to the rest of the organization.


Building a deeply integrated joint solution with a tech partner has huge potential upside at the risk of a lot of downside.

We’ve all worked through those partnerships that took tons of time and money and ultimately failed. It’s really unfortunate for everyone. It can cost jobs.


All of these facts can encourage a tendency toward risk aversion. This can slow or even stop potentially valuable tech partnerships dead in their tracks. Risk management is important–no one should be reckless. Risk aversion can limit your opportunities.



What to do about it

The Lean Startup taught product teams how to build software iteratively. You start with small hypotheses and invest small amounts in products or product features in order to learn if those hypotheses are true. (The term, which is very often misunderstood, is the “minimum viable product.”)


This same philosophy should apply to tech partnerships. Think in terms of the minimum viable partnership, then grow from there.


Ideally, you have a big vision for the kinds of deeply integrated product experiences you want to create with a partner–even better if with many partners. However, if you and those partners try to boil the ocean, it’s almost certain to be a failure.

Instead, use the big vision for orientation but deliver small. Start with just enough of the partnership relationship and the cross-product experience required to support it.


See what customers think about it. See what feedback they have. Then, incorporate that feedback into the next batch of small iterations. Build partnerships and the integrated product experience piece by piece, even if that means that sometimes you have to throw away bad ideas (this is a good thing).


You can’t eliminate risk from the equation, but building a tech partnership and an integrated product experience iteratively will help to manage the risk. It helps to ensure you only spend big where the juice is worth the squeeze.


Prefer to listen? Subscribe to our nearbound.com Audio Articles Podcast. Text-to-speech provided by our partner Voicemaker.in.

You’ll also be interested in these

Article
|
8
 minutes
Driving Partner Activation with ABM
Article
|
8
 minutes
Using Composable Ecosystem Management To Break Down Market Silos
Article
|
8
 minutes