Stigg case study

Go to desktop to view this case study

The case study includes detailed interactive product canvases designed for a larger screen.

Back to portfolio

Stigg · 2023 to 2026

Designing the model behind modern SaaS pricing

Three years shaping a monetization and entitlements platform, from pricing models and subscriptions to customer-facing experiences.

Role
Product Designer at Stigg
Focus
Product design, UX research, design systems
Design scope
Core platform workflowsCustomer and stakeholder researchBilling and entitlement interaction modelsDesign system established for the platform

What Stigg solves

Pricing decisions have to become product behavior

A plan may begin in a spreadsheet, but the product still has to know what every customer can access.

As SaaS companies grow, pricing decisions spread across billing, application code, sales agreements and customer experiences. Stigg creates one shared model so those decisions become reliable product behavior.

Business inputPricing strategyPlans · Packaging
→
Shared modelStiggProduct Catalog · Subscriptions · Entitlements
→
MoneyBilling
BehaviorProduct access
ExperienceCustomer UI

Research and framing

The tools were capable. The mental model was fragmented.

As part of my research, I studied how teams described pricing decisions and how competing products represented them.

I combined customer and stakeholder conversations with a review of Stripe, Chargebee, Maxio, Metronome and Orb. The opportunity was one coherent model for packaging, billing and access.

What the research established

01

People think in customers and plans.The system still needs products, charges, features and entitlement values.

02

B2B agreements need exceptions.Flexible configuration cannot make the default path feel unsafe or unpredictable.

03

The result must stay visible.Users need to understand the subscription they are assembling before they create it.

Modeling access

The model behind product access

The challenge was giving teams flexibility without exposing the complexity of the underlying authorization model.

I separated capabilities into Features and their rules into Entitlements, creating one interaction model for boolean access, metered usage, numeric limits and configuration values.

Interactive walkthrough

Explore how feature types become entitlement rules.

Analytics

A simple on or off entitlement. Adding it to a plan grants access to the capability.

{ access: true }

Feature Groups

One capability, different levels of access

The challenge was preserving one shared capability while allowing it to mean something different in every plan.

Feature Groups create the commercial layer: related features can be packaged and reused across plans while each tier retains its own entitlement values.

Interactive walkthrough

Create new feature group

Features
Support levelfeature-localizedaccess
Surge protectionfeature-surgeprotection
Bandwidthfeature-bandwidth

Creating a subscription

Turning a plan into a customer subscription

The challenge was preserving flexibility without making a high-impact workflow feel unpredictable.

I connected the customer, product and plan in one flow, keeping charges, schedule and billing decisions in context while a persistent preview made the result clear before creation.

Customers / Jared Dunn / Create subscription
Jared Dunnjared@piedpiper.com · customer-abc1234

Subscription content

Plan configuration

ChargeQuantityPrice
Base chargeRecurring platform fee
1
$20.00/month
Seatsfeature-seat
2
$39.00seat / month
API Callsfeature-api-calls
10,000
$0.01call / month
Templatesfeature-templates
3
$12.00template / month

Subscription schedule

Effective date
Ends at

Free trial

Trial period⇄

Discount

Coupon

Billing

Payment method on file · •••• 4242

Widget themes

One brand system, rendered with a company’s product data

The challenge was separating presentation from data without making either side feel disconnected.

I separated presentation from Product Catalog data through reusable themes for Checkout, Pricing Table, Customer Portal and Power-up Badge, with a live preview showing the result before publishing.

Pricing table previewDesktop · 100%
Essentials

$49/ month

Includes:
  • 10,000 API calls
  • 3 templates
  • 5 seats
Growth

$149/ month

Includes:
  • 100,000 API calls
  • Unlimited templates
  • 20 seats
Scale

Customannual

Includes:
  • Custom API calls
  • Unlimited templates
  • Custom seats

What the system enables

One product language, carried from customer decisions into delivery

Customer understanding

Configuration and its consequences stayed visible in the same workflow, helping complex subscription decisions remain understandable before creation.

Product coherence

Features, Entitlements and Feature Groups established a shared language for representing access across plans, subscriptions and customer experiences.

Design and engineering

Recurring decisions became tokens, implementation-ready specifications and Storybook components that could be reviewed and refined with engineering.

Reflection

Complexity becomes useful when consequences stay visible

Complex systems do not need to feel simple, but the decisions within them must remain understandable.

Across each workflow, clarity came from showing relationships, keeping consequences in context and giving flexible paths a dependable default.

How the practice evolved

In the final year, recurring decisions became tokens, implementation-ready specifications and Storybook components reviewed directly with engineering.

After launch: FullStory sessions helped identify hesitation and guide follow-up refinements.