I still do not know the right price for Penci.ly

I do not want Penci.ly to become another subscription that somebody enjoys using but eventually cancels because they cannot justify paying for it every month.

I generally believe that useful software and other digital services should be accessible to people with very different budgets, and I want that idea to influence how Penci.ly is priced.

The problem is that this becomes much more complicated when you have to turn that principle into an actual business model.

A web application has ongoing costs even after the initial product has been built. Files need to be stored somewhere, data needs a backend, infrastructure has to run continuously, and bugs still need to be fixed. As more people use the service, costs that look tiny for one user can become significant across thousands of users.

There is also the continuing development work. Releasing a feature does not mean the work around that feature is permanently finished because it still needs maintenance, improvements, and changes as people begin using it in ways I did not anticipate.

The question is therefore not simply how cheaply I can offer Penci.ly. I have to find a price that allows the service itself to continue existing.

I am trying to find a balance where somebody with a small budget can still get genuine value from Penci.ly while people who use the product more heavily help support the cost of running it.

One question I keep returning to is what a free user should actually be able to accomplish.

I do not want the free version to be some almost useless demo where every interesting action ends by asking for a credit card. Ideally, somebody using Penci.ly for free should be able to create something complete and genuinely useful because that is how they can understand whether the product belongs in their life in the first place.

I am much less certain about where the paid boundary should begin. More storage is an obvious possibility because storage has a real cost. Heavier usage or additional capabilities could also make sense, particularly for people who depend on the product more regularly.

What I do not want is to look at every useful feature and immediately decide that it is another opportunity to charge somebody.

I still do not have a final pricing model, which is fine because the product itself is still developing. What I do know is that affordability is part of the product I want to build, while sustainability is what would allow me to keep that promise over the long term.