TL;DR — Most partnerships produce logos on slides and nothing else. These ten actually generated revenue. The common thread: a specific commercial structure, not just a press release. Each one has something replicable — if you're willing to do the structural work most companies skip.
Partnership announcements are easy. Revenue from partnerships is rare. I've spent the last fifteen years building, brokering, and advising on partnerships — some worth billions, some that never got past the MoU. The difference between the two is never enthusiasm. It's always structure.
Here are ten that actually worked. Not "worked" in the sense of generating impressions or filling a slide deck. Worked in the sense of money moving.
1. Dell & Atos — turning 30-year rivals into a $3.5B pipeline
This one's mine, so I'll be direct about what happened. Dell and Atos had been competitors for three decades. Different corporate cultures, overlapping enterprise customers, plenty of institutional suspicion. The strategic logic was obvious — their capabilities were genuinely complementary — but strategic logic doesn't close deals. People do.
We didn't start with a joint press release or a partnership framework document. We started with a shared pipeline target — $3.5 billion in incremental pipeline, jointly owned. Every major account had a named lead from each side. Every quarterly review put both teams in the same room looking at the same numbers. The executive sponsors weren't names on a steering committee. They were senior leaders whose reputations depended on this delivering. When blockers appeared — and thirty years of rivalry creates a lot of them — those sponsors cleared them personally. The commercial architecture forced alignment even when the cultures resisted it.
What's replicable: don't start with the relationship. Start with the number. A shared, jointly owned pipeline target changes behaviour in ways that goodwill and MoUs never will.
2. Shopify + Meta — commerce embedded where attention already lives
Shopify's integration with Meta (Facebook and Instagram Shops) works because it eliminated a step. Merchants didn't need to send traffic somewhere else. The purchase happened where the customer already was — inside the social platform — with Shopify handling fulfilment and payments underneath.
The commercial structure is straightforward: transaction-based revenue share. Every sale through a Meta surface that runs on Shopify infrastructure generates revenue for both sides. No complex attribution debates. No "influenced pipeline" hand-waving. A sale happens or it doesn't.
What's replicable: the best partnership structures remove friction from the customer's journey rather than adding a new step. If your partnership requires the customer to do something they weren't already doing, it's fragile.
3. HubSpot's Solutions Partner Programme — building an army that sells for you
HubSpot's partner programme is one of the most effective ecosystem GTM strategies in B2B SaaS. Over 6,000 agency and consulting partners who implement, customise, and — critically — sell HubSpot to their own clients. Partners generate a significant portion of HubSpot's new customer acquisition.
The structure rewards partners for customer retention, not just acquisition. Recurring revenue share that compounds as the customer grows. That alignment is what makes it work — partners are incentivised to ensure customers succeed, not just sign up.
What's replicable: if your product requires implementation or ongoing services, your service partners are your best sales channel. But only if the economics work for them long-term. One-off referral fees create one-off behaviour.
4. Stripe + Salesforce — technical integration as a distribution channel
Stripe's integration with Salesforce Billing turned a payments company into an embedded infrastructure layer inside the world's largest CRM. Salesforce customers processing payments through Stripe don't experience it as a "partnership." They experience it as a feature.
That's the point. The deeper the technical integration, the higher the switching costs, the more durable the revenue. Stripe processes payments. Salesforce gets a more complete billing solution. Neither company is doing the other a favour — both are building a moat.
What's replicable: if you can embed your product inside a platform your customers already use, you've turned a sales motion into a distribution motion. The partnership sells itself through product experience, not through a BD team scheduling joint calls.
5. AWS Marketplace — procurement as a sales shortcut
AWS Marketplace isn't a partnership in the traditional sense. It's infrastructure that makes partnerships unnecessary. Startups list their products on AWS Marketplace. Enterprise buyers purchase through their existing AWS contract — using committed cloud spend they've already budgeted. No new procurement process. No new vendor approval. No six-month security review.
The commercial impact is real. Companies like HashiCorp and Databricks have generated hundreds of millions through marketplace transactions. AWS takes a margin. The seller gets access to enterprise budgets that would otherwise require months of procurement theatre.
What's replicable: find the procurement shortcut. If your partner's customers have pre-committed budget that your product can draw from, you've eliminated the hardest part of enterprise sales — getting the purchase order signed.
6. Shell stakeholder engagement — relationships that unlocked a $19B project
Not every partnership involves two technology companies and a revenue share agreement. Sometimes the most valuable partnerships are about access to rooms that are otherwise closed.
On the Shell Prelude FLNG project — a $19 billion floating LNG facility — we built a stakeholder engagement programme spanning 36 countries. The competitive bid process was essentially closed. The relationships we developed with government stakeholders, local partners, and community leaders across those markets didn't just support the bid. They unlocked it entirely. They turned a closed process into one where our client had a genuine seat at the table. That's what strategic relationships do at their best — they don't generate pipeline in a CRM. They open doors that aren't visible from the outside.
What's replicable: partnerships aren't always about technology integration or revenue share. In complex, high-value deals, the partnership that matters most is the one that gives you access. Invest in relationships before you need them.
7. Microsoft + OpenAI — the defining tech partnership of the decade
Microsoft's multi-billion dollar investment in OpenAI reshaped the AI industry. But strip away the scale and the structure is instructive for smaller companies. Microsoft got exclusive cloud hosting (Azure runs OpenAI's infrastructure) and integration rights (Copilot, Bing, Azure OpenAI Service). OpenAI got capital and distribution through Microsoft's enterprise customer base.
The lesson isn't "invest $13 billion." The lesson is about what each side traded. OpenAI traded exclusivity for distribution. Microsoft traded capital for a technology moat. Each gave up something genuinely valuable — which is why it worked. Partnerships where neither side sacrifices anything tend to produce nothing.
What's replicable: ask what you're willing to give up. Exclusivity, margin, data access, integration priority. If your partnership proposal doesn't require you to sacrifice something, it probably isn't compelling enough for the other side to prioritise.
8. Slack + Salesforce — integration as acquisition prelude
Before Salesforce acquired Slack for $27.7 billion in 2021, the two companies had a deep integration partnership. Slack connected to Salesforce objects — deals, cases, accounts — so that sales and service teams could work in Slack without switching context. The integration drove adoption on both sides.
The commercial logic was clear long before the acquisition. Slack's presence inside Salesforce customers increased stickiness for both products. Salesforce saw that Slack was becoming the collaboration layer for its own customer base — and decided to own it outright rather than risk losing it.
What's replicable: deep integration partnerships can become acquisition pipelines. If your product becomes embedded in a larger platform's workflow, you're either building toward an acquisition or building leverage for a much larger commercial deal. Either outcome is good.
9. Xero + Stripe — complementary products, clean attribution
Xero's integration with Stripe lets small businesses accept payments directly through their accounting software. Invoice goes out, payment comes in, reconciliation happens automatically. Two products that serve the same customer doing different jobs, connected so tightly that the customer barely notices the seam.
The revenue model is clean. Stripe processes the payment and takes its standard transaction fee. Xero gets deeper product engagement and reduced churn — customers who use integrated payments are significantly less likely to leave. No complex revenue share. No attribution arguments. Each company makes money through its own established model, amplified by the other.
What's replicable: the simplest partnership structures often work best. If you and your partner serve the same customer but make money in different ways, you don't need a revenue share at all. You just need a good integration.
10. Machani Robotics + NVIDIA/Google — Tier 1 partnerships from zero
Building partnerships with NVIDIA and Google as an early-stage robotics company isn't supposed to be possible. These are organisations that receive thousands of partnership requests and say yes to a fraction. Machani had no installed base, no enterprise revenue, no leverage in the traditional sense.
What Machani had was a specific, high-value use case — autonomous systems in environments that matter to both NVIDIA and Google's strategic roadmaps. The partnerships weren't built on volume or revenue projections. They were built on strategic relevance. Machani's work validated capabilities that NVIDIA and Google wanted to showcase.
What's replicable: if you're small, don't try to pitch large partners on revenue. Pitch them on strategic narrative. What story does your success help them tell? If you can articulate that clearly, the size gap matters less than you think.
The pattern across all ten
Every one of these partnerships shares something. Not a template — they're too different for that. But a quality. In each case, someone did the hard structural work that most companies skip. They defined the commercial mechanism. They identified who makes money and how. They built the integration or the relationship or the framework that turns a partnership from an announcement into a revenue line.
That's the work. Not the signing ceremony. Not the press release. The architecture underneath.