Across nine practitioner calls the same picture surfaced. Account lists shared by spreadsheet. P2B data manually copied into Salesforce. Partner portal status checked by humans. Calendar coordination via Slack. None of it because anyone wants it that way; all of it because the systems don’t talk.
A partner ops leader at a Fortune 100 industrial OEM described the workflow precisely: “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.”
AI tools — even good ones — accelerate the parts around the manual work: drafting the email that asks for the data, summarizing the data when it arrives, prepping the meeting that discusses the data. The handoff itself stays manual. That is the ceiling.
What practitioners ask
- “Why is partner data still in spreadsheets in 2026?”
- “How do partnerships still run on Slack?”
- “Why is co-sell still manual when every other GTM motion has been automated?”
The answer
The honest diagnosis: partner data is still in spreadsheets because partner systems don’t talk to each other. The CRM has the opportunity. The partner portal has the partner-side status. The hyperscaler console — AWS Partner Central, Microsoft’s Partner Center, Google Cloud’s Partner Advantage — has a third slice. The partner’s own CRM has a fourth. None of them share an authoritative source of truth for the cross-company record. So the lowest-common-denominator interchange — a spreadsheet — fills the gap. Practitioner surveys from Partnership Leaders and ecosystem research from Forrester consistently land on the same finding: a strong majority of partner teams still run account lists, overlap analysis, and pipeline reporting in Excel or Sheets — not because they want to, but because there is nowhere else the data can live and be jointly trusted.
Slack is the second half of the same problem. It is the only system that actually connects two companies in real time, so calendar coordination, deal alerts, partner introductions, and handoffs to the field rep all collapse into Slack channels. That is not a tooling failure. It is the workflow surface that emerges because the systems of record on either side cannot share an authorization model. Slack becomes the cross-company workflow engine by default — fast for humans, invisible to AI, and impossible to audit. The AWS Partner Network blog and the Forrester partner ecosystems coverage both name the symptom (long cycle times, low partner-attach, leaky attribution); the cause is the missing layer underneath.
AI alone does not fix this. AI tools — even good ones — accelerate the parts around the manual work: drafting the email that asks for the data, summarizing the data when it arrives, prepping the meeting that discusses the data. The Agentic Execution handoff itself — submitting the referral, writing partner influence to the opportunity record, choreographing the introduction — stays manual unless an agent is authorized to act inside a sanctioned cross-company space. That is the architectural answer the Industrial OEM P2B practitioner voice keeps surfacing, and it is the gap that closes the Seller Activation Gap.
This is the layer the WorkSpan Partner Revenue Platform is built to provide: a sanctioned shared environment that sits between vendor and partner, with an authorization model both sides have signed off on, where AI agents can act on the data without either company exposing what stays inside their boundary. WorkSpan customers like Boomi use it to compress the manual P2B workflow that defines the Industrial OEM P2B baseline — turning copy-paste-and-Slack into agent-executable motions inside a system the buyer trusts.
Related concepts
- Agentic Execution — what replaces the manual handoff once the authorization model exists
- Seller Activation Gap — the downstream symptom of the manual baseline
- Industrial OEM P2B — the practitioner voice that documents the workflow precisely
- Boomi — a customer outcome that compresses the manual baseline
- Joe Estes — operator commentary on what the manual default costs
- AI-Era Buyer — why the manual baseline can no longer keep up with how buyers shop