How to Distribute SaaS via Cloud Marketplace

Distributing SaaS via cloud marketplace takes 4 to 8 weeks of technical integration and requires three fundamentals: a compatible legal entity, a billing stack, and a private offer model. This guide covers the seven steps to list on AWS, Azure, or GCP, solve tax compliance, and activate co-sell, taking you from zero to the first enterprise deal closed inside the marketplace.

Three marketplaces concentrate 85% of the enterprise software budget that flows through indirect channels. Enterprise customers have already committed budget under a hyperscaler contract. The marketplace is the shortest path to that budget. But only if the ISV treats it as a distribution channel, not as a product registry.

Prerequisites

1. Compatible legal entity. The disbursement account (ACH, wire) must be in the name of an entity with a valid tax ID. Brazilian ISVs typically operate with a US entity (Delaware C-Corp) that receives and remits to the local operation.

2. Defined billing model. Flat monthly/annual, usage-based, or private offer with custom pricing. The choice determines your metering stack and revenue projection.

3. Billing and metering stack. AWS requires AWS Marketplace Metering Service. Azure uses SaaS Fulfillment API v2. GCP requires Cloud Commerce Partner Procurement API.

The 7 Steps

1. Pick the marketplace by contract structure, not by market share
2. Structure the deal as a private offer, not a public listing
3. Integrate billing before listing your first product
4. Resolve the tax structure before the first transaction
5. Activate co-sell, don't wait for inbound
6. Treat the operation as a distribution channel, not as a registration desk
7. View the marketplace as acquisition infrastructure, not as an app store

Step 1: Pick the marketplace by contract structure, not by market share

The decision follows net payout rate, disbursement cycle, and co-sell availability for ISVs of your size.

AWS has the largest volume of committed budget and the lowest barrier for international ISVs. Azure has more aggressive co-sell for those who earn the badge, but adds 50% to the collection cycle. GCP has lower volume, but also the lowest competition for technical niche ISVs (security, DevOps, data).

Step 2: Structure the deal as a private offer, not a public listing

Listing with public pricing is the number one margin killer. A private offer is a bilateral contract executed inside the marketplace: the customer pays with budget already committed to the hyperscaler, and the ISV sets price and terms without exposing the rate card publicly.

All three hyperscalers support private offers. AWS calls it Private Offer (CPPO for multi-year deals). Azure adds Multiparty Private Offer for channel partner transactions. GCP is the simplest of the three.

The recommendation: start with private offers. The public listing serves as a credibility storefront. Enterprise deals close through commercial relationships, not catalog SEO.

Step 3: Integrate billing before listing your first product

The common flow across all three platforms:

1. Resolve customer. The marketplace sends a purchase token. The ISV resolves it to identify the customer, plan, and billing account.
2. Provision. Grant access to the SaaS. Resolution and provisioning must be atomic: if the second fails, the first is rolled back.
3. Meter. Send usage to the platform's metering API. Delays create backlogged billing and distort cash flow.
4. Entitlement change. Upgrades, downgrades, or renewals arrive via webhook. Process without interrupting service.
5. Unsubscribe. Cancellation requires deprovisioning and data export. An unanswered webhook can block the ISV's account in up to 72 hours.

Step 4: Resolve the tax structure before the first transaction

The hyperscaler is the merchant of record. It retains the listing fee and passes through the remainder. Tax liability on the disbursement belongs to the ISV — see the guide to nationalizing imported software in Brazil.

For the Latin American ISV, the critical decision is where revenue is recognized:

• US entity receives the disbursement. Revenue recognized in the US. Remittance to Brazil via withholding tax on dividends or an intercompany agreement.
• Local entity receives directly. Only works if the hyperscaler accepts disbursement in the home country. AWS accepts more jurisdictions; Azure restricts.

Recommended structure for Brazilian ISVs: US entity receives, intercompany agreement with the Brazilian operation, US accounting firm specialized in SaaS marketplace.

Step 5: Activate co-sell, don't wait for inbound

Listing a product does not generate pipeline. It generates a transaction point. Pipeline comes from co-sell.

• AWS ISV Accelerate: AWS field sales introduces the ISV to customers with AWS budget. Requires $2.5M in ACE-registered pipeline and two cases with AWS as the channel.
• Azure IP Co-sell: Microsoft field sales includes the ISV in Azure deals. Requires a solution badge and revenue history.
• GCP Partner Advantage: less structured. Connection via a designated partner manager.

Strategy: close your first 2 or 3 deals via private offer with your own outbound effort. That generates the revenue history that unlocks co-sell. Once enabled, the pipeline becomes shared with field sales.

Step 6: Treat the operation as a distribution channel, not as a registration desk

An ISV with channel maturity runs three processes:

1. Deal registration. Every enterprise deal must be registered in the partner portal (ACE on AWS, Partner Center on Azure, Partner Advantage on GCP). Protects margin against channel conflict.
2. Disbursement reconciliation. Cross-check every line of the disbursement report against internal billing. Metering discrepancies and chargebacks surface here.
3. Channel conflict management. Explicit rule: deals above $50k MRR go via private offer on the marketplace; below via direct sales. This prevents two salespeople from competing for the same customer.

Step 7: View the marketplace as acquisition infrastructure, not as an app store

CAC via co-sell is structurally lower than traditional outbound. A $120k/year deal closed via outbound costs 40% to 60% of the first year in CAC. The same deal via AWS co-sell costs 5% to 15%.

• Year 1: list on AWS and Azure. Close 3 deals via private offer with your own effort. The goal is revenue history.
• Year 2: active co-sell. Enterprise deals via marketplace. Direct sales handles expansion within existing accounts.
• Year 3: marketplace as the primary channel. Direct sales handles exceptions.

Consolidated Checklist

Before publishing the listing, verify each item:

1. Entity: active legal entity, business bank account, US EIN if applicable. No founder's personal tax ID on the publisher account.
2. Contract: first deal will be a private offer, not a public listing.
3. Billing: subscribe and unsubscribe flows implemented and tested. Unsubscribe webhook returns HTTP 200.
4. Tax: disbursement tax regime documented. If using a US entity, intercompany agreement with the local operation is active.
5. Co-sell: minimum revenue history to qualify for the platform program set as the first-quarter target.
6. Operations: deal registration process documented. Disbursement reconciliation report running monthly.
7. Acquisition: projected acquisition cost for year 1 with and without co-sell. If the delta is under 20 percentage points, the channel is not yet mature.

Common Pitfalls

• Listing without a compatible entity. Publisher account under the founder's personal tax ID, disbursement to a personal account. Result: audit block and tax liability — the cross-border payments guide for B2B SaaS covers the hidden costs of this model.
• Ignoring the cancellation flow. Unsubscribe webhook without a handler. Customer canceled, ISV keeps provisioning. Chargeback.
• Public pricing with no margin for private offers. List 20% to 30% above your site price. The private offer applies the actual discount.
• Inaccurate metering. Estimated usage, not actual. Customer disputes, marketplace claws back. Metering must be deterministic and auditable.
• Treating co-sell as free lead gen. Field sales works toward the hyperscaler's quota. Position your SaaS as a platform adoption accelerator.

FAQ

Do I need a US entity to list on AWS? Not strictly required. But the disbursement must land in a bank account compatible with the billing profile. For Brazilian ISVs, a US entity is the simplest path.

Which marketplace generates the most revenue for LatAm ISVs? AWS, due to enterprise budget volume and the lowest jurisdiction restrictions. Azure comes second, with Microsoft co-sell as the differentiator. Nexforce operates as the cross-border entry infrastructure for Latin American ISVs.

Does the hyperscaler issue invoices to the customer? Yes. AWS, Azure, and GCP are the merchant of record and issue invoices. The ISV's tax issuance obligation only applies if local law requires it.

How long does listing take? Technical integration: 4 to 8 weeks with a dedicated team. Listing review: 2 to 4 weeks on AWS and GCP, up to 8 weeks on Azure. The bottleneck is usually billing profile validation, not code integration.

Cloud marketplace distribution is the enterprise acquisition infrastructure of the next decade. The Latin American ISV that sets up this operation in the next 12 months reaches co-sell while the competition is still deciding whether it's worth it.

For ISVs that need tax and operational structuring to enter the marketplaces without opening their own foreign entity, Nexforce Marketplace operates as the merchant of record for Latin America, absorbing tax, FX, and billing profile complexity so the ISV can focus on product and sales.

References and Further Reading

• AWS Marketplace
• Azure Marketplace
• GCP Marketplace