[novitzmann]

It depends on how long you see the product lifespan, how fast and whether you develop it and release new versions at all, does the technical support you provide apply to all versions of the product? (in my opinion this is a bit crazy, unless you have a larger team). Does the license apply to the version you are currently selling or to all future versions you will produce? There are many variables that can be taken into account to have a bit of an advantage, putting the customer in a situation where: technical support applies only to new versions of the product (and you set the rodmap yourself so you can go far away from the features they liked when buying your product - thus not supporting them), offer custom work on the product, technical support for old versions - to be considered if at all possible. It may turn out that the one-time purchase cost for the customer will be more expensive than the renewed license.

[jainvivek]

Agreed. As it is a utility and simplistic product, it will not have many more features added later. Hence I sold lifetime deals with promise of all future upgrades and support.

[novitzmann]

Then ask yourself a question - how big of a support you gonna provide ? I would limit support hours to an annual amount you can accept, and treat larger needs beyond that limit as a separate development work order. Prepare a well-done documentation with examples, so you can say - for your own peace of mind - that support covers things not described in the documentation.

[jainvivek]

Due to nature of the product, most of the support is only needed during onboarding. Its pretty straightforward afterwards with full documentation available.

I guess I am not being able to generate enough trust in prospects even after 14 days no-question-ask-refund policy.