We've extended the supported pricing models for pay-as-you-go (PAYGO) charges, and now include support for tiered and volume pricing.

We've extended the tiered and volume pricing models to allow charging customers a flat fee for every usage tier.

With this change you can charge customers a flat fee, per unit fee or combination of both in each tier.

For example, you can now charge customers a flat $200 fee for the first 20 units, then $5 for every unit in the 21-50 tier, and $500 + 3$ per unit from the 51st unit and upwards.

We've added an ability to undo subscription's scheduled cancelations. To do so:

1. In the Stigg app - click on the "Cancel update" button.

2. Using the Stigg API and SDKs - leverage the cancelSubscriptionScheduledUpdates method.

When billing customers using invoices or payment links, it's now possible to customize the number of days before invoices are due.

Doing so allows you to customize customer billing according to the business terms that were agreed on.

By default, generated invoices are due within 30 days. 

We're excited to announce our native integration with Zuora!

Zuora is a billing solution loved by finance teams for its flexibility, yet it can be very complex for engineering teams to maintain.

Stigg abstracts Zuora away from your code, making changes to pricing and packaging effortless - after the integration is set up, changes to the Stigg product catalog (product, plans, add-ons), customers and subscriptions are automatically synced to Zuora.

Using this integration you can leverage Stigg for managing your pricing and packaging in no-code and Zuora for billing.

Stigg's native integration with Zuora is currently available in beta for customers of the Growth and Scale plans. 

More details about the integration can be found here.

We've added an ability to align the billing anchor of all paid subscriptions to the same anchor.

When selected and when customers have multiple active subscriptions either to the same product or to different products, the billing anchor of all of the paid subscriptions will be aligned to billing anchor as the first paid subscription. 

This allows invoices of multiple subscriptions to be generated on the same day. 

The configuration can be changed using no-code under the Account Settings section, and will affect all of the account's environments. Updating the configuration will affect all newly created subscriptions.

More details can be found here.

We've added an ability to schedule the cancelation of trial subscriptions. 

With this new change, trial subscriptions can be can be scheduled for cancelation at the end of the trial period or on a specific date. If the specific date is longer than the trial period, the trial will automatically be extended to accommodate for that.

When a trial is extended, its scheduled cancelation is removed. To cancel it, simply schedule its cancelation again.

When integrating Stigg via webhooks, canceled trials will be reflected via subscription.canceled events and expired trials via subscription.trial_expired events.

Scheduling cancelation of trial subscriptions is supported via the Stigg app, the Stigg API and Stigg SDKs.

We've extended the Subscription Details screen in the Stigg app to provide visibility for the next estimated bill. 

When clicking on the estimated bill amount, users can view a breakdown of all of the upcoming charges.

Viewing the next estimated bill is especially helpful for products that are monetized via pay-as-you-go and hybrid pricing models.

A common pricing model in SaaS is to offer team plans with separate usage enforcement for each team member. For example, as part of a team plan every team member gets access 100 AI actions per month.

We've made now it easier than ever to implement this pricing model by leveraging Stigg to automatically cancel the team members' subscription when the team subscription is canceled.

More details about this pricing model and how model it in Stigg can be found here.

Every event on the Stigg platform is audited, and visibility for these events is available via the Activity Log. 

Using the Activity Log users can answer the following questions:

1. What happened?

2. When did it happen?

3. Who (or what) triggered the event?

Thus, the Activity Log serves as an audit log for actions on the Stigg platform and can also be useful for troubleshooting.

The Stigg app includes both a general activity log with all of the events of a specific environment, as well as an entity-specific log with a pre-filtered list of events for that entity. Event are also accessible via API.

The Activity Log is available in beta for customers on the Stigg Growth plan or higher, and currently includes events from May 22nd, 2024 or later.

More details about the Activity Log can be found here.