The price and the limits agree.
Every plan needs an exact price, billing cycle, included capacity, and a clear explanation of what changes when a plan changes.
Pricing and access
A clear offer deserves the same care as a clear handover.
Stemma is aligning product scope, billing, and legal terms before publishing the final public plans. A price without exact limits and policies is not a useful answer.
The standard
Pricing should explain the commitment, not obscure it.
This public page will publish the real offer only once it reconciles with the shipping product and the terms a customer is actually accepting.
Plain language
Visitors should not need a sales call to understand the plan they are choosing.
Real boundaries
Every limit, option, and change in service needs to be concrete enough to evaluate.
One source of truth
The comparison, checkout, billing account, and subscription terms should say the same thing.
The test we use
A plan you could explain across a desk.
Price, limits, and terms should survive being read aloud to the person paying for them. That is the bar the published page has to meet.
Before we publish
Three checks prevent a bad pricing page.
They are ordinary checks, but they matter most when a product is trusted with important household information.
The product and the page agree.
The public comparison cannot promise a feature, release path, or export behavior that the current product does not support.
The terms and the promise agree.
Cancellation, retention, inheritance, and payment language need legal review before they become part of a visitor decision.
Get the launch note
One email when the plans publish.
Leave an address and we will send a single note when price, limits, and terms reconcile — no list, no sequence, nothing before then.
Start with the record
The best way to judge the product is to see whether it makes the first handover clearer.
Open a vault or contact the team with a question about access, plan scope, or the product itself.