Earlier quoted context omitted.
Why would you design a price for "value provided"? That's highly subjective to the user. Users also generally only pay for what they expect to pay, not the value they're getting. For instance, some utility might save hundreds of hours and thousands of dollars over the course of its usage, which is tremendous value . Yet if the average user expects that it should cost no more than, say, twenty dollars, that's what the…
I'm not Greg Kogan, of course, but... It is indeed highly subjective to the user. So, part of the job of marketing is, segment your market, decide which one is most lucrative, target them with pricing that optimizes the outcome for that segment, and then adjust the product packaging to give yourself the most flexibility to attempt to repeat the process with the next segment of customers. You learn the value your user…
That all implies that there is such a lucrative group that has the expectation to pay a handsome sum for your product. It implies that there is no competition that has already driven the price into the ground.
If your product is truly novel and there is no competition, better set a higher price. You can always go lower and see how much more revenue you can get. Over time however, competition will show up and put the price closer to cost, or even below cost. Users will no longer expect to pay the older prices, so they won't - no matter how much value they get.