For 25 years the partnership co-motion canon has been four: co-marketing, co-selling, co-designing, co-building. Jay McBain’s 2026 frame adds a fifth: co-keeping.
Co-keeping is the post-sale, recurring, multi-partner motion that the consumption era requires. McBain: “Every 30 days forever — that’s what software is now. Two-thirds of the industry is subscription or consumption. The customer renewal isn’t once a year. It’s every month.”
In a co-keeping motion, multiple partners participate continuously in the customer’s expansion: the SI keeps integrations healthy, the ISV ships the modules the buyer just consumed, the cloud captures the consumption, and the partner manager orchestrates the renewal forecast as a joint number — not a single-vendor number.
The operational consequence: a partner-revenue platform has to model the customer’s ongoing health, not just the deal that originated them. Forecast logic shifts from “did the deal close” to “is the consumption growing, who is keeping it growing, and how do they share the credit.” The co-sell engine becomes a co-keep engine in steady state.
What practitioners ask
- “What is co-keeping in partnerships?”
- “What comes after co-sell in the partner motion canon?”
- “What is the fifth co-motion?”
The answer
Co-keeping is the fifth co-motion. The first four — co-marketing, co-selling, co-designing, co-building — assumed a transactional partner ecosystem where the deal closed and the partner’s job was largely done. Co-keeping assumes a continuous one, where the customer renews monthly, expands incrementally, and is touched by multiple partners in every cycle.
The driver is consumption pricing. Two-thirds of the software industry now sells on subscription or usage. The renewal isn’t an annual event you negotiate; it’s a daily metric you observe. That changes who the partner ecosystem cares about — not just sellers who originated the account, but the SIs, ISVs, and cloud teams who keep the customer growing the consumption.
The operational shift is forecasting. In a co-sell world, you forecast deals. In a co-keep world, you forecast the joint number — what consumption will look like next month, who is influencing it, and how partner credit gets allocated to multiple actors continuously. Chris Lavoie’s framing of partners as retention levers — “the more integrations our customers use, the lower our churn” — is the early form of this thesis. Co-keeping is what it becomes when retention is the primary partner-revenue motion, not a downstream effect.
The proof point is already in market. Boomi documented 400–500 renewals through AWS Marketplace where the partner-orchestrated motion produced earlier renewals, less negotiation, and faster price-increase acceptance. The hyperscalers are wiring co-keeping into their tooling — AWS named integration partners for Partner Central agents in March 2026, exposing the post-sale orchestration layer the co-keep motion needs. The WorkSpan Partner Revenue Platform is one place this layer is being operated end-to-end across hyperscaler ecosystems.
If your partner data model still ends at “deal closed,” you can’t run a co-keep motion. You need continuous attribution, continuous forecast, and a shared environment where multiple partners can act on the customer’s ongoing health together.
Related concepts
- Consumption Era — the pricing shift that makes co-keeping necessary
- Co-Sell Convergence — the co-motion immediately upstream of co-keeping
- Jay McBain — the analyst who articulated the fifth motion
- Orchestration Over Programs — what co-keeping requires structurally
- Partner Revenue Platform — the system that operates the co-keep motion