Customize the close date in deals


When you create a deal, there is a default close date (end of current month). Every month, we have to postpone the close date of our deals to the next month.

In our industry, the time to close is more around 80 to 90 days. The deal forecast will be more accurate with a close date set 2 or 3 months after the create date. close_date.png




HubSpot updates
Customize the close date in dealsHubSpot Product Team

Hi everyone, 


My name is Sophie, I work on the team that builds HubSpot CRM. I wanted to address this idea and the frustration expressed recently at the end of this thread. The ability to set customize when the close date is set (or what is set to) for each account is something that we are interested in exploring in the future, but it's not on the immediate roadmap for this year.


We treat the deal Close Date property as the expected close date for the deal (until it is actually closed). The property is used in the Deal Forecast report to forecast revenue by month/quarter/year and so we set it automatically to ensure all deals show up in that report. While this property is given a default value, it is expected that the user will change this value to represent the expected close date when the deal is first created. If the user knows that the deal cycle is usually 80-90 days long, they should set the close date to 3 months time to reflect that (ensuring the deal forecast report is somewhat representative of the pipeline). When the deal is finally moved to a closed lost or closed won stage, we will update the deal close date to that day automatically to ensure accurate reporting and reduce the effort required to close a deal. 


In terms of why this feature request has not been addressed sooner, while it is absolutely true that the more votes an idea gets the more likely it is to be reviewed by HubSpot's product team, there is no guarantee that ideas will be implemented based on a critical mass of votes. That said, it's not our intention, ever, for customers to feel unheard and we're actively looking into means of closing the loop in a faster and more transparent way.


If you have specific feedback about the CRM that you believe will make it easier and more efficient to use, please don't hesitate to message me directly. 



- Sophie

83 Replies
Esteemed Contributor

Hey Kim,


Same dealio here. When we open deals, we don't know the close date. So we'd rather have it empty by default. 


Ideally, there'd be an 'Expected Close Date' property, which would use the deal owners 'Average Days to Close' to estimate a when the deal might close.


Close date would only be populated when a deal is set to Won or Lost. 

Occasional Contributor

Same deal here. Is there a way to change the default? 

New Contributor

Same here why is this not changeable? Very weird...

New Contributor

This is important for me as well. I have no idea when a deal will close when I first create it and now there is bad data relating to close dates in my DB since I often create deals when multi-tasking on a call with a prospect.

Occasional Contributor

+1 to the idea for customizing the default closing date.   I'd like to use a # of business days offset.

Regular Contributor

 Agreed! Having this default to the last day of the existing month is not appropriate. We don't know the exact close date and would prefer the Close Date field NOT be populated until the deal actually closes. We created a custom field titled Expected Close Date and use that to show what deals are delayed or stalled.

Please allow the Close Date field to NOT auto-populate (remain blank) when a deal is created.

New Contributor

Yes, our company needs this as well. We need a close date 6 months out because of our sales cycle. Quite surprised you are not able to customize this.

New Contributor

Auto populate needs to be eliminated.  It creates confusion and inaccuracies.  This frustration with the users.

New Member

+1 to the idea for customizing the default closing date - Rob

New Member

I also would like to be able to turn off the auto filling of the Close date.  We use a different field for expected close date.  I do not understand why you would auto populate a bogus date.  That makes no sense at all.