How ISVs List Their SaaS on Cloud Marketplaces — and Activate the Channel
Cloud marketplaces have quietly become a procurement requirement rather than a distribution experiment. Enterprise buyers commit annual cloud budgets upfront through agreements like AWS Enterprise Discount Programs, Azure Microsoft Azure Consumption Commitments, and Google Cloud Committed Use Discounts. The mechanism is straightforward: when buyers must spend a committed budget through their cloud vendor, they naturally gravitate to products they can purchase through that same portal. An ISV without a transactable listing is simply not in the running for a meaningful and growing slice of that addressable market.
Why Marketplace Presence Is Now Table Stakes for ISVs
The procurement shift is structural, not cyclical. Buyers who have negotiated large cloud commitments are under internal pressure to consume them — finance teams track utilization against commitment, and software purchases that can be routed through the marketplace help hit that target. AWS and Microsoft have both published data showing that marketplace transaction volumes have grown at double-digit rates year over year, with enterprise deals increasingly the driver.
The implication for ISVs is straightforward. A product that cannot be purchased through the marketplace requires the buyer to go off-budget for that spend — which adds procurement friction and budget-approval steps that a marketplace-listed competitor avoids. The default has shifted: the marketplace listing is now the path of least resistance for the buyer, not a novel option.
Understanding the Three Listing Types
SaaS (Transactable)
A transactable SaaS listing routes payment through the marketplace. The buyer pays the cloud vendor through their standard account billing; the cloud vendor remits to the ISV after deducting the marketplace fee, which typically starts around 20% of gross merchandise value and steps down to 3-5% above certain revenue thresholds. Transactable listings are the only type that enables marketplace budget consumption for the buyer, unlocks co-sell incentives for the ISV, and supports reseller and CPPO transactions through channel partners. For ISVs serious about cloud channel distribution, this is the only listing type worth building toward.
Free Trial / BYOL
Free-trial and bring-your-own-license listings provide marketplace discovery and lead generation without enabling a marketplace transaction. The buyer finds the product in the marketplace catalog, clicks through, and then converts off-marketplace under a direct or partner agreement. This removes the need for metering API integration and speeds time to listing, but it does not count toward the buyer's cloud commitment and does not generate co-sell credit or support CPPO mechanics. It is a useful starting point for ISVs building toward transactable status, but should not be mistaken for a channel-ready listing.
Professional Services Listings
Implementation and advisory work can also be listed on marketplace — a product listing can be accompanied by associated service offerings. Margins on professional services tend to be higher per engagement than on software subscriptions, but volume is lower and discovery is secondary to the product listing itself. Some ISVs use services listings to surface implementation capacity to buyers at the point of product evaluation.
Meeting Onboarding Requirements Before You Apply
The technical and legal onboarding requirements vary by hyperscaler, but they share a common pattern: the technical integration is achievable in four to eight weeks, while legal and compliance review often runs in parallel and proves the longer gate.
On AWS, a transactable SaaS product must integrate with either the AWS Marketplace Metering Service or the Contract Service API to enable metered billing or subscription entitlements. SAML SSO via AWS SSO is strongly preferred. ISVs pursuing co-sell tiers must pass the AWS Foundational Technical Review, a security and architecture assessment. A complete EULA and published support SLA are required before listing.
On Azure, onboarding runs through Azure Partner Center. A transactable SaaS listing requires Azure Active Directory integration for single sign-on and must be designated as MACC-eligible to count toward buyer Azure Consumption Commitment spending. Microsoft conducts a security and privacy review as part of the approval process.
On Google Cloud, ISVs must hold membership in the Google Cloud Partner Advantage program and integrate with the Google Cloud Marketplace procurement API. Discovery Engine compliance governs how the product is surfaced in catalog search.
ISVs that need to build or retrofit marketplace integrations — metering API callbacks, SAML SSO provisioning, entitlement webhooks — often engage an external custom software development team to accelerate the technical onboarding work. The integration surface is well-documented across all three hyperscalers, but execution requires focused engineering capacity that most product teams cannot easily spare mid-sprint.
Designing Pricing for Marketplace Economics
Pricing strategy on marketplace differs from direct pricing in one critical respect: the ISV must model the margin after marketplace fees. AWS's tiered fee structure starts at approximately 20% for most SaaS products and falls to 3% above $50 million in annual marketplace revenue. Azure and Google Cloud have broadly similar fee curves. An ISV that prices its marketplace listing at the same rate as its direct sales price is effectively taking a 15-20% margin reduction without a commercial rationale for doing so.
The major pricing models available — per-seat subscription, usage-based metered billing, and flat-rate annual contract — carry different implications for co-sell eligibility and private offer flexibility. Metered pricing offers the most flexibility for buyers with unpredictable usage but requires robust metering API instrumentation. Flat-rate annual contracts are simpler to administer and align with enterprise procurement preferences, but limit the ISV's ability to offer mid-term expansions as a separate transaction.
Private offers allow ISVs to negotiate custom pricing for specific enterprise accounts, presented to the buyer through their marketplace portal rather than a direct quote. This matters enormously for high ACV deals where a public rate card is just a starting point. Private offers are a distinct mechanism from CPPO — see Cloud Marketplace Private Offers and CPPO for a full treatment of both mechanics and when to use each.
Co-Sell Designation: The Multiplier ISVs Underuse
A transactable listing makes an ISV visible to buyers. Co-sell designation makes the ISV visible to the cloud vendor's own field sellers — and those sellers are compensated to recommend co-sell-eligible products alongside their core cloud services. This is the distribution multiplier that most ISVs with an active listing fail to pursue.
AWS ISV Accelerate is the high-impact co-sell program. Requirements include an active transactable listing, a minimum annual revenue threshold on the marketplace, and customer references. Benefits include AWS seller co-engagement on qualified opportunities, AWS Partner Network credits, and access to a dedicated partner manager. The baseline ISV Partner Path tier is more accessible and serves as the entry point before ISV Accelerate eligibility is reached.
Azure IP Co-sell Ready is the base co-sell tier; Azure IP Co-sell Incentivized is the tier that materially changes partner economics. At the Incentivized tier, Microsoft field sellers receive a financial incentive to recommend the ISV's product — not just permission to, but active motivation to. The distinction between the two tiers is significant and often misunderstood by ISVs who believe they have completed co-sell activation when they reach the Ready designation.
Google Cloud Ready and the Google Cloud Partner Advantage program are less formalized than their AWS and Azure equivalents at present, but GCP's marketplace is growing in transaction volume and the co-sell motion is maturing alongside it. See also Co-Selling with Cloud Vendors for a tactical breakdown of how to engage co-sell programs effectively after achieving designation.
Enabling Channel Partners to Transact Through Your Listing
A transactable listing also enables channel partners to front marketplace transactions on the ISV's behalf. On AWS, this mechanism is the Consulting Partner Private Offer (CPPO): a certified AWS partner creates a private offer from the ISV's listing to an end customer, earns reseller margin on the transaction, and the buyer's payment counts against their AWS EDP. The ISV retains the co-sell credit. Azure's equivalent runs through the indirect CSP model; Google Cloud operates a Reseller Program with similar mechanics. The Cloud Hyperscaler Marketplace Partner Playbook covers these partner-side mechanics in depth.
The ISV's job in enabling this motion is three-fold: establish reseller agreements that define the partner discount structure, protect enough margin to make the transaction worthwhile for the partner, and educate partners on why transacting through the marketplace matters for the ISV's co-sell metrics. The third item is often neglected. Partners default to direct invoicing because it is familiar and because the margin looks the same to them either way. ISVs that explain the co-sell credit implications and offer margin-protected CPPO terms tend to see faster partner adoption of the marketplace transaction path. See also What Partners Actually Need to Sell Your SaaS for a fuller view of how to prepare the channel to transact.
Measuring Marketplace Performance as a Channel Motion
The most important metric is marketplace-attributed ARR, tracked against the ISV's total ARR to understand what share of the business flows through the channel motion. AWS Customer Revenue (ACR) is particularly worth tracking because it counts toward the buyer's EDP utilization — a fact that can be used in enterprise sales conversations to increase the ISV's competitive position when the buyer is under commitment pressure.
Co-sell win rate versus direct win rate reveals whether the field-seller co-engagement is actually producing outcomes. If co-sell opportunities close at the same rate as direct, the co-sell motion may not be additive. If they close higher, that differential justifies the investment in maintaining co-sell designation and engaging AWS or Microsoft field teams proactively.
The attribution gap is a persistent operational problem. Many ISVs cannot reliably connect marketplace-sourced transactions to CRM opportunities because the hyperscaler reporting APIs use different customer identifiers than the ISV's sales system. Closing this gap requires deliberate integration work, but it is the only way to measure the channel motion honestly rather than relying on anecdotal deal stories.
Finally, renewal workflows on marketplace require specific attention. Annual contracts in some hyperscaler configurations auto-renew by default. ISVs need operational processes — owner alerts, CRM renewal tasks, and review windows — to manage expansions and non-renewals before they happen silently in the portal. The ISV that treats the marketplace listing as a passive presence misses most of the economics; the one that wires it into partner, sales, and renewal motions has a structural advantage that compounds over time.
Frequently Asked Questions
Do ISVs have to pay to list on AWS, Azure, or Google Cloud marketplaces?
There is no direct listing fee, but marketplaces charge a transaction fee — typically 3-20% of gross merchandise value, tiered by volume. ISVs fund the listing through margin management rather than a one-time payment.
What is the difference between a transactable listing and a BYOL or free-trial listing?
A transactable listing lets buyers pay through their cloud account, enabling marketplace budget consumption and supporting CPPO and reseller transactions. BYOL and free-trial listings provide discovery and lead generation but do not enable marketplace payments or generate co-sell credit.
How long does marketplace onboarding typically take?
Four to twelve weeks depending on the hyperscaler and the complexity of the technical integration — metering API, SSO, and EULA review. AWS is generally fastest for SaaS; Azure's Partner Center review adds time for MACC eligibility processing.
What is CPPO and how does it let channel partners sell a marketplace-listed product?
Consulting Partner Private Offer (AWS) allows a certified AWS partner to resell an ISV's marketplace listing to an end customer at a custom price, earning reseller margin while the transaction still counts against the buyer's AWS EDP. Azure and GCP have equivalent mechanisms through indirect CSP and the GCP Reseller Program respectively.
Is co-sell designation available to early-stage ISVs?
Base tiers — AWS ISV Partner Path and Azure IP Co-sell Ready — are accessible at relatively low revenue thresholds. The high-impact tiers (AWS ISV Accelerate, Azure IP Co-sell Incentivized) require demonstrated marketplace revenue and customer references, typically achievable after six to eighteen months of active listing with real transactions.