<story><title>Design Strategies for a Successful Pricing Table</title><url>http://uxmovement.com/design-articles/7-useful-design-strategies-for-a-successful-pricing-table</url><text></text></story><parent_chain></parent_chain><comment><author>JangoSteve</author><text>So, far every article I&apos;ve seen from uxmovement.com has anecdotal advice with no sources, and no numbers to back them up.&lt;p&gt;Also, when creating the tiered plans for your web-app, I highly recommend NOT having anything that is &quot;unlimited&quot; in any of your plans. It is very hard to go back and un-unlimit your plan. Don&apos;t leave it open-ended.&lt;p&gt;Sure, make the limits high on the top plan, hell make them higher than anyone could possibly need, but still have limits. If someone needs more than that, you can work something out. If nothing else, have a per-instance-pricing plan ($50/mo for 500 things + $0.05 per additional thing).</text></comment>
<story><title>Design Strategies for a Successful Pricing Table</title><url>http://uxmovement.com/design-articles/7-useful-design-strategies-for-a-successful-pricing-table</url><text></text></story><parent_chain></parent_chain><comment><author>d_r</author><text>I loved the post, but would be interesting to see some actual data behind these observations.&lt;p&gt;Some of these seemingly contradict each other: one &quot;rule&quot; claims that ascending order of prices is better, another claims the opposite.</text></comment>