Why Most Co-Selling Motions Fail Before the First Joint Meeting

A partner rep and a direct AE agree to co-sell a deal. They have a great briefing call. They both say the right things. Six weeks later, the deal is stuck at procurement, they have not spoken in a month, and the customer is going with the competitor because they got a coherent pricing conversation and yours had two owners with different numbers.

Co-selling does not fail in the customer conversation. It fails in the internal handoffs before, during, and after. Here is where those failures happen, and the operating cadence that prevents them.

What actually breaks in a co-sell motion?

Three specific handoff points, in order of frequency.

• The initial deal briefing. Both sides walk out with different mental models of who owns what. The AE thinks the partner will run technical validation. The partner thinks the AE will drive the executive sponsor conversation. Neither happens.
• The mid-cycle stakeholder shift. A new procurement lead joins the buying committee, or a technical objection surfaces. One side learns about it, the other does not. Two weeks pass before both sides realize the deal moved.
• The closing negotiation. The AE offers a discount to close by quarter-end. The partner has a different urgency (their commission accrues differently) and is holding line on price. The customer sees two vendors, not one, and the deal loses momentum.

None of these are about capability. They are about coordination cost that nobody's incentive plan actually pays for.

Why is the initial deal briefing where most failures start?

Because most briefings are treated as introductions rather than operating agreements.

The briefing call should produce a written plan with five specific decisions.

1. Single-thread owner on each side. The AE from your team, the partner rep from theirs. Both named, both on every future communication.
2. Role assignment for the deal. Who runs discovery, who runs the demo, who leads the pricing conversation, who handles procurement. Not "we'll figure it out"; specifically written down.
3. Communication cadence. Weekly sync, day and time locked, who dials whom, what happens if it gets skipped.
4. CRM record and shared workspace. Where the deal lives (the CRM), where planning notes live (the shared workspace), who has access to what.
5. Escalation path. Who each side escalates to if the counterpart goes dark. Named person, named process.

A briefing that ends without these five decisions is a briefing that produced a lost deal in slow motion.

What does a working weekly sync look like?

Fifteen minutes. Fixed agenda. Never canceled without rescheduling.

• What advanced this week? Each side names one thing that moved forward. If both sides say "nothing," the deal is dying and needs escalation.
• What is blocked? Each side names one specific blocker. Someone owns the unblock by the next sync.
• Who is doing what next? Three or four commitments, each with a named owner and a day-of-week target. Written down, visible in the shared workspace.
• Stakeholder changes. Anyone new on the buyer side, any change in champion, any executive introduction pending.

The fifteen-minute limit is the discipline. If the sync consistently runs over, something is broken structurally: the deal is too complex for weekly touches, or the roles were unclear from the briefing.

Canceling this sync is the strongest single predictor of a lost deal in co-sell motions. If you learn one thing from this post, it is that the calendar entry itself is doing more work than any playbook.

Who owns the CRM record?

The direct AE, always. The partner rep is visible on the record, ideally through a partner portal that shows stage, amount, next steps, and any notes shared for their view.

Trying to give both sides write access to the same CRM record creates three problems.

• Data conflicts. The partner rep updates the stage. The AE updates the amount. Neither sees the other's change, or worse, they overwrite.
• Audit trail confusion. When something goes wrong, who changed what and when becomes unrecoverable.
• CRM governance friction. Your RevOps team has strict field controls for good reasons. Handing partner reps write access to the CRM breaks those controls or requires exceptions that create security risk.

Instead, run a shared workspace outside the CRM for planning: the account plan, the stakeholder map, the meeting notes, the objection log. Both sides write there. The CRM stays the source of truth for stage, amount, and forecast; the workspace stays the collaboration surface.

What does the account plan look like?

One page. Five sections. Updated in the weekly sync.

1. Buying committee. Named people, roles, our champion, their skeptic, the economic buyer, the technical evaluator. Owner from each side per relationship.
2. Value proposition, tailored. The three specific outcomes the customer bought this evaluation to solve for. Refreshed if it changes.
3. Competitive picture. Who else is in the deal, what their strongest angle is, what our shared counter-narrative is.
4. Timeline and milestones. Discovery complete, technical validation complete, business case delivered, procurement engaged, contract executed. Real dates.
5. Risk log. Two or three things that could kill this deal. Owned by whichever side can influence each risk.

Five sections. One page. If your account plan template is longer than that, no one will maintain it, and unmaintained account plans are worse than none.

What incentive design supports co-selling?

If the direct AE's comp plan pays the same for a solo deal as a co-sold deal, they will avoid co-sell. If the partner rep's comp accelerates when they close deals independently, they will avoid co-sell. The default incentive structure on both sides works against joint motion.

Two adjustments help.

• Direct-side. Attach a modifier (typically 1.0x to 1.1x, not lower) on co-sold deals. The AE should not lose money for co-selling; ideally they gain slightly, reflecting that these deals close larger. Never make co-sold deals worth less than solo deals.
• Partner-side. Offer commission or MDF pull-through on co-sold deals that closes the gap between what the partner would have earned selling alone. This is often a fixed dollar bonus per co-sold win, funded from marketing rather than sales budget.

Small adjustments. High leverage. The whole point is that neither side should feel they took a personal loss to make the motion work.

When should you not co-sell?

Three cases where refer or resell beats co-sell.

• Small deals. The coordination overhead is not worth it under a certain deal size. Set a threshold (often $50K to $100K ACV) below which the motion defaults to partner-sourced solo or direct-only.
• Standard implementation. If your product does not require partner delivery expertise, the partner's ongoing involvement adds friction without adding value. Better to accept a referral and move on.
• First-time partners. Co-sell with a partner your team has never worked with before is high-risk. Do referral for the first few deals, then graduate the partner to co-sell once trust and cadence are established.

The mistake is treating co-sell as universally superior. It is a specific motion for a specific class of deal, and using it elsewhere burns team capacity.

The mistake to avoid

The pattern is this: leadership announces a co-sell motion, everyone nods, and then the operating discipline never lands because the coordination cost is invisible until deals start slipping. Co-sell works when the weekly sync is uncancellable, the account plan is maintained, and both sides' incentives make joint motion at least as attractive as going solo. It fails when leadership treats co-sell as a strategic intent rather than an operating cadence. Fix the cadence, or drop the motion. The middle path (announcing without operationalizing) loses more deals than either extreme.