Layered Appsmith billing interfaces connected as one resilient system

Case study

Appsmith Billing

Designing billing across cloud, self-hosted, licences, and recovery

Appsmith

Choose your depth

The problem, my contribution, outcomes, and strongest screens.

My role

Product design · Experience strategy · Systems modelling

Product focus

A cross-product billing and licensing system spanning usage, pricing, purchase, access, failure, and recovery.

Overview

I led the experience strategy for Appsmith’s billing and licensing journey across the customer portal and self-hosted product. The system connects usage, pricing, plan selection, licence setup, payment health, and recovery without making customers learn a different model at every handoff.

The problem

Billing crossed cloud and self-hosted products, usage-based pricing, Community, Business, and Enterprise plans, trials, licence keys, payment failures, and downgrades. The challenge was to make those relationships understandable while keeping routine actions direct and consequential actions explicit.

What I drove

  1. Mapped how plan, licence origin, usage, account role, payment status, and lifecycle stage affect the next available action.
  2. Turned scattered business rules and edge cases into a shared decision model for product and engineering.
  3. Designed connected journeys for evaluation, upgrade, installation, licence management, payment recovery, and downgrade.

What changed

  1. Created one shared model for usage, plan, licence, payment, role, and lifecycle states.
  2. Gave product and engineering explicit behaviour for high-risk billing moments across cloud and self-hosted products.

Impact

What the work was designed to move

Business impact

Unified usage, billing, and licensing rules reduced cross-team ambiguity across the customer portal and self-hosted product.

Customer impact

Customers can see what a plan costs, what it unlocks, and what changes before they upgrade, recover a payment, or downgrade.

Revenue impact

Supports trial conversion, upgrades, and payment recovery through clearer next steps at each revenue-critical moment.

Continue reading

See the product strategy and decisions.