What would be the disadvantage of making one pipeline per service (about 2 to 5) ?

Options
Paul_5750
Paul_5750 Member Posts: 14
edited July 2022 in Sales CRM #1

What would be the disadvantage of making one pipeline per service (about 3 to 5) ? 

Our business offer mostly 2 services. I am wondering the benefits and disadvantage of making one pipeline for each. 

Comments

  • Mike van der Valk
    Mike van der Valk Pipedrive Team Posts: 3,072 PIPEDRIVE TEAM
    First Anniversary 5 Likes 5 LOLs First Answer
    edited June 2020 #2
    Options

    @Paul a Pipeline should be seen as a process, not as a service, a product, a region, etc... if your process is exactly the same then I suggest working in one pipeline and using tags/custom fields and filters to keep the overview. If you have different processes that need different stages it will make sense to split them up.

  • Paul_5750
    Paul_5750 Member Posts: 14
    edited June 2020 #3
    Options

    Thanks @Mike Murphy  for this piece of advice! 

  • RRyan
    RRyan Member Posts: 5
    Photogenic First Comment
    Options

    I would like to expand on this topic. I am running multiple mandates for clients, and I am essentially doing a service for one client by finding them investors from my internal contact base. Would a pipeline for each mandate not be easier than tags? Especially since the mandates expire after 6 months?

  • Manuel Oliveira
    Manuel Oliveira Admin Posts: 1,134 COMMUNITY MANAGER
    5 Likes First Answer First Anniversary First Comment
    Options

    Hi @RRyan , if the stages are the same across mandates then it might be more convenient to keep the same pipeline. You can then use tags or even custom fields to filter the deals.

  • RRyan
    RRyan Member Posts: 5
    Photogenic First Comment
    Options

    Okay so say they are in the same pipeline, what about creating a product then to attach to each deal? The product being the mandate that we are then sell g to the rest of our CRM database?

    My point is that I am indifferent if it's tags, products or custom fields that we adopt. I am more concerned about the most efficient and trackable method so that reporting works. The clients that we have these mandates for want the analytics of who and when we engage with others. The tracking would mainly be for this but secondarily for understanding conversions for internal improvement. I haven't found examples others in the community using PipeDrive from similar purposes so looking for ideas. Your input is greatly appreciated.

  • Tony Xavier
    Tony Xavier Pipedrive Team Posts: 68 PIPEDRIVE TEAM
    5 Likes First Answer First Anniversary First Comment
    Options

    Hello @RRyan,

    Even in this case, we suggest not having multiple Pipelines and rather creating Mandates as Products within Pipedrive. Once you have these Mandates created as Products, you can link them to Deals and use the Product information to track them within the Insights section.

    In the Insights section, you can create a filter based on the Product(Mandate) to get an overview of all deals using this specific Mandate and break it down based on the Deal Status, Deal's Linked Contact Person, etc

    I hope this helps