Cloud Marketplace Pricing Strategy: How ISVs Get It Right on AWS, Azure, and GCP

Most ISVs price their products for direct sales: a conversation, a proposal, a negotiated contract. When they enter cloud marketplaces, those price points follow them unchanged — and they start underperforming. Marketplace adds a fee layer that compresses net margin, changes the buyer's psychology from negotiation to catalog selection, and ties purchasing decisions to committed-spend draw-down mechanics that direct sales never had to accommodate. The ISVs consistently winning on AWS, Azure, and GCP Marketplace did not adapt their direct-sales pricing to fit the marketplace. They designed pricing for the marketplace's economics first, then back-ported the model to direct. This piece explains how.

Why Marketplace Pricing Is a Different Game

The differences between marketplace and direct sales pricing are structural, not cosmetic. Understanding each one is a prerequisite for designing pricing that actually works in the channel.

Discovery-led buying. In direct sales, the ISV's SDR teams control initial contact and can qualify price expectations before presenting a number. On a marketplace, the buyer discovers the product in a catalog, reads the public price, and forms a reference point before any ISV representative enters the conversation. Price anchoring happens before the sales motion begins.

Marketplace fee layer. AWS Marketplace charges ISVs a transaction fee — typically between 3% and 15% of each transaction depending on product category and agreement type. Azure Marketplace and GCP Marketplace operate on comparable fee structures. ISVs who port direct-sales price points to the marketplace absorb those fees as margin compression with no corresponding change in what the buyer pays. The economics of the product can deteriorate significantly before the ISV notices.

MACC and EDP draw-down mechanics. Enterprise customers with active Azure Consumption Commitments (MACC) or AWS Enterprise Discount Programs (EDP) have a financial incentive to route software purchases through the marketplace: doing so draws down their committed balance rather than representing incremental spend. ISVs whose listings are MACC- or EDP-eligible gain access to budget that a direct-sales motion cannot reach. ISVs whose pricing structure makes them ineligible for those programs simply will not appear in the buyer's shortlist for committed-spend accounts.

Co-sell scoring. Hyperscaler co-sell teams assess ISV listings for quality signals before committing their field time to joint opportunities. Clean, standard SKUs with clear pricing — particularly annual contract options — score better than complex multi-tier catalogs with no public price point. A co-sell team that cannot quote a customer quickly will move on to a listing they can.

The Four Pricing Models and When to Use Each

Subscription (Per Seat / Per Tier / Per Instance)

Subscription pricing charges a fixed amount per user, per tier, or per instance for a defined period — monthly or annually. It is predictable for buyers, easy to compare across vendors in a catalog, and well-suited to SaaS products where value delivery is relatively consistent across accounts. It also integrates cleanly into procurement workflows because the finance team knows the cost before the purchase order is raised.

The risk of subscription pricing is that it undermonetises accounts with disproportionately high usage. A customer with five hundred power users on a per-seat model pays the same effective rate as a customer with ten. If the product's value scales with usage, per-seat pricing leaves revenue on the table at the top of the account.

Consumption / Metered (API Calls, Data Volume, Compute Units)

Metered pricing ties the bill directly to usage: API requests processed, gigabytes stored or transferred, active sessions, model inferences, or any other quantifiable unit the product can measure. The appeal is that revenue scales with value delivered — accounts that extract more value pay more, without requiring a separate negotiation. Metered offers on Azure Marketplace qualify for MACC draw-down once enrolled, and AWS similarly supports metered billing through its Marketplace Metering Service.

The operational cost of metered pricing is significant. It requires the ISV to build and maintain metering infrastructure, integrate with the marketplace's entitlement and metering APIs, and handle the reconciliation of usage data against billing records. The customer-facing risk is billing unpredictability: finance teams at enterprise buyers frequently resist metered pricing because they cannot produce a reliable forecast for the approval process. Building metering hooks that reliably report usage to marketplace APIs is a genuine engineering undertaking that benefits from custom software development purpose-built for entitlement integration. Consuming the AWS Marketplace Metering Service API is not a configuration task; it requires durable, tested integration code.

Annual SaaS Contract

Annual contracts — where the buyer commits to a fixed total for twelve months — represent the largest transaction sizes available through cloud marketplaces and are the primary mechanism for MACC draw-down on Azure and EDP draw-down on AWS. A customer with an active MACC wants to route annual-commitment software purchases through Azure Marketplace specifically because it depletes the balance; an ISV without an annual contract SKU is functionally absent from that buyer's evaluation.

Annual contracts are typically negotiated as private offers: the public catalog price establishes a reference, and the specific enterprise deal is structured as a cloud marketplace private offer with custom payment terms, contract length, or feature scope. This keeps the public catalog clean while accommodating enterprise requirements without broadcasting them.

Free Trial / Freemium Entry

A free tier or time-limited trial reduces friction for self-service discovery — the buyer can evaluate the product without a procurement cycle. In a marketplace context, the trial must be structured as a marketplace-native offer, with the conversion path from trial to paid handled through the marketplace's entitlement system rather than through an out-of-marketplace direct contract. ISVs who convert trial users to paid subscriptions outside the marketplace forfeit committed-spend draw-down eligibility and complicate the co-sell motion for any subsequent enterprise expansion. Keep the trial SKU architecturally separate from the paid committed-spend SKUs; conflation creates entitlement ambiguity that marketplace billing systems handle poorly.

The Private Offer Lever

Public list prices on a marketplace serve two functions that private offers cannot: they establish a price anchor for discovery-led buyers, and they demonstrate the ISV's co-sell eligibility to hyperscaler field teams who assess listings before engaging. But public prices cannot accommodate the variance in enterprise deals — volume discounts, multi-year payment structures, bundled entitlements, or region-specific terms.

Private offers fill that gap. An ISV can maintain a clean public catalog with two or three SKUs while negotiating bespoke enterprise deals as private offers that transact within the marketplace, qualify for MACC/EDP draw-down, and appear in the hyperscaler's co-sell reporting. The full mechanics of private offer structure, including three-party CPPO scenarios where the channel partner needs to be party to the transaction, are covered in the analysis of cloud marketplace private offers and CPPO mechanics.

The practical rule: use the public catalog for discovery and eligibility; use private offers for everything with an enterprise contract attached.

Aligning Pricing to Co-Sell and Committed Spend

Hyperscaler co-sell teams are evaluated on joint pipeline generated, not on how many ISV partners they support. They allocate their time to ISVs whose listings can move quickly in committed-spend accounts. A listing with unclear pricing, no annual contract option, or no MACC/EDP eligibility is a listing the co-sell team will route around.

For Azure specifically, MACC eligibility requires the ISV to enroll the offer in the Azure IP Co-sell program and meet a set of technical and business requirements that Microsoft documents in Partner Center. On AWS, EDP draw-down for ISV software requires the offer to be transacted through AWS Marketplace and the customer's EDP to cover the relevant product categories. The broader mechanics of how committed spend programs reshape partner deal economics are examined in hyperscaler committed spend and the cloud channel.

The practical pricing rule for co-sell alignment: every listing should have at least one public annual-contract SKU. That SKU demonstrates MACC/EDP eligibility, gives the co-sell team a number to quote, and serves as the baseline from which private offer discounts are calculated. ISVs who rely entirely on private offers with no public price anchor are invisible to self-service discovery and difficult for co-sell teams to introduce.

Five Marketplace Pricing Mistakes That Stall ISV Growth

1. Porting direct-sales pricing unchanged. Direct-sales prices were set before accounting for a 3–15% marketplace fee. Listing them unchanged means the ISV either absorbs that fee as margin loss or presents a price point that looks inflated relative to competitors who priced for the marketplace first. Neither outcome is acceptable at scale.
2. Publishing too many SKUs. Marketplace buyers compare options across a short list. More than three or four public tiers generates comparison fatigue and slows the self-service purchase path. Complexity that belongs in an enterprise negotiation belongs in a private offer, not the public catalog.
3. No annual contract SKU. Without a public annual commitment option, the ISV is ineligible for MACC draw-down on Azure and disadvantaged in EDP accounts on AWS. The co-sell team has no quoted price to bring into the committed-spend conversation. This single omission can exclude an ISV from the majority of enterprise marketplace opportunity.
4. Misaligned trial-to-paid path. Free trials that convert to contracts outside the marketplace — through a direct purchase order or a separate billing relationship — create entitlement gaps, bypass co-sell reporting, and forfeit committed-spend eligibility for the resulting account. The entire post-trial path must run through marketplace entitlement hooks.
5. Ignoring pricing in the co-sell brief. When an ISV submits a co-sell referral, the hyperscaler's overlay team needs to understand the pricing structure in thirty seconds. A complex pricing narrative slows the co-sell motion. ISVs who can describe their pricing in two sentences — one public SKU per segment, private offers for custom enterprise — accelerate every joint deal.

A Practical Pricing Architecture for Marketplace ISVs

The following five-step sequence produces a marketplace pricing architecture that serves discovery, committed-spend draw-down, and co-sell alignment simultaneously.

1. Audit your margin after marketplace fee and support cost. Start from the net margin target, not the gross revenue aspiration. Model the post-fee margin at each candidate price point. This number is the floor; no public price that falls below it makes commercial sense regardless of what the market appears to bear.
2. Define two buyer segments. For most ISVs, the relevant segments are self-service SMB buyers (who will transact on a public subscription price without sales involvement) and enterprise accounts (who require a co-sell motion and will close as private offers). The pricing architecture should serve both without conflating them.
3. Map one public SKU per segment. Two public SKUs — one SMB subscription, one enterprise annual contract — is a complete public catalog for most ISVs. The enterprise SKU establishes MACC/EDP eligibility and co-sell quoting; the SMB tier serves discovery and self-service conversion. Private offers handle every enterprise variation from there.
4. Add a consumption tier only if the metering infrastructure already exists. Metered pricing is valuable for usage-correlated products, but the integration work is non-trivial. Do not add a consumption SKU as a planning aspiration; add it when the metering API integration is production-ready and tested against the marketplace billing service.
5. Review against co-sell scorecard feedback every six months. Co-sell teams surface pricing friction in their deal notes. ISVs who close the feedback loop — adjusting SKU structure, price points, or private offer terms in response to what the co-sell overlay reports — improve their co-sell conversion rates over time. Those who treat pricing as a one-time decision find the co-sell motion stagnating as market conditions change.

The ISV listing strategy context — how to get listed, maintain listing quality, and build pipeline through marketplace discovery — is covered separately in ISV cloud marketplace listing strategy. Pricing architecture and listing mechanics are related but distinct disciplines; solving one does not substitute for solving the other.

Common Questions

What is the standard marketplace fee on AWS, Azure, and GCP, and how does it affect ISV pricing? AWS Marketplace charges ISVs a percentage of each transaction, typically between 3% and 15% depending on product category and any negotiated enterprise agreements. Azure Marketplace and GCP Marketplace operate on similar fee structures. ISVs must factor this fee into their net-margin calculation when setting list prices — selling at direct-sales price points without adjustment erodes margin significantly. The practical approach is to model the post-fee margin first, then set list price to preserve the margin target, rather than adding the fee on top of an existing price and hoping buyers will accept the uplift.

Can an ISV list both a public price and a private offer price on the same marketplace? Yes, and most enterprise-focused ISVs do exactly this. The public listing establishes a standard price that serves discovery, co-sell eligibility, and SMB buyers. Private offers allow an ISV to negotiate custom terms — different pricing, payment schedules, contract lengths, or bundled entitlements — for specific enterprise buyers without changing the public catalog. Private offers are transacted within the marketplace, so they still qualify for MACC draw-down on Azure and EDP draw-down on AWS.

Does consumption-based pricing qualify for Azure MACC draw-down? Metered SaaS offers on Azure Marketplace do qualify for Microsoft Azure Consumption Commitment (MACC) draw-down, provided the ISV has enrolled the offer in the MACC-eligible program and the customer's MACC agreement is active. The key requirement is that the offer must be transacted through Azure Marketplace — private billing arrangements outside the marketplace do not count. Consumption offers that go through the marketplace meter and are billed through the Azure invoice qualify automatically once enrolled.

How many pricing tiers should an ISV publish on a cloud marketplace listing? The practical answer for most ISVs is two to three public SKUs: one entry-level or SMB tier, one standard or professional tier, and optionally one enterprise or high-volume tier. More than three tiers generates comparison fatigue for marketplace buyers who are accustomed to selecting from a short list. Enterprise-specific pricing should be handled through private offers rather than additional public tiers — this keeps the public catalog clean and protects list-price discipline.

What is the difference between a per-seat and a metered pricing model for marketplace listings? A per-seat model bills the buyer a fixed amount per user per period — a month or a year. The buyer knows their cost in advance, which simplifies budgeting and procurement approvals. A metered model bills based on actual consumption of a defined unit such as API calls, data processed, or active sessions. Metered pricing scales revenue with value delivered but introduces billing unpredictability that can slow enterprise approvals. Most ISVs with enterprise buyers offer a subscription base price with an optional consumption overage, which gives finance teams a predictable floor and lets high-usage accounts pay more without a separate negotiation.