depending on target audience realize that introducing any additional variable expense to a company is an obstacle to adoption/purchase. Businesses like to be able to budget/plan (or at least think they can) a specific amount each month. In the end it depends on what your users/customers are primarily using the images for. Is it for their (our) own use, or is it primarily to package and resell after we create the 'solution' on top of the image (i.e. specific application for end user). The former creates less of a challenge IMHO then the latter. If its resold utilizing ec2 then there is a variable expense on top of a variable expense and generating margins on an unknown will be a significant challenge for both the end user and those packaging the image.
also, and just to admit my own bias, I am not a fan of % pricing. Even if variable based on tiers, static $/mo is simply more pallatable.
variable expense creates budgeting issues
depending on target audience realize that introducing any additional variable expense to a company is an obstacle to adoption/purchase. Businesses like to be able to budget/plan (or at least think they can) a specific amount each month. In the end it depends on what your users/customers are primarily using the images for. Is it for their (our) own use, or is it primarily to package and resell after we create the 'solution' on top of the image (i.e. specific application for end user). The former creates less of a challenge IMHO then the latter. If its resold utilizing ec2 then there is a variable expense on top of a variable expense and generating margins on an unknown will be a significant challenge for both the end user and those packaging the image.
also, and just to admit my own bias, I am not a fan of % pricing. Even if variable based on tiers, static $/mo is simply more pallatable.