We're in the process of overhauling the Brainfood.com site and I'm trying to leverage the SFA system. I see some simple things that don't work, like it not storing address and telephone information, but those are easy fixes. I'm more interested in what the workflow is for dealing with leads on an ongoing basis.
To me it would be logical if a Lead could be graduated to an Opportunity and an Opportunity could, in turn, be graduated to a Project. Leads seem mostly to be a special case of a party and the use of the partyStatusId as a lead state tracking mechanism seems like an abuse to me. It seems to me that the process of qualifying a lead should probably have its own distinct data element. Depending on your point of view, it could be a WorkEffort or at least a CommunicationEvent that has child CommunicationEvents associated with it. Thoughts? -- Ean Schuessler, CTO Brainfood.com [email protected] - http://www.brainfood.com - 214-720-0700 x 315
