|
|
||||||||
|
|
|
|
|
|
|
|
Go
![]() |
New
![]() |
Find
![]() |
Notify
![]() |
Tools
![]() |
Reply
![]() |
|
|
Apprentice |
Hello,
I'm interested in making fuller use of Daylite in my resume writing business. To date, I haven't been using Projects at all; I've used Opportunities and a single pipeline for all phases of work with a client. But I see in these forums that many people use Opportunities for the sales cycle, then create Projects for the work stemming from a sale. Why is that distinction useful? Robert Robert Dagnall, ResumeGuru.com "Resumes Expertly Written, Not Merely Typed" robert@ResumeGuru.com |
||
|
|
Journeyman |
I am a Landscape Architect and design sports complexes. I use Opportunities for things that I am marketing but don't have a contract on yet. So it is an opportunity for me at that point in time, and if all goes right it will turn into a contract. Opportunities have different tasks. More lunches, shmoozing, etc.
Once i get a contract, then it is a Project. I now have tasks with deadlines and staff working on it. We are producing work. This makes it much easier to track what clients you are marketing and hoping to get work from and what clients you have that you are now servicing. Daylite has a feature that you can turn an opportunity into a project so you don't have to reinput all of your linked contacts, etc. And, it makes it easy to track how good you are at turning opportunity into dollars. The Opportunity/Project setup is really 99% of what I use Daylite for. Of course the beauty of Daylite is you can do exactly what you are doing now and it will work perfectly. Customize your pipeline and you can track where you are in your particular process. It really doesn't matter if you consider it an opportunity or a project. |
|||
|
| Previous Topic | Next Topic | powered by eve community |
| Please Wait. Your request is being processed... |
|

