Chapter 15 · Part 5: Growth

Partnerships and Ecosystems

“If you want to go fast, go alone. If you want to go far, go together.”

— proverb

Two partnerships

In the same year, Brindlepath signed two partnerships that looked equally promising on paper.

The first was with a large consulting firm that advised health systems on care transitions. The firm’s partners loved Brindlepath’s product and agreed to recommend it to their clients. A press release went out. A joint webinar drew a big audience. Twelve months later, the partnership had produced one qualified lead. The consultants were paid for advice, not software, and recommending Brindlepath did nothing for their own targets.

The second was with a regional home-health company that cared for many of the patients Brindlepath’s customers discharged. It began as a modest technical integration: when a navigator assigned a patient to home health, the referral flowed directly into the home-health company’s system, with the discharge summary attached, instead of by fax. Within a year, the home-health company was asking its own hospital partners to adopt Brindlepath, because the integration cut its intake time in half. Three new customers came through that channel.

The difference was not enthusiasm. Both partners were enthusiastic. The difference was that the second partnership created value for both companies, every day, in the normal course of their work. The first depended on goodwill.

Why partner at all

Partnerships extend what a product can do and where it can reach, without building everything yourself. They are worth pursuing when they do at least one of four things:

  1. Complete the product. A partner fills a capability gap your customers need but that is not your core, such as Brindlepath’s integration with a scheduling partner when it retired its own scheduling product in Chapter 7.
  2. Extend reach. A partner gives you access to customers, channels or markets you could not reach efficiently alone.
  3. Strengthen the outcome. A partner sits elsewhere in the customer’s workflow, so connecting to them makes the end result better, as with the home-health integration.
  4. Accelerate innovation. A partner brings technology, data or expertise that lets you build something new faster, such as an AI model provider or a research institution.

Partnerships that do none of these are usually press releases.

Types of partnerships

Partnerships come in several forms, each with different economics and demands.

Technology and integration partners connect products so data and workflows flow between them: record systems, home-health and post-acute providers, identity providers, analytics platforms. They are the most common and often the most valuable, because they make the product more useful every day.

Platform and marketplace partners distribute your product through their ecosystem: an app marketplace attached to a record system, a cloud provider’s marketplace, or a larger vendor’s catalog. They can extend reach dramatically, at the cost of fees, rules and some dependence on the platform owner.

Channel and reseller partners sell your product, often bundled with their own services. They work best when selling your product helps them meet their own goals.

Services and implementation partners help customers deploy and get value from your product. For complex products, they can make implementation scalable.

Strategic and co-development partners build something new together, sharing investment, risk and rewards. They require the most trust and governance.

Choosing the right partners

Partnerships take real time and attention from small teams, so be selective. Before committing, assess each candidate on a few dimensions:

  • Mutual value: what does each side gain, concretely and measurably? If you cannot write down the partner’s gain in one sentence, the partnership will drift.
  • Customer overlap: do you serve the same customers, so that working together helps them?
  • Workflow fit: does the partnership connect naturally to how customers already work?
  • Incentive alignment: does working with you help the partner’s people hit their own targets?
  • Capability and commitment: does the partner have the people, technology and executive sponsorship to follow through?
  • Risk: data sharing, reputation, dependency, competition and regulatory exposure.

The consulting firm in the opening story scored well on customer overlap and poorly on incentive alignment. The home-health company scored well on almost everything, especially workflow fit.

Building the partnership

Once you choose a partner, treat the partnership like a product.

Agree on shared goals and measures. Referrals made, integrations live, patients transferred, time saved, joint revenue. Write them down and review them together.

Start small and prove value. Begin with a pilot: one integration, one region, one shared customer. Expand when it works.

Name owners on both sides. Every partnership needs a person on each side who is accountable for its success and has the authority to make decisions.

Make it easy to work together. Clear technical documentation, a sandbox for testing, simple commercial terms and a regular meeting rhythm.

Get the agreements right. In healthcare, any partnership that involves patient data needs the right data agreements, including business associate agreements where appropriate, as Chapter 11 described. Agree on data use, security, liability, intellectual property and how the partnership can end.

Building an ecosystem

As a product grows, its partnerships can become an ecosystem: a network of partners, customers and developers who build on and around the product. Ecosystems create value that no single company could: more integrations, more use cases, more reasons for customers to stay.

Ecosystems usually grow from a few foundations:

  • Open, well-documented interfaces that partners can build on without lengthy negotiation, using industry standards where they exist, such as HL7 FHIR in healthcare.
  • A partner program with clear tiers, benefits and requirements.
  • A marketplace or directory where customers can find partner integrations.
  • Shared success stories that show customers and prospective partners what is possible.

Brindlepath’s ecosystem began with three integrations and grew to more than twenty in three years: home-health and post-acute providers, transportation services, community organizations that helped patients with food and housing, and analytics partners. Each integration made the core product more valuable to every customer.

Navigating partnership challenges

Even good partnerships hit trouble. The most common problems are predictable.

Misaligned incentives. Priorities shift and the partnership stops serving one side. Review mutual value regularly, not just at signing.

Competing priorities. The partnership is your top priority and the partner’s tenth. Executive sponsorship on both sides helps; so does making the partnership part of each side’s measured goals.

Integration decay. Partners change their systems and integrations break. Monitor every integration, with alerts when data stops flowing, and agree on how changes will be communicated.

Becoming a competitor. A partner may build what you offer, or you may build what they offer. Discuss the boundaries openly and early, and plan for the possibility.

Dependence on a platform. If a large share of your business flows through one platform or marketplace, its rule changes can hurt you badly. Diversify where you can.

Ending well. Some partnerships should end. Plan how customers will be supported, how data will be handled and how integrations will be retired, as Chapter 7 described for products.

Brindlepath in practice: from referral to ecosystem

The home-health integration described at the start of the chapter grew into Brindlepath’s partner program over two years, and the way it grew is instructive.

It began with one integration, built to solve one shared problem: referrals sent by fax lost information and took days. The first version did one thing: when a navigator selected home health for a patient, the referral, with the discharge summary and medication list, appeared in the home-health company’s intake system within minutes. Both companies agreed on two measures, the time from referral to first home visit and the share of referrals that needed a follow-up phone call for missing information, and reviewed them monthly.

The results were strong enough that the home-health company started recommending Brindlepath to the hospitals it worked with, and other post-acute providers began asking for the same integration. Rather than build each one from scratch, Brindlepath turned the work into a standard referral interface based on HL7 FHIR, published its documentation, and created a simple partner program with two tiers: integrated partners, who had built and tested the interface, and strategic partners, who also shared measures and planning with Brindlepath.

The program grew to more than twenty partners: home-health agencies, skilled nursing facilities, transportation services and community organizations that helped patients with food and housing. Each partner integration was monitored, with alerts when referrals stopped flowing, and each had a named owner at Brindlepath.

Two partnerships ended along the way. One partner was acquired by a company that built a competing product; Brindlepath gave customers six months’ notice and helped them move referrals to other providers. Another never produced meaningful referral volume and was retired by mutual agreement. Ending partnerships well, as Chapter 15 recommends, kept the program’s reputation intact.

Common mistakes

Partnering for the press release. Announcements are easy. Partnerships that change nothing in either company’s daily work quietly fade.

Ignoring the partner’s incentives. If working with you does not help your partner’s people hit their targets, enthusiasm will not survive the next quarter.

Too many partners, too soon. Each partnership needs attention. A small company with twenty partners usually has twenty shallow ones.

No owner on either side. Partnerships without a named, accountable person on each side drift as soon as the first sponsor moves on.

Integrations without monitoring. A partner changes an interface, data stops flowing, and nobody notices until customers complain.

Becoming dependent on one platform. When a large share of revenue flows through one marketplace or platform, its rule changes become your crisis.

Try this

List your current and candidate partners. For each, write one sentence on what you gain and one on what they gain, then score them from one to five on customer overlap, workflow fit, incentive alignment and commitment. Any partnership where you cannot write the partner’s sentence, or that scores low on incentive alignment, deserves a frank conversation or a graceful exit. For your strongest partnership, agree on two shared measures and a date to review them together.

How AI changes this

AI model providers are a new kind of critical partner. Many products now depend on third-party AI models. That partnership carries the same questions as any other, mutual value, risk and dependency, plus new ones: how the provider handles your customers’ data, whether it trains on it, how model changes will affect your product’s quality, and what happens if prices change or a model is retired. Treat model providers as strategic partners, and design your product so you can switch providers if you must.

Integrations get easier, and more important. AI tools can help generate integration code and map data between systems, lowering the cost of new integrations. At the same time, AI features are only as good as the data they can reach, so integrations that bring in more context become more valuable.

AI agents will act across partner boundaries. As customers adopt AI agents that work across several systems, partnerships will increasingly be about how agents from different vendors can safely work together: what data they can exchange, what actions they can take, and who is accountable when something goes wrong. Emerging standards, such as protocols for connecting AI assistants to tools and data, are worth watching.

Partnership management benefits from AI too. Assistants can monitor partner integrations, summarize partner performance before reviews and spot co-selling opportunities across shared customers.

Chapter checklist