Whatever you want to call them, Contact Processes need to be revived - they actually work now, but are not supported on the web.

This needs to be modernized so that they work for both, and improve the flexibility.

One area is third party processes - where one person's action causes the process to do something affecting another user needs to be more flexible, to include some standard scenarios, like scheduling a ToDo for the AccountManager of a Contact.

Another is to give it "awareness" of itself. Things like CurrentProcessId and other fields in the Process record like (UserDefined) CAMPAIGNID, OPPORTUNITYID,etc.

Contact processes is rapidly becoming one of the tools you can use to keep people from defecting from SalesLogix because it makes the system "respond" to actions that are being tracked. Right now, it depends on having vbscript modules thrown in to make it all work - it needs to be fixed.

Lead processs? - absolutely!  Get a new lead, have a process against it and when it is ready for conversion, have the workflow not only automated, but something the internal admin can build and maintain. 

Opportunity Process? - on closed-won have it push a To Do to somebody internal that needs to know the project is official and they can start planning.

There is no shortage of uses for this as long as it is something the customer can build and maintain in house at the sales admin / power user level.

I mean seriously - how many sales admins would IT trust with a copy of Visual Studio and/or give access to the server?