How to expand a live technology partnership
How to deepen a working SaaS partnership: more scope, a new motion from referral to co-sell, more regions, or a second integration, without pretending activity is growth.
The temptation, once a partnership is live, is to start another one. The cheaper move is usually to expand the one that already works: deeper scope, a second motion, another region, a second integration. That is how a technology partnership gets more valuable. It is also how teams hide. "We are expanding" can mean a real bet, or a new workstream on a still-unused connector.
Expansion is a project on top of a healthy base. The base is adoption, an owner, and a motion you can describe. If those are missing, you do not have an expansion problem. You have a success problem. Read this after you can point at usage or pipeline, not instead of fixing silence.
This post is the menu and the tests. When to deepen the product, when to change the go-to-market motion, when a new region or a second integration is worth it, and how to say not-this-expansion without killing the relationship.
The 60-second version
If you only read one section, read this one:
- Expand what is already working. Flat adoption plus a bigger scope is denial.
- Pick one expansion type at a time. Deeper scope, new motion, new region, or second integration. Not all four.
- A new motion is a change in who sells, not a press release. Referral to co-sell needs a sayable joint value proposition and a seller who will use it.
- A second integration is a second product bet. Score it as if it were a new partner.
- Regions follow demand, not flags on a map. A local champion and a deal, then the kit, then the listing language.
- Write the expansion as a scoped project with owners, a date, and a kill criterion. Put it through the same prioritization as a new logo.
- Hold is a valid expansion decision. Not every live partner should get bigger this quarter.
Confirm the base before you add surface
Run a short gate. If you fail it, stop.
There is a named owner on each side. Weekly active connections are real, or you have sourced or influenced pipeline you can defend. Errors are not the main story. The first motion still has a next step. You are not expanding to rescue a launch that never landed.
| Gate | Pass | Fail |
|---|---|---|
| Adoption or pipeline | Actives or deals you can show | Neither, only a listing |
| Owners | Two humans who still answer | "The partner" as an abstraction |
| First motion | Still described the same way on both sides | Nobody can pitch the original story |
| Reliability | Errors owned, not climbing | Tickets are the relationship |
| Capacity | A real slice for this project | Expansion as leftover evenings |
If you fail the gate, the work is partner success or a freeze, not a bigger footprint. Expanding a stall makes the stall more expensive.
The HBR piece on customer value propositions in business markets is still the right test for a bigger partnership: what value, for whom, compared with what. If you cannot say that for the expansion, you are adding activity.
Four expansion types
Treat these as different projects. They cost different people.
Deeper scope. Same products, more of the workflow. A second object in the sync, write where you only read, a new trigger. This is the cheapest expansion when customers already live in the first slice and are asking for the next step. Scope it like any integration change: stories, acceptance, a beta with the people who already use it.
New motion. Same products, different GTM. The usual path is referral to co-sell, sometimes later a reseller. Read referral, reseller, co-sell before you change the commercial shape. Co-sell needs a co-selling engine you can actually run: account mapping, deal registration, a seller-facing story. A new motion without enablement is a PDF.
New region. Same motion, new people. This fails when you translate a landing page and call it done. It works when a partner team in that region has a deal or a champion, you train them, and support hours make sense. Do not open a region because the partner's HQ asked for global coverage on a slide.
Second integration. A new surface: another product line, another marketplace app, another workflow. Score it as a new deep bet that happens to share a relationship. It will need its own scope, launch, and success owner. Relationship warmth does not reduce engineering cost as much as people hope.
| Type | You are buying | Do not do it if |
|---|---|---|
| Deeper scope | More complete workflow for users you already have | Nobody uses the first slice |
| New motion | More of their sellers in the room | No JVP, no registration, no one to train |
| New region | Local distribution | No champion and no demand in that region |
| Second integration | Another product bet | The first still needs reliability work |
Co-marketing can support any of these. It is not an expansion type by itself.
How to pick which expansion, and how to run it
Pick from evidence, not from what would look good in a QBR deck.
If users are hitting a wall in the workflow, deepen scope. If partner sellers already mention you and then fumble the close, you need a motion and a kit, not more objects in the API. If a specific country team is sending deals, resource that region. If a different product line is showing up in the same accounts, consider a second integration.
Run it through one QBR as a single bet. The QBR joint plan should not contain four expansions. One bet, each side's commitment, a target, a date. Put commercial changes (rev share, MDF, incentives) in the same paper as the motion change so you do not enable co-sell with referral economics, or the reverse.
A simple expansion brief, one page:
- Type and why now (the evidence).
- What will be true in 90 days.
- What you will not do in that window.
- Owners, capacity, dependencies (legal, marketplace, engineering).
- Kill criterion: the number or date that says stop.
Share it with the partner before you staff it. Expansion that is a surprise to their engineering or their regional sales team will stall in week two.
Tiers can help here. Premier gets expansion conversations. Registered does not. That is not unkind. It is how you stop every live listing from demanding a second app.
What not to expand, and how to hold
Hold is an expansion decision. You keep the current scope, you keep it healthy, you do not add surface. Use hold when the base is fine and capacity is not, or when the partner wants a motion you cannot staff, or when the next obvious step is a second integration that fails the score.
Say it in the QBR with the scoreboard, not in a vague "let's revisit." "We will keep invoice sync and referral. We will not open co-sell or a second product this half. Review date is March." That is a professional hold. A smile and no staff is how they feel ignored.
Do not expand into a competitive overlap you are pretending not to see. If they shipped a feature that does your job, a co-sell motion will get weird. Name it. If they want a bigger story and the numbers are dead, that is a sunset conversation, not a second listing.
Common mistakes, and the fix
Expanding to create the adoption you never got. The fix: fix or freeze the first slice. New scope will not teach people to use the old one.
Changing motion and product at the same time. The fix: one type per quarter. Sellers cannot learn a new pitch and a new workflow on the same Friday.
Global rollout as a slide. The fix: one region with a champion, then copy the kit.
A second integration because the alliance manager is friendly. The fix: score it like a new partner. Warmth is not pull.
No kill criterion. The fix: a date and a number in the brief. If neither moves, you held by accident. Write the hold.
Paying more before the motion exists. The fix: incentives follow a working motion, they do not create one.
FAQ
When is a partnership ready to expand? When the first motion has real usage or defensible pipeline, owners still answer, and you can staff one new project. Readiness is evidence plus capacity, not tenure.
Is moving from referral to co-sell always the next step? No. Co-sell is for when their sellers are in deals where your product belongs and they will actually pitch it. Some partners should stay referral forever. That can be a good partnership.
How do we expand into a new region with a tech partner? Find the local team that already has a reason, train them, set support hours, and only then change public language. HQ enthusiasm is not a region.
Who pays for a second integration? Whoever's roadmap it is. Do not assume the partner builds the second one because they built the first, or the reverse. Put it in the brief before anyone writes code.
Can we expand without changing the agreement? Often for deeper scope on the same surface. Usually not for reseller, exclusive regions, or new data uses. Read your agreements before you promise a motion.
What if they want expansion and we want hold? Show the gate table. Offer a review date. A clean hold with a date beats a fake expansion you will not staff.
Should expansion live in OKRs? Yes, as an outcome on that partner (adoption, pipeline, a shipped second slice), not as "expand three partnerships." See partnership OKRs.
How is this different from signing a new partner? You already paid for the relationship and some of the trust. You did not prepay engineering, enablement, or a new motion. Price those honestly.
Further reading
- Go-to-market for the motion change you are actually making.
- Customer value propositions in business markets for whether the bigger story is still a real offer.
- Referral vs reseller vs co-sell for the motion menu.
- Joint value proposition for the sentence a seller needs before co-sell.
- Partner QBR for where the expansion bet should be chosen.
The short version
Expand a live technology partnership only when the first slice is working. Pick one type: deeper scope, a new motion, a new region, or a second integration. Staff it like a project with a brief, owners, and a kill criterion. Hold is allowed. A second motion without a joint story, a region without a champion, or a second app on a dead first app is not expansion. It is a new way to get busy.
If you want a ranked expansion versus new-logo sequence on your current live set, that is what a Partner Audit is for.