How To Survive a Patent Challenge?

An anonymous reader writes "I have written a nifty application that helps me run my own business, and could really help in running almost any business. It has been abstracted well enough that it could very plausibly be made a sale-able product. There are several very good, possibly patentable ideas within it. However, they are overshadowed by virtually an infinite number of possible bs challenges to its more mundane parts. I'm rather fearful of bringing this to market for that reason, and so far have only deployed it as a 'consulting' project with two other small companies (who love it). Does anyone have suggestions about how to proceed?" Other than a generic "hire a lawyer!", are there practical steps a software author can do here?

Comments

PLEASE submit a brief to the SC in Bilski v. Doll

[H4x0r Jim Duggan]

    In the case Bilski v. Doll, the Supreme Court is reviewing the patentability of software for the first time since 1981. This is a very rare chance to fix things, and you're exactly the type of case they want to hear.

    For the most part, briefs are being submitted by the mega corporations and the groups of patent lawyers. Ordinary programmers and small businesses are not participating, and they're exactly the groups that are bearing the costs and restrictions of software patents.

    Please help spread the word. I'll be sending out more info about this in the coming days via the EndSoftwarePatents mailing list.