Lastly....
I think I read that you don't have any specific goals, but that you are looking for redundant bits of the process.
In fact the sales process will have a goal - making sales. And it appears your review is looking for improvements to efficiency (ie reducing cost/waste.)
In sales the quickest win is often a rationalisation of products - get rid of the low selling ones or the ones that are complex to deliver. These take up sales people's time but don't deliver much incremental revenue. It's not a process improvement, so proess analysis won't pick it up. Look at higher level isues like these first if efficiency is the goal.
If your scope is purely around process improvements I think your quickest path to ideas is probably via a Context diagram. See the ATM example/case study in the forums for some examples.
Context diagrams will show you where there are information flows across organisaitonal boundaries (Arrgh!! there be problems here) and will show when information flows into one place (system, team) but doesn't flow out. In this later case ask them (who?) why they pass things into this dead end space, and what value it adds. In the former case (boundaries) there are always improvements to be made by bringing people closer together through organisational redesign or clarifying/managing service level agreements and KPIs.
These are usually faster issues to resolve than process improvement projects or IT system implementations.
Craig Brown
Better Projects
and MA core team member