Some ways to be hated:
When marketing and selling your business product, aim for people with purchasing authority who won't have to use it. Then you don't have to worry about usability.
Ideally, pricing should be confusing and irrational. Have multiple versions with functionality that's not clearly differentiated. Ideally, have one or two particularly desirable features high up on the price scale, so people get the feeling they have to pay big for a lot of things they won't use.
If you have enough power, make later versions of your software not quite compatible with their predecessors, and don't offer upgrade discounts. For extra points, remove functionality that people might be used to.
Advertise features that don't really work. If you've got sufficient control of the product, remove some of them with more or less forced upgrades.
Leave some bugs in, preferably intermittent bugs. Come up with reasons why, if something happens, it isn't your fault. Stonewall your complaining customers. Alternatively, come up with a fix that actually makes the product less usable.
Quality control is for companies that want customer satisfaction. You've got a lot of potential beta testers out there: use them. You'll get reports even if you don't give them any feedback. You can fix a lot of them in the next version (see above about slight incompatibilities, no upgrade pricing, and removing functionality).
Mess up the users' computers. DRM is great here, particularly if you don't tell anybody about it ahead of time (and particularly if they won't expect DRM on something like your product).
Anti-piracy measures are great. Make sure your detection algorithms have plenty of false positives. It isn't necessary to have convenient or easy ways to correct the false positives.
Long confusing EULAs that claim ridiculous things are commonplace nowadays. To get hated over them, you have to bury something onerous in there and enforce it afterward.
Documentation is for wimps. Make sure it's virtually impossible to figure out how to do a few important things from the docs. (Unfortunately, this has become too common over time to be really effective.)
Rebates that require awkward documentation and application procedures are good. Remember that many receipts nowadays are printed in a way that fades over time, so you can save a lot of money by requiring the original receipt and taking long enough to process them.
Arrogance and well-publicized anti-competitive practices are always useful here.
(No points for guessing which suggestions I wrote with companies in mind, or even which ones, or which I've suffered through personally.)