Overview

Plans represent the functionality of a product that customers are billed for during a pre-defined time period (for example: monthly or annually).

Stigg's allows product manager and growth team members to manage plans, their content, price and trial configuration without requiring additional engineering changes.

The functionality that’s included in each plan is defined by a combination of features and their configuration, referred to in Stigg as entitlements.

Published plans appear in paywalls that are rendered to customers using Stigg's SDK.

Viewing the list of plans

To view the list of plans of a specific product:

1. Select the relevant product from the Products sub-section of the Product Catalog.
2. Scroll down to the Pricing > Plans section of the selected product.

📘

Also see the product's "Modeling your pricing" section.

Viewing a flat list of all of the plans of all of the products is possible by selecting the Plans sub-section of the Product Catalog from the left navigation pane.

Creating plans

To add a plan, click on the "+ Add plan" button under the Plans section of the selected product.

Enter the below details in the opened modal:

1. Name - the name of the plan.
2. ID - will be auto-generated by Stigg. Use this ID to refer to the plan in your application. To link an existing plan, override the auto-generated value.
3. Description (optional) - the plan's description.

📘

The values that are entered in the "Name" and "Description" fields will be leveraged by Stigg to render the customer-facing paywall and customer portal; therefore, it’s recommended to use customer-friendly texts.

Confirm the action by clicking on the "Create" button.

New plans are created as drafts. Plans must be published in order to be visible to customers and be able to create subscriptions for them.

🚧

Before publishing a plan, make sure to assign features to the plan and define their pricing.

Defining the plan's price

The price that's defined in Stigg will be shown to customers in the paywalls that are rendered using Stigg's SDKs. When Stigg is integrated with a billing solution (for example: Stripe), subscriptions will be created in the billing solution using the price that was defined in Stigg.

Click on the "Set" button under the Pricing section of the selected plan.

In the opened modal, select the plan type (free, paid, custom) and enter the actual price when relevant.

Click "Save changes".

Free plans

Free plans are usually intended to allow your customers to access a limited functionality of your product, and charge them a premium for supplemental or advanced features - this is usually referred to as a "Freemium" model.

Customers are not required to enter any payment information in subscribe to such plans.

Paid plans

Paid plans in Stigg are intended to be used in order to allow your customers to subscribe to your product in a self-served manner.

When defining paid plans, the following information is also required:

1. Pricing model
   1. Flat fee - represents a fixed recurring fee.
   2. Per unit - represents a recurring fee according to the feature quantity that customers sign up for upfront.
      1. Per unit pricing is dependent on a fluctuating metered feature.
      2. Minimum and maximum quantity restrictions can also be set:
         1. The quantity restrictions only apply to subscriptions that are created in a self-served manner - the restrictions will be visible in Stigg's plan pickers widget, and when Stigg is integrated with a billing solution also enforced in the rendered checkout page.
         2. The restrictions are not enforced during manual creation of subscriptions in the Stigg Console.
   3. Usage based - charge customers according to the actual consumption of the plan's features. Usage based pricing is dependent on a feature with an incremental meter.
2. Billing period - monthly, annually, or both.
   1. For usage-based pricing only a monthly billing period can be set.
3. Price in each billing period in USD.

📘

Per-unit and usage-based pricing depend on metered features. A relevant entitlement for the dependent feature will automatically be added to the plan.

If the plan already includes entitlement for that feature, it will be overridden by the value of the price point.

Custom plans

Custom plans are intended to be used when the price of subscriptions to them is negotiated with each customer and therefore varies between different customers, as is usually the case in sales-led opportunities.

📘

When Stigg is integrated with a billing solution, subscriptions to plans with a custom price will not be created in the billing solution.

Defining free trial periods

Paid and custom plans can be configured to start with a free trial period when a subscription is created.

Stigg's allows product manager and growth team members to add, modify and remove trial period for plans without requiring additional engineering changes.

To add a default trial period

1. Click on the "Add free trial" link in the Pricing section.
2. Set the default trial period in days or months.
3. Click on "Add".

To change the default trial period

1. Click on the dotted menu icon under the "Free trial" section and select the "Edit" action.
2. Enter the updated default trial period.
3. Click on "Save changes".

To remove the default trial configuration

1. Click on the dotted menu icon under the "Free trial" section and select the "Remove" action.
2. Confirm the action.

📘

Plans with a default trial configuration will have a proper indication in the product's "Pricing" section and plan list screen.

🚧

In the self-served flow:

1. Customers can only have one free trial per product.
2. When a customer has already paid for a plan, they're not eligible for a free trial - the reasoning behind this behavior is that free trials are intended to allow customers to try the product before they pay for it. If they already paid for it, they don't need to try it.

📘

Stigg provides maximum flexibility for administrators when manually creating subscriptions via the Stigg Console, specifically:

1. Subscription of paid plans can be manually created by an administrator to start with a free trial period, even when no default trial period is configured for the plan.
2. Subscriptions of plans with a default trial period can be manually created as paid subscriptions by administrators, even when a default trial period is configured for the plan.
3. Trial subscriptions can be created by administrators via the Stigg Console even if the customer had already trialed the product in the past or has paid for subscription.

More details can be found in the "Creating subscriptions" section.

Assigning features to plans

The functionality that’s included in each plan is defined by a combination of features and their configuration, referred to in Stigg as entitlements.

Inheriting entitlements from other plans

Stigg allows admins to define inheritance between plans. When a plan inheritance is defined, all of the entitlements of the base plan will included in the child plan.

The plan inheritance ensures that when entitlements are added to a base plan, they're automatically added to a child plan; thus enforcing a good-better-best model and preventing the need to manually updated each plan separately.

To inherit entitlements from a base plan, under the "Entitlements" section of the selected plan, select the relevant child plan from the "Everything included in" control.

Adding entitlements to a plan

To add entitlements to a plan, click on the "+ Add" button under the Entitlements section of the selected plan.

Search for the features that you'd like to assign to the plan and select them from the list.

Apply the relevant configuration for the selected features:

1. Configuration features must be defined with the configuration value.
2. Metered features can be defined with a limit or without one. Features with an incremental meter also need to be specified with the reset period (monthly, weekly, daily, or hourly), for example: to represent a feature with a limited number of API calls per month.

📘

Boolean features don't require any additional configuration.

Confirm the action by clicking on the "Add" button.

Overriding entitlements from other plans

When the plan inherits entitlements from a base plan, adding entitlements to the child plan overrides the configuration of the child plan. For example: if the entitlement in the base plan is for 10 seats, and an entitlement in the child plan is added for 50 seats, the entitlement of the child plan will override that of the base plan.

To override an entitlement in the child plan:

1. Scroll down to the "Entitlements" section.
2. Expand the "Everything in..." row to view the entitlements that are inherited from the base plan.
3. In the row of the entitlement that you'd like to override click on the dotted-menu item, and select the "Override entitlement" action.
4. Enter the new value that you'd like to set for the overriding entitlement.
5. Click on "Override".

🚧

Entitlements to boolean features can't be overridden.

Overriding entitlements will have an icon appear next to their value.

The value of overridden entitlements in will be crossed out.

Defining variable entitlement values

Entitlements of plans with a custom price can be defined as having a variable value, which will be required to be set during the provisioning of subscriptions of that plan to each customer.

This allows you leverage plans with a custom price as templates, where the actual entitlement value is set according to the contract that's defined with the relevant customer.

To define an entitlement as having a variable value between each subscription click on the "variable entitlement value" icon in the entitlement modal.

To change a variable entitlement to an entitlement with a defined limit, click on the "variable entitlement value" icon again.

Defining the entitlement order

By default, the order of entitlements in pricing tables that are rendered using Stigg (either using Stigg's pricing table widget or custom widgets) is determined according to the order that they were added to the plan.

The order can be changed using a drag-and-drop gesture, by dragging drag handle that appears in the left-most area of the entitlement row.

Controlling the entitlement visibility

By default, all entitlements that are added to a plan are visible to customers in pricing tables that are rendered using Stigg (either using Stigg's pricing table widget or custom widgets).

The entitlement visibility can be changed by clicking on the dotted-menu icon in the row of the relevant entitlement and selecting the "Customize display text and visibility" action.

In the opened modal, update the entitlement visibility and click "Save changes".

Customizing the entitlement display text

By default, entitlements appear in pricing tables that are rendered using Stigg (either using Stigg's pricing table widget or custom widgets) in the following format: <ENTITLEMENT_LIMIT> <FEATURE_UNITS>, for example: 10 seats, unlimited campaigns, 100 API calls per month.

To customize the display text, click on the dotted-menu icon in the row of the relevant entitlement and select the "Customize display text and visibility" action.

In opened modal, enter the custom display text.

Even when changed, Stigg will provide an indication for the default generated text.

To use the default display text, simply remove the custom display text.

To save the changes, click on the "Save changes" button.

📘

An indication about the default display texts that have been overridden by custom display texts will also appear in the Products > Pricing section

Removing entitlements from a plan

To remove an entitlement from a plan, click on the dotted-menu icon in the row of the relevant entitlement and select the "Remove" action.

Confirm the action by clicking "Remove".

Controlling the plan's visibility

By default, all published plans are visible to customers in pricing tables that are rendered using Stigg (either using Stigg's pricing table widget or custom widgets).

The plan's visibility can be changed by clicking on the "Edit" button that appears under the "Plan details" section.

In the opened modal, update the plan's customer visibility and click "Save changes".

Storing metadata

It's possible to store metadata on each plan. The metadata can then be leveraged by the hosting application and third-party solutions via the Stigg SDKs, API and webhooks to implement custom functionality.

To store metadata on a specific plan, under the "Metadata" section of selected plan click on the "Add" (if there's no metadata) or "Edit" buttons.

Enter the relevant keys and values.

Click "Add" (if there was previously no metadata) or "Save changes" buttons to apply the changes.

Publishing plans

After defining the basic details, entitlements and pricing of draft plans, click on the "Publish" button to make the plan available to all of your customers.

Editing published plans

Stigg's allows product managers and growth team members to make frequent and rapid changes to plans without requiring additional engineering changes.

Changes can be rolled out to both existing and new customers (for example: when adding or removing an entitlement from a plan), or only to new customers (for example: when changing the plan's price).

Stigg uses a versioning mechanism to support this functionality - every time a plan is edited a new version is created. Changes to the plan can be published or discarded.

To edit a plan, click on the dotted menu icon of the relevant plan, and select the "Edit" action.

Apply the relevant changes to the plan.

📘

Some properties of a plan (for example: its ID), cannot be modified after the plan is created.

📘

Plans with unpublished changes will have a proper indication in the product offering and plan list screens.

Reviewing changes

To review the changes to the plan since the last published plan version, click on "review changes" or "Review & publish" in the plan's header.

In the change review modal:

1. Green backgrounds represent items that were added since the last published version.
2. Orange backgrounds represent items that were updated since the last published version.
3. Red backgrounds represent items that were removed since the last published version.

Publishing changes

📘

Changes must first be reviewed before they can be published.

To publish changes, in the change review modal select the target audience to which the changes will be applied:

1. New subscriptions - the changes will only affect subscriptions that are created after the new plan version is published.
2. Both existing and new subscriptions - in addition to (1), existing active subscriptions will be migrated to use the new plan version.

When applying changes to existing subscriptions, an acknowledgment of a series of disclaimers is required.

🚧

Default grandfathering of subscription pricing when rolling out pricing changes

Pricing changes are automatically published only to new subscriptions. Existing subscriptions can be migrated to the latest price manually using the Stigg UI or programmatically.

Discarding changes

To discard pending changes from a plan, click on "Discard changes" in the plan's header. Confirm the action in the opened dialog.

Deleting plans

Deleting a plan is possible from the Plans sub-section of the Product catalog.

To delete a plan, click on the dotted menu icon of the relevant row, and select the "Delete" action.

Confirm the action by clicking on the "Delete" button in the opened modal.