Testing pricing and optimizing are 2 diff things. If you want to test that someone might pay for your service – prompt them. Put a fake upgrade page with a bunch of feature and a big “Upgrade” button – when they click it, add them to a list and let them know you were just gaging interest and when/if you deploy those features you’ll let them know. This way you can track the features, price, conversion – without building anything. Optimizing is a way longer conversation.
| you type: | you see: |
| *italics* |
italics |
|
* item 1 * item 2 * item 3 |
|
|
1. item 1 2. item 2 3. item 3 |
|
|
Paragraphs are separated by one or more blank lines:
The first paragraph. Another paragraph. |
The first paragraph. Another paragraph |
-
It's worth mentioning that, while tempting, one has to be careful with A/B testing prices. This article which hints at the right way to do it, may be of interest: http://visualwebsiteoptimizer.com/split-testing-blog/ab-testing-price-testing/
-
1 vote by Mike C. Hayashi,
Great points by Dan & Antonio. Price testing is different for each type of product or service you are offering (e.g. tangible/intangible), but there are key strategies that can be applied for many scenarios. Antonio offers a link (http://bit.ly/hfym1Y) which includes a great E-Book describing how to price software and the article itself provides great pointers. I would also recommend two more articles for the knowledge pleasure: 4 Pricing Strategies That Work for Small Companies (http://bit.ly/elqvd9) and 4 Pricing Mistakes You Need to Stop Making (http://bit.ly/eNpyqg). Good Luck and see you on the cover of Fortune..
-
-
-
-
-
-
Here's a technique I've found useful for testing pricing, especially pre-launch. We're always tempted to ask, "How much would you pay?" but it turns out that question gets lousy feedback, because everyone wants it free. Rather, I found it effective to 1) pitch the product and wait until they ask "How much?" then 2) try a number, use the present tense, "It's costs $99/month" and 3) see if they flinch. If not, then try a little higher next time. 4) repeat.
-
-

