Hola! ¡Tenemos nuestra Comunidad en Español!

Pipeline specific Default Deal Properties

Hello Team, 

 

Our use case:

We have various pipelines, for various sales cycles and sometimes various types of contacts or companies.

The Deal's information we need to access depend on the pipeline the deal is in. Since the "default deal properties" is made to display the "most important" information of a deal, we need this group of "most important" information to be pipeline specific.

 

Our suggestion:

To propose to create multiple "default deal properties", each one having a name. Then, admin should be able to decide to which pipeline to apply this "default deal properties". A "default deal properties" may be applied to one or more pipelines. It's ok to have a limit on the possible numbers of possible "default deal properties" if needed. 10 or 20 maximum would already be amazing.

 

Note: I've written the above with the understanding that "default deal properties" are controlling both the "about" section on the deal and the properties available when creating a new deal on the card that's opening on the right of the screen.

 

Best, 

Adrien

64 Replies
Felix1002
New Member

PLEAASSE DO SOMETHING HERE HUBSPOT!

HubSpot Employee
HubSpot Employee

Submitting on behalf of my customer, who was looking for a similar feature. 
Use Case is they run financial services, and would like to have the About section of the deal different for each of their pipeline to quickly get an over view of the deal properties most important to that pipeline.

plandes
Occasional Contributor

155 Votes, more than 2 years since initial request, 0 reaction from HubSpot. This is really disgrace. 

HubSpot Moderator
HubSpot Moderator

Hi HubSpot Community,

We really appreciate the continued feedback on this post. Allowing pipeline specific deal properties is certainly something we hope to look in to. However, at this stage the work has not been planned or scheduled. Please continue to provide examples and use-cases for this feature - it will help us build a better solution when the time comes. We'll update this post when we have further clarity on when we plan to build this functionality. 

 

- Dylan

blawlorSJ
Occasional Contributor

We could really use this on the Service Hub Pipeline side. We've got three pipelines on Service Hub, with different users using different pipelines. There are many extra steps to see all the fields for the appropriate data to be entered into the ticket. Pipeline Default Properties or Default Property Views would solve this issue. 

 

Thanks,

Ben 

TomSelten
Occasional Contributor

We definitely want this feature to make different default deal properties per pipeline. Besides using Hubspot for sales we would really like to use it as well for funding/investor relations and supplier selection. Hopefully Hubspot will implement this feature asap Smiley Happy

TomSelten
Occasional Contributor

Please add this feature asap, we really need this to have other departments easily working with pipelines as well (like investor relations, supplier selection).

 

Also, a suggestion could be to change the name Sales to Pipeline as the dealflow/pipeline functionality is applicable for other departments as well.

jhicks
Occasional Contributor

@TomSelten  You may want to look into utilizing Tickets for departments outside of sales. So once a deal reaches a certain stage you can have a workflow create a ticket and assign it to the desired deptment. Creating the ticket using a workflow automatically associates the ticket to the correct deal as well so it a bit neater.

 

The rule we adopted is: If there is not a dollar amount then it is not a deal. 

Daveonearth
Occasional Contributor

I am very surprised this is not an obvious inclusion in the system. It is urgently needed. My sales team are very frustrated seeing totally unrelated fields on their deals. 

 

 

SMA
Occasional Contributor

I am a bit surprised this isn't a feature yet and that HubSpot still need more use cases to consider implementing this.

 

When working with enterprise customers we notice a bigger demand for this. We have several customers who have sales offices across the world. There are properties used in the US that wouldn't be used in Europe and Asia. Also working across various industries in the same company there are custom properties that is used in one business unit but not in the others. 

 

This should also be implemented in the Ticket Pipelines