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 they'll be ready to pay.
This is why anchoring is beneficial, it gives you the opportunity to tilt that expectation a little bit.
Is that "tricking the user"? Arguably, but since you can't know the value users will actually get out of your product, any claims in that regard will fall under "marketing BS" as well. Pick your bullshit wisely.
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 they'll be ready to pay.
This is why anchoring is beneficial, it gives you the opportunity to tilt that expectation a little bit.
Is that "tricking the user"? Arguably, but since you can't know the value users will actually get out of your product, any claims in that regard will fall under "marketing BS" as well. Pick your bullshit wisely.