Running AI-Native Partnerships

Like digital-native or cloud-native shifts before, we're in a new era where products and companies born post-AI are shaped differently and behave differently than the ones that came before. You can't compete by adding chatbots and agents to an outdated partner motion.

AI-native partnerships leverage AI to accelerate and scale partner execution to serve a market defined by rapid innovation and continuous value exchange.

Chatbot adoption inside partnership organizations is now near-universal. The dominant tools are general-purpose language models — Claude, ChatGPT, Gemini — used mostly for meeting prep, knowledge search, and document drafting. The practitioners doing it well — building reusable workflow automations, running morning call-prep agents, eliminating hours of research — deserve credit.

But the benchmark this measures is whether individuals have gotten faster at the documentation tasks they were already doing. That is not the same thing as AI transforming partnerships as a revenue function. Faster call prep doesn't change how a co-sell motion runs, how sellers activate, or what happens between account overlap and closed revenue. The ceiling on time-saving AI is a few hours saved per week.

Partner operators set a higher bar for AI transformation.

The Market Has Already Moved: Co-Sell Is the Convergence Motion

When software was sold as perpetual licenses, the transaction was the relationship and the partner's job was to move product. Once the check cleared, the work was done.

That model is gone for two-thirds of the industry. Today technology is sold on subscription and consumed on usage. The transaction is now the beginning of the work, not the end of it. Customers don't commit upfront — they commit to the outcome, renewed every quarter.

Jay McBain has tracked this shift across the largest technology companies on earth. The customer relationship transitions post-close into a delivery phase requiring partner involvement — implementation, managed services, adoption, renewal, expansion, and now co-keeping the customer through every renewal cycle. Every partner type is being forced beyond the point of sale. The average enterprise deal now involves 6.3 partners coordinating around a single customer; on large deals, more than ten.

McBain catalogs thirteen distinct co-motions partners now run — co-marketing, co-development, co-sell, co-deliver, co-keeping, and the rest. Co-sell is the convergence motion, because co-sell is where the deal lives. McKinsey estimates roughly $80 trillion in annual ecosystem revenue by 2030. Partnerships are not a side function; they are how enterprise software actually gets sold.

The Partner Leader Becomes a Partner Operator

The shift to co-sell didn't just change how software is sold. It changed what partnership professionals actually have to do. The previous era's job description made internal sense — manage a portfolio of partners, maintain the relationship, administer the program, track certifications, issue MDF, approve deal registrations.

That role doesn't scale in a co-sell world. When the average enterprise deal involves 6.3 partners and the co-sell motion lives in deals opening and closing weekly, the relationship-manager model breaks. The work is fundamentally different: not managing a relationship over time, but deploying the right partner capability against the right deal at the right moment.

Rob Moyer calls this the death of the partner manager and the rise of the Partnership Operator. The operator doesn't maintain relationships — they run systems. Inputs, levers, and loops. Not portfolios and QBRs. The operator's job is to make the co-sell motion repeatable: trigger identification, partner matching, pre-call brief, meeting choreography, log-tag-track. And to know when the system is working — Rob's benchmark is under 60 seconds to find the right partner for a deal stuck at VP level. If it requires a Slack message, the system is manual, not operational.

Sales has known this shift for a decade — sellers spend over 70% of their time in non-selling activity. Partner managers now have the same problem. The new partner manager is focused on deal velocity, working pipeline, and helping the co-sell get to closed-won. The old one was focused on connections, lunch-and-learns, and certifications.

AI Has to Serve the Partnership Operator

The operator's job creates a specific calculus for AI. Time-saving hacks help individuals; they don't change the system. The co-sell motion runs across a CRM that doesn't see the partner's pipeline, a partner portal that doesn't see the seller's deal, and a shared environment that the AE has never logged into. AI that just summarizes documents inside one of those silos cannot move co-sell forward.

Rob Moyer puts the gap precisely:

"There's still a whole lot of people that are bringing their own AI to work, doing the lowest-hanging-fruit AI to make their job better. The actual AI that helps is more as part of a system. The CRM is the system of record. The right tools with the right mindset of partner manager — the AI becomes the system of action. Without it, it's just like time-saving AI hacks."

Moyer names the missing layer. Time-saving AI makes individual operators faster. System-of-action AI changes the function. The distinction is structural, not one of model capability — and for partnerships, the system layer has three specific requirements that general-purpose AI cannot meet. Three bars to clear before partnerships are actually transformed.

01 Live Partner Context AI that can apply your partner playbook to live deals

When a partner manager using ChatGPT has to provide the context on the account, the opportunity, and the partner relationship in every interaction, the human is working to make the agent effective. It's supposed to go the other way.

The research we gathered across nine companies reveals a consistent pattern we're calling manual as default: partnership workflows exist, but they run on Slack threads and spreadsheets, not structured platforms. A partnerships leader at a frontier AI company described their process for ingesting cloud partner data: "We don't log into their partner portal they have. It's just shared through like a Slack or a spreadsheet." A partnerships lead at a mid-market governance/compliance SaaS described account targeting with advisory firm partners as "we'll fill out an Excel sheet, download it to our desktop, send it via email for them to fill out on their end."

The portal exists. The process exists. The data exists. And almost none of it is in a state where AI can act on it, because the data is in Slack, in an email thread, in a spreadsheet someone downloaded to their desktop.

Copying and pasting every referral into ChatGPT is not the answer.

An effective AI-driven motion has a specific architecture, described by Rob Moyer and Chris Lavoie in the Co-Sell Engine: trigger identification → partner matching → pre-call brief → meeting choreography → CRM logging. Every step requires real-time knowledge of deal state, partner capability, and account context. Moyer's standard: "Under 60 seconds to find the right partner for a healthcare deal stuck at VP level. If it requires a Slack message to the partner team, the system is manual, not operational."

The current generation of practitioners is not operating at this standard yet. They are using AI to accelerate the research phase while the execution phase remains fully manual. That is not a criticism — it is an honest description of what's available to them. General-purpose AI tools don't have deal context. The platform layer that provides it is the missing piece.

02 AI That Executes Text generation doesn't change the economics of partnerships

Using chatbots to generate content, summarize information, or prepare documents makes them output tools. They produce text that a human then acts on.

Real AI adoption for partnerships requires AI that acts. Not "draft the referral email" — submit the referral. Not "here are the P2B scores to paste into Salesforce" — write the scores directly to the opportunity record. Not "here's a scheduling email to send" — analyze both calendars, match a time, send the invite, and confirm receipt.

This is agentic execution. Partner operators need co-sell machinery that cuts out the manual steps and catches the missed actions. When it works, partner teams know which deals need co-sell. They know which partners to activate. When it doesn't, the motion stalls because the actual mechanical steps — referral submission, account matching, private offer creation, meeting scheduling — are each small but collectively create enough friction that sellers don't do them.

The evidence from customer calls is unambiguous. A partner ops leader at a Fortune 100 industrial OEM described their propensity to buy (P2B) data workflow: send account list to regional leads, wait for them to run manual lookups, receive data back, manually enter it into a specific Salesforce field. Two human handoffs per batch. The barrier isn't knowledge — everyone knows the P2B data should be in Salesforce. The barrier is that every step requires a person to take an action.

Don't use AI to help with your administrative tasks.
Give AI your administrative tasks.

03 Operate Across the Trust Boundary Partnerships built for agentic execution between two companies

This is the bar the industry hasn't fully articulated yet.

Partnership AI isn't single-company AI. A co-sell motion by definition involves two companies with different CRMs, different security postures, different data governance policies, and different views of the same account. An AI agent that operates inside Company A's Salesforce instance cannot see what Company B knows about that account. It cannot submit a referral to Company B's portal. It cannot receive the acceptance back and update Company A's CRM record. It can only generate text.

The consequence of this architectural reality is visible in the primary research. An alliance leader at a global systems integrator — one of the largest and most AI-forward professional services firms in the world, which has trained tens of thousands of professionals in Claude — described what happens when an AI agent tries to access partnership data:

"That's where the blockers all come in on our side. It's an agent or an outside force acting upon data, and they consider that data to be sacred."

He went further: "How could I use any AI tool, even one that we built ourselves?"

The blocker is not vendor trust. It is the absence of a sanctioned shared environment — a space where both parties have explicitly authorized access, where data governance rules from both companies are enforced, and where AI can act on partnership data without becoming an "outside force."

This is architecturally different from anything general-purpose AI provides today. ChatGPT cannot be given field-level access to two companies' CRM records simultaneously. Claude cannot execute a referral workflow that requires authentication in two partner portals. Google Gemini cannot generate a private offer that passes compliance review at both the ISV and the cloud marketplace simultaneously.

The risk practitioners feel — homegrown automations introducing vulnerabilities they didn't realize they were building in — is the same shape as the architectural one. It isn't a security problem alone. It's that DIY AI tools operating on partnership data do so without the authorization model that enterprise partnerships require. When the firm's IT team blocks an AI agent from touching partner data, they are correct. The agent is not operating in a sanctioned shared environment. It is an outside force.

What's required is a purpose-built execution layer: a space that exists between two companies — not inside one — with enterprise-grade security enforced at the object, team, and field level; with workflows that initiate in one company's CRM, execute in the partner's environment, and return results; and with AI agents that are authorized to act on behalf of both parties because both parties have sanctioned the environment.

The AI era is the partnerships era

Outside of channel sales, complex partnerships were built on relationships — joint roadmap reviews, multi-year alliance commitments, the patient work of two companies learning to trust each other. Trust still holds. What changed is how it's built. The cloud era gave even the most complex alliances a way to encode trust into shared systems and shared data — and the pathway from "we partner" to "we close predictable revenue together" stopped being mysterious. It became infrastructure.

AI isn't a productivity upgrade for partner managers. It's a new capability to accelerate building trusted business relationships — at the scale and speed the AI market demands. That's the role shift. The partner manager becomes the Partnership Operator — accountable not for activity, but for what their partnerships produce. Agents are the operating layer of the function, not a tool a few people use cleverly. Just as sales operators built on CRMs and marketing operators built on ABM platforms, partnership operators build on agents.

The companies that started building this are already showing what it looks like. ClearScale's AWS referrals are 100% automated — at the pace of the deal, not the partner team's calendar. Boomi's marketplace revenue grew 30× in a year. Win rates rise from 22% to 47% when sellers are activated inside the deals they're already working. These aren't predictions. They're the early operating model — the one that defines partner-led efficiency for the AI era.

Sources: WorkSpan interviews — Rob Moyer, BlueThread (4/23/26); Jay McBain, Canalys / Omdia (4/23/26). Primary calls drew on partnership leaders at nine companies across enterprise software, cloud platforms, integration platforms, professional services, and industrial OEMs — including Joe Estes (Boomi). Vault canon: Co-Sell Engine (Moyer/Lavoie), Operator OS, PTM, Partner Revenue Platform, Seller Activation. Customer proof points: ClearScale, Boomi, win-rate shift, $513B pipeline.

WorkSpan's mission is to help businesses achieve more together.

Cloud built the infrastructure of trust between businesses. AI is how that trust scales.

The operators building this layer now are writing the rules everyone else will operate by.