The ultimate guide to commercial models

Explore the key components of commercial models—from how products charge, to how you can build your own. This guide walks through core building blocks, real-world examples, and emerging trends to help you design a model that fits.

Commercial model
Monetisation strategy
Pricing structure
Revenue mechanic
Billing logic

What is a commercial model—and why should you care?

You've built something valuable—a tool, a platform, or a service people actually want to use. But how do you turn that value into profit?

It's time to build your commercial model.

A commercial model defines how your product makes money, how customers pay, and how that money flows into your business. That might be as simple as a flat monthly fee, or more dynamic, with usage-based pricing, tiered plans, or outcome-based contracts.

Getting this right isn't just about setting a price; your commercial model should evolve as your customer base grows. Aligning the value your product delivers to your customers is often a moving target, and there are a range of different pricing approaches available to maximise profit while maintaining a great customer experience.

In this guide, we'll break down the key components of a commercial model, explain how they fit together, and show how leading products—and flexible platforms like Salable—handle this in the real world.

We've analysed how successful products approach this, and what we're sharing here reflects industry best practices. So, it all starts with the building blocks.

A stylized diagram of a commercial model, showing monetization strategy, pricing structure, revenue mechanics, and billing logistics.

The building blocks of a commercial model

A commercial model is the full go-to-market blueprint, combining a monetisation strategy, pricing structure, revenue mechanics, and billing logistics into one cohesive system. To understand what this looks like in practice, let's break down the commercial model of one of the most talked-about businesses in the world right now: OpenAI.

Monetisation strategy: your plan to make money

To start off with, monetisation defines where revenue will come from. It’s your high-level strategy for turning value into income.

OpenAI’s monetisation strategy for its API is usage-led, it doesn't charge for access or setup. Instead, it earns when customers interact with its products and services. OpenAI monetises on activity, and ties its revenue to the number of tokens consumed–not the number of users for instance. 

OpenAI actually monetises two main services:

  • ChatGPT: the Chat interface that users can interact with
  • OpenAI API: the API that powers ChatGPT, and developers can integrate into their application

Each of these is monetised independently, creating multiple revenue streams, all anchored to real product usage.

Revenue mechanics: how money actually flows

If monetisation is the strategy, the revenue model is the execution. Your revenue model describes the way money is earned—the specific behaviours your customers take that generate income.

The OpenAI API's revenue model, when using the API, is built around per-token fees. Large Language Models (LLMs) break down the ‘cost’ of generating text and images into smaller pieces, or "tokens", which a user pays a fee for each.

While enterprise customers may negotiate pricing and terms, the basic revenue model is the same: customer actions in the product.

Don’t mix them up!

Monetisation is the high-level play—it answers where the money comes from: "We make money when people use our API."

Revenue is the engine underneath—it shows how that money flows in: "They consume tokens, and we bill them monthly."

One spots the opportunity. The other runs the system.

Pricing structure: how the offer is packaged

Pricing is how you package and present your value. It defines how much your customer pays, and for what.

OpenAI’s pricing is:

  • Transparent: all rates are publicly listed and easy to understand.
  • Usage-based: customers are charged per execution or action.
  • Modular: customers only pay for the services they use (e.g. the API, ChatGPT, Codex)

This model works well for developer tools and infrastructure products. It keeps the barrier to entry low and ensures that pricing grows with usage.

At this point, it's good to take a minute to expand on the different revenue models that are available. Salable stands out here, giving businesses full control to design pricing models that match their product, customer base, and growth goals.

  • Per-seat pricing for team-based tools
  • Flat-rate plans for simplicity
  • Usage-based metering for scalability
  • Feature-based tiers that lock or unlock functionality
  • Modular pricing for product components

Salable is built for composable pricing–so you can mix and match models, test new structures, and adapt as your product and customer base grow.

Whether you want to charge a flat platform fee, add usage overages, gate features by tier, or sell optional modules, Salable lets you combine it all into one flexible plan. No need to choose just one model or rewrite your backend when you need to change.

Plans vs tiers—what's the difference?

There’s no universal rule, but here's a helpful way to think about it:

  • Plan: what the customer sees and selects—e.g. Free, Pro, Enterprise. It defines features, limits, and pricing.
  • Tier: a level within or across plans—often used internally to manage usage, scale pricing, or unlock support.

Some products use just plans. Others use tiers inside a plan. Make sure your terms are clear and consistent.

Billing: how and when customers are charged

With your monetisation, revenue, and pricing strategy under control, the last step is understanding your approach to billing. Billing defines when your customers pay and how payments are collected—monthly vs annual, prepaid vs postpaid, automated vs invoiced.

OpenAI uses:

  • Monthly billing in arrears: customers are invoiced for actual usage at the end of the billing period.
  • Automated payments: charges are typically collected via saved payment methods.
  • Custom terms: larger customers may receive enterprise contracts with negotiated billing terms or invoicing.

This setup allows OpenAI to align revenue collection with customer activity, keeping cash flow predictable and scaling without friction.

OpenAI’s commercial model works because each component reinforces the others:

  • The monetisation strategy is tied to customer activity—OpenAI earns when its users actually use their products.
  • The pricing structure is transparent and usage-based—making it easy for developers and founders to adopt
  • The billing system is flexible—handling everything from startups to enterprise scale.

Together, these components create a commercial model that's simple to adopt, scales with usage, and aligns value delivery with revenue.

Of course, not every part is optimised for profitability today. OpenAI, like many others, also leans on a loss-leader strategy—offering generous free tiers to grow adoption and build long-term value.

How leading products charge—and how you can too with Salable

Notion

Freemium + Tiered Pricing + Per-User Billing

  • Pricing model: Tiered (Free, Plus, Business, Enterprise)
  • Billing model: Monthly or annual prepayment
  • Monetisation: Free to paid upgrade + workspace-based expansion

💡 With Salable:

You'd set this up with feature gating across plans, usage thresholds, and per-seat pricing logic. Salable handles tier visibility, billing intervals, and conversion flows automatically.

👉 Why it works:

Free users see value fast. Teams can expand gradually. Billing grows with usage.

Slack

Seat-Based + Tiered Plans + Postpaid Billing

  • Pricing model: Per user, with active user billing
  • Billing model: Monthly, with postpaid billing on actual active users
  • Monetisation: Trials + pay as your team grows

💡 With Salable:

You can define usage metrics per seat (e.g. "active" user logic), bill monthly based on real usage, and support trial-to-paid transitions. Salable's metering logic supports this directly.

👉 Why it works: Customers only pay for what they use. Easy onboarding, minimal friction.

AWS (S3, Lambda, etc.)

Usage-Based + Graduated Pricing + In Arrears Billing

  • Pricing model: Graduated usage pricing (e.g. £0.01 per GB, cheaper after 50 TB)
  • Billing model: In arrears, billed monthly based on usage
  • Monetisation: Scale-based, with discounts at higher tiers

💡 With Salable:

Use Salable's metering system to track API calls, storage, or bandwidth. Apply graduated pricing and bill monthly in arrears. Optional usage caps, alerts, or credit top-ups are supported.

👉 Why it works: Aligns revenue with value delivered. Low entry barrier, highly scalable.

Midjourney

Token-Based + Prepaid Credits + Subscription Bundles

  • Pricing model: Monthly subscription includes a credit pack (images per month)
  • Billing model: Prepaid, with auto top-ups or manual recharge
  • Monetisation: Credit exhaustion triggers upsell or top-up

💡 With Salable:

Enable token or credit-based pricing via credit burndown. Define consumption units (e.g. generations, API calls), offer prepaid packs, and allow custom refill logic or automation.

👉 Why it works: Easy to manage consumption while offering predictable base revenue.

Figma

Freemium + Tiered + Usage Metered for Enterprise

  • Pricing model: Free → Pro → Org, with seat-based pricing
  • Billing model: Monthly or annual; enterprise plans often usage-metered or custom
  • Monetisation: Start free, grow by team or usage

💡 With Salable:

Use tier gating and seat pricing for self-serve, and add granular usage tracking (file usage, editor count) for enterprise. Salable allows flexible pricing by user role or activity.

👉 Why it works: Matches growth stage—individuals start free, orgs can scale.

Spotify

Freemium + Flat-Rate Subscription + Add-On Bundles

  • Pricing model: Free with ads, then flat monthly fee for Premium; bundles for Duo, Family, etc.

  • Billing model: Recurring monthly billing, optional trials

  • Monetisation: Ad revenue + upgrade conversion

💡 With Salable:

Use free vs paid plan gating, with bundle support (linked accounts or group seats). Billing cadence logic and promotional pricing rules help deliver trials and loyalty discounts.

👉 Why it works: Multiple paths to revenue; lets customers choose their preferred experience.

HubSpot

Tiered Base Plan + Usage-Based Add-Ons + Bundled Products

  • Pricing model: Fixed tiers per product (CRM, Marketing Hub) + usage-based features (contacts, API)
  • Billing model: Monthly/annual for tiers; usage tracked separately
  • Monetisation: Land and expand—platform growth equals revenue growth

💡 With Salable:

Set a base price per product module, then layer in usage-based add-ons. Use feature flags, entitlements, and billing events to handle expansion pricing easily.

👉 Why it works: Modular, scalable pricing that matches product value.

Revolut

Freemium + Tiered Subscription + Transaction Commission

Pricing model: Free, Plus, Premium, Metal (flat monthly fee) + variable commission on some services

* Billing model: Monthly billing + per-transaction revenue

- Monetisation: Mix of subscriptions, interchange, and commission

💡 With Salable:

Combine subscription plans with pay-per-use monetisation. Salable's hybrid model support makes it easy to define bundled value + transactional overages

👉 Why it works:

Low base price, monetisation grows as users engage more.

Building your own model

You've seen how others do it—now it's your turn.

Designing a commercial model doesn't start with pricing tables or billing software. It starts with understanding your product, users, and value delivery. Below is a framework to help you think it through—no jargon, no overthinking.

1. Who are your users?

  • Are they individuals or teams?
  • Are they technical, non-technical, or both?
  • Are they price-sensitive, or willing to pay for convenience?

Why it matters: Per-seat pricing works great for teams. Usage-based pricing might be a better fit for solo power users.

2. What value do they get, and how often?

  • What's the core job your product helps them do?
  • Are they using it daily, weekly, or occasionally?
  • Do they rely on a single key feature or use many?

Why it matters: Daily-use tools lend themselves to subscriptions. Spiky usage might call for a pay-as-you-go approach.

3. What do you want to monetise?

  • Access (e.g. subscription to core platform)?
  • Usage (e.g. API calls, reports, storage)?
  • Features (e.g. premium templates, AI tools)?
  • Outcomes (e.g. results achieved)?

Why it matters: Salable lets you monetise any of these with different models, so clarity here gives you flexibility later.

4. When should customers pay?

  • Do they try before they buy? (→ Free tier or trial)
  • Should they commit upfront? (→ Annual plans or credit packs)
  • Do they scale slowly or in bursts? (→ Usage-based or hybrid)

Why it matters: Matching your billing rhythm to the customer's buying pattern reduces friction and churn.

5. How much flexibility do you need?

  • Do you want to test new plans quickly?
  • Will you have multiple customer segments?
  • Are you launching into different regions or currencies?

Why it matters: Your first model won't be your last. Salable makes it easy to adapt pricing and plans without engineering effort.

Start simple, then optimise

You don't need the perfect model from day one. Many of the companies we admire started with something simple and evolved over time.

A good starting point:

  • One free tier
  • One paid tier
  • Clear upgrade path
  • Transparent billing cycle]


With Salable, you can then add usage metering, custom tiers, hybrid models, and billing logic as your business grows.