I plan on adding a few simple pricing plans to my consumer-focused site. Only two options will be available - a pay-as-you-go plan for 99 cents or unlimited, lifetime access for $4.99. The feature-set and functionality will be the same for both options.<p>How best do I show this in a pricing/features table when price is the only meaningful difference? Any suggestions on how best to structure such a table for maximum conversion when the audience comprises of younger, casual internet users who will view my web app as a utility they might use a couple of times in the year? (I'd really like them to purchase the $4.99 plan, but 99 cents per use has a nice ring to it.)<p>Note: I have not launched yet, expect to start with a free beta at first, market the hell out of the web app to gauge interest, tweak web app with feedback, and then launch with pricing.