.png)
89% of companies are listed on a cloud marketplace. Only 22% generate more than 20% of revenue through it.
That gap, between presence and performance, is the defining strategic problem in cloud marketplace go-to-market in 2026. The listing is not an achievement. It is the starting point. And the chasm between a marketplace listing and a marketplace channel is where the majority of ISVs are currently stuck.
Co-selling is supposed to be the bridge. In theory: the ISV brings a deal, the cloud provider's field seller endorses it, the enterprise buyer transacts through the marketplace, and everyone wins. In practice, the majority of co-sell programmes underperform because the ISV has mistaken activity for strategy. They are submitting referrals. They are not co-selling.
The distinction that changes everything: co-sell as a relationship, not a transaction
The most important strategic reframe in cloud marketplace co-sell is this: co-sell is not a lead generation programme. It is a long-term joint go-to-market partnership with a field organisation that has its own quotas, its own priorities, and its own definition of a good deal. ISVs that treat co-sell as a referral-submission workflow are optimising for a metric, submissions accepted, that is entirely disconnected from the outcome they actually want: revenue closed.
The question that separates high-performing co-sell ISVs from average ones is not 'how many referrals have we submitted this quarter?' It is 'how many Microsoft or AWS field sellers know our product well enough to mention it in a customer conversation without prompting?' That number is the real measure of co-sell health.
"59% of companies report higher win rates on co-sell deals. The ones in the other 41% are co-selling, they are just doing it as an administrative exercise rather than a sales motion."
59% of ISVs report higher win rates on co-sell deals vs non-co-sell deals
The co-sell framework that high performers actually use
The ISVs generating consistent co-sell revenue operate within a structured framework that most of their peers do not have. It is not complex. But it requires deliberate investment in three areas that are systematically underinvested by ISVs focused on building their listing and submitting referrals.
1. Field seller alignment before deal submission
The highest-impact co-sell activity is not submitting a referral. It is building a relationship with the regional Microsoft or AWS field seller before you need them to act on a specific deal. ISVs that invest in quarterly briefings with regional field teams, partner-facing webinars that explain their solution in the cloud provider's language, and joint pipeline reviews that give field sellers visibility into the ISV's enterprise accounts consistently receive more proactive deal routing than those who only appear in the system when they need something.
2. Co-sell materials written for the cloud seller, not the end customer
A field seller presenting your product to a customer needs to answer three questions in under 60 seconds: what does this product do, which of my customers should have it, and why should they buy it today rather than next quarter. If your co-sell brief does not answer all three, concisely, in the cloud provider's commercial language, the seller will move on to an ISV whose materials do the work for them.
- Solution brief format: One-page solution brief structured around the cloud provider's current campaign priorities, not your own messaging hierarchy
- Pitch deck structure: A pitch deck with two slides maximum on product overview and three slides minimum on customer business outcomes and relevant use cases for the seller's customer segment
- Customer success stories: Two verified customer success stories with quantified outcomes and documented Azure or AWS consumption impact, formatted for the seller to share directly
3. Opportunity qualification before co-sell submission
Every low-quality or poorly scoped co-sell submission that an AWS or Microsoft field seller receives from an ISV costs that ISV trust and prioritisation. Field sellers have limited time and operate against their own quota pressure. An ISV that consistently submits well-qualified, complete, commercially relevant referrals will receive more attention, faster responses, and more proactive engagement than an ISV that submits volume.
The five mistakes that explain most co-sell underperformance
The mistakes that separate the 22% who generate serious marketplace revenue from the 67% who have a listing and minimal results are not subtle.
1. Submitting co-sell referrals with incomplete or inconsistent data. Validation failures delay acceptance, reduce field seller confidence, and reset engagement momentum. Every submission should be complete and accurate before it leaves your CRM.
2. Treating co-sell as a one-directional referral channel. Co-sell is bidirectional. The ISVs with the highest co-sell win rates are as focused on sourcing and nurturing deals that come from the cloud provider's field organisation as they are on submitting their own pipeline.
3. Neglecting the relationship between co-sell submissions and marketplace readiness. An ISV whose Private Offer infrastructure is not configured, whose listing has no trial option, and whose MACC eligibility is not enabled is sending interested field sellers to a dead end.
4. Measuring co-sell success by submissions accepted rather than revenue influenced. The only co-sell metric that matters is revenue closed on deals where the co-sell motion was part of the process. Track that number from the start.
5. Building a co-sell programme as an activity owned by one person. At scale, co-sell requires RevOps infrastructure, CRM integration with the ACE or Partner Center pipeline, and shared visibility across sales, partnerships, and customer success. A single person managing co-sell manually is a programme waiting to break.
Aligning with cloud provider priorities: the timing dimension
Microsoft operates on a fiscal year that begins in July. AWS operates on a calendar year. Both cloud providers' field sales organisations have defined quarter-end dynamics, campaign priorities that shift by season, and incentive structures that determine which co-sell opportunities receive priority treatment at different points in the year.
ISVs that align their co-sell outreach with these cycles, increasing submission and relationship activity in the weeks before field sellers' quarter-end closes, updating co-sell materials at the start of each new fiscal quarter to reflect the cloud provider's current campaign themes, report materially higher field seller engagement than those treating co-sell as an always-on, time-neutral programme.
Microsoft's fiscal Q1 begins in July. The first 90 days of Microsoft's fiscal year are when field sellers are most receptive to new ISV relationships because they are building their annual pipeline. ISVs that make their strongest co-sell investment in July through September set the relationship foundation that pays returns for the remaining three quarters.
$163Bn projected hyperscaler cloud marketplace sales by 2030, growing from $45Bn in 2025
At $163 billion in projected marketplace transactions by 2030, the strategic question is not whether to build a co-sell programme. It is how long you can afford to operate a co-sell listing instead of a co-sell programme while the ISVs who have made this investment build compounding enterprise relationships that become progressively harder to compete with.
