This guide covers every pricing model available on AWS, Azure, and GCP marketplaces — flat-rate, per-seat, usage-based, BYOL, and private offers — and gives you a decision framework for choosing the right one. It is written for ISV founders, VP Sales, and partnership leaders who are preparing their first listing or re-evaluating an existing pricing structure that is not converting.

The 5 Pricing Models Available on Cloud Marketplaces

Cloud marketplaces support five distinct pricing models. Each maps to a different buyer expectation, billing relationship, and technical integration requirement.

Choosing the wrong one is the single most common pricing mistake Aein Esk has seen in working with 60+ ISVs through listing and go-to-market on AWS, Azure, and GCP — and it is the mistake that is hardest to fix after your listing is live.

Flat-Rate Subscription

The simplest model. You define tiers — Starter, Professional, Enterprise — with a fixed monthly or annual price for each. Buyers know exactly what they will pay before they commit.

This model works well when your product delivers consistent value regardless of how much a buyer uses it, and when your ICP skews toward SMB or mid-market buyers who want budget predictability. It performs poorly for products where usage varies dramatically across customers.

Per-Seat Pricing

Buyers pay a fixed rate per licensed user per month. Common in security, productivity, and collaboration tools where value is clearly tied to the number of people using the product.

The challenge on cloud marketplaces is seat count management: customers expect to be able to add or remove seats without friction, and your marketplace integration needs to handle entitlement updates accordingly.

Usage-Based (Metered) Pricing

The most powerful model for infrastructure and API-first products, and the most technically demanding. You define one or more billing dimensions — API calls, gigabytes of data processed, events ingested, model inferences — and charge customers based on actual consumption.

AWS, Azure, and GCP all have dedicated metering APIs that your application must call to report usage in near real time. We cover this model in depth in the section below.

BYOL (Bring Your Own License)

Primarily used for ISVs migrating an existing on-premises product to a cloud deployment model. The marketplace handles the packaging and deployment; billing continues through your existing license agreement.

BYOL listings are technically simpler but do not benefit from the marketplace's committed spend draw-down, which is increasingly where enterprise buyers want to transact.

Contract and Private Offers

Private offers let you deviate from your public listing price for a specific buyer. You define custom pricing, contract duration, payment schedule, and terms — and the buyer transacts through the marketplace with those bespoke terms.

Deals still count against the buyer's committed cloud spend. We cover the private offer mechanics in a dedicated section below.

How to Choose the Right Pricing Model: A Decision Framework

The right pricing model is determined by three things: how your product delivers value, how your buyers are evaluated internally, and what the committed spend dynamics look like for your ICP. Getting all three right is what separates marketplace listings that drive revenue from listings that generate impressions but no transactions.

Step 1 — Map Value to a Billable Unit

Ask: what does a customer get more of when they use your product more? If the answer is a discrete, countable output — API responses, processed documents, ingested events — usage-based metering aligns your revenue with the value delivered.

If the answer is access to a capability that does not change with consumption — a security scanner running continuously, a compliance dashboard — flat-rate or per-seat pricing makes more sense.

Step 2 — Understand Your Buyer's Budget Model

SMB buyers optimize for predictability. They want to know what the invoice will be before they sign.

Usage-based pricing creates budget anxiety in buyers who cannot forecast consumption. For this segment, flat-rate tiers with clearly defined feature gates outperform metered models even if metered pricing would be lower for their actual usage.

Enterprise buyers are increasingly evaluated on consumption of committed cloud spend. For this segment, any model that transacts through the marketplace — flat-rate, metered, or private offer — is preferable to a direct purchase, because the marketplace transaction draws down their MACC, EDP, or CUDS commitment.

The model matters less than the fact of transacting through the marketplace.

Step 3 — Assess Your Engineering Capacity for Metering

Usage-based pricing requires a production-grade metering pipeline: event buffering, retry logic, idempotent submissions, and reconciliation against marketplace billing records. Building this from scratch takes a senior engineering team three to four weeks.

If your engineering organization cannot absorb that investment right now, start with flat-rate or per-seat pricing and migrate to metered billing once your listing is generating revenue. Automatum's platform handles the metering infrastructure without requiring your engineering team to build or maintain it.

Usage-Based Metered Pricing: What You Need to Know Before You Commit

Metered pricing on cloud marketplaces is billed in near real time against dimensions you define at listing time. AWS uses the Marketplace Metering Service; Azure uses the Commercial Marketplace metering API; GCP uses the Cloud Commerce Procurement API.

Each has different event schemas, different submission cadences, and different reconciliation behaviors — they are not interchangeable.

Defining Your Metering Dimensions

A dimension is the unit you charge for. You can define up to 24 dimensions on AWS and similar limits on Azure and GCP. Common dimensions include:

• API calls — per 1,000 requests processed
• Data volume — per GB ingested, stored, or transferred
• Events — per event record processed or enriched
• Compute units — per hour of model inference or processing job
• Active users — per unique user who triggered a session in the billing period

Keep dimensions to the minimum needed to capture value. Listings with five or more dimensions confuse buyers and complicate reconciliation. Most successful metered listings use one or two dimensions.

Reporting Cadence and Late Records

AWS requires usage records to be submitted within six hours of consumption. Records submitted after the six-hour window are rejected and the usage is not billed — which means revenue is lost with no path to recovery.

Azure and GCP have similar window requirements. Your metering pipeline must be reliable enough that a server restart, network partition, or deployment event does not cause a reporting gap.

Reconciliation

At the end of each billing period, compare your internal usage logs against what the marketplace reported to the customer. Discrepancies happen — clock drift, network timeouts, race conditions in your submission logic.

Catching a 5% reconciliation gap on a $200K annual customer means $10,000 in recovered or corrected revenue. Without a reconciliation process, that gap is invisible.

How Marketplace Fees Affect Your Pricing

Every cloud marketplace charges a commission on transactions. The standard rate is 3% on AWS (for SaaS listings enrolled in ISV Accelerate — otherwise up to 5%), 3% on Azure, and 3% on GCP. The fee is taken before disbursement; you receive the net amount.

The practical implication: if you want to net $97 on a $100 deal, the marketplace math works out. But if your public pricing is already at the floor of your target gross margin, a 3–5% fee creates a margin problem at scale.

The correct approach is to build the marketplace fee into your pricing before you publish the listing — not to treat it as an unexpected cost after transactions start flowing.

How to Bake In the Fee Without Losing Competitive Edge

A 3% fee on a SaaS product priced at $50,000 per year is $1,500. That is not a number that should drive your pricing decision. The real variable is whether the marketplace channel reduces your customer acquisition cost.

In our experience working with ISVs, marketplace deals close 30–40% faster than equivalent direct deals because procurement routing through a master cloud agreement eliminates the new vendor evaluation step. A faster close at a 3% fee structure has a higher net present value than a slower direct close with no fee.

Build the fee into your list pricing by incorporating it as a standard cost of sale, the same way you would factor in Salesforce licenses or commissions. Most ISVs who account for it correctly find that the fee has no material impact on their go-to-market price point.

Private Offer Pricing: When and How to Deviate from Your Public Listing

A private offer is a custom-priced, custom-termed transaction issued directly to a specific buyer through the marketplace. It appears in the buyer's marketplace dashboard, transacts against their committed spend, and is billed through the marketplace's standard payment infrastructure — but the price, duration, and terms are negotiated between you and the buyer outside the public listing.

When to Use a Private Offer

• The deal size is large enough to warrant custom pricing (typically $50K+ ARR)
• The buyer wants a multi-year term that your public listing does not expose
• The buyer's procurement team requires payment milestones instead of auto-renewal
• The buyer is using a reseller or channel partner under a CPPO or MPO structure
• You are giving a renewal discount to an existing customer without changing your public price

What Private Offers Do Not Change

The marketplace fee still applies. Private offers transact through the same billing infrastructure as public purchases — the cloud provider still takes their 3–5% on the negotiated price.

This is often misunderstood: private offers do not give you a fee waiver, they give you pricing flexibility while keeping the transaction inside the marketplace ecosystem.

We have seen ISVs leave 20–30% of deal value on the table by issuing custom invoices directly instead of private offers — losing the committed spend draw-down for the buyer, losing the co-sell credit for the cloud provider's field team, and losing the transaction history that strengthens future co-sell relationships.

How Buyers Think About Price When Using Committed Cloud Spend

Enterprise buyers signing commitments with AWS (EDP — Enterprise Discount Program), Azure (MACC — Microsoft Azure Consumption Commitment), or GCP (CUDS — Committed Use Discounts) face a specific financial dynamic: the committed spend must be consumed or it is forfeited. Unused commitment at the end of a contract period is money left on the table.

This creates a buying environment where your price is evaluated not against a line-item budget, but against the alternative of not spending the committed dollars at all. In this context, a buyer who has $500K of uncommitted Azure spend at the end of a fiscal quarter is highly motivated to find software they can purchase through the Azure Marketplace to apply that spend.

Your pricing does not need to compete with free — it needs to be compelling enough to move faster than the alternatives available in the same marketplace.

The implication for your pricing strategy: products priced between $25K and $250K per year are in the sweet spot for committed spend deployment. Products priced below $10K are often not worth the procurement routing overhead relative to the benefit.

Products priced above $500K typically require private offer structures and executive-level engagement on the buyer side.

Common Pricing Mistakes ISVs Make on Cloud Marketplaces

These are patterns we have seen repeatedly across 60+ ISV listings. None of them are fatal after the fact, but all of them are costly to unwind.

Mistake 1: Too Many Tiers and Dimensions

A listing with six pricing tiers and four metering dimensions is not sophisticated — it is confusing. Buyers evaluating your product in a marketplace do not have a procurement team to analyze pricing complexity.

They are comparing options in a category view. Listings that communicate price clearly and simply convert at higher rates than listings that require a call with your sales team to decode the pricing page.

The practical rule: start with two or three tiers and one primary metering dimension. You can add complexity after you understand how buyers are actually engaging with the listing.

Mistake 2: Pricing Below Your Direct Channel

Some ISVs price their marketplace listing below their direct sales price, reasoning that the marketplace is a self-serve channel and should be cheaper. This creates a channel conflict that your enterprise sales team will notice immediately.

When a buyer can buy through the marketplace for 20% less than your sales rep quoted, the sales rep loses trust in the pricing and starts discounting the direct price to stay competitive.

The correct approach: marketplace price equals or closely approximates your direct list price. Volume discounts and custom terms go through private offers. This preserves the integrity of both channels.

Mistake 3: Not Accounting for Committed Spend Draw-Down in Deal Qualification

When a buyer has $2M of uncommitted AWS EDP spend and your product is $200K per year, the draw-down dynamic is part of your value proposition — not a footnote. ISVs who do not train their sales teams to lead with the committed spend angle are losing deals to competitors who do.

Buyers who understand that their marketplace purchase counts against committed spend they were going to spend anyway will move faster than buyers evaluating a pure price comparison.

Mistake 4: Setting Prices Without Testing Private Offer Willingness

Your public listing price anchors buyer expectations, but most enterprise deals ultimately close as private offers. If you set your public price at the same level as what you would offer a whale account in a private offer, you are leaving no room to negotiate.

Set public list prices at full rate and reserve discounts, multi-year incentives, and custom terms for the private offer layer.