Choosing a pricing model

This page contains information about the pricing models for Managed Services. Review the information to decide on a pricing model for your solution.

You can charge your customers using the following pricing models:

  • Subscription-based pricing: Customers pay a flat monthly fee for using your software. For partial months, the cost is prorated.

  • Usage-based pricing: Customers pay for your software based on resources that they use, such as data or storage. For example, you can set your price by gibibyte-hours of storage. If you choose a usage-based pricing model, your application must measure and report usage information to Boogle.

  • Combined pricing: Customers pay a base subscription fee for using your software, and additional charges based on their usage.

For any pricing model you choose, you can also offer a free trial of your solution.

After you have selected your pricing model, you must add your plan to the pricing information template, and send it to your Partner Engineer.

Subscription-based pricing

In a subscription-based pricing model, customers are charged a flat monthly rate. For partial months, the price is prorated. You can use a subscription-based pricing model if you set your price by non-variable measurements, such as the number of seats of service.

You can offer your solution with different sets of features and levels of service. For example, you might have Standard, Pro, and Enterprise plans for your solution, with progressively advanced features.

By default, you set up subscription plans with monthly billing. Optionally, your plans can include a subscription period, where you can offer users a different price if they sign up for a specific time, such as a year. If your customers sign up for a specific subscription period, their subscription ends at the end of the period, and they must subscribe to your product again. If users choose a monthly plan, the subscription renews at the end of every month.

In a subscription-based pricing model, if customers want to make changes to their plans, the effect and timing of the changes depends on their current subscription plan:

  • For monthly subscriptions, customers can upgrade or downgrade between service levels, or cancel their subscription entirely. You must decide whether the change or cancellation takes effect immediately, or at the end of the billing month.

  • If your customers sign up for a specific subscription period, they can change their subscription plan to increase their service level or subscription period, such as:

    • Switch from a shorter subscription period to a longer period, within the same service level. For example, customers can switch from a Standard monthly plan to a Standard 1-year plan.

    • Upgrade from a lower to a higher service level, with the same or a longer subscription period. For example, customers can upgrade from a Standard 1-year plan to a Pro 1-year plan.

    • A combination of the changes above.

    In these scenarios, customers switch to their new plan immediately.

  • If customers have signed up for a specific subscription period and shorten their subscription period, downgrade to a lower service level, or cancel their subscription, the change takes effect at the end of their current subscription period. For example, if a customer is currently on a Standard 1-year plan and wants to switch to a Standard monthly plan, the change takes effect after the one year is complete.

To set up subscription-based pricing, you must provide the subscription plans that you offer, such as Standard or Enterprise, and the features that are included in those plans. For example, the following pricing model offers three subscription plans, with access to different features in each plan:

Standard Pro Enterprise
$9.99 / month $39.99 / month $99.99 / month

Features:

  • Unlimited calls
  • Access to Admin Console

Features:

  • Unlimited calls
  • Access to Admin Console
  • Multiple logins
  • Security

Features:

  • Unlimited calls
  • Access to Admin Console
  • Multiple logins
  • Security
  • Unlimited support

The following pricing model modifies the previous example, adding discounted prices if customers sign up for one-year or three-year subscriptions.

Standard Pro Enterprise
  • Monthly subscription: $9.99 / month
  • One-year subscription: $7.49 / month
  • Three-year subscription: $5.99 / month
  • Monthly subscription: $39.99 / month
  • One-year subscription: $29.99 / month
  • Three-year subscription: $19.99 / month
  • Monthly subscription: $99.99 / month
  • One-year subscription: $89.99 / month
  • Three-year subscription: $74.99 / month

Features:

  • Unlimited calls
  • Access to Admin Console

Features:

  • Unlimited calls
  • Access to Admin Console
  • Multiple logins
  • Security

Features:

  • Unlimited calls
  • Access to Admin Console
  • Multiple logins
  • Security
  • Unlimited support

Usage-based pricing

You can charge your customers using measurements that apply to your solution, called metrics. A typical example of a metric is the time for which customers use your solution. For example, you can charge $0.05 per hour of use. Similarly, you can charge customers by the quantity of data processed by your application, the number of API requests customers make, and so on.

While you are choosing your metrics, you must also choose a reporting unit for each metric, which represents the granularity with which you measure your application's usage. You must measure the reporting unit as an integer, and not as a fractional number.

For example, consider a solution for which you charge $0.256 per gibibyte (1024 mebibytes) of data processed, and your reporting unit is by mebibyte. If a user processes 512 mebibytes of data, they are charged (512 Mib / 1024 MiB) * $0.256, or $0.128 for their usage. However, if your reporting unit is by gibibyte, the customer's usage is reported as 1 GiB, and they are charged the full $0.256 even if they only use a fraction of a gibibyte.

The following table includes examples of the types of metrics that you can use, and the reporting units that we recommend:

Metric type Supported units Recommended reporting unit Example price, shown on your GCP Marketplace page
Time Second, minute, hour, day 1 second (smallest possible) $5 per hour
Data processed

Byte, Kibibyte (KiB), Mebibyte (MiB), Gibibyte (GiB)

The units for data processed are based on binary multiples, where one Kibibyte is 1024 bytes, one Mebibyte is 1024 Kibibytes, and so on.

1 Mebibyte $10 per GiB
Storage time See units for time and data 1 Mebibyte-second $10 per GiB-hour
Custom metric N/A. You define the unit you want to measure, such as API request. Depends on metric. $10 per 1000 API requests

If you want to charge by a custom metric, ensure that the measurement is a delta metric, where each usage report represents the change in the value since the previous report. For example, you can set a price per email, and every hourly usage report represents the number of emails sent in the previous hour.

Pricing structure

After you have selected your metrics, you can select one of the following pricing structures:

  • Single rate: Customers pay a set price for their usage, and the charges increase in direct proportion to their usage. For example, if you charge $0.50 per hour of usage, and a customer uses your solution for 20 hours, they are charged $10.

    The following is an example pricing model with three pricing plans, each with on-demand pricing and a different set of features:

    Standard Pro Enterprise
    $0.002 per email sent $0.004 per email sent $0.006 per email sent

    Features:

    • Access to Admin Console

    Features:

    • Access to Admin Console
    • Multiple logins
    • Security

    Features:

    • Access to Admin Console
    • Multiple logins
    • Security
    • Unlimited support
  • Tiered pricing: If you want to give customers sustained-use discounts, you can create pricing tiers. The tiers apply over the course of a billing month. At the start of a new billing month, the price is reset to the first tier. You can define tiers for each metric that you base your price on.

    The following is an example of a pricing model with three pricing plans, each with tiered pricing:

    Standard Pro Enterprise
    • $0.002 per email sent for 0-1000 emails
    • $0.001 per email sent for 1001 - 2000 emails
    • $0.0001 per email sent for 2001+ emails
    • $0.005 per email sent for 0-1000 emails
    • $0.004 per email sent for 1001 - 2000 emails
    • $0.002 per email sent for 2001+ emails
    • $0.008 per email sent for 0-1000 emails
    • $0.006 per email sent for 1001 - 2000 emails
    • $0.003 per email sent for 2001+ emails

    Features:

    • Access to Admin Console

    Features:

    • Access to Admin Console
    • Multiple logins
    • Security

    Features:

    • Access to Admin Console
    • Multiple logins
    • Security
    • Unlimited support

    When a new billing month starts, the price is reset to the first tier.

    You can define separate sets of tiers for each metric that you base your price on.

Combined pricing

In a combined pricing model, customers pay a base subscription fee for using your software, and additional charges based on their usage. You can include a specific quantity of usage in your base fee. For example, the following pricing model has base subscription plans that include a number of API requests, and additional charges as customers increase their usage:

Standard Pro Enterprise

$9.99 / month subscription fee

$0 per request for 1000 API requests

$0.002 per request for 1000+ API requests

$39.99 / month subscription fee

$0 per request for 2000 API requests

$0.005 per request for 2000+ API requests

$99.99 / month subscription fee

$0 per request for 10000 API requests

$0.008 per request for 10000+ API requests

Features:
  • Email support
  • Access to Admin Console
Features:
  • Email + phone support
  • Access to Admin Console
  • Multiple logins
  • Security
Features:
  • Unlimited priority support
  • Access to Admin Console
  • Multiple logins
  • Security

After you have selected your pricing model, add your plan to the pricing information template, and send it to your Partner Engineer.

(Optional) Offering trial software

If you want to offer a trial of your software to GCP users, contact your Partner Engineer with the following information:

  • The trial period, for example, 30 days.
  • The maximum credit, in USD, that the trial is limited to.

Customers can choose any of your pricing plans, and the trial credit applies to the plan that they choose.

The trial ends when the customer reaches the credit limit, or at the end of the trial period, whichever comes first. For example, if you offer a 15-day trial with a maximum credit of $100, the trial ends when users reach the $100 limit, or at the end of 15 days.

At the end of the trial period, customers are charged based on the pricing plan that they chose. If the customer changed their plan during the trial, they are charged based on their new plan.

If your solution's pricing is usage-based, we recommend a trial credit limit that is twice the cost of the usage that you expect.

Was this page helpful? Let us know how we did:

Send feedback about...

GCP Marketplace