A couple of years ago, I was sitting in a meeting with the CTO of a mid-size security software company. They had a solid product, good customers, growing revenue. They wanted to list on Azure Marketplace because one of their biggest prospects told them, "We can only buy through our Microsoft Enterprise Agreement. If you’re not on the marketplace, we can’t do business."
So they tried. And three months later, they were still trying. Their engineering team had spent weeks figuring out the SaaS fulfillment APIs, webhook integrations, billing reconciliation, and metering. Their product team was frustrated because they’d pulled two developers off the roadmap to work on marketplace plumbing. And they still didn’t have a live listing.
That conversation is basically why SaaSify exists.
What’s Actually Happening With Cloud Marketplaces
If you’re not tracking this space, here’s the short version: Microsoft, AWS, and Google are all pushing hard to get software vendors to sell through their marketplaces.
Why? When a customer buys your software through Azure Marketplace, that spend counts against their MACC (Microsoft Azure Committed Use Discount). They get to burn committed cloud budget on your product instead of letting it sit unused. AWS has similar mechanisms with their Enterprise Discount Programs. For ISVs, this means you’re suddenly accessible to customers with pre-committed budgets they need to spend. And the cloud providers actively co-sell with you, meaning their sales teams bring you into deals.
The numbers back it up. Azure Marketplace partner revenue grew over 100% year-over-year. AWS Marketplace crossed $5 billion in annual customer spend. This isn’t a side channel anymore.
The Problem Nobody Warns You About
Here’s where it gets messy. Listing on a cloud marketplace isn’t like listing on the App Store. You don’t just upload a binary and write a description.
For Azure Marketplace SaaS offers, you need to:
- Build a landing page that handles the marketplace purchase flow
- Implement the SaaS Fulfillment API v2 (webhooks for subscription creation, updates, cancellation, suspension)
- Handle metered billing if your pricing has usage-based components
- Manage private offers for enterprise deals with custom pricing
- Deal with ISV-to-customer billing reconciliation (because the marketplace takes a cut and pays you, and the numbers need to match your own records)
- Get your offer reviewed and approved by Microsoft
AWS Marketplace has its own set of requirements. Different APIs, different billing mechanisms, different offer structures. If you want to be on both marketplaces, you’re essentially building two separate integration stacks.
Most ISVs I talk to massively underestimate this. They think it’s a two-week project. It’s more like two to four months of engineering work, and that’s if your team has done it before. If they haven’t? Add time for figuring out documentation that’s, let’s say, not always clear.
And here’s the kicker: marketplace integration isn’t your product. It’s plumbing. Every week your engineers spend on billing webhooks is a week they’re not spending on the features your customers actually pay for.
What We Built
SaaSify handles the marketplace integration so ISVs don’t have to build it themselves. Let me be specific because "we handle it for you" means nothing without details.
We provide the complete transactable SaaS layer for Azure Marketplace and AWS Marketplace. The ISV’s product stays exactly as it is. We sit between the marketplace and their existing systems. The landing page customers see when they click "Get It Now"? SaaSify generates that. SaaS fulfillment webhooks? Handled. Metered billing? We have an SDK that ISVs call from their app, and we submit usage to the marketplace APIs on schedule (Azure requires hourly metering submissions, and if you miss the window, you can’t bill for it retroactively).
Private offers are a big deal for enterprise sales. An ISV might need custom pricing for a specific customer, with annual commitments or volume discounts. On Azure, this involves Partner Center. On AWS, it’s the Marketplace Management Portal. Both are clunky. SaaSify manages them through a single dashboard.
We also handle co-sell pipeline management. When you’re working on a joint deal with Microsoft or AWS sales, there’s referral and pipeline tracking that needs to happen in Partner Center or ACE (AWS’s partner system). Most ISVs skip this and miss out on co-sell benefits. We automate it.
Why I Care About This
We went through the Azure Marketplace listing process ourselves with CloudLabs. Our team spent weeks debugging webhook retry logic because Azure’s documentation was confusing about idempotency requirements. We dealt with subscription lifecycle edge cases, figured out private offers the hard way.
After all of that, we realized every ISV faces the same problems. Most don’t have the Azure API expertise we’d built up over years. So we productized what we’d learned. It wasn’t a grand strategy. It was "we suffered through this, other people are suffering through this, let’s build something."
What’s Working
We achieved our Microsoft Solutions Partner designation earlier this year. That matters because it signals to Microsoft’s sales teams that we’re a vetted partner they can bring into deals.
Our AWS partnership is growing fast too. We’ve been working closely with the AWS ISV team, and the interest from ISVs who want to add a second marketplace (Azure to AWS or vice versa) has been strong.
The number I’m proudest of: average time from "we want to be on Azure Marketplace" to a live transactable listing with SaaSify is about 2-3 weeks. Without us, that same process typically takes 2-4 months.
Some of the Gotchas
I’d be dishonest if I said marketplace selling is all upside. A few things ISVs should know.
Marketplace fees are real. Azure Marketplace takes a 3% transaction fee (reduced from the previous 20% for co-sell eligible offers, which is good). AWS takes a percentage too, and it varies by category. You need to factor this into your pricing.
Not every customer wants to buy through a marketplace. Some procurement teams prefer direct purchasing. Marketplace should be one of your go-to-market options (probably the fastest-growing one), but not the only one.
Private offers get complicated at scale. Fifty enterprise customers with custom pricing and different renewal dates? That’s its own job.
And marketplace compliance requirements change. Microsoft and AWS update policies, API versions, and certification requirements regularly. This is actually one of the strongest reasons to use a platform like SaaSify instead of building in-house: we absorb that maintenance burden.
Where We’re Headed
GCP Marketplace is on our roadmap. It’s smaller than Azure’s or AWS’s right now, but ISVs are asking for it. The goal is for SaaSify to be the single layer connecting ISVs to all three major cloud marketplaces.
We’re also building better analytics: conversion rates, average deal sizes, co-sell pipeline performance. The data ISVs need to treat marketplace as a serious sales channel, not just a checkbox.
If you’re an ISV thinking about cloud marketplaces, or if you’re already listed but the integration is a maintenance headache, I’d love to chat. You can reach us at saasify.com or just drop me a message.
Happy selling, folks!
Amit
Assisted by AI during writing
