Some general points&#x2F;comments.<p>1. Most new developers&#x2F;entrepreneurs always under price their product&#x2F;service.  If you are new to this and the price feels a little uncomfortable you are probably getting closer to its real value.<p>2. Discounting screams you don&#x27;t know the value of your product&#x2F;service.  Try not to &quot;discount&quot; your product&#x2F;service, instead A&#x2F;B testing is smarter to set some parameters.  Also, I&#x27;d second what taprun says on discounts too in his comment.<p>3.  Set your pricing not based on what the service costs you to operate, develop, maintain etc.  Set your pricing based on the value you provide to the client.<p>4. Don&#x27;t immediately reach change the price when you are starting out.  Evaluate everything equally to price, it may be who you are marketing to, product&#x2F;market fit etc.  And much of that is far more impactful than just price alone.<p>5. Try to keep you pricing scheme simple.  The easier it is to understand the better.  Ideally I like to see at most 3-4 &quot;levels&quot; of pricing, more than that and users start getting confused what to select and are more likely to bail and not try any of them.<p>6. Experiment with free trials to see if it may help your conversion rate.  I can&#x27;t say it is ideal in all situations nor does it work in all, but it is worth evaluating.