A price makes a promise before somebody has used the product.
It tells them something about what the relationship will be: a purchase, a recurring service, a free tool, or a game supported in another way. If the terms are hard to understand, the uncertainty becomes part of the experience.
Working in operations and finance makes me attentive to both sides of that relationship. The person needs to know what they are agreeing to. The company needs to understand the work and cost that the agreement will leave it with.
Explain the arrangement
A product page should make the practical terms easy to find. What can somebody try? What costs money? Is the payment one-off or recurring? Are there ads? Is there a limit that matters to the task they have in mind?
These are useful questions even for a small application. “Free” should have enough detail behind it that a person is not surprised at the point where they want to finish their work. A purchase should describe what is included without relying on an optimistic interpretation of a headline.
Different products can reasonably have different arrangements. Roomy is offered as a free tool. StetPDF, still in development, is being presented around a one-off purchase rather than a subscription. The individual product page is where the current terms belong.
Time belongs in the calculation
The price on a page is visible. Other costs arrive as effort. Creating an account, understanding a licence, getting a file out, asking for support: each can take time from the person who wanted to do a straightforward job.
That does not mean every step can be removed. It means a step ought to have a reason proportionate to the product. A small tool should be able to explain why it needs what it asks for.
The same attention helps the company. Complicated terms generate questions. Unclear limitations turn into disappointment. An arrangement that is easy to explain can be easier to administer and easier to honour.
Leave room to keep the promise
There is no universal price that makes a product responsible. The relevant question is whether the arrangement supports the work behind it and makes sense for the people using it.
For an independent studio, this is closely connected to scope. A modest product with clear boundaries can be something we are able to maintain over time. Expanding what is included creates obligations as surely as expanding the code.
The terms are therefore a design decision as well as an operating decision. We should be able to describe them plainly, keep them consistent with the product and explain a change before it becomes a surprise.
A good relationship with a customer has room for ordinary questions. What does it do? What will it cost me? What can I expect after that? Those deserve ordinary, understandable answers.