A public marketplace listing is a storefront. It is good for being found, good for self-serve purchases, and almost irrelevant to how large software deals close.
Enterprise deals close as private offers. If you are planning your marketplace motion around the public listing, you are planning around the smaller half of the channel.
What a public listing cannot do
Your public listing carries standard pricing, standard terms and your standard licence agreement. That is the point — it is buyable without a conversation.
The constraints show up the moment a real deal appears:
- One price for everyone, so no negotiated discount
- Your standard EULA, which enterprise legal teams rarely accept unaltered
- USD only
- No custom payment schedule
- Term options limited to what you published
None of that is a defect. It is simply a different product from a negotiated contract.
What becomes negotiable
A private offer is an offer to one named customer, and almost everything that was fixed becomes adjustable:
- Price, at whatever discount you agree
- Term length and start date
- Payment schedule, including installments rather than one up-front charge
- A custom end-user licence agreement, which in practice is the item that unblocks legal review
- Currency, from a wider set than the public listing’s USD
The legal point deserves emphasis because it is undersold. Being able to attach negotiated terms is often what makes the marketplace viable at all for a large customer. Without it you are asking a procurement team to accept click-through terms on a seven-figure purchase, which they will not do.
The fee structure rewards size and renewal
Private offers are priced by deal size rather than deployment method. Under the structure AWS put in place in January:
- Less than $1M total contract value — 3%
- $1M to less than $10M — 2%
- $10M or more — 1.5%
- All renewals — 1.5%
Two consequences worth internalising.
First, private offer rates ignore deployment method. A public AMI listing carries 20%; the same software sold as a negotiated private offer carries 3% or less. If you sell server products, this is not a rounding difference, it is a reason to think carefully about whether a public listing is where you want volume.
Second, renewals are 1.5% regardless of size. AWS has deliberately priced to keep recurring revenue on the platform. Your second year is cheaper than your first at every deal size, which means the economics improve exactly where your business compounds. We covered the full rate card in what AWS Marketplace actually is.
Selling through a reseller adds a 0.5% uplift, calculated on the wholesale price you give the partner rather than what they charge the customer.
Creating them got less painful this month
AWS reworked the private offer creation experience in May. If your impression of private offers is based on wrestling with the older flow, it is worth looking again — particularly if you had written off doing them at volume because each one took too long to assemble.
That matters more than a usability note usually would, because offer creation time is deal cycle time. An offer that takes three days to produce is three days of a deal sitting still.
Approvals and expiry
Two operational details that cause more lost revenue than any pricing decision.
Approvals. Who in your company can create an offer, and who must sign off on a discount? If the answer is “whoever has the login”, you will eventually discover an offer nobody authorised. If the answer involves four people and a spreadsheet, you have made offer creation the bottleneck.
Expiry. Private offers have an expiration date. An offer the customer never accepted does not sit waiting indefinitely — it lapses, and then somebody has to notice and recreate it. The common failure is not a rejected offer, it is an offer that quietly expired while the champion was on holiday and nobody was tracking it.
Both of these are tracking problems rather than marketplace problems, which is why they are usually nobody’s job.
Renewals are the actual revenue
A first-year deal is a sale. The renewal is the business. And on a marketplace, renewal is a motion you have to run rather than an event that happens.
The change that makes this manageable landed in January: future dated agreements let you create a private offer with a start date in the future. The customer accepts now; entitlement begins when the current term ends.
That separates three things that used to be welded together — when the deal is booked, when the invoice is scheduled, and when the customer starts using the product. Practically, it means you can paper a renewal in the quarter where you have the customer’s attention rather than waiting for the old term to run out and hoping the conversation is still warm.
If you have ever lost a renewal to timing rather than to a competitor, this is the mechanism that fixes it.
What to put in place
Three things, none of them technical:
- A price book for private offers. Discount bands with approval thresholds, so offer creation does not require a meeting.
- An offer register. Every outstanding offer, its expiry date, and who owns the follow-up.
- A renewal calendar built backwards from term end dates, using future dated agreements to book early.
That is the operating layer CloudX’s marketplace platform provides — offers with approvals and renewals tracked as records rather than as emails, and agreements and disbursements in one place across clouds.
The summary
Public listings handle discovery and self-serve. Private offers handle the money, and they come with their own fee curve that rewards size and rewards renewal. Set up approvals and expiry tracking before you need them, and use future dated agreements to stop losing renewals to the calendar.