PTM names the act of choreographing three different sales roles — internal seller, internal alliance manager, partner-side rep — across a single deal motion. Each has different incentives, different views of the deal, and different next steps.
Where Co-Sell Engine is the deal-level architecture, PTM is the team-level. Both are required: motion without team coordination is theater; coordination without motion architecture is overhead.
PTM is what makes the seller activation number move. When the field rep, the alliance manager, and the cloud partner rep are all looking at the same deal in the same state, the rep activates. When they’re not, the rep reverts to direct selling — which is exactly the seller-activation gap we see across SAP, ServiceNow, and WorkSpan’s own dormant-seller telemetry.
What practitioners ask
- “What is Partner Team Motion?”
- “What is PTM in partnerships?”
The answer
Partner Team Motion (PTM) is the orchestration layer that coordinates the trio that actually closes a partner-influenced deal: the internal seller, the internal alliance manager, and the partner-side rep. The term originated with Rob Moyer, who articulated PTM as the team-level companion to the Co-Sell Engine. The engine defines the deal-level architecture — trigger, match, brief, meeting, log. PTM defines the team-level choreography that makes those steps fire across three different roles with three different incentives.
The reason PTM exists as a named concept: most “co-sell breakdowns” aren’t engine breakdowns. They’re trio breakdowns. The seller doesn’t know the alliance manager has matched a partner. The alliance manager doesn’t know the partner-side rep is already in the account. The partner-side rep is reading a stale view of the opportunity. Each role is doing their job — and the deal still stalls because no shared state binds them.
PTM is also where seller activation actually moves. When the field rep, the alliance manager, and the cloud partner rep all see the same deal in the same state, the rep co-sells. When the trio is desynced, the rep reverts to direct selling. This is the operational explanation behind the seller-activation gap visible across SAP, ServiceNow, and the broader telemetry Rob Moyer and Chris Lavoie document in The Partnership Operator’s Manual for the AI Era.
A Partner Revenue Platform is what gives PTM a place to run. Without a shared environment across both companies’ systems, the trio cannot share state, and PTM stays a meeting cadence rather than an operational motion.
Use this framework
The PTM choreography — the trio motion behind every co-sell deal
1. MATCH THE TRIO Seller + alliance manager + partner-side rep — identified per deal
2. SYNC THE STATE All three see the same opportunity, same stage, same next step
3. CHOREOGRAPH Route the next action to the role best positioned to execute it
4. LOG TO BOTH Write the outcome to both companies' CRMs — not just one
5. MEASURE Seller-activation rate is the headline metric, not pipeline volume
Operational test: if the trio relies on Slack threads to stay in sync, PTM is a
meeting cadence — not an orchestration layer.Related concepts
- Co-Sell Engine — the deal-level architecture PTM operationalizes at the team level
- Operator OS — the daily system the alliance manager runs to keep PTM live
- Orchestration > Programs — the broader shift from quarterly programs to always-on motion
- Seller Activation Gap — the metric PTM is designed to close
- Rob Moyer — author of the PTM framing
- Partnership Operator — the role that owns the PTM motion