.png)
The first $1 million in marketplace revenue is a proof of concept. It proves the listing works, that enterprise buyers will transact through the channel, and that your product fits the commercial framework of the marketplace. What it does not prove is that you have a scalable marketplace revenue motion. The architecture required to go from $1M to $10M is categorically different from the architecture that produced the first million. Most ISVs do not understand this until they spend 18 months optimising the wrong things.
$163Bn projected hyperscaler marketplace sales by 2030, growing at 29% CAGR from current levels
The $1M to $3M phase - from transactable to repeatable
At sub-$1M marketplace ARR, the primary constraint is almost always pipeline volume. There are not enough deals flowing through the marketplace channel to identify patterns, test offers, or build predictability. The move from $1M to $3M is about making the motion repeatable, establishing the commercial infrastructure that allows you to process deals at volume rather than one at a time.
Private Offers at scale
Direct marketplace purchases at list price work for lower ACV, self-serve transactions. They do not work for enterprise deals. Every ISV that has scaled past $1M in marketplace ARR has done so primarily through Private Offers because Private Offers are the mechanism that makes the marketplace commercially viable for the enterprise deal sizes that drive ARR.
- Speed: Configure standard Private Offer templates for your most common enterprise deal structures so that issuing a customised offer takes hours, not days
- Coverage: Enable Private Offers on all three hyperscalers even if your primary marketplace is one of them, enterprise accounts often have committed spend across multiple clouds
- Velocity: Use Private Offers to compress deal cycles by reducing the number of procurement touchpoints to a single transaction through an already-approved vendor framework
Qualifying your ICP accounts by cloud commitment
Not every enterprise account has the same marketplace procurement incentive. The accounts most likely to transact quickly through the marketplace are the ones approaching their cloud commitment renewal with underspent budgets, or those whose IT procurement teams have been instructed to route software purchases through committed cloud spend wherever possible.
Building a committed spend overlay into your ICP qualification process, identifying which target accounts have AWS EDP, Azure MACC, or Google Cloud committed agreements and what their current utilisation trajectory looks like, converts marketplace pipeline prioritisation from guesswork into a data-informed decision.
$470Bn in enterprise cloud commitments currently held across hyperscaler platforms, the budget pool marketplace transactions draw from
The $3M to $7M phase - co-sell as a systematic revenue source
Reaching $3M in marketplace ARR through direct sales and Private Offers proves the commercial model but it does not yet prove scale. The move from $3M to $7M requires activating a revenue source that does not depend entirely on your own sales capacity: hyperscaler co-sell as a systematic pipeline contributor.
Co-sell-sourced deals are structurally different from directly sourced marketplace deals. They come with an implicit endorsement from the cloud provider's field seller, they typically involve customers who are already deeply committed to the cloud provider's ecosystem, and they close through the marketplace with the procurement speed advantage of a transaction within an existing vendor relationship.
Revenue benchmark: ISVs that achieve IP Co-Sell Eligible status on Azure or Active co-sell status on AWS and invest actively in field seller enablement report co-sell-sourced pipeline representing 30 to 50% of their total marketplace ARR within 18 months of activation. This is not a bonus revenue channel, it is a primary one for ISVs above $3M.
Measuring co-sell contribution correctly
Co-sell contribution measurement is the most commonly broken revenue attribution in ISV go-to-market reporting. The correct metric is not 'deals submitted through the co-sell portal.' It is 'ARR closed on deals where co-sell engagement was part of the sales process, ' tracked from initial submission through marketplace transaction. ISVs that build this attribution correctly make better investment decisions about which co-sell relationships to deepen and which hyperscalers to prioritise.
The $7M to $10M phase - Marketplace amplification
The third scaling phase introduces a distribution multiplier that the first two phases do not require: channel partners transacting on your behalf through marketplace mechanisms. AWS's Channel Partner Private Offer programme and Azure's Cloud Solution Provider programme allow your channel partners to resell your marketplace listing to their own enterprise accounts, creating distribution reach that your direct sales capacity cannot replicate.
50%+ of hyperscaler marketplace sales projected to flow through channel partners by 2027
Enabling channel partner marketplace distribution does not happen automatically. It requires configuring your offer for CPPO on AWS and CSP on Azure, building channel-specific pricing tiers and partner margins, and investing in partner enablement materials that mirror the quality of your field seller co-sell materials. The partners that generate meaningful ISV marketplace revenue are the ones whose own customers have committed cloud spend — and who have been equipped to position the ISV's solution as a committed-spend-eligible purchase in their customer conversations.
What top ISVs do that others do not
The ISVs consistently in the top quartile of marketplace revenue performance share a set of operational behaviours that are invisible from the outside but directly explain their commercial performance.
1. They review listing analytics weekly, not monthly. Marketplace search position, click-through rate, and trial conversion data changes faster than monthly reporting can capture. Weekly review allows rapid response to listing performance degradation before it affects the pipeline.
2. They run A/B testing on listing descriptions, pricing plan names, and trial configuration. Small listing optimisations compound significantly at scale, a 10% improvement in trial conversion rate is worth more at $5M ARR than at $500K.
3. They treat marketplace revenue attribution as a first-class data problem. Every closed deal is tagged with its marketplace touchpoints, co-sell involvement, committed spend utilisation, and Private Offer versus list price transaction type. This data informs every subsequent investment decision.
4. They invest in co-sell enablement at the start of each cloud provider fiscal year, not reactively. The ISVs with the deepest field seller relationships are the ones who showed up with fresh materials and proactive outreach in July, not the ones who requested attention in December.
"The marketplace is not a passive revenue channel that rewards the best product. It rewards the most prepared commercial motion. The listings that scale to $10M and beyond are the ones that have built the infrastructure to deserve that revenue."
Marketplace revenue scales when three conditions are simultaneously true: the commercial infrastructure is configured to close enterprise deals efficiently, the co-sell motion is generating and converting pipeline from the cloud provider's field organisation, and the channel partner layer is distributing the listing to accounts outside the direct sales reach. Each of these is a programme. None of them are features. The ISVs that scale marketplace revenue are the ones that invest in running all three at once.
