Just a suggestion: Consider instead framing it as giving a discount to people who use a newer web browser, since "they didn't require the extra work supporting older, buggy web browsers does" (or similar phrasing). It makes the same point, but may be less likely to make potential customers resentful.

Either way, you'll probably want to run this by a bunch of actual customers. People with the sort of personality quirks that draw them to (and make them good at) programming might respond to this very differently than customers/clients at large. Also, note that some people will not be allowed to change web browsers, e.g. for administrative reasons. (Whether or not they're good reasons is beyond your control.)

I don't know if it's a good idea from a business standpoint, but I like it.

Yeah, the way it's framed can be made easier, probably. The "discount perspective" is always easier to swallow.

What I'd like for us to do, as real businesses do, is to turn the discussion into one of costs and stop pretending to our community that IE6 support comes for free.

"You live in Canada and we have to charge you more because it costs us more to send our product to you."

People understand this-- it might not occur to them at first, but I think it might be a good idea to begin showing customers how they increase their own prices. The majority of IE6 users may not even know they cause the trouble they do.

At my company we haven't found a way to charge more, especially with clients that have internal apps that will only work with IE6. What we have been doing is itemizing any hourly work spent on IE6 optimization (hacks). So, at least for clients with multiple projects in the works, it make them think twice about requesting IE6 support on their next project.

I've recently intentionally removed some of the hacks for making IE6 look sane in our apps. PNG transparency is the most obvious...so in IE6, our products have grey boxes around all the images. It still all works--nothing is impossible to do in IE6. It just looks stupid. This, of course, is the easiest thing to fix in IE6, so I'm still spending an inordinate amount of time making sure everything still works in IE6. But, it's my passive aggressive way to make it clear that IE6 is not an appropriate browser for modern applications.

I don't know that this does anything positive for the world, but it gives me a small piece of satisfaction. (Of course, IE6 is less than 5% of our users, so it's not really a revolutionary act.)

Definitely charge people extra for making intranet sites IE 6 compatible because they have control over that and they should upgrade. Otherwise you can consider a small surcharge for IE6 on internet sites but it's kind of unfair to punish your clients for the browsers their customers use because they can't really do much about it. On your own site more ads are okay along with copious upgrade links and links to Firefox/Opera.

Funny story: I've been working on a project for the past 2 weeks and I basically finished it in Safari and I was getting ready to do a long day or two of debugging for IE6 when I opened it up in IE6 and lo and behold it was (nearly) perfect! I was so happy, tears nearly ran down my face.

Make sure one of the ads is for Firefox... :-)

This made me smile. I'm sure everyone who has built even a simple page has had the urge to break something after seeing their perfectly designed page in Firefox explode in IE6.

That said, you'll want to test on a small segment of your IE6 users before full implementation if possible. IE6 users are actually more qualified buyers a lot of the time depending on your industry. As a gross overgeneralization, IE6 users tend to pirate less, are less likely to be aware of competitors to your services, and might be more likely to be business customers at work depending on who you to sell to.

I wonder if IE6 users are more prone to click on ads anyway. Overall, this is an interesting idea. If you implement it, follow up in a couple months with what the effects are. My company has thousands of pageviews a day, with about 25% being IE6. I would love to push this idea internally because A) it makes the marketing dept happier if we make more money and B) it makes me and the other front-end engineer happy.