Will I regret using a Pipeline for simple projects?
I have a need to track projects through three phases of lifecycle. I mainly need to get a quick view of which projects are in which stage. I also need a "home" in which to keep notes and record a handful of data points per project. I have no need to track detailed tasks.
Will I regret creating a three-stage pipeline for the above? It would save me money over paying for the Projects feature, and the Projects interface is cumbersome and I don't enjoy it.
Is anyone else using a simple pipeline to track projects? Have you run into any unexpected gotchas? One worry I have is that there might be some reporting gotcha that bites me down the line.
Answers
-
Should be fine. You can filter out reports at the deal level by filtering using the Pipeline field, but reporting at the contact/org levels can get messy.
0 -
How I do it and like mentioned only thing that gets messy is the contact/org.
Projects just isn't there yet, I currently pay for it but am not using it.
0 -
I've decided to stay with Projects. I move between projects and deals often enough that it's convenient to just be able to click the Projects icon in Pipedrive's sidebar. The slightly different user interface immediately clues my brain to the fact that I'm looking at a project instead of a deal, so that I'm less likely to make a mistake. I also worry about the reporting down the road. I guess I prefer that my projects be recognized as projects rather than kluging a deals pipeline for that purpose.
The Projects user interface is not that great, but it's good enough for what I'm doing. I just need a place to keep notes and other details during the project lifetime.
0
