byTrevor Lever11-12-200902:26 PM - edited 11-13-200911:49 AM
Many of my clients use ACT to track "projects" within their database. A "project" is a piece of work that they do for a client. At the moment you can use Groups and, to some extent, Opportunities to track a "project" but this really is using and customising what is there, rather than having in ACT what is needed.
As an entitiy a "Project" would have a start date, estimated end date and the option to add other customised fields. The "Project" could be associated wth the Client Contact(s) and the ACT user(s) involved in that "Project". Tasks, Documents and Notes - specific to that project - could be added. A "Project" might have several stages (a bit like an Opportunity) that are used to track the progess of te project through it's key stages. In this regard a "Project" has some attributes similar to an Opportunity. It would also be possible to send an email to all contacts associated with a "Project". In this regard a "Project" has some attributes similar to a Group.
It would be possible to product reports for "Projects" that are similar
to the pipeline report for Opportunities so that an overview of all
"Project" may be created.
Finally, when an Opportunity is closed off as "Won" the user will be asked if he wants to create a "Project" based upon that Opportunity. All contacts, history etc from the Opportunity will then be copied over to the "Project".
Message Edited by Trevor Lever on 11-13-2009 07:49 PM