When it comes to B2B SaaS, provisioning enterprise subscriptions isn’t just about toggling a few features on or off. It’s about adapting to contracts, handling variability, and doing so at scale with both precision and flexibility. Stigg is purpose-built to solve these challenges with a system that supports price overrides, variable entitlements, and provisioning-only setups, all through no-code tools or deep API integrations.

​

Entitlements-only provisioning with Stigg

You keep your enterprise billing logic exactly where you want it (your billing platform, invoices, CPQ, ERP, or internal tooling), while Stigg becomes your system of record for entitlements.

​

Step 1: Model your product packaging in Stigg

Even when Stigg is used only for entitlements, price modeling is still valuable because it keeps packaging coherent, provides a structured place to define the plan and makes it easier to scale from self-serve plans to enterprise templates. Define:

• Features and entitlements (e.g. seats, usage limits, access flags)
• Plans that bundle these entitlements
• Even if billing is external, this keeps packaging consistent across product, sales, and engineering

​

Step 2: Create a custom plan

Custom plans are used when both price and content are negotiated per customer. When Stigg is integrated with a billing solution, subscriptions to custom plans will not be created in the billing system. To create a Custom Plan:

1. Create a new plan.
2. Select Custom as the plan type.
3. Continue to the default free trial configuration.

Subscriptions to custom plans are not created in the billing system, making them ideal when billing is managed separately.

​

Step 3: Add entitlements to the custom plan

Now define what customers on this plan can do—features, limits, access flags, quotas, etc. For example:

• Seats
• API calls/month
• Data retention days
• Environments (prod/sandbox)
• SSO / SCIM access
• Advanced modules

You’ll define these as entitlements on the plan.

​

Step 4: Mark entitlements as variable

Enterprise contracts usually differ only in values, not structure. To define a variable entitlement:

1. Open the entitlement modal.
2. Click the Variable entitlement value icon.

Variable entitlements must be set when provisioning a subscription.

​

Step 5: Provision a subscription

When a deal is closed, provision the customer subscription using the custom plan. You can do this in two ways:

​

Using the Stigg app UI

1. Select the customer.
2. Provision a subscription to the custom plan.
3. Enter the negotiated values for each variable entitlement.

​

Using the Stigg SDK

1. Create the subscription programmatically.
2. Pass the variable entitlement values from your CRM, CPQ, or internal tools.

​

Step 6: Enforce entitlements in your product

Your application checks Stigg entitlements at runtime to control access and limits, while billing remains fully managed in your own system.

​

Stigg is used as the single system for both entitlement provisioning and customer billing

For many teams, Stigg is used as the single system for both entitlement provisioning and customer billing. This is ideal when you want consistent packaging, flexible enterprise pricing, and invoice-based billing—without maintaining parallel systems.

​

Step 1: Model your product and pricing in Stigg

Start by defining:

• Features and entitlements
• Paid plans that bundle those entitlements
• Base pricing for plans and add-ons

This creates a clear, maintainable pricing model that supports both self-serve and enterprise customers.

​

Step 2: Create paid plans

Paid plans represent subscriptions that are billed through Stigg. Use paid plans when:

• Billing is handled by Stigg
• You want subscriptions to generate invoices
• Pricing is mostly standardized, with room for overrides

These plans serve as the baseline for enterprise subscriptions.

​

Step 3: Provision a subscription

When a customer is ready to go live, provision a subscription to a paid plan. You can provision subscriptions:

• Manually via the Stigg app UI
• Programmatically via the Stigg SDK

At this stage, the subscription inherits the plan’s default pricing and entitlements.

​

Step 4: Override plan charges at the subscription level

Enterprise deals often require custom pricing while keeping the same plan structure. Stigg allows you to override the default plan price per subscription, without creating new plans.

​

How plan price overrides work

You can override prices when provisioning or updating a subscription, allowing you to apply a different recurring price for the same plan while Stigg continues to manage the subscription billing.

​

Using the Stigg app UI

1. While provisioning or editing a subscription, hover over the plan charge.
2. Select Edit price.
3. Enter the negotiated price.
4. A visual indication appears next to the overridden charge.
5. Confirm the subscription to apply the changes.

This lets you offer the same plan at different price points across customers.

​

Step 5: Override add-on prices at the subscription level

Add-ons can also be priced differently per customer, which is especially important for enterprise deals where volume-based or bundled add-ons are commonly negotiated, while still keeping add-ons reusable and standardized and maintaining pricing flexibility at the subscription level.

​

Using the Stigg app UI

1. Hover over the relevant add-on charge.
2. Select Edit price.
3. Enter the custom price.
4. A visual indicator shows the override.
5. Confirm provisioning.

Both plan charges and add-on prices can be overridden in the same subscription.

​

Step 6: Bill customers using invoices

Enterprise customers often pay via wire transfer rather than card payments. Stigg supports this through invoice-based billing.

​

Prerequisites

• A paid plan is defined in Stigg
• Stigg is integrated with Stripe
• The customer has a valid email address
• Bank details are available on invoices (via Stripe ACH or invoice fields)

​

Provision an invoice-billed subscription

When provisioning the subscription in the Stigg app:

1. Open the customer.
2. Click + Add under Subscriptions.
3. Configure:
   • Plan
   • Add-ons
   • Price overrides (if applicable)
4. Under Payment, select Generate an invoice to the customer to pay manually.
5. Ensure Invoice status is set to Open.
6. Optionally define payment terms (e.g. number of days to pay).
7. Create the subscription.

​

Share the invoice with the customer

Invoices can be shared either via a payment link or as a PDF. The payment link provides an interactive invoice UI that allows customers to pay using wire transfer or card and automatically expires after 30 days by default. Alternatively, the invoice can be downloaded as a PDF from the subscription details, including all required bank transfer information.

​

Payment and invoice status

When a subscription is paid via ACH through Stripe, the invoice is automatically marked as paid. If payment is made outside of Stripe, the invoice must be manually marked as paid in the Stigg app. Marking an invoice as paid updates the billing status in both Stigg and Stripe but does not affect entitlement activation, as access is already granted when the subscription is created. If an open invoice is not paid within the allowed payment interval, the subscription is automatically canceled.

​

Recurring billing behavior

For subsequent billing cycles, if the customer has a payment method on file, Stripe automatically attempts to charge it. If no payment method exists, an invoice is generated and sent to the customer by email. Invoice reminders and related billing behavior can be configured in Stripe. Stigg currently displays the latest invoice for each subscription, while the full invoice history is available through the Stripe dashboard.

​

Full automation from Salesforce

For sales-led organizations, subscription provisioning and billing often start in the CRM. With Stigg’s native Salesforce integration, you can fully automate the flow from deal close to active subscription—covering entitlements, pricing, and invoicing—without manual steps or custom glue code. With recent enhancements, Salesforce can now provision paid subscriptions, including subscription-level price overrides, not just custom (entitlements-only) plans. This allows Stigg to act as an abstraction layer for billing, even when provisioning is initiated directly from Salesforce.

​

How it works

When an opportunity is closed in Salesforce:

1. Salesforce triggers subscription provisioning in Stigg.
2. A paid plan is selected.
3. Plan charges and add-on prices can be overridden based on the negotiated deal.
4. Stigg creates the subscription, grants entitlements, and generates invoices.

This enables basic quote-to-cash (Q2C) flows while keeping fulfillment, entitlements, and billing logic centralized in Stigg.

​

What this enables

• End-to-end automation from Salesforce to production access
• Support for enterprise pricing without creating customer-specific plans
• Centralized entitlement enforcement in Stigg
• Invoice generation and billing managed by Stigg, even when sales owns provisioning
• Reduced operational overhead between Sales, Ops, and Engineering

​

Typical flow

1. Sales negotiates pricing and add-ons in Salesforce.
2. Opportunity is marked as Closed-Won.
3. Salesforce provisions a paid subscription in Stigg.
4. Price overrides are applied at the subscription level.
5. Entitlements are activated immediately.
6. Invoices are generated and managed by Stigg.