We've added an ability to programmatically calculate the cost of a subscription before it's created and before updates to it are applied.

The new APIs allow you to provide your customers with an estimation of the subscription cost, and save you significant development time by removing need for implementing the calculation yourself. When updating a subscription, these APIs allow you to preview the effect of the changes on the current subscription cost.

When Stigg is integrated with a billing solution (for example: Stripe), Stigg will leverage the customer and subscription information from the billing solution, such as proration and customer credits, for the calculation of the subscription cost; thus, providing more accurate estimation of the subscription cost.

The new APIs are available in the Node.js SDK version 0.56 or later. More details about the APIs can be found in our technical documentation.

The default plan order throughout the Stigg platform is now determined according to their price:

1. Free plans appear on the left
2. Plans with a custom price (i.e. enterprise plans) appear on the right
3. Paid plans will appear between free and custom plans, and will be ordered according to their price from lowest to highest. Plans with a usage-based price will appear after plans with a flat fee and per-unit price.

The updated plan order is also reflected paywalls that are rendered using the Stigg JavaScript SDK (from v0.44.0 or later) and the Stigg React SDK (from v0.15.0 or later).

Stigg allows admins to define inheritance between plans. When a plan inheritance 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.

We've improved the user experience of the plan inheritance definition and moved it to the "Entitlements" section of the plan details, which better communicates the effect of the inheritance.

To inherit entitlements from a base plan, select the relevant child plan from the "Everything included in" control.

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.

We're excited to share that the Stigg platform can now be leveraged to run pricing experiments on your customer base.

Using this new functionality you can run A/B tests to test different pricing strategies, and determine which strategy results in an increased conversion rate, revenue and overall customer lifetime value (LTV).

The first supported use-case allows you to test how changes to your product's customer journey affect the conversion rate of your users to paying customers.

For example: using this experiment you can determine whether it's preferable to define your customer's initial access to your product using a freemium, a free trial period, or even a reverse trial model.

Basic analysis of the experiment results can take place inside the Stigg platform:

More thorough analysis can take place using third-party applications, such as Mixpanel and Amplitude, by integrating Stigg with them.

Together with Stigg's ability to provide insights about your pricing strategy and support for plan and add-on versioning, the new experimentation capability allows you to test and rollout packaging and pricing changes to your customers with confidence.

To learn more how you can run your first experiment, click here.

⚠️ In order to run experiments on the customer journey, customers must be created using the provisionCustomer API.

We've extended our API and SDKs to allow developers to programmatically update existing subscriptions by adding and removing add-ons. The new APIs also allow updating of the add-on quantity.

When integrated with a billing solution such as Stripe:

The next step would be to include add this functionality to the Stigg Console UI.

The relevant SDK documentation can be here and here.

We've improved the navigation experience to products that are defined on the Stigg platform.

When only a single product is defined, clicking on the "Products" item from the left navigation pane will immediately take the admin to relevant product.

Adding additional products is possible using the "+ New product" action in the drop-down menu that appears in the top-left corner of the product details screen.

When there are more than one product, the aforementioned drop-down menu also allows quick switching between the different products. Alternatively, admins can click on the "Products" item in the left navigation pane and select the relevant product that they'd like to view.

We've extended integration with Stripe to support importing of plans that have per-unit and usage-based pricing.

The import flow now also supports searching for specific Stripe product and customers; thus, allowing gradual import of entities from Stripe to Stigg.

The Stigg product catalog now includes support for coupons.

Coupons can be used to grant percentage discounts (X% off) to specific customers for all of their subscriptions.

The discounted price is reflected under the customer details screen in the Stigg Console, as well as the customer portal that can be generated using the Stigg SDK.

Coupons are synced to Stripe, and when a coupon is applied or removed from a customer in the Stigg, the action is also propagated to Stripe - this de-facto means that Stigg can be used to manage coupons in Stripe.

We've adapted the UX of the Stigg Console to better cater to developers' needs - since the integration between the app's codebase and Stigg takes place at the feature-level, we've added instructions on how to integrate each feature directly within the Stigg Console.

Developers can simply copy the relevant snippets and see Stigg in action immediately 🚀, read our documentation or invite additional team members.

The instructions also include syntax highlighting for the platforms that we support.

We've added an ability to store customers' payment details in Stripe directly from the Stigg Console.

Valid payment methods are required in order to create subscriptions for paid plans and add-ons.

The new functionality allows CS and technical support representatives enter the relevant payment information directly from the Stigg Console. The payment details are stored directly in Stripe.

Storing the payment details can be done proactively for each customer under the Customer details section of the Customer details screen, or as part of the subscription creation flow when the customer doesn't have any valid payment details defined.

The Stigg Console provides visibility whether the customer has a valid payment method defined and the last 4 digits of that payment method under the Customers > Customer details screen.