Clavem

Upgrade pricing

Upgrade pricing is a discounted price that existing customers pay to move to a new major version of your software, instead of the full price a new customer pays.

How it works

An upgrade offer needs four decisions.

  1. The boundary. Usually a major version: the first number in semantic versioning, such as 3.x to 4.0. Updates inside a major version stay free.
  2. Who is eligible: owners of the previous version only, or of any earlier one.
  3. The price: a flat amount or a percentage off the new-customer price.
  4. The proof: how you know they own the old version, usually the email on their order or their license key.

Upgrade pricing is what lets a perpetual license pay for continued development without a subscription. The alternative for the same problem is software maintenance, a time-based fee.

A worked example

An illustrative case: version 4 costs $79 for new customers, and owners of version 3 pay $49. The discount is (79 - 49) / 79 = 38 percent.

If 1,000 people own version 3 and 25 percent upgrade (an assumed rate, not a benchmark), that is 250 x $49 = $12,250. At a $79 full price the same 250 would pay $19,750 if they all bought new, but most would not. The upgrade price is a bet that a lower price brings more owners across.

Mechanics with Stripe and Clavem

This is one approach, not a built-in feature. A Clavem license belongs to one product, and each product has its own device limit, validity and Ed25519 key pair. So a new major version is cleanly sold as its own product:

  1. Create a product for version 4 in Clavem.
  2. In Stripe, create two prices for it: the full $79 and the upgrade $49. Map both to the version 4 product. A mapping to a price wins over a mapping to its Stripe product, so either price can be mapped on its own.
  3. Give owners of version 3 a way to reach the $49 price: a promotion code, or a link you send privately. Stripe’s Checkout supports promotion codes.
  4. Look up eligible owners with the management API: GET /v1/admin/licenses?email=ada@example.com.

The version 4 app verifies tokens against the version 4 public key and product id. A version 3 token does not verify there, which is the point: the buyer gets a new key when they upgrade, and their version 3 key keeps working in version 3.

Upgrade pricing versus a free update

A free update arrives inside the same major version and needs no new purchase. An upgrade changes the product and asks for a new payment, with a discount as the reason to accept. Be explicit about which versions fall on which side. The longer treatment is in upgrade pricing for major versions.

How Clavem handles it

Clavem has no upgrade flow, no eligibility check and no automatic key swap. It issues the version 4 key when the Stripe checkout is paid, as for any purchase. Everything about who may buy at the upgrade price is yours: your records, a coupon code, or a private link. The old license stays untouched, active or expired as it was.

Questions

Should old license keys work in the new version?

Only if you decide so. If the new version is sold as a new product, old keys belong to the old product. Say in the upgrade offer that the buyer receives a new key.

How do I prove someone owns the old version?

Look the buyer up by email or key in your own records. Then send them a promotion code or a private link for the upgrade price.