There's a document that sits at the center of every partnership. It's the joint value proposition — the story of why this partnership exists, what the two companies do better together than separately, and what that creates for a shared customer.

It's also the document I see treated with the least respect in most partner programs.

The pattern is consistent. A new partnership gets signed. Two marketing teams spend a few weeks aligning on positioning. They produce a JVP — usually a slide, sometimes a one-pager, occasionally a longer messaging house. Everyone agrees it's good. It gets shared in a kickoff meeting. And then, more often than not, it gets filed somewhere and never opened again.

A quarter later, someone is building a webinar with that partner and asks the question that exposes the whole problem: wait, what was our joint value proposition again?

Why the JVP Keeps Getting Treated as a Deliverable

Most partner programs are structured around discrete deliverables. Onboarding pack. Partner portal. Tier badges. MDF process. Co-sell motion. Each one gets built, gets handed off, and gets considered "done."

The JVP gets caught up in that same model. It's a deliverable. It's something that needs to exist so we can say we have one. Once it exists, the task is complete.

The problem is that the JVP isn't actually a deliverable. It's a foundation. Every co-marketing campaign, every co-sell talking point, every partner-facing event, every enablement asset should be building off of it. When it's static, every downstream effort starts from scratch — or worse, starts from a slightly different version of the story each time. Which is how you end up with three different elevator pitches for the same partnership depending on who's in the room.

What "Living Document" Actually Means

The shift I'm starting to see in the most mature programs is treating the JVP as living infrastructure rather than a one-time output.

That means a few specific things in practice.

The JVP gets versioned and dated. If a partner releases a new product, if your company launches a new use case, if an industry shift moves the buyer's priority — the JVP gets updated. Not in a six-month review cycle. In real time, as the inputs change.

It's the source of truth for downstream assets. When the partner marketing team builds a campaign, the messaging traces back to the JVP. When sales builds a co-sell talk track, it traces back to the JVP. When the partner manager runs a QBR, the JVP is on the table. Everything builds from it instead of around it.

It's queryable, not just openable. A JVP locked inside a PDF on a shared drive isn't operational. It needs to live somewhere that internal teams, partner-facing tools, and partners themselves can actually pull from. That's a content-architecture problem before it's a tooling problem.

It captures the joint planning context, not just the messaging. A great JVP isn't only "here's what we say together." It's also "here's who we sell to together, here's the buyer pain we solve, here's the segment we're aligned on, here's the moment in the customer journey where we add value." That's the layer that makes downstream execution work.

Why This Matters More Now

The reason the static-JVP problem is becoming urgent — rather than just annoying — is that the rest of the partner program is starting to operate at AI speed.

Partner managers are using AI to draft co-sell emails. Marketing teams are using AI to generate campaign briefs. Sellers are asking AI tools to summarize what a partner does and why this deal benefits from their involvement. All of those workflows are pulling from somewhere. If that somewhere is a six-month-old slide nobody updated, the output is going to be six-month-old positioning at high speed.

The partner programs that win the next phase won't only be the ones with the best agents and the cleanest workflows. They'll be the ones whose underlying content — joint value propositions, joint marketing plans, partner profiles, co-sell playbooks — is being maintained as a living foundation. Static foundations produce stale outputs no matter how good the technology layered on top is.

What to Do This Quarter

If you're running or building a partner program right now, the JVP is one of the highest-leverage places to look.

Pick your top three to five partners. Pull up the joint value proposition for each one. Ask three questions: When was this last updated? Is the team that builds downstream assets actually using it? If a new partner manager joined this week, could they find it, understand it, and act on it?

If the answers are "I'm not sure," "not really," and "probably not" — that's the work. Before any agent. Before any new tool. Just the discipline of treating the JVP as the foundation it actually is.

The shift isn't dramatic. It's deciding that the most important document in the partnership deserves more than a folder.

Have thoughts on this? Connect with me on LinkedIn.