SaaS Pricing Models in the Cloud Marketplace for ISVs

The deal closed. The vendor approved the discount, agreed on the timeline, mapped the renewal. One decision remains that none of those three touches: the pricing model, the way the money comes in. For ISVs (Independent Software Vendors, software companies that sell their product to other companies) selling SaaS through a cloud marketplace, the available SaaS pricing models resolve into three, and each one moves the financial result on a different front: a private offer closed per deal, a recurring subscription, and a usage-based subscription. Margin, revenue predictability, and the billing operation are not details of the sales proposal. They are its content.

The choice is conditional, and the condition is the revenue shape. Recurring subscription for a base with stable consumption. Usage-based when customer consumption varies. Private offer when the scope closes per project. This piece covers solution 2 from Nexforce, selling through a cloud marketplace with Nexforce operating that path, and names the alternative channel, selling in LatAm through Nexforce, solution 1. The terrain is real: 73% of enterprise software in Brazil is foreign, according to ABES, the association of the country's software companies.

What are the SaaS pricing models in a cloud marketplace?

The three SaaS pricing models in a cloud marketplace are: the private offer, a deal closed directly between vendor and customer with negotiated scope, value, and term; the recurring subscription, a periodic payment for access to the software; and the usage-based subscription, where billing follows recorded consumption. Each carries its own margin, predictability, and billing operation.

The occasion for the series is dated: the pricing documentation for AWS Marketplace sellers, consulted in September 2026, organizes seller options around these same three families, private offers, subscriptions, and pay-as-you-go. The nomenclature changes from channel to channel. The financial structure behind it does not.

The private offer is the closed-project model: the sale has a beginning, a middle, and an end, and revenue follows the contract, not the calendar. The recurring subscription is the continuous-access model, and it turns the customer base into annual recurring revenue, the ARR that sustains planning. The usage-based subscription is the alignment model: the customer pays as they use, and the vendor's revenue follows the customer's growth.

The decision comes before the listing.

How does the private offer work in the marketplace?

In the private offer, the deal closes directly between vendor and customer: scope, value, and term negotiated case by case and recorded as a private offer in the channel. Margin locks by contract, and revenue predictability depends on the sales pipeline, not on recurrence. This is the model for scoped deployments and projects with a delivery date.

Margin is the strength of this pricing model. The vendor prices the whole scope, embeds the delivery cost, and is not exposed to the customer's consumption. If the deployment blows past the deadline, the overrun belongs to the vendor; if the customer uses more than planned, the gain does too. Margin locks by contract, not by month.

The risk changes place. Because revenue does not repeat by nature, every new month is a month to sell, and the predictability of the aggregate depends on pipeline health. The failure mode is known: the deal closes in the sales conversation, and the negotiation restarts inside the paperwork, because on the direct path the channel imposes its own contract standard and program structure on the vendor, paper and process that are not the ISV's. This is where solution 2 changes the balance: Nexforce works with the ISV's own contract standard and programs, so the vendor's existing process does not change, and the deal closes on the paper it already uses.

How does the recurring subscription work in the marketplace?

The recurring subscription is the model in which the customer pays a periodic amount, monthly or annually, for access to the software. It is the structure that generates ARR, the annual recurring revenue that turns a customer base into planning. Next month's revenue is computed from the current base, net of churn.

Predictability is the product this pricing model delivers. With the base formed, the vendor knows how much comes in next month, how much needs to be sold to grow, and how much can be invested. Churn, the loss of customers in the period, is the variable that erodes that count, and the subscription operation lives on renewal and churn reduction.

The friction of the direct path appears before the first charge: transacting on the direct channel requires a commitment to one specific cloud, and the vendor who does not want to tie the offer to a single provider finds that the commitment is a condition of entry. It reappears in the flow of money, because a subscription contract means a gap between delivering and getting paid, and that gap is the vendor's working capital.

It is in the flow of money that solution 2 changes the math: Nexforce pays the ISV upfront and installments the end customer in up to 12 monthly payments. The vendor carries no receivable, and the buyer gains time. Regional payment methods follow the design, with Pix, boleto, and local cards accepted in the billing.

How does the usage-based subscription (consumption) work in the marketplace?

The usage-based SaaS subscription is the model in which billing follows the customer's consumption, with two common configurations: fixed consumption pricing, a negotiated rate over the total consumed in the period, and per-unit billing, where each unit consumed, transaction or account, carries its own price. It is the model that trades predictability for value alignment.

The two configurations share the same principle. In fixed consumption pricing, vendor and customer agree on the rate, and billing applies the rate to the recorded consumption, which gives the customer a predictable cost per usage level. In per-unit billing, the price is per transaction, per call, or per account processed, and the bill grows in exact proportion to use. In both, the vendor's revenue follows the customer's curve, up when the customer grows and down when they cut back.

Metering is the price of the variable gain.

The operation is the heaviest of the three pricing models: measure consumption in production, guarantee that measurement matches billing, and explain the bill to the customer every cycle. And the flow of money carries the layer of any international sale, settlement, the moment when the earned value converts into what the vendor actually receives. The cost of that layer in the region is measured in the comparison of local payments for selling SaaS in Latin America.

Which model preserves margin and predictability for the ISV?

In SaaS pricing in a cloud marketplace, the answer is conditional: recurring subscription preserves predictability for a stable base; private offer preserves margin when the scope closes per deal; usage-based preserves alignment when consumption varies. Margin is defended by the model that reduces what the vendor absorbs in payment terms, currency exchange, and operations.

The matrix below consolidates the comparison of the three SaaS pricing models across the four criteria that decide the vendor's math.

Reading by case. A customer base with stable consumption and predictable renewal calls for a recurring subscription, because next month's revenue is already in the base. A closed project, locked scope, and margin that does not dilute call for a private offer, because margin locks per deal. Consumption that swings between customers and months calls for usage-based, because the model captures growth without renegotiating the contract. No model wins on all four criteria at once, and the common mistake is deciding by commercial preference instead of by revenue shape.

What does each model demand of operations and billing?

The private offer demands pipeline and negotiation, with one-off per-project invoicing. The recurring subscription demands churn and renewal management, and billing automates after configuration. The usage-based subscription demands metering, the measurement of consumption in production, and metered billing, the heaviest operation of the three models. The weight changes place, it never disappears.

Channel execution has a separate manual: the step-by-step of listing and operating is in the guide to distributing SaaS via cloud marketplace. What matters here is the cost of operating each pricing model and the cost of operating the channel itself.

On the direct path, the vendor adds up seven frictions before putting the first contract on the street:

1. Listing and review cycles before the first contract goes live.
2. A per-transaction fee discounted from every charge in the channel.
3. The marketplace's own paper and program imposed on the vendor, with contract and program structure defined by the channel.

Entry solves the listing. The money does not resolve that fast:

1. A commitment to one specific cloud as a condition to transact.
2. A foreign fiscal entity opened just to receive in the region.
3. Settlement in USD, with exchange cost embedded in every receipt.

And the seventh friction runs through everything: compliance for the entire operation stays in the vendor's hands, from calculating what applies to each sale to the documentary proof of what was charged, with no local infrastructure to sustain it.

The solution 2 path trades that list for a different structure, and the product facts are seven. Nexforce works with the ISV's own contract standard and programs, so the vendor's existing process does not change. Transacting through Nexforce requires no commitment to a specific cloud. The cost is lower for the ISV and lower for the end customer than the same contract through the cloud providers, both ends measured in the same structure. The currency is local across all of Latin America, and the scope covers the entire region. A reseller network places the software in the local buyer's hands.

The seventh piece of the structure is the software alliance. Nexforce generates savings in the rest of the customer's or prospect's software spend, and it is that savings that makes the ISV's deal viable, the mechanism the vendor's own discount cannot reach. Two recorded cases give the measure: ConectCar, from the Itaú group, cut 10% of software cost, and Softplan, 17%. The ISV's deal pays for itself inside the buyer's total software spend, and that is why the model closes deals that a standalone discount does not.

The package closes with what is already in the agreement: zero cost for the ISV, no minimum deal size, regional payment methods in the billing, Pix, boleto, and local cards, and Nexforce paying the ISV upfront while installing the end customer in up to 12 monthly payments.

How do you decide the model by revenue shape?

The ISV's revenue shape decides the model: a customer base with stable consumption calls for a recurring subscription; consumption that swings by customer and by month calls for usage-based; scope closed per project calls for a private offer. The decision follows the revenue, not the commercial preference, and the tree below summarizes the path.

The checklist reduces the decision to five checks:

1. Map the dominant revenue shape for the next 12 months: stable recurrence, variable consumption, or per-project scope.
2. Choose the matching pricing model: recurring subscription, usage-based, or private offer.
3. Audit the operation the model demands: metering, churn management, or per-deal negotiation, and confirm the current team sustains the weight.
4. Verify who carries the receivable and the payment terms in each model on the chosen channel.
5. Compare the total cost of the path: per-transaction fee, cloud commitment, and USD settlement on one side; the Nexforce structure on the other.

This text decides the model inside the channel. The earlier decision, whether and how to enter the region and which channel to sell software through a cloud marketplace, is in the cloud marketplace guide for LatAm and the international ISV roadmap for selling SaaS software in Latin America.

FAQ: SaaS pricing models in the marketplace

What are the SaaS pricing models in a cloud marketplace?

Three: the private offer, with scope and value closed per deal between vendor and customer; the recurring subscription, with periodic payment for access to the software; and the usage-based subscription, with billing following recorded consumption, in fixed consumption pricing or per unit. Each model distributes margin, predictability, and operational load differently.

Which model generates the most predictable revenue for the ISV?

The recurring subscription. The periodic payment forms an ARR base that lets the vendor compute next month's revenue from the current base, net of churn. A private offer has per-contract predictability, but the aggregate depends on the pipeline. Usage-based is the least predictable of the three SaaS pricing models, because it follows each customer's consumption.

How does usage-based pricing work in a marketplace?

In two common configurations. In fixed consumption pricing, vendor and customer agree on a rate over the total consumed in the period. In per-unit billing, each unit consumed carries its own price, per transaction, call, or account. The model demands metering, the measurement of consumption in production, and converts consumption into revenue, with lower predictability.

Does the ISV need to change its standard contract to sell in a cloud marketplace?

On the direct path, yes: the marketplace imposes its own paper and program structure on the vendor. Through Nexforce, no. Nexforce works with the ISV's own contract standard and programs, so the vendor's existing process does not change, and the deal closes on the paper it already uses.

References and Further Reading

• How to distribute SaaS via cloud marketplace: listing and channel execution
• Cloud marketplace LatAm: the channel choice guide
• How to sell SaaS software in Latin America: the international ISV roadmap
• Local payments: the cost of selling SaaS in Latin America
• Nexforce Marketplace

From choosing the model to the first contract in LatAm

The pricing model closes the design of the sale, and the next step is the first contract in the region. Nexforce opens both channels to the international ISV, and the choice between them belongs to the vendor: sell in LatAm through Nexforce, with local infrastructure and no fiscal entity of its own, or sell through a cloud marketplace with Nexforce operating that path, keeping the vendor's contract and program intact. Both accept the pricing model the revenue calls for, private offer, recurring subscription, or usage-based. The next contract in the region can start at Nexforce Marketplace.