Begin with the real object
The product is the relationship between a person and the thing they own: what a unit represents, which rights it carries, how value changes, where income comes from, and what limits transfer. Explain that object before introducing price or return.
Separate verification from availability
People need to distinguish “the asset was checked” from “this is suitable for me” and “this unit is available now.” One reassuring badge cannot safely represent all three. Use distinct states, show who performed the check, and make its date and scope visible.
Make action state impossible to confuse
- Show exact amount, units, fees, and resulting position before approval.
- Separate submitted, pending, completed, failed, and reversed states.
- Provide a human-readable receipt connected to the underlying record.
- Explain recovery paths before asking people to contact support.
Design for risk comprehension
Risk should live beside the decision, not only in a distant legal document. Liquidity limits, valuation assumptions, income variability, custody, and jurisdiction should be expressed in plain language with progressive detail.
Keep evidence available
Abstraction and transparency are not opposites. Default to a calm interface, then let people inspect source documents, transaction references, and verification evidence. The product earns trust by making complexity optional, not invisible.