What Is Co-Selling? How Vendors and Partners Work One Deal Together

Most partner models split the work cleanly. A reseller buys and sells. A referral partner passes a name and steps back. Co-selling is different, because two sales teams stay in the deal at the same time. One company owns the product, the other owns the relationship, the integration or the services, and both talk to the customer.

That overlap is why co-selling is attractive and why it's hard. It can win deals neither side would close alone. It can also produce two reps calling the same buyer, arguing over credit, and neither one knowing what the other promised. This article defines the term, separates it from neighbouring models, walks through how the three big cloud vendors document their co-sell programs, and covers the mechanics, crediting and pitfalls.

What Co-Selling Means

Co-selling is a collaborative sales motion in which a vendor and a partner jointly pursue a specific customer opportunity, each contributing something the other lacks. The vendor might bring product depth, executive access or a procurement route. The partner might bring a customer relationship, implementation capacity or a complementary product.

Microsoft's own definition is deliberately broad. Its Partner Center documentation says co-selling is any collaborative engagement between Microsoft and its partner ecosystem, and lists building demand, sales planning, sharing sales leads, accelerating partner-to-partner empowered selling and delivering marketplace-led commerce (Microsoft Learn). That breadth is a useful reminder. In practice "co-sell" covers everything from a single warm introduction to a joint account plan with named sellers on both sides.

Three features separate real co-selling from a loose partnership:

• A named opportunity. The work centres on a specific customer and deal, not a general intent to collaborate.
• Two active sales teams. Both companies assign people to the pursuit.
• Shared visibility. Each side can see the state of the deal, usually through a shared system or a registration record.

Co-Selling vs Resale, Referral and Partner-Sourced Deals

The models get confused because partners often do several at once. The table sorts them by who does what.

Two clarifications matter. First, "partner-sourced" describes where a deal came from, while co-selling describes how it gets worked. A partner-sourced deal can be co-sold, and a vendor-sourced deal can too. Origin and collaboration are separate axes, which is why partner attribution needs separate fields for each.

Second, resale and referral are cleaner to run because one party leads. For a closer comparison of those two, see referral vs affiliate vs reseller. Co-selling is the more demanding model because responsibility is shared, and shared responsibility needs written rules. It's one of the main motions inside a channel sales model and a core mechanic of partner-led growth.

How Hyperscaler Co-Sell Programs Are Structured

The three large cloud vendors run the most formal co-sell programs, and they publish how they work. Read them as examples of structure, not as templates to copy. Programs, thresholds and benefits change, so everything below is as stated on the vendor's pages.

Microsoft: Co-Sell Statuses and Referrals

Microsoft organises co-sell around the solution a partner lists on Microsoft Marketplace. For Azure solutions, its documentation names three co-sell statuses: in-market, co-sell ready and Azure IP co-sell eligible (Microsoft Learn). Each unlocks more.

• Co-sell ready exposes the solution to Microsoft sales teams. The requirements page lists steps such as publishing the offer on Microsoft Marketplace, completing a business profile, providing a sales contact for each co-sell-eligible geography, and submitting listing documents including a one-pager and a pitch deck (Microsoft Learn).
• Azure IP co-sell eligible allows a partner to submit co-sell referrals, and the overview states it lets sales of the offer contribute toward customers' Microsoft Azure Consumption Commitments (Microsoft Learn)., the requirements page asks for at least USD 100,000 of Azure Consumed Revenue or Marketplace Billed Sales over the trailing 12 months, plus technical validation and a transactable Marketplace offer (Microsoft Learn).

The overview also names four categories of co-sell work: with Microsoft sales teams, partner to partner, private deals (sharing what you're working on independently so it shows up in Microsoft's reporting) and solution assessments (Microsoft Learn). Private deals are a useful idea on their own. Even when the vendor isn't helping, telling it what you're working on keeps pipeline data honest.

In the Referrals workspace, a partner creates a deal and invites Microsoft. To see the outcome, the FAQ says to open the deal in Partner Center and check its Microsoft status section. It also lists decline reasons, including that no Microsoft seller directly manages the customer, and notes that no reason is shown if the deal expired before Microsoft responded or the deal value is under USD 25,000 (Microsoft Learn).

AWS: ACE and the Pipeline Manager

AWS runs co-selling through the APN Customer Engagements program, known as ACE. Its documentation says partners in ACE can create, share and receive opportunities for collaboration with AWS (AWS Partner Central). The program page says partners share sales opportunities with AWS through the ACE Pipeline Manager, and encourages them to keep opportunities updated through the life cycle to maximize visibility with AWS Sales (AWS).

AWS's sales guide shows the shared pipeline stages: Prospect, Qualified, Technical validation, Business validation, Committed, Launched and Closed lost (AWS Partner Central). Having both sides use one stage vocabulary is the quiet foundation of the whole system.

The most instructive part is how engagement is decided. The guide says every opportunity is assigned a co-sell motion, which determines who leads it: AWS Field-engaged (the opportunity is matched with an AWS sales team for direct collaboration), Agent-engaged (the AWS Partner Central agent qualifies and enriches it with the partner), or Partner-led (the partner drives it with agent support). Each opportunity also gets a 0 to 100 Opportunity Quality score. AWS states that a higher score may increase the likelihood that an AWS field seller engages, but doesn't guarantee it (AWS Partner Central).

The takeaway: registering a deal isn't the same as getting a seller. The vendor decides how much of its team's time a deal earns, and complete, specific records earn more of it.

Google Cloud: Co-Selling as a Partner Path

Google Cloud's public material is lighter on mechanics. Its partner network page describes a program that rewards real-world efforts like co-selling and technical innovation, and says partner paths are tailored to a business model, whether it focuses on co-selling, services or technology (Google Cloud). Its launch post for the program says it rewards successful co-sell sales efforts, high-quality service delivery and shared innovation with ISVs (Google Cloud blog).

The step-by-step opportunity registration flow sits behind the partner portal, and its details aren't on a public page, so none are cited here. If you're evaluating Google's program, read the current documentation inside the portal, not a summary written for a different program version.

The Mechanics of a Co-Sell Motion

Underneath the vendor-specific forms, the same six steps recur. A vendor-agnostic program will need all of them.

1. Account mapping. Both sides compare target account lists to find overlap: accounts where the vendor has a relationship and the partner has a use case, or the reverse. Most co-sell failures start with skipping this and chasing accounts one side has never touched.
2. Opportunity registration. One side records the deal: customer, problem, estimated value, timing, who's involved. Microsoft's flow has the partner create a deal and invite Microsoft, and AWS's has partners share an opportunity through Pipeline Manager. Deal registration is the general pattern.
3. Acceptance or decline. The other side reviews. Acceptance means a named seller is assigned. Microsoft's FAQ shows declines happen, with reasons attached, and AWS's engagement model shows acceptance is a matter of degree.
4. Roles and rules of engagement. Who contacts the customer? Who owns the proposal, pricing and contract? Who runs the technical validation? These need a written answer per deal, ideally agreed on a first call.
5. Shared pipeline visibility. Both sides update the record as the deal moves, using the same stage names. Stale records are the biggest drain on trust.
6. Close and review. The outcome, win or loss, goes back into the system, and a partner business review looks at what worked.

On the partner side, how you treat inbound requests affects what you get next. Microsoft's FAQ advises responding quickly, being selective about the deals you accept, and reporting estimated deal sizes, closing dates and final statuses, and says it uses that information to provide quality referrals (Microsoft Learn).

Compensation and Incentives

Co-selling only works if the individual sellers on both sides benefit. If a vendor rep gets nothing for helping a partner's deal, the rep will quietly ignore it. Microsoft's overview ties this to its status model: the Business Applications co-sell incentive statuses, Standard and Premium, are described as incentivizing Microsoft sales teams to sell the partner's offer (Microsoft Learn). Confirm exactly how seller quota credit works for co-sold deals in each program, and treat any claim about "quota retirement" with caution until you see it in the program's own terms. For your own program, decide the question explicitly: does a vendor rep get full credit when a partner closes a co-sold deal, and does the partner team get credit when the vendor leads?

How Co-Sold Deals Are Credited

The crediting question has two parts, and mixing them is where disputes start.

Who gets credit for the revenue or pipeline? This is a reporting question. Partner programs usually track sourced, influenced and co-sold contributions separately, and the safe rule is to count each deal once under one primary role. The full treatment is in partner attribution.

Who gets paid, and how much? This is a compensation question. It might involve partner margin, a referral fee or a rebate, and seller commission or quota credit on the vendor's side. These flow from the partner agreement and the rules of engagement, not from the attribution report.

Practical advice:

• Write the credit rule before the first deal, not after the first dispute.
• Record the role each side played (originated, qualified, technical lead, closed), since a single yes or no can't capture a joint deal.
• Keep a dated registration record. When two reps both claim a deal, the timestamp and the notes settle it.
• Review disputed deals quarterly and tighten the rule where it keeps failing.

Pitfalls

Key Facts: Co-Selling

• Microsoft defines co-selling as any collaborative engagement between Microsoft and its partner ecosystem, including building demand, sales planning and sharing sales leads (Microsoft Learn). -, Microsoft's Azure IP co-sell eligibility asks for at least USD 100,000 of Azure Consumed Revenue or Marketplace Billed Sales over the trailing 12 months (Microsoft Learn).
• AWS assigns every opportunity a co-sell motion (AWS Field-engaged, Agent-engaged or Partner-led) and a 0 to 100 Opportunity Quality score, which may raise the likelihood of AWS seller engagement but doesn't guarantee it (AWS Partner Central).
• AWS's shared pipeline runs six stages from Prospect to Launched, plus Closed lost (AWS Partner Central).
• Microsoft's referral FAQ says no decline reason is shown if a deal expired before Microsoft responded or the deal value is under USD 25,000 (Microsoft Learn).
• Google Cloud says its partner program rewards real-world efforts like co-selling, with paths tailored to co-selling, services or technology (Google Cloud).

Channel Conflict

Co-selling puts two sales forces in front of one customer, which is the exact setup for channel conflict. The usual triggers are the vendor's direct team already working the account, two partners claiming the same deal, and discounting that undercuts one side. Rules of engagement that name an owner for each account type prevent most of it. The rest need an escalation path with a decision-maker and a deadline.

Thin Records and Ghost Deals

A registered deal with a one-line description and no next step is a ghost: it exists in the system and nowhere else. AWS's guidance on opportunity hygiene is specific about what good looks like, including naming the customer, workload and delivery model in the title, describing the customer's actual business problem, keeping the stage accurate and writing next steps with an owner and a date (AWS Partner Central). That advice transfers to any program.

Data-Sharing Limits

Sharing pipeline means sharing customer information. Before you do, check what the customer agreement and your partner agreement allow, and share only the fields each side needs to do its part. Internal pricing and margin data usually stay on their own side. If you operate in markets with competition-law constraints on what rivals may exchange, get legal advice on what to put in a shared record, particularly where two partners compete with each other. No specific rule is cited here, because the right answer depends on your jurisdiction and your agreements.

Misaligned Incentives

If the vendor's rep is paid only on direct deals, a co-sold deal is a favour. If the partner's rep is paid only on their own product, the vendor's product is an afterthought. Check both sides' compensation before launching a joint motion, and see partner relationship management for how to keep the day-to-day cadence going.

Co-Selling Without Fit

Co-selling suits specific situations: complex deals, solutions that need integration or services, and accounts where the partner has the relationship. It's a poor fit for simple transactional products. Vendors that sell through independent software vendor partners often co-sell on the vendor's cloud marketplace, while consulting firms co-sell on the strength of implementation capacity.

Related Reading

• What is a partner ecosystem?
• What is co-marketing?
• Cloud and app marketplace listings
• What is ecosystem-led growth?
• Deal registration
• Partner attribution
• Channel conflict
• Partner-led growth
• Channel sales model
• Independent software vendor
• Referral vs affiliate vs reseller
• Partner relationship management