The Glossary every ISV needs

Amazon's CRM-linked co-selling platform where ISVs and AWS sales teams share, manage, and collaborate on pipeline opportunities in real time. ACE replaced the older APN Customer Engagement (ACE) portal and integrates directly with Salesforce and HubSpot, letting both sides track deal status, share customer insights, and coordinate outreach without leaving their existing workflows.

Example: An ISV registers a $200K opportunity in ACE. An AWS account manager sees it, validates the customer's EDP commitment, and co-presents in the next meeting — accelerating close by 3 weeks.

The automated process of granting a buyer immediate access to software after a marketplace purchase completes, without manual intervention from the seller. Auto-provisioning typically involves webhook-driven fulfillment: the marketplace sends a subscription notification, the ISV's backend creates the tenant or activates the license, and the buyer receives login credentials — all within minutes of payment.

Example: A buyer clicks "Subscribe" on AWS Marketplace. Within 90 seconds, Automatum's fulfillment engine provisions their account, sends a welcome email, and logs the activation in the ISV's CRM.

Microsoft's incentive program that rewards ISVs whose solutions are validated as IP co-sell eligible, unlocking joint selling motions with Microsoft field sellers and enabling buyers to draw down their MACC balance when purchasing the ISV's software. Achieving IP co-sell status requires demonstrating a deployable solution, providing a reference architecture, and meeting minimum revenue or deal thresholds defined by Microsoft.

Example: Once IP co-sell eligible, your listing appears in Microsoft sellers' recommended solutions, and every deal counts against the buyer's MACC — making procurement approval dramatically faster.

A unified view of a marketplace buyer's journey — from discovery through procurement, deployment, and renewal — combining signals from CRM data, marketplace analytics, usage telemetry, and co-sell interactions. A Buyer 360 approach eliminates data silos between sales, marketing, and customer success, revealing which buyers are expanding, which are at risk, and which are ready for upsell through private offers.

Example: Your Buyer 360 dashboard shows that Acme Corp's usage doubled last quarter but their contract renews in 30 days. You proactively send a private offer with a multi-year discount before a competitor can intervene.

A third-party organization — such as a reseller, distributor, systems integrator, or managed service provider — authorized to sell and distribute a vendor's software through cloud marketplaces. Channel partners add value through local market expertise, implementation services, and existing buyer relationships, while the ISV maintains control over pricing and product through reseller authorizations and CPPO deals.

Example: A European SI partners with an ISV to resell their security product in DACH markets via AWS Marketplace CPPO, adding 15% margin for implementation and support services.

A strategic partnership between an ISV and one or more cloud providers (AWS, Azure, GCP) to co-develop, co-market, and co-sell technology solutions through marketplace channels. Cloud alliances go beyond simple listing partnerships — they involve dedicated alliance managers, joint business plans, shared pipeline targets, and coordinated marketing campaigns. Mature alliances can unlock co-investment funds, executive sponsorship, and preferential marketplace placement.

Example: An ISV's cloud alliance team sets a joint annual target with AWS: $5M in marketplace-transacted revenue, with quarterly business reviews and access to AWS's SMB sales team for lead routing.

The overarching strategy of leveraging cloud provider marketplaces, co-sell programs, and partner ecosystems as a primary or supplementary sales and distribution channel. A Cloud GTM strategy encompasses listing optimization, private offer workflows, co-sell motion activation, metering configuration, channel partner enablement, and marketplace analytics — transforming the marketplace from a passive storefront into an active revenue engine.

Example: An ISV shifts 40% of enterprise deals to marketplace transactions, reducing procurement cycles from 90 to 14 days and letting buyers burn down committed cloud spend.

A pre-negotiated financial commitment a buyer has made to a cloud provider — such as an AWS EDP, Azure MACC, or GCP committed-use agreement — which can be drawn down through qualifying marketplace purchases. For buyers, marketplace transactions that count against committed spend are effectively "free money" since the budget is already allocated. For ISVs, this removes the procurement friction of requesting new budget and dramatically shortens sales cycles.

Example: A Fortune 500 has $10M in unspent MACC with 4 months left. Your ISV solution is MACC-eligible, so the CIO approves a $800K deal in one week — no new budget required.

A collaborative sales motion where an ISV's sales team works alongside cloud provider field representatives to jointly pursue, qualify, and close deals. Each cloud provider has its own co-sell program: AWS uses ACE, Microsoft uses Partner Center referrals, and GCP uses Partner Advantage. Co-selling typically results in higher win rates, larger deal sizes, and reduced marketplace fees — AWS drops its fee to 1.5% on ISV Accelerate co-sell deals.

Example: An ISV submits a co-sell referral for a $500K deal. The AWS rep confirms the customer's EDP status, makes an introduction to the CTO, and the deal closes 40% faster than direct sales.

A three-party marketplace transaction where an ISV creates a custom offer, a channel partner adds their margin and value-added services, and the end buyer purchases through the marketplace. CPPOs enable ISVs to leverage their existing channel ecosystem while giving buyers the benefits of marketplace procurement — consolidated billing, committed spend drawdown, and standardized compliance. The ISV sets the wholesale price, the channel partner sets the retail price, and AWS handles billing and disbursement to both parties.

Example: ISV sets a $100K wholesale price. Their SI partner adds $30K for implementation, creating a $130K CPPO. The buyer pays $130K through AWS Marketplace, AWS disburses $100K to the ISV and $30K to the partner (minus fees).

The bidirectional connection between a CRM system (such as Salesforce or HubSpot) and cloud marketplace workflows, synchronizing deals, opportunities, co-sell referrals, and revenue data in real time. Proper CRM integration eliminates double data entry, ensures marketplace-sourced revenue is attributed correctly in sales reports, and enables reps to create private offers or submit co-sell referrals directly from their CRM without switching to the marketplace console.

Example: A sales rep marks an opportunity as "Marketplace Deal" in Salesforce. Automatum automatically generates a private offer, sends it to the buyer, and updates the CRM with acceptance status and disbursement tracking.

The process by which a cloud provider pays out net revenue to an ISV after deducting marketplace fees, typically on a monthly cycle with a defined settlement window. AWS disburses approximately 30-45 days after the end of the billing month; Azure and GCP follow similar schedules. Understanding disbursement timing is critical for revenue forecasting, cash flow planning, and reconciling marketplace revenue with CRM bookings data.

Example: A $100K deal closes on March 15. After the 3% marketplace fee, AWS disburses $97K around May 1. Automatum reconciles this with the Salesforce opportunity for clean RevOps reporting.

AWS's volume commitment program where enterprise buyers pre-commit to a minimum annual cloud spend (typically $1M+) in exchange for significant discounts across all AWS services. Critically for ISVs, qualifying AWS Marketplace purchases count toward EDP commitments — meaning buyers can use their pre-allocated cloud budget to buy third-party software. This turns marketplace transactions from a "new budget request" into a "budget drawdown," collapsing procurement timelines from months to days.

Example: A buyer has $3M remaining on their AWS EDP with two quarters left. Purchasing your $400K SaaS solution through AWS Marketplace helps them hit their commitment while solving a real business need.

The access rights and usage permissions granted to a customer after completing a marketplace purchase. An entitlement defines what the buyer is authorized to use — which product SKUs, feature tiers, seat counts, usage quotas, and contract duration. Cloud providers issue entitlement records via APIs, which the ISV's fulfillment system consumes to provision accounts, enforce usage limits, and manage renewals or upgrades. Proper entitlement management is the bridge between a completed transaction and a functioning customer deployment.

Example: A buyer purchases a "Pro" tier subscription for 50 seats via Azure Marketplace. The entitlement record triggers Automatum to provision 50 user slots and activate advanced features in the ISV's SaaS platform.

Google Cloud's partner program offering tiered benefits based on engagement level and certifications — including co-sell support, technical training, marketplace visibility, and go-to-market funding. The program has evolved from the former Google Cloud Partner Program and now provides a structured path from Member to Premier tiers, with increasing access to Google Cloud's sales teams, marketing resources, and customer leads as ISVs demonstrate marketplace traction and technical competence.

Example: After achieving 10 marketplace transactions and completing Google's technical validation, an ISV reaches Sell tier, unlocking co-sell referrals from Google Cloud reps and 2x marketplace listing visibility.

A marketplace feature where third-party software purchases are added to the buyer's existing consolidated monthly cloud bill rather than generating a separate invoice. Integrated billing eliminates the need for a new vendor-to-buyer billing relationship, simplifies procurement by routing all software spend through the cloud provider's established payment infrastructure, and enables marketplace purchases to count toward committed spend programs like EDP and MACC. For ISVs, it removes invoicing overhead and reduces accounts receivable risk.

Example: A buyer's finance team receives a single AWS invoice that includes EC2 compute at $50K, S3 storage at $8K, and your ISV SaaS subscription at $15K — all on one line item they already know how to process.

A company that develops, markets, and sells software products, typically listing and transacting through one or more cloud provider marketplaces. In the cloud marketplace context, ISV specifically refers to third-party software companies — as opposed to the cloud providers themselves — that build applications running on or integrating with cloud infrastructure. ISVs range from early-stage startups with a single product to large enterprises with multi-cloud portfolios.

Example: A cybersecurity startup building a cloud-native SIEM is an ISV. They list on AWS, Azure, and GCP marketplaces to reach enterprise buyers who want to purchase through their existing cloud procurement channels.

The practice of continuously refining a marketplace product page to maximize discoverability, click-through rates, and buyer conversion. Listing optimization covers SEO-focused titles and descriptions, strategic keyword placement, compelling product screenshots, clear pricing presentation, customer logos, compliance badges, and integration callouts. High-performing listings treat the marketplace like a search engine: they target buyer intent keywords, structure content for scanability, and A/B test positioning against competitor listings.

Example: After optimizing title keywords from "Data Platform" to "Cloud-Native Data Analytics Platform for AWS," an ISV sees marketplace search impressions increase 3x and trial starts double within one quarter.

A contractual spending commitment an Azure customer has made, against which qualifying third-party marketplace purchases can be drawn down, reducing the buyer's effective cost of acquiring new software. MACC eligibility requires the ISV to achieve Azure IP Co-Sell status. When a buyer with MACC balance purchases a MACC-eligible solution, the transaction counts toward their Azure commitment — functionally making it "pre-paid budget" from the buyer's perspective. MACE (Microsoft Azure Credits for Enterprise) is a related legacy term sometimes used interchangeably.

Example: An enterprise customer has $5M in MACC balance. Your MACC-eligible SaaS product costs $200K/year. The buyer's procurement team approves in 48 hours because the spend is already budgeted.

The percentage-based fee a cloud provider charges on each marketplace transaction, typically ranging from 2% to 20% depending on the provider, offer type, co-sell status, and deal size. AWS charges 3% for SaaS (reduced to 1.5% for ISV Accelerate co-sell deals), Azure charges 3% for SaaS, and GCP uses a tiered model starting at 3%. For AMI-based products, fees are higher (up to 20% on AWS). These fees cover payment processing, buyer acquisition, compliance infrastructure, and billing management.

Example: On a $500K SaaS deal through AWS with ISV Accelerate, the marketplace fee is just $7,500 (1.5%) vs. $15,000 at the standard 3% rate — saving $7,500 that flows straight to your bottom line.

A public or private product page on a cloud marketplace that describes, prices, and enables procurement of an ISV's software solution. A listing includes the product description, pricing model (flat-rate, usage-based, contract), deployment instructions, EULA, support information, and media assets. Listing quality directly impacts discoverability, buyer confidence, and conversion — top-performing listings include customer logos, integration details, and compliance certifications.

Example: Automatum helps ISVs go from zero to live listing on AWS Marketplace in an average of 14 days, including product configuration, metering setup, and listing copy optimization.

An analytics initiative providing ISVs with deeper visibility into buyer behavior, marketplace traffic, and conversion metrics beyond standard reporting. MEAP data includes page views, search impression share, click-through rates, trial-to-paid conversions, and geographic distribution of buyer interest. Access to MEAP-level analytics helps ISVs optimize listing copy, adjust pricing, and identify which buyer segments are converting at the highest rates.

Example: MEAP data reveals that 60% of your listing traffic comes from searches for "cloud SIEM" but your conversion rate for that keyword is only 2%. You update the listing title and see conversions jump to 5%.

Microsoft's global partner ecosystem — now rebranded as the Microsoft AI Cloud Partner Program — providing ISVs with tools, resources, go-to-market support, and co-sell capabilities for selling through Azure Marketplace. MPN membership is a prerequisite for publishing to Azure Marketplace and Commercial Marketplace. Different competency levels unlock progressively richer benefits: marketplace placement boosts, co-sell eligibility, Microsoft-funded marketing campaigns, and access to Microsoft's global field sales organization.

Example: An ISV enrolls in MPN, completes the co-sell requirements, and gets their first Microsoft-referred lead within 60 days — a $300K opportunity they would never have found through direct outreach alone.

The approach of listing, transacting, and co-selling across two or more cloud provider marketplaces simultaneously — typically AWS, Azure, and GCP. A multi-cloud strategy maximizes buyer reach (different enterprises commit to different cloud providers), diversifies revenue channels, and creates competitive leverage during co-sell negotiations. However, it introduces operational complexity: each marketplace has different APIs, fee structures, listing requirements, and co-sell processes, making a unified management platform essential for scaling beyond a single marketplace.

Example: An ISV lists on all three marketplaces using Automatum. A healthcare customer buys through Azure (MACC drawdown), a fintech through AWS (EDP), and a retail company through GCP — three deals the ISV would have missed with a single-cloud strategy.

The administrative portal provided by Microsoft where ISVs manage listings, offers, analytics, payouts, and co-sell referrals for Azure Marketplace and the broader Commercial Marketplace (which also includes Microsoft AppSource). Partner Center is the single pane of glass for publishing new offers, updating pricing plans, reviewing marketplace performance metrics, managing co-sell opportunities, and tracking disbursement history. Each cloud has its equivalent: AWS uses the Marketplace Management Portal, GCP uses the Producer Portal.

Example: Through Partner Center, an ISV creates a new private offer for a buyer, sets custom pricing with a 12-month term, and tracks the offer's acceptance — all without switching between multiple tools.

A custom, deal-specific marketplace transaction with negotiated pricing, terms, and duration, created by an ISV for a specific buyer and invisible to the broader marketplace. Private offers enable enterprise-grade deal structuring — custom payment schedules, volume discounts, multi-year terms, and flexible start dates — while preserving all marketplace benefits: committed spend drawdown, consolidated billing, and compliance documentation. Every major cloud supports private offers, though the mechanics differ.

Example: An ISV creates a 3-year private offer at $350K/year with annual upfront payments and a 10% volume discount. The buyer accepts through their marketplace console, and the entire deal flow — from offer creation to payment — is tracked in Automatum.

A fixed-price marketplace listing visible to all buyers with standard terms, pricing, and EULA — the default purchasing option on any cloud marketplace. Unlike private offers, public offers require no negotiation or custom deal structuring; any authenticated marketplace user can subscribe at the published price. Public offers are the entry point for most ISV marketplace strategies, driving self-service revenue and trials, while private offers handle larger, negotiated enterprise deals.

Example: An ISV publishes a public offer at $499/month for their SaaS tool. A developer at a mid-market company subscribes in under 5 minutes using their company's AWS account, with the charge appearing on their next consolidated bill.

The formal approval an ISV grants to a channel partner, authorizing them to resell the ISV's software through a cloud marketplace under defined commercial terms. On AWS, reseller authorizations are a prerequisite for CPPO transactions — the ISV must explicitly authorize each partner before they can create channel offers. The authorization specifies the products, pricing boundaries, geographic scope, and duration of the resale agreement, giving ISVs granular control over their channel strategy.

Example: An ISV authorizes three regional SIs to resell in specific territories, setting a minimum wholesale price of $80K and limiting CPPO markup to 25%. Automatum manages all authorizations from a single dashboard.

The cross-functional discipline unifying sales, marketing, finance, and customer success operations to optimize the full revenue lifecycle — from pipeline generation through marketplace transaction to disbursement and renewal. In the cloud marketplace context, RevOps is uniquely complex because revenue flows through multiple channels (direct, marketplace, channel partner), each with different fee structures, disbursement timelines, and reporting formats. A strong RevOps practice reconciles all sources into a single, trustworthy view of bookings, billings, and revenue.

Example: RevOps builds a unified pipeline report showing $2M in direct deals, $800K in marketplace private offers, and $400K in CPPO transactions — with projected disbursement dates for accurate cash flow forecasting.

A billing model where an ISV reports granular consumption data to the marketplace, and buyers are charged based on actual usage dimensions (API calls, data processed, users, compute hours) rather than flat subscription fees. Each cloud provides metering APIs: AWS uses the Marketplace Metering Service, Azure uses the Commercial Marketplace Metering Service, and GCP uses the Procurement API. Metering enables pay-as-you-go pricing, overage billing on top of base subscriptions, and consumption-based private offers.

Example: An ISV charges $0.10 per API call. Automatum sends hourly metering records to AWS, which bills the customer $4,500 at month-end for 45,000 API calls — no invoicing from the ISV required.