This is a complete over-simplification, but...<p>I&#x27;d start by thinking about how much your product is worth to the company.  How much money will it save&#x2F;make them?  Don&#x27;t just look at the functionality that you provide, but also at risk reduction.  Charging based on value is called value pricing ( <a href="https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Value-based_pricing" rel="nofollow">https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Value-based_pricing</a> ).  You&#x27;ll want to charge less than what your customer has to gain (otherwise they won&#x27;t buy).  This is the number you should be working from (using out-of-pocket costs to determine pricing is called time and materials pricing and is a great way to go broke <a href="https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Time_and_materials" rel="nofollow">https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Time_and_materials</a>).<p>Your original app pricing has little to do with what you can charge enterprise customers, because the product that you&#x27;re offering is different.  Yes, your old pricing will act as a bit of a psychological anchor, but if they&#x27;ve contacted you for a custom plan, they are probably willing to spend quite a bit.<p>Source: I write a blog on the subject of product pricing (and wrote a book specifically about software pricing - <a href="http:&#x2F;&#x2F;taprun.com&#x2F;pricing&#x2F;" rel="nofollow">http:&#x2F;&#x2F;taprun.com&#x2F;pricing&#x2F;</a> ).