Yes that makes sense. Though, it would be hard to apply edits limits because the number of edits can vary greatly, independently from the purchasing power of a customer (for example a startup would change it's home page every other day while a large corporate would barely touch it once a quarter). The bandwidth or page views limits seem to be raising the same issue and the logic for us is simply to avoid server costs that would be too high for a single site that would pay a basic monthly subscription.
If a large company is not updating their site very often, then you do not have a great value proposition anyway. Your core product is ease of updating/editing and customization, no? Makes sense to charge based on that aspect.
Of course you need some sort of traffic restriction for things not to spiral out of control. Putting this restriction on actual MB's transferred is an acceptable safeguard. Cache bandwidth is cheap using the right strategies, so your bounds could be pretty high while keeping it profitable.
cool, great feedback. We'll look into implementing bandwidth restriction instead of page view, I had the same conversation with an agency yesterday and they were leaning toward your point of view.
